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 gu
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
Yes that worked.
Thanks for your help.
Regards
Gary
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249635#4249635
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249635
___
j
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=bb&op=viewtopic&p=4249464#4249464
Reply to the post :
http://www.jboss.
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:
|
|
|
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249452#4249452
Reply to the post :
http://www.jboss.org/index
No, still no luck - just to check, the jboss-classloading.xml in esb.deployer
is:
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
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.
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
