[jbossws-dev] Re: Integrating apache-cxf

[Thomas Diesler]

Hi Daniel,

thanks for your effort - please stay with me ...

On Thu, 2007-08-23 at 16:35 -0400, Daniel Kulp wrote:
> Thomas,
> 
> 
> On Tuesday 21 August 2007, Thomas Diesler wrote:
> > as promised some days back, I changed the jbossws-cxf build system
> > such that we can now integrate an arbitrary Apache-CXF snapshot.
> > Please see
> >
> > http://jbws.dyndns.org/mediawiki/index.php?title=Building_From_Source#
> >Checkout_and_build_JBossWS-CXF
> >
> > for details.
> 
> I've been trying to follow these instructions and haven't seemed to 
> gotten anywhere.   
> 
> First off:  building the jbossas module doesn't work with those 
> instructions.   It seems to download all the thirdpart stuff to 
> jbossas/../thirdparty, but then it tries to find some jars in 
> jbossas/thirdparty.    

This is bizarre and yes you are right. It seems that the checkout
directory cannot be called 'jbossas'. I updated the page to use the
default checkout name.

> I worked around this by adding 
> a  -Dproject.thirdparty=/path/to/thirdparty flag when I called build.sh.   
> That needs to be documented on that page or (preferably) the build needs 
> to be updated so it actually works.
> 
> Second: when I run JBoss, I see:
> 16:20:18,614 INFO  [NativeServerConfig] JBoss Web Services - Native
> 
> Fine.   However, when I then go into the cxf build dir and run the 
> deploy, i now get all kinds of errors in jboss due to /jbossws already 
> being there.     From that point on, jboss is completely screwed.   I 
> cannot even shutdown jboss and restart.   All kinds of errrors occur on 
> restart.   I pretty much have to wipe out the jbossas output dir and 
> rebuild.
> 
> I then tried to build jbossas, then "undeploy" the native stuff and 
> deploying the CXF stuff before running the run.sh.   I then get:
> *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required 
> State:Actual State}
> 
> WSCXFDeploymentAspectInstallerEJB
>  -> WSDeploymentAspectManagerEJB{Configured:** NOT FOUND **}
>  -> WSDeploymentAspectInstallerEJB{Start:** NOT FOUND **}
>  -> WSDeploymentAspectInstallerEJB{Create:** NOT FOUND **}
> 
> WSCXFDeploymentAspectInstallerPostJSE
>  -> WSDeploymentAspectInstallerPostJSE{Start:** NOT FOUND **}
>  -> WSDeploymentAspectManagerPostJSE{Configured:** NOT FOUND **}
>  -> WSDeploymentAspectInstallerPostJSE{Create:** NOT FOUND **}
> 
> WSCXFDeploymentAspectInstallerPreJSE
>  -> WSDeploymentAspectInstallerPreJSE{Start:** NOT FOUND **}
>  -> WSDeploymentAspectManagerPreJSE{Configured:** NOT FOUND **}
>  -> WSDeploymentAspectInstallerPreJSE{Create:** NOT FOUND **}
> 
> WSEndpointRegistry
>  -> WSMBeanServerLocator{Configured:** NOT FOUND **}
> 
> WSServerConfig
>  -> WSMBeanServerLocator{Configured:** NOT FOUND **}
> 
> 
> If I try to run the tests in that state, the test fails and I see:
> 
> 16:29:52,175 ERROR [[TestEndpoint]] Allocate exception for servlet 
> TestEndpoint
> java.lang.ClassCastException: 
> org.jboss.test.ws.jaxws.samples.asynchronous.TestEndpointBean
> 
> That wouldn't be a CXF issue.
> 

Yes, you need to undeploy jbossws-native first. I updated the page to
that respect. Yesterday I also fixed a bug where undeploy-jboss50 would
incorrectly remove the container integration as well. This was the cause
of the errors you describe above.

> 
> Basically, I'm completely stuck.   Can you PLEASE provide some better 
> instructions on how to get it running.   

Yes of course. I updated the page with feedback from this thread.

>  I know pretty much nothing 
> about JBoss (or most any other J2EE app server for that matter), so 
> there really needs to be very good instructions as well as some 
> indication of what to I should expect to see on the consoles so I know 
> it's working correctly (or incorrectly as the case may be).

Done.

> 
> Thanks!
> Dan
> 
> 
> > The current situation is that the last cxf binary release (2.0) passes
> > 16 out of 109 jaxws tests from our general jaxws test suite. Native
> > and Metro pass all. CXF trunk does not build in hudson.
> >
> > http://jbws.dyndns.org:8180/hudson/
> >
> > I individually looked at all failing tests and tried to identify the
> > problems. Respective jira issues are created here
> >
> > http://jira.jboss.org/jira/secure/IssueNavigator.jspa?reset=true&mode=
> >hide&pid=12310050&sorter/order=DESC&sorter/field=priority&resolution=-1
> >&component=12311066
> >
> > I also mirrored these jira issues in the Apache CXF bug tracking
> > system. The next natural step would be to decide which bug tracking
> > system to use (I don't have a strong preference - either would work
> > for me).
> >
> > When this has been agreed on, jira developer rights should be setup
> > such that the teams can assign issues to each other. On our end that
> > would be me initially. Would you be able to name a person that I can
> > assign issues to and work with to get these integration issues
> > resolved in a timely manner?
> >
> > If there is anything else you require, please let me know.
> >
> > cheers
> > -thomas
> >
> > PS: I'll be available until the end of this week. Then I'll be on
> > holiday until Mon,17-Sep. During that period Heiko Braun will take
> > over.
> 
> 
> 
-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx