Ian, I can confirm that Apollo does either always require a reference property or never uses a reference property.
I think this is a perfectly reasonable choice to make for an implementation. It is much more intuitive to think about always needing a reference property or never using one, than allowing both. Even though a service may choose to offer both, it is not violating any rule by not offering both in the same service. I asked the question because I was thinking about a factory with N instances at the same endpoint address. My work-around was to use a special reference proeprty for the factory, but I am actually going to move to using 2 different addresses for the factory and instances as you have done in the WSRF interop example. The reason is that a factory ineviteably has a slightly different interface than the instance (create is only valid for a factory), so using 2 different WSDL documents makes sense. Don't change anything. I think you have made the right choice. Bryan -----Original Message----- From: Ian Springer [mailto:[EMAIL PROTECTED] Sent: Thursday, March 17, 2005 9:03 AM To: [email protected] Subject: Re: Reference properties Bryan, I don't think Apollo currently supports having a single endpoint that can act as both a factory and the resource instances. This is because in a service's config, you specify a ResourceKeyName that is the QName of the SOAP header to be used for disambiguation. If no ResourceKeyName is specified in the config, this indicates that the service is a singleton (e.g. a factory). Do you think this is acceptable, or do you think we ought to support having an endpoint that exposes both a factory and instances? I kind of like the way it is because it enforces the notion of one endpoint exposes one "type" of resource, which I find most intuitive. Ian Murray, Bryan P. wrote: >I don't know how to write the code to do this. Can you explain what >needs to be done? Is this something special in the xxxHome.java >generated file? > >Thanks, >Bryan > >-----Original Message----- >From: Campana Jr., Salvatore J >Sent: Tuesday, March 15, 2005 7:30 AM >To: [email protected] >Subject: RE: Reference properties > > > >>>How do you configure a service to have an endpoint for a factory with >>> >>> >no reference properties and the same URL with > > >>>reference properties for the instances? Or would it be better to use >>>2 >>> >>> >different endpoints, one for the factory as a > > >>>singleton, and one for the instances with reference properties? >>> >>> > >Exactly... > >I would use the pattern as in the WSRF interop...Define your factory as >an endpoint with no resourceid, and then define the services to use a >resourceid.... > >-Sal > >-----Original Message----- >From: Murray, Bryan P. >Sent: Monday, March 14, 2005 5:42 PM >To: [email protected] >Subject: Reference properties > >The tutorial has some discussion about how to configure an endpoint to >accept a reference property to identify a resource or how to configure >the service as a singleton. > >How do you configure a service to have an endpoint for a factory with >no reference properties and the same URL with reference properties for >the instances? Or would it be better to use 2 different endpoints, one >for the factory as a singleton, and one for the instances with >reference properties? > >Thanks, >Bryan > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
