[jboss-user] [Microcontainer] - Re: Class loading conflict
Hi Ales Using the same domains in the riftsaw.esb and sar worked fine, but introduced another problem when I deployed some ESB examples that depended upon the action I had defined in the riftsaw.esb, and I don't think it would be a good idea for me to set the domain inside the ESB example to be based on riftsaw, as an ESB service in reality maybe using a number of other thirdparty custom ESB actions - and I assume it cannot be part of multiple domains? So I thought it best to outline the overall scenario, to see whether there is a good overall solution, rather than presenting the side effects of each individual change as I have currently being doing. 1) The riftsaw.sar, which had the original jar conflict, is not dependent upon JbossESB. It does however have some interfaces that need to be used externally. 2) If the JBossESB integration is being used, then currently there is a single BPEL invoke action that needs to access the interface from the riftsaw.sar 3) Other ESB services - that may need to use the BPELInvoke action. Currently ESB services don't need to do anything specific in their configuration to pick up ESB actions defined in other .esb modules - so either this approach needs to continue, or an approach needs to be used that would enable the ESB example to reference multiple ESB actions potentially defined in different isolation domains. Hope this gives a clearer outline of the dependencies and what we are wanting to achieve. Regards Gary View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4250085#4250085 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4250085 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Microcontainer] - Re: Class loading conflict
The problem I see with the first approach is if the same ESB example needed to use another third party ESB action that was in yet another domain - then the example could not be in two different domains (i.e. one associated with riftsaw and one associated with the other actions to be used). I guess (2) is an option, but would require ESB project to do part of the work, and have to wait for the next ESB release. Thanks for the help - I have a short term solution now, so buys me some time to find a longer term solution. Regards Gary View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4250270#4250270 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4250270 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Microcontainer] - Re: Class loading conflict
Yes that worked. Thanks for your help. Regards Gary View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4249635#4249635 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4249635 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Microcontainer] - Re: Class loading conflict
Hi, Tried that approach, but now I have a problem in that the ESB is complaining about classes not being found. The jboss-classloading.xml is placed in the esb.deployer, so I assume that isolation is now causing the jbossesb.sar to not resolve classes that it previously referenced from the esb.deployer. So I assume to overcome this, I would need a jboss-classloading.xml in the jbossesb.sar? The jbossesb.sar has a deployment.xml but it does not have a dependency on the deployer - if it did, would this overcome the problem? or do all deployment units that depend upon the ESB need to have its own jboss-classloading.xml? i.e. any .esb distribution? The other problem with this approach is that it requires me to modify the ESB distribution. Is there no mechanism to just enable my sar to indicate that it wants to have only its own libs, and the jboss AS libs on its classpath? Regards Gary View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4249415#4249415 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4249415 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Microcontainer] - Re: Class loading conflict
No, still no luck - just to check, the jboss-classloading.xml in esb.deployer
is:
classloading domain=jboss.esb:service=EsbDeployer,extension=LoaderRepository
xmlns=urn:jboss:classloading:1.0 name=EsbDeployer
import-all=true export-all=NON_EMPTY version=0.0.0
j2seClassLoadingCompliance=false parentDomain=DefaultDomain
and it causes exceptions like:
15:34:00,679 ERROR [AbstractKernelController] Error installing to Instantiated:
name=jboss.esb:service=PropertyService state=Described mode=Manual
requiredState=Configured
java.lang.ClassNotFoundException:
org.jboss.soa.esb.common.JBossESBPropertyService from
baseclassloa...@127d5a0{vfsclassloaderpolicy@3a0533{name=vfsfile:/...
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4249437#4249437
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4249437
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Microcontainer] - Re: Class loading conflict
I hadn't tried with all those attributes, so I just tried it with the same result :( Just to make sure, this is what I have used: | classloading domain=jboss.bpel:service=BPELEngine,extension=LoaderRepository xmlns=urn:jboss:classloading:1.0 name=BPELEngine | import-all=true export-all=NON_EMPTY version=0.0.0 | j2seClassLoadingCompliance=false parentDomain=DefaultDomain | /classloading | View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4249452#4249452 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4249452 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Microcontainer] - Re: Class loading conflict
Yes, still picking up the xbeans-2.2.0.jar from the esb.deployer lib, instead of my local xmlbeans-2.3.0.jar in my sar's lib folder. Tomorrow is ok. Thanks. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4249464#4249464 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4249464 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Microcontainer] - Class loading conflict
Hi I have a sar that includes xmlbeans 2.3.0 - which works fine in AS 5.1. However when I installed ESB4.6, which has version 2.2.0 of this jar in its esb-deployer, I get schema version problems. What is the best way to isolate my sar from being affected by jar versions in other non-dependent deployments? Regards Gary View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4249182#4249182 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4249182 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
