Problems getting WS into ESB

[thomas.diesler]

Trevor sais

When trying to integrate the WS CP into the ESB I hit problems with
jbossws-jboss42.jar not having the required classes. Since WS SP2 this
jar is no longer shipped as part of WS see
http://jira.jboss.org/jira/browse/JBWS-1851. We need some method of
getting this jar into the ESB.

Comments please.

Trev

[thomas.diesler]

For jbossws-2.0.1.SP2, which was targeted jor jboss-4.2.2, the container integration lives in the AS code base.

We probably first need to understand how the ESB is related to the AS. i.e. does it use an AS release or is it a fork of the AS code base?

[kconner]

ESB is currently based on AS4.2.1 and will be for our 4.2.1 release (in less than one weeks time).

A subsequent release will support AS 4.2.2.

We are currently using WS2.0.0 in the ESB as 2.0.1 was not backwardly compatible with our code. I believe this may have been fixed in a recent CP release but we cannot use those in the project.

I still don't know whether the SP2 release includes this fix or not, you owe me an answer on that one ;)

[kconner]

I believe the EAP is also based on 4.2.1 at this point in time but Trevor may be able to comment further on this.

[thomas.diesler]

I still don't know whether the SP2 release includes this fix or not, you owe me an answer on that one ;)

Yes it does.

When you say

ESB is currently based on AS4.2.1

do you mean

#1 there is a fork AS4.2.1 that we maintain in SVN http://path_to_some_branch

#2 we use the AS4.2.1 binary relase

In both cases installing jbossws-2.0.1.SP2 is not trivial because the AS container integration has moved to Branch_4_2 after the AS4.2.1 release.

Please show me exactly how you attempted to install jbossws-2.0.1.SP2 from that I can probably see how it should be done properly.

[kconner]

I still don't know whether the SP2 release includes this fix or not, you owe me an answer on that one ;)

Yes it does.

Thank you :)

#2 we use the AS4.2.1 binary relase

Yes, we use the binary.

In both cases installing jbossws-2.0.1.SP2 is not trivial because the AS container integration has moved to Branch_4_2 after the AS4.2.1 release.

Which is the issue Trevor is finding. I am assuming that 'after the AS4.2.1 release' means 'AS4.2.2 and later', is this correct?

Please show me exactly how you attempted to install jbossws-2.0.1.SP2 from that I can probably see how it should be done properly.

I believe Trevor is using your installation scripts to handle this aspect.

[thomas.diesler]

Ok, in that case I verify the deploy-jboss42 target against AS4.2.1

[thomas.diesler]

I updated the deploy target in the 2.0.1.SP2 tag. You should see

[tdiesler@tddell jbossws-native-2.0.1.SP2]$ ant deploy-jboss42
...
deploy-jboss421:
 [copy] Copying 1 file to /home/tdiesler/svn/jbossas/tags/JBoss_4_2_1_GA/build/output/jboss-4.2.1.GA/server/default/lib
 [copy] Copying 1 file to /home/tdiesler/svn/jbossas/tags/JBoss_4_2_1_GA/build/output/jboss-4.2.1.GA/client

...

BUILD SUCCESSFUL
Total time: 7 seconds

The binaries are not affected

[thomas.diesler]

Please note, the AS4.2.1 container integration jar (jbossws-jboss42.jar) is copied conditionally if there is not already a jar with that name in the server lib directory.

In AS4.2.2 this exists already because it is build and installed as part of the AS build, so deploy-jboss42 does not copy the AS4.2.1 container integration jar.

For AS4.2.2 deploy-jboss421 should do nothing