[JBoss Messaging] - Re: Problems with concurrent.jar
by timfox
"kkoster" wrote : Tim, as I said at the outset, this is not necessarily a JBoss Messaging issue.
|
That much, at least, you're right about.
anonymous wrote : However, that said, the use of AOP with or independently of the JBoss AS (4.2.0.GA BTW) should not break the implementation of messaging since the jar in question is provided externally to Red Hat (Doug Lea's concurrency utilities) Since JBoss AS (4.2.X) is using this version of AOP anyway, why should the jar's be different.
|
The jars you should use for JBM are clearly specified in the userguide.
If you're using a different jar, don't blame me if it doesn't work. Nothing would be broken if you were using the jars we test against, verify and specify in the guide.
anonymous wrote :
| Also, there have been many conversations of the evils of using jbossall-client.jar
|
The version of concurrent.jar in jbossall-client.jar is the same as the one in the JBoss AS client dir, you can use that one if you don't like jbossall-client.jar, it's the same jar
anonymous wrote :
| This is more of a request to the AOP team to get the concurrent.jar in line with everything else.
|
If this is a request to the AOP team, why are you posting it on the JBM user forum? ;)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058891#4058891
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058891
18Â years, 9Â months
[JBoss Messaging] - Re: Problems with concurrent.jar
by kkoster
Tim, as I said at the outset, this is not necessarily a JBoss Messaging issue. However, that said, the use of AOP with or independently of the JBoss AS (4.2.0.GA BTW) should not break the implementation of messaging since the jar in question is provided externally to Red Hat (Doug Lea's concurrency utilities) Since JBoss AS (4.2.X) is using this version of AOP anyway, why should the jar's be different.
Also, there have been many conversations of the evils of using jbossall-client.jar if you would care to search the lists for them. It has been repeatedly recommended that explicit collection of client jars required be used for deployment. This allows significantly more flexibility when moving part of the container to newer versions.
This is more of a request to the AOP team to get the concurrent.jar in line with everything else.
Regards,
Karl
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058887#4058887
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058887
18Â years, 9Â months