Skip to main content

Deploying handler chains using jaxrpc-ri.xml and wsdeploy - possible bug?

5 replies [Last post]
mattgelbman
Offline
Joined: 2005-11-10
Points: 0

Hi.

I'm trying to deploy a handler chain in my web service using the wsdeploy tool. I believe that I have the jaxprc-ri.xml correct (pretty straight forward). In the generated Tie class, the HandlerIno class is not loaded in the constructor, so the chain does not work.

When I do basically the same thing using the wscompile tool, the Tie class has the HandlerInfo data and it works fine.

The problem is, using the wscompile tool to generate the class files and then trying to get those into the 'cooked' .war file is a huge pain. You can't just swap the Tie class because the different tools name them differently. It's possible to use the -keep option on wsdelopy to get the java files, make the necessary changes, compile them and then .war it, but that is also a pain because oof the different file structure and class names. You have to change the jax-rpc-ri-runtime.xml file, etc.

I did all that and it worked, but I really don't want to do that everytime I change the service (it's still in development).

Any suggestions? Is this a bug? Is there a patch? I'm using the latest jwsdp 1.6. Should I use an earlier version?

Any help is greatly appreciated.

-Matt

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
bbissett
Offline
Joined: 2003-06-16
Points: 0

> I'm trying to deploy a handler chain in my web
> service using the wsdeploy tool. I believe that I
> have the jaxprc-ri.xml correct (pretty straight
> forward). In the generated Tie class, the HandlerIno
> class is not loaded in the constructor, so the chain
> does not work.

Can you post the jaxrpc-ri.xml file? Also, is wsdeploy giving you any error output?

Bobby

bbissett
Offline
Joined: 2003-06-16
Points: 0

Also, you may want to send questions like this to the users@jax-rpc.dev.java.net users list. You may get more people to see it that way and hopefully get an answer sooner.

Cheers,
Bobby

mattgelbman
Offline
Joined: 2005-11-10
Points: 0

Thanks for responding to the question. Below is the jaxrpc-ri.xml file. There were no errors on output.....

xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/dd"
version="1.0"
targetNamespaceBase="http://newdev01.mlb.com:2880/"
typeNamespaceBase="http://newdev01.mlb.com:2880/types/"
urlPatternBase="/service">

name="SimpleWS"
displayName="Simple Service"
description="A simple web service"
wsdl="/WEB-INF/wsdl/SimpleWS.wsdl"
interface="ws.SimpleWS"
implementation="ws.SimpleWSImpl">

runAt="server"
handler="handler.ServerHandler1"
property="propName" value="propValue"/>

name="SecondWS"
displayName="Simple Service"
description="A simple web service"
wsdl="/WEB-INF/wsdl/SecondWS.wsdl"
interface="ws.SecondWS"
implementation="ws.SecondWSImpl"
/>

endpointName="SimpleWS"
urlPattern="/ws/simple">

endpointName="SecondWS"
urlPattern="/ws/second"/>

bbissett
Offline
Joined: 2003-06-16
Points: 0

Hi again,

It looks like there's a problem in your handler chain element, but it may also be the way it looks once it's formatted by my browser. Try this and see if it works.

Instead of:

>
>
> > runAt="server"
> handler="handler.ServerHandler1"
> property="propName" value="propValue"/>
> ="propValue"/>
>

>

Try:







I'm not positive about the init params anymore, so try that first to see if the handler is incorporated into the service. Then try this to see if init params are passed in properly:





Sorry I can't get the spacing to show up, but with each element on its own line I hope that makes sense.

Cheers,
Bobby

mattgelbman
Offline
Joined: 2005-11-10
Points: 0

Thank you, that totally did it!

In the documentation I looked at, I never saw the syntax:

It was documented as this:

It didn't give a parse error like that either. I made other syntax errors when I was first trying to deploy a handler, and wsdeploy would throw a parse exception. The documentation for it is a little thin.....

Thank you very much for the help!

-matt