Hi, I'm new to this, but I've done a deployment where the beanMapping element is enclosed between <service> and </service>.
Have you tried that? My service seems to deploy fine. Dave Oppenheim -----Original Message----- From: James Goodwill [mailto:[EMAIL PROTECTED] Sent: Friday, February 27, 2004 5:36 PM To: [EMAIL PROTECTED] Subject: Undeployment and Bean Mappings Hi, USING: Tomcat 4.1.30 and Axis 1.2 Alpha I came across something odd today and I was wondering if I might have missed something or is this expected behavior. I have a simple example web service called InventoryService that passes an InventoryItem back and forth. To deploy this example I use the following WSDD: <deployment xmlns="http://xml.apache.org/axis/wsdd/"; xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";> <service name="InventoryService" provider="java:RPC"> <parameter name="className" value="com.bob.InventoryService"/> <parameter name="allowedMethods" value="*"/> </service> <beanMapping qname="myNS:InventoryItem" xmlns:myNS="urn:InventoryService" languageSpecificType="java:com.bob.InventoryItem" /> </deployment> I deploy and test the service without any trouble, but when I try to undeploy using the following: <undeployment xmlns="http://xml.apache.org/axis/wsdd/";> <service name="InventoryService" /> </undeployment> I notice that the bean mapping added to the server-config.wsdd is not removed. Is this expected behavior or am I missing something in the <undeployment>? Thanks, James
