>From what I know about EAR deployment it should work. Not sure what JEERI is, but there are two steps I would follow to try and figure out what is going on.
1. Try and deploy your EAR file in Tomcat and see what behavior you get. If it works fine it means there is some sort of configuration problem in JEERI, if it doesn't work then it's either a muse problem or a container problem (from looking at it I am inclined to say it's a J2EE container problem, or Axis2 problem) 2. Look at the log files for your container. It should have something displaying like this (log taken from WebSphere, so messages might be different but the general meaning should be the same - that the application is started): [7/20/07 13:28:00:984 EDT] 00000016 ApplicationMg A WSVR0200I: Starting application: AutonomicCoordinator_war [7/20/07 13:28:01:093 EDT] 00000016 ApplicationMg A WSVR0204I: Application: AutonomicCoordinator_war Application build level: Unknown [7/20/07 13:28:03:578 EDT] 00000015 ServletWrappe I SRVE0242I: [AutonomicDecisionMaker_war] [/AutonomicDecisionMaker] [AxisServlet]: Initialization successful. [7/20/07 13:28:03:593 EDT] 00000015 VirtualHost I SRVE0250I: Web Module Apache-Axis2 has been bound to default_host[*:9080,*:80,*:9443,*:5060,*:5061,*:443]. [7/20/07 13:28:03:687 EDT] 00000015 ApplicationMg A WSVR0221I: Application started: AutonomicDecisionMaker_war and something showing like this [7/20/07 13:28:26:046 EDT] 00000016 SystemErr R [INFO] DeploymentEngine - Deploying module : addressing-1.1 [7/20/07 13:28:26:046 EDT] 00000016 SystemErr R [INFO] DeploymentEngine - Deploying module : muse-wsa-action-2.1.0 [7/20/07 13:28:26:078 EDT] 00000016 SystemErr R [INFO] DeploymentEngine - Deploying module : soapmonitor-1.1 [7/20/07 13:28:26:750 EDT] 00000016 SystemErr R [INFO] DeploymentEngine - Deploying Web service muse WebSphere puts them in two separate files as some are sent as SystemErr and some are sent as SystemOut. You should have two instances of this being deployed. Although to be honest I do not think it's a deployment issue, as your container routes to the other resource (shown by the fact that instead of displaying no endpoints, it displays the other resource's endpoint as available). I wonder if this is not some sort of strange behavior for Axis2 deployment of EARs. Zhang, Jin-Zhai wrote: > > Hi, now I have perfomed some experiment in a clean environment. > The experiment material is JEERI 9.x, Tomcat 5.5.x, MUSE 2.2.0 and 3 war: > the wsn_produer_a.war,wsn_produer_.war and wsn_consumer.war I mentioned in > last mail. > > Experiment 1: deploy all the 3 war files into tomcat (5.5.x), then the > consumer can work with these 2 producers, no any exception. > Experiment 2: deploy the 2 producer war files into JEERI (9.x), and > deploy the consumer war into Tomcat(5.5.x), then the consumer > can work with these 2 producers, no any exception. > Experiment 3: package the 2 producer war files into an EAR, deploy > this ear into JEERI(9.x),and deploy the consumer war into Tomcat(5.5.x), > then got "DestinationUnreachable" fault. > > > > So, as Vinh Nguyen and Bogdan Solomon had discussed, the problem is (at > least partly) because the WAR files are inside an EAR. > In ear application.xml, the war modules defined as: > > <application> > <display-name>wsn_producers_test</display-name> > <module> > <web> > <web-uri>wsn_producer_a.war</web-uri> > <context-root>/wsn_producer_a</context-root> > </web> > </module> > <module> > <web> > <web-uri>wsn_producer_b.war</web-uri> > <context-root>/wsn_producer_b</context-root> > </web> > </module> > </application> > > And when I deploy these war's outside ear as in the experiment 1 and 2, > the context paths as the same:/wsn_producer_a and /wsn_producer_b. > > I am still trying to understand the result of experiment 3. > -- View this message in context: http://www.nabble.com/One-endpoint-but-two-wsn-producer-EPRs-tf4134220.html#a11810706 Sent from the Muse User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
