Hi,

This is an interesting observation about a possible limitation in WebLogic Workshop while working with WebServices. With SOAP and WSDL standards this is something I would not expect.

The limitation is that I cannot use a simple standard format of a URL to specify a service endpoint using weblogic workshop.

Lets say the simple format of the service endpoint is:

http://localhost:7001/SimpleProcessProject/Service1

but WebLogic workshop makes this almost impossible for me without using its custom extensions to files specific to WebLogic platform. I feel for SOA applications this is not what is intended.

To explain, I have created a simple JPD with a synchronous method call with a return.

I want to expose it as a webservice, and using workshop generated the WSDL and .jws files. (WSDL snippet below ).

To invoke the webservice I want to specify to the client a URL like:

http://localhost:7001/SimpleProcessProject/Service1
for Service 1,
http://localhost:7001/SimpleProcessProject/Service2
for Service2 and so on.

However, the default address location getting created in the WSDL is: address location="http://localhost:7001/SimpleProcessProject/processes/SimpleJPD.jpd

I simply want to provide the service name to the client in the URL as described above and NOT the jpd name. How do I do this?

I tried editing the application.xml file to specify the context-root as the URL I want to give the client and web-uri as the actual path to the JPD but that did not work (default entry given below). It gets overwritten whenever I build the application in the workshop.
Is there any entry I need to make in any of the xml files, deployment descriptors?

			

			*********** From the wsdl file **********
			

			

			

			

			

			

			

			

			

			

			

			

			

		

**************From the application.xml file below*******
***Current default entry ********

SimpleProcessProject
SimpleProcessProject

*****************************************************

Does anyone have a solution to this? I do not want a URL redirection by having a WebServer in between.

Thanks and Regards,

Rommel Sharma.