DO NOT REPLY [Bug 19995] New: - java:MSG provider does not support EJB invocation

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19995>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19995

java:MSG provider does not support EJB invocation

           Summary: java:MSG provider does not support EJB invocation
           Product: Axis
           Version: 1.1rc2
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Basic Architecture
        AssignedTo: axis-dev@ws.apache.org
        ReportedBy: anamitra.bhattacharyya@mro.com


I was trying to deploy a message style web service and in the deploy.wsdd we 
had 

 <service name="ejbdoctest" provider="java:MSG" style="message">
	<wsdlFile>c:/anamitra/ejbdoctest.wsdl</wsdlFile>
	<parameter name="allowedMethods" value="processData"/>
	<parameter name="wsdlPortType" value="WSTest"/>
	<parameter name="scope" value="Request"/>
	<parameter name="wsdlServicePort" value="WSTest"/>
	<parameter name="wsdlTargetNamespace" value="www.mro.com/mea"/>
	<parameter name="wsdlServiceElement" value="WSTestService"/>
  	<parameter name="className" value="test1.SimpleDocTest"/>
 </service>

And my class method is like 

public Document processData(Document doc) - inline with the MSG style 
Webservices of Axis.

This works perfectly .
 But if we try to invoke an EJB [which has the same method processData] - thats 
where the java:MSG provider is failing. 

 <service name="ejbdoctest" provider="java:MSG" style="message">
	<wsdlFile>c:/anamitra/ejbdoctest.wsdl</wsdlFile>
	<parameter name="wsdlPortType" value="WSTest"/>
	<parameter name="scope" value="Request"/>
	<parameter name="wsdlServicePort" value="WSTest"/>
	<parameter name="wsdlTargetNamespace" value="www.mro.com/mea"/>
	<parameter name="wsdlServiceElement" value="WSTestService"/>
	<parameter name="beanJndiName" value="testdoc"/>
	<parameter name="homeInterfaceName" value="test1.TestHome"/>
	<parameter name="remoteInterfaceName" value="test1.Test"/>
	<parameter name="jndiURL" value="t3://localhost:7001"/>
	<parameter name="allowedMethods" value="sayHello"/>
	<parameter name="jndiContextClass" 
value="weblogic.jndi.WLInitialContextFactory"/>
 </service>

So I changed it to a java:EJB provider - but in that case it expects the client 
to give a "Document" object and tries to serialize/deserialize that. This is a 
bit strange as either the java:MSG provider should be able to handle calling 
EJB's or EJB provider has to support that same thing as the MSG provider - ie 
bypass the java/XML data types binding.