So, I've finally gotten back to this issue, with no luck.  I have my .war file 
and I deploy it with the Deploy Web Services box unchecked.  And I have ALL of 
my jars referenced individually in the classpath for reference libraries.  I 
also have parent_last loading checked for my application. 

Unfortunately, my application doesn't load at all.  Instead, I receive...

[9/17/09 15:44:21:974 EDT] 00000022 CompositionUn A   WSVR0190I: Starting 
composition unit WebSphere:cuname=desktop_war in BLA 
WebSphere:blaname=desktop_war.
[9/17/09 15:44:22:037 EDT] 00000022 ApplicationMg A   WSVR0200I: Starting 
application: desktop_war
[9/17/09 15:44:22:052 EDT] 00000022 ApplicationMg A   WSVR0204I: Application: 
desktop_war  Application build level: Unknown
[9/17/09 15:44:23:615 EDT] 00000022 webapp        I 
com.ibm.ws.webcontainer.webapp.WebGroupImpl WebGroup SRVE0169I: Loading Web 
Module: desktop.war.
[9/17/09 15:44:23:631 EDT] 00000022 WASSessionCor I SessionContextRegistry 
getSessionContext SESN0176I: Will create a new session context for application 
key default_host/desktop
[9/17/09 15:44:24:146 EDT] 00000022 extension     W 
com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor createServletWrapper 
Servlet InitializationServlet is currently unavailable: SRVE0201E: Servlet 
[com.docfinity.servlet.InitializationServlet]: not a servlet class
[9/17/09 15:44:24:209 EDT] 00000022 extension     W 
com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor createServletWrapper 
Servlet LocalFileProxyServlet is currently unavailable: SRVE0201E: Servlet 
[com.docfinity.servlet.io.LocalFileProxyServlet]: not a servlet class
[9/17/09 15:44:24:209 EDT] 00000022 webcontainer  I 
com.ibm.ws.wswebcontainer.VirtualHost addWebApplication SRVE0250I: Web Module 
null has been bound to default_host[*:9081,*:80,*:9443,*:5060,*:5061,*:443].
[9/17/09 15:44:24:240 EDT] 00000022 ApplicationMg A   WSVR0221I: Application 
started: desktop_war
[9/17/09 15:44:24:240 EDT] 00000022 CompositionUn A   WSVR0191I: Composition 
unit WebSphere:cuname=desktop_war in BLA WebSphere:blaname=desktop_war started.
[9/17/09 15:44:37:475 EDT] 0000001c FfdcProvider  I 
com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted 
on C:\Program 
Files\IBM\SDP\runtimes\base_v7\profiles\was70profile1\logs\ffdc\server1_47804780_09.09.17_15.44.37.36517595.txt
 com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest() 302
[9/17/09 15:45:11:725 EDT] 0000001c CompositionUn A   WSVR0192I: Stopping 
composition unit WebSphere:cuname=desktop_war in BLA 
WebSphere:blaname=desktop_war.
[9/17/09 15:45:11:741 EDT] 0000001c ApplicationMg A   WSVR0217I: Stopping 
application: desktop_war
[9/17/09 15:45:11:772 EDT] 0000001c ApplicationMg A   WSVR0220I: Application 
stopped: desktop_war
[9/17/09 15:45:12:553 EDT] 0000001c CompositionUn A   WSVR0193I: Composition 
unit WebSphere:cuname=desktop_war in BLA WebSphere:blaname=desktop_war stopped.

I don't understand why it doesn't load at all.  This seems very strange to me.  
Any other ideas?  Any other samples or tutorials on this matter?

Thanks,

Aaron



-----Original Message-----
From: Paweł Lipka [mailto:p.li...@amg.net.pl] 
Sent: Wednesday, September 09, 2009 8:45 AM
To: dev@cxf.apache.org
Subject: RE: Websphere and CXF

I did not have to put any of the CXF jars as a shared library. All I did
is create a shared library containing the XmlSchema.jar. The library has
to have the inverted class loading order i.e. 'self-first' and your web
app has to reference this shared library (in my WebSphere version you
configure it in one of the deployment screens).

hope that helps,

/PL
On Wed, 2009-09-09 at 08:35 -0400, Aaron Ehrensberger wrote:
> Well, I did originally leave that unchecked and that's when I had the issue 
> with the mismatched namespaces.  You mentioned the shared libraries and so I 
> wonder...do I have to specify the CXF libraries for my .war deployment?
> 
> Aaron
> 
> 
> -----Original Message-----
> From: Paweł Lipka [mailto:p.li...@amg.net.pl] 
> Sent: Wednesday, September 09, 2009 8:28 AM
> To: dev@cxf.apache.org
> Subject: RE: Websphere and CXF
> 
> Make sure that you leave the 'Deploy Web Services' option unchecked on
> one of WebSphere's application deployment screens. 
> If you check this option you make WebSphere scan all the classes for
> JAX-WS annotations. As a result your SEIs and their impls are processed
> by WebSphere's native JAX-WS stuff rather than CXF (as if you did not
> use CXF at all)
> I've one of the latest WebSphere versions + CXF 2.2.2 without any issues
> related to stax. The only problem i noticed is that sometimes CXF was
> unable to generate the WSDL at all due to XmlSchema.jar incompatiblity
> (which i bypassed by defining a WebSphere's shared library with inverted
> classloading order).
> 
> cheers.
> 
> /PL
> 
> On Wed, 2009-09-09 at 07:46 -0400, Aaron Ehrensberger wrote:
> > Thank you for responding!  At least you gave me a starting point.  Now,
> > with that in mind, is there a good starting point for documentation on
> > this stuff?  Any hints on that?
> > 
> > Aaron
> > 
> > 
> > -----Original Message-----
> > From: Daniel Kulp [mailto:dk...@apache.org] 
> > Sent: Tuesday, September 08, 2009 4:39 PM
> > To: dev@cxf.apache.org
> > Cc: Aaron Ehrensberger
> > Subject: Re: Websphere and CXF
> > 
> > On Fri September 4 2009 4:35:32 pm Aaron Ehrensberger wrote:
> > > Hi all,
> > > 
> > > I'm trying to deploy my webservices on Websphere.  Originally using
> > > Eclipse IDE, Jboss/Tomcat, Spring and CXF, I have the webservices
> > > deploying with no issues.
> > > 
> > > However, when bringing the code into Websphere and attempting to
> > deploy
> > > the same .war file created and tested in the first setup, I get a
> > > different WSDL that is missing multiple namespaces.  This causes the
> > > WSDL to not load and give me headaches.
> > > 
> > > Does anybody have any thoughts as to what is changing things?  Our
> > code
> > > is mainly straight java and so it should port between the two app
> > > servers without any migration issues, but it doesn't.  Ideas on what I
> > > can look into?
> > 
> > It's PROBABLY due to the STAX implementation.  If you can try getting
> > woodstox 
> > in there to be used, it would probably be better off.    The IBM stax
> > stuff is 
> > notorious for choosing alternative interpretations of the spec and
> > generally 
> > making it harder to use.     It also doesn't perform as well as
> > woodstox.
> > 
-- 
Paweł Lipka
Senior IT Architect
AMG.net, A Bull Group Company
ul. Łąkowa 29
90-554 Łódź
tel.: (+48 42) 634 56 78
www.amg.net.pl

Treść niniejszej wiadomości może być poufna.
Jeżeli nie jesteście Państwo jej adresatem, to rozprowadzanie
lub wykorzystywanie zawartych tu informacji jest zabronione.

This e-mail contains material that is confidential for the sole
use of the intended recipient. Any review, reliance or distribution
by others or forwarding without express permission is strictly
prohibited. If you are not the intended recipient, please contact
the sender and delete all copies.

Reply via email to