WS-Eventing In JDeveloper 10.1.3

Question

Hi Folks..
I've been looking into trying to get WS-Eventing to work within JDeveloper and the OC4J container. There are two areas that I have come across that are making it difficult and I am hoping that some of you might have some insight into this... (It may very well be that its not possible in the current version of JDeveloper)
1) There are two schema definitions that WS-Eventing requires to work correctly.. http://schemas.xmlsoap.org/ws/2004/08/eventing
http://schemas.xmlsoap.org/ws/2004/08/addressing
Is there anyway to get JDeveloper to generate the appropriate java classes for from these schemas to use when I am creating the web service?? I tried creating a simple WSDL that imported these schemas then used the create Web Service Proxy to generate the service skeletons.. but when it was finished it hadnt generated the complete set of classes that it should have. IE One of the complex types in the Schema is called _Subscribe.. this class was not generated when running the wizard.
2) I was able to eventually generate the necessary java classes with an axis tool.. WSDL2Java.. and from there to create my implementation. The problem I have from there was creating the web service from the implementation. When trying to create the J2EE 1.4 Web service.. I am able to fill out the first page of the wizard... indicating what implementation file to expose.. but when I click to go to the next page.. the Next button becomes disabled and I remain on the first wirard page. No error message is indicated. Im assuming that the wizard is choking on the WS-Eventing types that are declared in the implementation file, although Im not sure.
Anyways.. not sure I will get any feedback on this.. as WS-Eventing is fairly new... but I thought I would put it out there.
Thanks for any help
Dave

Answer 1

Thanks Eric..
I will look into the WSA route. Ive included my WSDL below with the hope that someone might see where I've gone wrong. As you can see I am importing the Eventing Schema... http://schemas.xmlsoap.org/ws/2004/08/eventing this schema in turn references the Addressing Schema.. http://schemas.xmlsoap.org/ws/2004/08/addressing.. When I use JDeveloper to create the skeleton classes... it seems to generate all the Addressing classes correctly.. but it only generates one of the types from the Eventing Schema.
Thanks again for your help..
Dave
<?xml version="1.0" encoding="UTF-8" ?>
<definitions name="Notify" targetNamespace="http://tempuri.org"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://tempuri.org"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:ns7="http://schemas.xmlsoap.org/ws/2004/08/eventing">
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://tempuri.org"
elementFormDefault="qualified" xmlns:tns="http://tempuri.org"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/">
<xsd:import namespace="http://schemas.xmlsoap.org/ws/2004/08/eventing"
schemaLocation="http://schemas.xmlsoap.org/ws/2004/08/eventing"/>
<complexType name="getMessage">
<sequence/>
</complexType>
<complexType name="getMessageResponse">
<sequence>
<element name="result" type="string" nillable="true"/>
</sequence>
</complexType>
<complexType name="setMessage">
<sequence>
<element name="String_1" type="string" nillable="true"/>
</sequence>
</complexType>
<complexType name="setMessageResponse">
<sequence/>
</complexType>
<element name="getMessageElement" type="tns:getMessage"/>
<element name="getMessageResponseElement"
type="tns:getMessageResponse"/>
<element name="setMessageElement" type="tns:setMessage"/>
<element name="setMessageResponseElement"
type="tns:setMessageResponse"/>
</schema>
</types>
<message name="NotifyServer_getMessage">
<part name="parameters" element="tns:getMessageElement"/>
</message>
<message name="NotifyServer_setMessageResponse">
<part name="parameters" element="tns:setMessageResponseElement"/>
</message>
<message name="NotifyServer_getMessageResponse">
<part name="parameters" element="tns:getMessageResponseElement"/>
</message>
<message name="NotifyServer_setMessage">
<part name="parameters" element="tns:setMessageElement"/>
</message>
<message name="subscribePushMessageResp">
<part element="ns7:SubscribeResponse" name="parameters"/>
</message>
<message name="subscribePushMessage">
<part element="ns7:Subscribe" name="parameters"/>
</message>
<message name="unsubscribePushMessage">
<part element="ns7:Unsubscribe" name="parameters"/>
</message>
<message name="pushMessageResponse"/>
<message name="pushMessageRequest">
<part element="tns:in1" name="in0"/>
</message>
<portType name="Notify">
<operation name="getMessage">
<input message="tns:NotifyServer_getMessage"/>
<output message="tns:NotifyServer_getMessageResponse"/>
</operation>
<operation name="setMessage">
<input message="tns:NotifyServer_setMessage"/>
<output message="tns:NotifyServer_setMessageResponse"/>
</operation>
</portType>
<portType name="pushMessagePort">
<operation name="subscribePushMessage">
<input message="tns:subscribePushMessage"/>
<output message="tns:subscribePushMessageResp"/>
</operation>
<operation name="unsubscribePushMessage">
<input message="tns:unsubscribePushMessage"/>
</operation>
<operation name="pushMessage" parameterOrder="in0">
<input message="tns:pushMessageRequest" name="pushMessageRequest"/>
<output message="tns:pushMessageResponse"
name="pushMessageResponse"/>
</operation>
</portType>
<binding name="NotifyServerSoapHttp" type="tns:Notify">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="getMessage">
<soap:operation soapAction="http://tempuri.org:getMessage"/>
<input>
<soap:body use="literal" parts="parameters"/>
</input>
<output>
<soap:body use="literal" parts="parameters"/>
</output>
</operation>
<operation name="setMessage">
<soap:operation soapAction="http://tempuri.org:setMessage"/>
<input>
<soap:body use="literal" parts="parameters"/>
</input>
<output>
<soap:body use="literal" parts="parameters"/>
</output>
</operation>
</binding>
<binding name="pushMessageSoapBinding" type="tns:pushMessagePort">
<binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="subscribePushMessage">
<input>
<body use="literal" parts="parameters"/>
</input>
<output>
<body use="literal" parts="parameters"/>
</output>
</operation>
<operation name="unsubscribePushMessage">
<input>
<body use="literal" parts="parameters"/>
</input>
</operation>
<operation name="pushMessage">
<operation soapAction=""/>
<input name="pushMessageRequest">
<body use="literal" parts="parameters"/>
</input>
<output name="pushMessageResponse">
<body use="literal" parts="parameters"/>
</output>
</operation>
</binding>
<service name="Notify">
<port name="NotifyServerPort" binding="tns:NotifyServerSoapHttp">
<soap:address location="http://dburgess-xp:8888/Apps-EventServer-context-root/Notify"/>
</port>
<port binding="tns:pushMessageSoapBinding" name="pushMessageIF">
<soap:address location="http://dburgess-xp:8888/Apps-EventServer-context-root/pushMessageIF"/>
</port>
</service>
</definitions>