- This topic has 9 replies, 2 voices, and was last updated 18 years ago by Riyad Kalla.
-
AuthorPosts
-
rtseMemberI am trying to deploy a web service as part of an EAR. The web service is in a separate web services project. I am getting the following error when the server starts up, or whenever I try to call the web service —
I am using MyEclipse 5 to deploy to Sun Java Application Server PE 9
[#|2006-11-01T15:08:14.039-0700|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.container.web|_ThreadID=15;_ThreadName=httpWorkerThread-8080-1;_RequestID=97f43f17-713f-4596-979b-eb0bbf104da7;|StandardWrapperValve[XFireServlet]: Allocate exception for servlet XFireServlet
java.lang.NullPointerException
at org.apache.xbean.spring.context.impl.XBeanHelper.createBeanDefinitionReader(XBeanHelper.java:18)
at org.codehaus.xfire.spring.XFireConfigLoader.getXFireApplicationContext(XFireConfigLoader.java:71)
at org.codehaus.xfire.spring.XFireConfigLoader.loadContext(XFireConfigLoader.java:39)
at org.codehaus.xfire.transport.http.XFireConfigurableServlet.loadConfig(XFireConfigurableServlet.java:75)
at org.codehaus.xfire.transport.http.XFireConfigurableServlet.createXFire(XFireConfigurableServlet.java:51)
at org.codehaus.xfire.transport.http.XFireServlet.init(XFireServlet.java:45)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
… etc …Any ideas of what the problem might be? If I deploy just the web services project alone, then there are no issues.
thanks,
Rob
Riyad KallaMemberRob,
I asked someone from our web services team if they had any idea why this would be happening and both of us were at a loss of ideas. The case (just to refresh) is that if you deploy it independently, it works, but as part of an EAR, it fails with that error?
rtseMemberHi Riyad,
That is correct … I can deploy the web services project independantly and it works fine. If I package it as part of my current EAR, then I get the above error message when the server starts up.Rob
Riyad KallaMemberRob,
If you compare the dir contents to the individual deployment and then the EAR deployment, are they the same or are there parts missing from the web service deployment in the EAR? I hate that the exception raised is not more descriptive (like a file name or something that could help us).
rtseMemberRiyad,
Looks like both deployments produce identical structure and files.
Does it maybe not like something else in my EAR? maybe something is getting loaded first that’s causing this to misbehave? How would I figure out what is causing it?
Riyad KallaMemberWhat does your application.xml file look like in your ear?
rtseMemberHere is the application.xml in the EAR project:
<?xml version=”1.0″ encoding=”UTF-8″?>
<application xmlns=”http://java.sun.com/xml/ns/j2ee” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” version=”1.4″ xsi:schemaLocation=”http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd”>
<display-name>connectEAR</display-name>
<module id=”myeclipse.1121113613835″>
<web>
<web-uri>connect.war</web-uri>
<context-root>/connect</context-root>
</web>
</module>
<module id=”myeclipse.1121123627823″>
<web>
<web-uri>mapxtreme.war</web-uri>
<context-root>/mapxtreme</context-root>
</web>
</module>
<module id=”myeclipse.1120770003907″>
<web>
<web-uri>encore_drill_log.war</web-uri>
<context-root>/encore</context-root>
</web>
</module>
<module id=”myeclipse.1162312985128″>
<web>
<web-uri>connect_web_services.war</web-uri>
<context-root>/connectws</context-root>
</web>
</module>
</application>I haven’t made any modifications to it – just used whatever was generated.
Riyad KallaMemberIs this set of projects something that could be trimmed down to a smaller set of projects and sent to me for testing?
rtseMemberNot sure… I’ll try.
thanks.I gather you’ve been unable to reproduce this problem yourselves?
Rob
Riyad KallaMemberRob,
That is correct. In the few demos I’ve thrown together they have been working as expected both independently and in an EAR. -
AuthorPosts