-
-
-
-
4. Re: JBossTS jar names
"dimitris@jboss.org" wrote:
Maybe that could be fixed in repository.jboss.com if JBossAS is the only consumer.
It's not. JBoss Messaging relies on this component dependency as well. -
5. Re: JBossTS jar names
Off topic, but since this thread looks to be the place where both Mark and I noticed the use of JBossTS in 4.2, I'll give Dimitris a quick FYI.
This will break the Hibernate/JBC integration. See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=97247.
We were going to have to fix that pretty soon anyway, but the 4.2 timeline is definitely shorter. We can discuss that on the other forum topic. -
6. Re: JBossTS jar names
Just to clarify. So the roadmap that was agreed back in November 2005 was that all of the 4 series for JBossAS would ship with JBossTM by default and JBossTS would be a separate download from the JBossTS labs page. Is that not still the case? AFAIK only JBossAS 5 will have JBossTS as the out-of-the-box transaction manager.
-
7. Re: JBossTS jar names
Here's the roadmap http://labs.jboss.com/portal/jbosstm/resources/integrationroadmap.html that was agreed with Shaun and others. The 4.2 timeline is short and I am concerned about changing plans at this stage. The way things currently work is that the JBossTS team provide a separate download, with separate installation and integration instructions for those people who want to change the TM. IMO that's the way it should continue for 4.2.
-
8. Re: JBossTS jar names
Here's the roadmap http://labs.jboss.com/portal/jbosstm/resources/integrationroadmap.html that was agreed with Shaun and others. The 4.2 timeline is short and I am concerned about changing plans at this stage. The way things currently work is that the JBossTS team provide a separate download, with separate installation and integration instructions for those people who want to change the TM. IMO that's the way it should continue for 4.2.
-
9. Re: JBossTS jar names
"bstansberry@jboss.com" wrote:
Off topic, but since this thread looks to be the place where both Mark and I noticed the use of JBossTS in 4.2, I'll give Dimitris a quick FYI.
This will break the Hibernate/JBC integration. See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=97247.
We were going to have to fix that pretty soon anyway, but the 4.2 timeline is definitely shorter. We can discuss that on the other forum topic.
It's not necessarily off-topic. It shows that there are cross-project dependencies that still need to be ironed out. We were looking to do this for the AS 5 timeframe, which is far more realistic. -
10. Re: JBossTS jar names
"dimitris@jboss.org" wrote:
It was in JIRA already:
http://jira.jboss.com/jira/browse/JBTM-80
Sure, the jar name change was in JIRA - I added it ;-) But that's not the same as replacing the default TM in 4.2. -
11. Re: JBossTS jar names
"mark.little@jboss.com" wrote:
"bstansberry@jboss.com" wrote:
Off topic, but since this thread looks to be the place where both Mark and I noticed the use of JBossTS in 4.2, I'll give Dimitris a quick FYI.
This will break the Hibernate/JBC integration. See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=97247.
We were going to have to fix that pretty soon anyway, but the 4.2 timeline is definitely shorter. We can discuss that on the other forum topic.
It's not necessarily off-topic. It shows that there are cross-project dependencies that still need to be ironed out. We were looking to do this for the AS 5 timeframe, which is far more realistic.
Precisely. This specific issue is something we need to fix, but it is not on the JBC 1.4.1 roadmap. And trying to get this in place in time for AS 4.2 is pretty unrealistic. -
12. Re: JBossTS jar names
I agree with 4.2 being unrealistic for this. I don't necessarily agree with the suggested solution to the Hibernate/JBC issue, but that's definitely a separate discussion ;-)
-
13. Re: JBossTS jar names
Would you like that solution better if we added a little Rube-Goldberg diagram to the docs showing how it works? ;-)
-