Hi.

As suggested I break up my questions into separate emails. This one covers the topic of extending the RegisterPublisher request from WS-BrokeredNotification.

As I wrote in my first email, the service I intend to implement might realize the RegisterPublisher and Notify operation from WSN. It "might" realize these operations because in some use cases there may be other ways on how the service gets the required information from my event producing entities (i.e., the sensors). However, if the additional operations are implemented, the RegisterPublisher request would make use of the extensibility mechanism defined in the OASIS specification for that operation to send also the sensor description in XML.

After compiling my wsdl (SASallinone.wsdl), I had the following question concerning the realization of the RegisterPublisher operation:
The registerPublisher method (in MyCapability1) takes the elements contained in a usual RegisterPublisher request, i.e. as they are listed in the schema from OASIS, as parameters. As I said earlier I would like to make use of the extension mechanism for that operation. Do I therefore have to modify the schema before generating source code or is there some way to retrieve the pure request body via muse?
Allen wrote:
Were you planning on extending it using the <xsd:extension>system?
I thought that this could be handled on the fly, i.e. I would not have to extend the operations base schema but could just insert additional elements into the request body and retrieve those somehow on the server side. So that is why I am asking.

You mentioned that I could use my custom serializer for handling the request body. If so, maybe that will do the trick. Usually I am working with XMLBeans and I think that it would provide the means to extract the additional elements from the request.

Cheers,
Johannes



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to