Hello Ralph,
Sorry for the very very late reply. I suppose you have solved your
problem already, but if you haven't:
[EMAIL PROTECTED] wrote:
Follow the example in the URL:
1. your impl class implements javax.xml.rpc.server.ServiceLifecycle
2. implement init(Object ctx) and destroy()
My problem is hat the init and destroy method is only called, if I implement
the ServiceLifecycle interface in the Skeleton class. But this is not what I
want to do, because this class is not very nice and would be overwritten if
I do another Java2WSDL task.
I tried rebuilding your service with the skeletonDeploy option to false
(no skeletons). The init method in the impl class was called correctly.
I never used skeletons, so I am not sure what to expect if you do
generate them.
I am a little bit confused about the ServiceLifecycle. The ServiceLifecycle
seems to be called every time if I call
http://localhost:7070/myapp/services/SyncService?method=getPerson
in the browser etc.. That's OK and what I want to have. But in some
documentations and also in books they write the init method of a service
will be called only ONCE before he can accept requests. I think that's not
correct?!?
It depends on what you specify for the deployScope option. If you choose
"application", the init method will be called only once.
PS:
Another ugly thing why overwrites Axis with every java2wsdl task the
ServiceImpl class?
I think you mean the wsdl2java task.
The ant task designer must have thought that the reason you are
rerunning the wsdl2java task is to update your Java classes after you
changed the interface. If the interface is changed, the old impl class
would not work anymore anyway. Why don't you keep the generated source
and your own implementation class separate (with the 'output' attribute)
and update your impl by hand if necessary.
Regards,
Dies
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
