NoClassDefFoundError in JBossEsb 4.2.GA

[claudio_br]

Hi,

I am trying install Jboss esb 4.2.GA, but I got this in Jboss console:

*** DEPLOYMENTS IN ERROR:
WSEndpointJAXBIntrosCustomizationsDeployer -> java.lang.NoClassDefFoundError: org/jboss/wsf/spi/deployment/AbstractDeployer
WSWebMetaDataAdapter -> java.lang.NoClassDefFoundError: org/jboss/wsf/container/jboss42/WebMetaDataAdapter

I am using Jboss AS 4.2.1.GA, Jboss Messaging 1.3.0.GA, and JbossWS 2.0.1.GA.
I ran ant patch-jbossws.

What am I doing wrong?
Thanks.

[kconner]

In that case it looks like the application server did not have JBossWS installed when it started.

Can you look in the server/default/lib directory and see if there is a jbossws-spi.jar file?

[claudio_br]

Hi Kevin.

The problem is in JbossWS 2.0.1.GA.

In JbossWS 2.0.1.GA the file jbossws-spi.jar doesn´t contain org/jboss/wsf/spi/deployment/AbstractDeployer

In JbossWS 2.0.1.GA the file jbossws-jboss42.jar doesn´t contain org/jboss/wsf/container/jboss42/WebMetaDataAdapter.

In JbossWS 2.0.0.GA both files exists.

What should I do?
Thanks

[burrsutter]

I had thought we (the ESB) wanted to use JBossWS 2.0, not 2.0.1.

You might also download the ESB Server version as it is pre-configured to work "out of the box" with everyting ready to go. It will at least show you which version of JBossWS we really want.

Burr

[kurtstam]

That is what I thought too. I used 2.0.0 in the esb-server. --Kurt

[marklittle]

Yes, it's always been JBossWS 2.0.0GA for the ESB and platform. I will check with the JBossWS team to see what's going on.

[kconner]

Yes, 2.0.0 is the version we have tested against but it is surprising that the SPI has changed in this way between point releases.

This is something to be aware of when we update JBossWS.

[marklittle]

Yes, I find the SPI change surprising too. Already raising that point.

[tfennelly]

Just use 2.0.0 as stated in the readmes.

Long term, the JBossWS guys will need to manage the deployment aspects for the ESB (as they do for the Servlet and EJB containers). Sure it's surprising that the SPI changed, but that's a different argument I suppose. The SPI is all new stuff and I'd imagine we're the only ones outside of the JBossWS team that are using it.

[kconner]

"tfennelly" wrote:
Just use 2.0.0 as stated in the readmes.

Yep, this is the solution to Claudio's problem. It is the version we support and is stated in the release notes.

"tfennelly" wrote:
Long term, the JBossWS guys will need to manage the deployment aspects for the ESB (as they do for the Servlet and EJB containers). Sure it's surprising that the SPI changed, but that's a different argument I suppose. The SPI is all new stuff and I'd imagine we're the only ones outside of the JBossWS team that are using it.

You may be right about this but it is still surprising :)

[tfennelly]

You may be right about this but it is still surprising :)

The world's full of surprises :-)

[kconner]

"tfennelly" wrote:
The world's full of surprises :-)

ROFL. I suspect we may have gone off topic now :)

[marklittle]

Yes, it's wrong from the perspective that JBossWS 2.0.0GA is the last release I agreed with Thomas would be in the ESB and Platform. If they need to change that then that's fine, but I need to know first ;-)

[heiko.braun]

I verified the issue and indeed it's a compatibility problem.
The customizations applied through 'ant patch-jbossws' are addressing two problems:

* Add JAXBIntro (http://wiki.jboss.org/wiki/Wiki.jsp?page=JAXBIntroductions) capabilities to JBossWS
* Fix a deployment error (http://jira.jboss.com/jira/browse/JBWS-1747)

The later one was fixed in 2.0.1.
The patch process, however, does only need to be applied if JAXBIntros are being used.
If you skip the patch everything deploys fine.

On the long run, we need address these issues appropriately,
however, if people want to use 2.0.1 and don't rely on JAXBIntro's they could follow the steps described above.