Hi,
>
> But that's exactly what we have now, e.g. you could do:
>
> javax.xml.ws.Endpoint = delegate.createEndpoint(applicationConfig, javax.xml.ws.Endpoint.class);
>
> (assuming the impl supports javax.xml.ws.Endpoint as an endpoint type).
Ok, this code would have a chance to be more portable :-) My only concern is that it might not be a solid portable code (given some
of the robust feedback earlier :-)). Consider a TCK test case which would verify that the info passed in the ApplicationConfig is
preprocessed properly (though Spring might help here). IMHO having a dedicated JAX-RS specific Endpoint interface wouldn't be too
bad, though I appreciate the concerns about some duplication.
I'm just looking now at a JAX-WS endpoint interface and it seems it may not fit perfectly well, at least initally with the
JAX-RS view of the world, with its getBinding(), etc...
Endpoint {
ApplicationConfig getApplicationConfig();
start();
stop();
boolean isStarted();
// and then later add some more useful stuff
}
would possibly do...
I'd like to be able to say basically this to the users of the JAX-RS based product :
here's the mainline code, you right it and then you can substitute the underlying implementation from CXF to Jersey or to
Restlets/RestEasy or the other way around. My concern that even though JAX-RS is a specification there's no 100% portable way to
submit an aplication config and have an endpoint up and running with the Runtime.createEndpoint.
Cheers, Sergey
>
> The reason for the current design is to avoid a dependency on a particular type while still offering a standard way to talk to
> the delegate endpoint factory.
>
>> Perhaps it might be worth giving more thought to the idea of introducing a new interface. While it would resemble the jaxws one,
>> it can have more useful JAX-RS specific methods on it, etc... In the end of the day people can write RESTful services with
>> JAX-WS Provider<Source> just fine (we ceratinly have some experience), without even sprinkling the code with annotations :-),
>> but it didn't stop the JAX-RS experts to come up with a new/fresh idea, even at the cost of duplicating some of the
>> functionality which can be achieved with JAX-WS today...
>>
> Similarly you can do:
>
> javax.xml.ws.Provider = delegate.createEndpoint(applicationConfig, javax.xml.ws.Provider.class);
>
> and then use the Provider with an Endpoint to publish the application (again, assuming the delegate impl supports Provider as an
> endpoint type).
>
> Marc.
>
> ---
> Marc Hadley <marc.hadley at sun.com>
> CTO Office, Sun Microsystems.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jsr311.dev.java.net
> For additional commands, e-mail: users-help_at_jsr311.dev.java.net
----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland