Hi Laura,
maybe it would help if you can pass the exception thrown by the AdminClient.
Id using Tomcat you should see this in the tomcat-console.
But are you sure your languageSpecificType parameter in bean-tag is right?
Try the praefix 'java:', therefor you defined the namesapce in
deplyment-tag. And remember to specify the package!!
<beanMapping qname="myNS:AssetData" xmlns:myNS="urn:PPServer"
languageSpecificType="java:mypackage.AssetData"/>
Hope that helps Greetings from Hamburg/Germany
Seppo
-----Urspr�ngliche Nachricht-----
Von: Slaybaugh Laura J IHMD [mailto:[EMAIL PROTECTED]]
Gesendet: Freitag, 17. Januar 2003 18:21
An: '[EMAIL PROTECTED]'
Betreff: [axis] beanMapping and deploy.wsdd help
Hello,
I'm using the following wsdd to deploy a service that uses a custom class.
Or rather, that's what I'm trying to do. When I actually deploy with
AdminClient, it seems to process the file, but never actually makes the
service available. I know the problem lies somewhere in the beanMapping
because if I remove that tag, I can at least deploy the service, but I"m not
quite sure what the problem is. I copied the wsdd from the ProcessOrder
example available with Axis and just changed the names of the service and
classes. Is there some subtlety I'm missing here?
Any advice?
Thanks,
Laura
-------------------------------------------------------------------
<deployment xmlns="http://xml.apache.org/axis/wsdd/";
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";>
<service name="PPService" provider="java:RPC">
<parameter name="className" value="PPServer"/>
<parameter name="allowedMethods" value="*"/>
<beanMapping qname="myNS:AssetData" xmlns:myNS="urn:PPServer"
languageSpecificType="AssetData"/>
</service>
</deployment>
-------------------------------------------------------------------
