Doesn't this approach seem a little overly complex?
-Polar
Dan Diephouse wrote:
Hi Polar,
You're assumptions about how the portName is created is correct.
If you want to override the portName you can look into the
ReflectionServiceFactory. You can provide your own
ServiceConfiguration to
it if you desire which allows you to specify your own portname:
JaxWsServiceFactoryBean sf = new JaxWsServiceFactoryBean();
sf.getServiceconfigurations().add(0, new AbstractServiceConfiguration() {
QName getEndpointName() { ... }
});
I believe you can pass in the service factory to the EndpointImpl or
you can
use the JaxWsServerFactory bean and access the Service Factory by calling
getServiceFactory(); I think I wrote up some docs here:
http://cwiki.apache.org/CXF20DOC/server-service-and-client-factorybeans.html
- Dan
On 3/28/07, Polar Humenn <[EMAIL PROTECTED]> wrote:
Is there any documentation on how Endpoint names are arrived at?
Is seems some are assigned by @annotations on the implementor class.
If it's not set (or should I say empty ("")) it seems to be the class
name appended
with "Port".
Is there anyway to override this static-ness?
I can't seem to rename an endpoint without creating another class with
different annotations.
Shouldn't there be a way to name the endpoint, like with this call,
which doesn't
(yet) exist?
new EndpointImpl(
getBus(),
new GreeterImpl(),
"MyOwnGreeterPort",
"http://apache.org/hello_world";,
getClass().getResources('resources/hello_world.wsdl");
Is there some need for the Implementation Class (not instance) always to
be statically associated with an endpoint name?
Cheers,
-Polar
