facebook

Websphere 6.1/ Spring WS Classloader issues from MyEclipse

  1. MyEclipse IDE
  2.  > 
  3. WebSphere Development
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #296195 Reply

    ADP-1
    Member

    I am looking to move to MyEclipse Blue, and am starting by only using the Servers view, without the MyEclipse deployment integration. I have an existing (working) EAR deployed on WAS 6.1.0.15 with the Web Services feature pack. We use Spring Web Services. Because of some issues with the WSDL4J.JAR that comes bundled with WAS, we deploy the Spring specific WSDL4J.JAR to c:\websphere\appserver61\lib. Note that this has been working for over a year. When I start WAS from the command line (startServer.bat), our web services work properly. However, when I start WAS from the Servers view in MyEclipse Blue, I receive the following error when testing the web services:

    [3/16/09 14:05:40:705 EDT] 0000001f ServletWrappe E SRVE0100E: Did not realize init() exception thrown by servlet spring-ws: org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘BenefitConfig’ defined in ServletContext resource [/WEB-INF/spring-ws-servlet.xml]: Invocation of init method failed; nested exception is org.springframework.ws.wsdl.wsdl11.Wsdl4jDefinitionException: WSDLException: faultCode=CONFIGURATION_ERROR: No Java extensionType found to represent a ‘{http://www.w3.org/2001/XMLSchema}schema’ element in the context of a ‘javax.wsdl.Types’.; nested exception is WSDLException: faultCode=CONFIGURATION_ERROR: No Java extensionType found to represent a ‘{http://www.w3.org/2001/XMLSchema}schema’ element in the context of a ‘javax.wsdl.Types’.:
    Caused by: org.springframework.ws.wsdl.wsdl11.Wsdl4jDefinitionException: WSDLException: faultCode=CONFIGURATION_ERROR: No Java extensionType found to represent a ‘{http://www.w3.org/2001/XMLSchema}schema’ element in the context of a ‘javax.wsdl.Types’.; nested exception is WSDLException: faultCode=CONFIGURATION_ERROR: No Java extensionType found to represent a ‘{http://www.w3.org/2001/XMLSchema}schema’ element in the context of a ‘javax.wsdl.Types’.:
    Caused by: WSDLException: faultCode=CONFIGURATION_ERROR: No Java extensionType found to represent a ‘{http://www.w3.org/2001/XMLSchema}schema’ element in the context of a ‘javax.wsdl.Types’.:

    I compared the “Current Environment” section from the systemout logs when I start WAS via the command line versus through MyEclipse Blue. The only difference is the “Java Library Path”. When I start through the command line, it contains a fairly large path. From MyEclipse Blue, it contains only c:\websphere\appserver61\java\bin;c:\websphere\appserver61\bin. I’ve no idea if this is related.

    Any ideas?

    #296313 Reply

    Loyal Water
    Member

    By default the connector builds the *default* launch classpath, if you are adding custom libraries to the server configuration, you needs to go to the connectors Path page and augment the setting there — for example, appending that Spring JAR to your classpath on that page and retrying.

    #296380 Reply

    ADP-1
    Member

    Thanks. I added the jar to the classpath and that did the trick. I assume that the was startserver.bat picks up everything in the LIB folder.

    #296457 Reply

    Loyal Water
    Member

    Awesome. Your welcome.

Viewing 4 posts - 1 through 4 (of 4 total)
Reply To: Websphere 6.1/ Spring WS Classloader issues from MyEclipse

This topic is marked as closed to new replies, however your posting capabilities still allow you to do so.

You must be logged in to post in the forum log in