The required header is actually for the resource instance
itself...The only way around this is to make you resource a
singleton.....
We could define some arbitrary attribute in the wsdl file
to denote this, however the spec does not outline
this...
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jan Christian Bryne
Sent: Sunday, April 30, 2006 3:14 PM
To: wsrf-user@ws.apache.org
Subject: Question about factory pattern
Hi,
This question have previously been asked but I didn't get a reply, so I try again.
When communicating with a factory/instance pair of WSRF Web Services, a client first creates a new resource using the factory service. The EPR returned to the client is used to identify the resource, which can be reached using the instance service. This requires that the client place a header element in the request soap envelope.
The factory service is a singleton service, so it doesn't need a resource identifier in the header element. The problem is that it seems to me that the factory service still needs a header element to be present.
When using libraries used for vanilla web services, this makes it harder to use the factory service. The compulsory header element is not described in the WSDL file for the factory service (or can this be done?), so the client has no way to determine that the factory need a header element. This makes it necessary to implent a client on a lower level, making sure that the header is there.
So, are there any way to either disable the requirement of a header element for the factor service, or alternatively, is there a way to describe in the wsdl file for the factory that a header element is necessary?
Friendly regards,
This question have previously been asked but I didn't get a reply, so I try again.
When communicating with a factory/instance pair of WSRF Web Services, a client first creates a new resource using the factory service. The EPR returned to the client is used to identify the resource, which can be reached using the instance service. This requires that the client place a header element in the request soap envelope.
The factory service is a singleton service, so it doesn't need a resource identifier in the header element. The problem is that it seems to me that the factory service still needs a header element to be present.
When using libraries used for vanilla web services, this makes it harder to use the factory service. The compulsory header element is not described in the WSDL file for the factory service (or can this be done?), so the client has no way to determine that the factory need a header element. This makes it necessary to implent a client on a lower level, making sure that the header is there.
So, are there any way to either disable the requirement of a header element for the factor service, or alternatively, is there a way to describe in the wsdl file for the factory that a header element is necessary?
Friendly regards,
Jan Christian Bryne
