As mentioned before, the Dice service does not auto deploy on WebLogic Server 10. According to the WLS Web Service documentation a weblogic ant task ‘JwscTask’ is needed to compile the annotated web service and produce the necessary WAR and EAR for deployment.
The build script I put together looks like this:
It successfully builds and deploys the web service. The deployed web service endpoint is /Dice/Dice so the service name makes up the context and the servlet url-pattern. As mentioned in a previous post both JBoss and OC4J default the servlet url-pattern to diceserviceport while Glassfish defaults to DiceService.
Also of note is that the WSDL on WLS is so different from the others by using the SOAP array type and ignoring the Die structure in the schema. That means that the size attribute is missing.
The big thing to note though is that there is a runtime error when trying to test the web service:
So the mystery tour continues. I might just try the top down route based on a WSDL from the Dice service deployed on another platform. Naturally, I will keep you posted.
4 thoughts on “More problems with Dice service on WLS”
As an update to this article I did eventually get the web service working on WLS by setting the type attribute to JAXWS in the jwc ant task. See Dice service working on WLS
Did you have any luck with jwsc in packaging apps when used in presence of other libraries like beehive controls? seems like lot of trouble to me…
> Did you have any luck with > jwsc in packaging apps when > used in presence of other > libraries like beehive controls?No. There were no extra libraries apart from the what is distributed with WLS v10. The environment was kept ‘clean’ on purpose.
The writer of http://www.soastation.org has written a superior article. I got your point and there is nothing to argue about. It is like the following universal truth that you can not disagree with: Stuff happens, then more stuff happens. Stuff will continue to happen until stuff stops happening. I will be back.