Java Webservice Developer Pack client code generation

Hi,
I am working on Weblogic Webservices, i am trying to generate client code using 'xrpcc' tool.
Client code has been generated, and i am able to invoke webservices on the server. But i am not able to receive return value from the server and getting follwing error.
D:\TMP\java\webservices\wsdl\test\checkfree\nawf>java test.checkfree.nawf.NAWFCl
ient
java.rmi.RemoteException: Runtime exception; nested exception is:
java.lang.NullPointerException
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:234
at test.checkfree.nawf.GateWayPort_Stub.receiveAccountInfo(GateWayPort_S
tub.java:60)
at test.checkfree.nawf.NAWFClient.main(NAWFClient.java:10)
Caused by: java.lang.NullPointerException
at org.apache.xalan.transformer.TransformerIdentityImpl.transform(Transf
ormerIdentityImpl.java:354)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:95)
... 2 more
Please, can any one tell immdly?
Thanks
Shiva

could u post more info !!! like your wsdl ?

Similar Messages

Java WS Developer Pack available...

SUN just released the Java WS Developer pack EA1 at
http://java.sun.com/webservices/webservicespack.html
This pack provides functionality for implementing Web Applications
and Web Services.
For Web Services, the pack provides access to early versions of the
standard Java APIs that are being developed through the JCP process.
The release includes EAs of base XML technology (JAXP 1.2, including
XML schema support), SOAP based RPC (JAX-RPC), SOAP-based messaging
(JAXM), and registry client support (JAXR). We also include a
tutorial, a UDDI registry for testing, and other features.
For Web Applications, the pack includes the EA3 release of the JSTL,
the JSP standard tag library being developed through JCP and
implemented at Apache. This tag library includes actions for
many common needs of JSP developers, including XML manipulation
actions that can be used also in the context of Web Services.
The pack also includes the popular Ant building tool from Apache,
some management (more in later EAs), installation, etc.
We are bundling a version of Apache Tomcat so our developers can start
using the JWSDP right away using Servlets 2.3 and JSP 1.2.
The final release of the pack is targetted by this summer.
We hope you will find this EA useful.
- eduard/o

The installer looks at the following Windows registry keys to determine the
location of the J2SE SDK. These registry keys are created by the J2SE SDK
installer:
HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Development Kit\1.3\JavaHome
HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Development Kit\1.4\JavaHome
Common problems that we have seen are:
1. Neither of these keys exist - This is due to mapping a J2SE SDK
installation from a different machine that already has the J2SE SDK
installed on it. To correct this situation, you need to run the the
J2SE SDK installer on your machine so that Windows registry entries get
created.
2. The directories in either of these keys are incorrect - This usually
happens when you install the J2SE SDK and then move the installation
directory. To correct this situation, you need to use the "regedit"
command and put the updated directories in the above keys to match the
actual directory that your J2SE SDK now resides in.
Hope that helps,
Patrick

Problem while Consuming Java Webservice from WCF client

Hi,
I am trying to Consume Java Webservice from WCF client.The webservice main functionality is digital data management.The client can Query Digital data and upload digital data by calling webservice methods.Problem is when i am trying to call webmethod from WCF client its giving "Unrecognised message versions".I have no idea about how the message objects are processed at serverside.but at server side they have used JAXP for XML document parsing.
The response content type is Multipart/related and applicatio/XOP+XML.
Can u plz help me how to handle this situation.I have minimum knowledge in Java WS architecture.Basically i am .Net programmer.
Can U please guide me in a proper way to resolve the problem.

Hi Abinash,
I have the same problem. Have you solve that problem?
I am using a java program to call a webservice too. And I have generated the client proxy definition for Stand alone proxy using NWDS. When I call the method of the webservice I am getting the correct result but along with the result I am getting one error and one warning message in the output.
The java code to call the webservice is as follows.
MIDadosPessoaisSyncService service = new MIDadosPessoaisSyncServiceImpl();
MIDadosPessoaisSync port = service.getLogicalPort("MIDadosPessoaisSyncPort");
port._setProperty("javax.xml.rpc.security.auth.username","xpto");
port._setProperty("javax.xml.rpc.security.auth.password","xpto");
String out = port.MIDadosPessoaisSync("xpto", "xpto");
System.out.println(out);
The result I am getting is :
Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
Error Message is :com/sap/guid/GUIDGeneratorFactory
<b>The result of the WS is correct!!!</b>
The Java project does not have any warning. But the stand alone proxy project has following warnings associated with it.
This method has a constructor name     MIDadosPessoaisSync.java
The import javax.xml.rpc.holders is never used     MIDadosPessoaisSyncBindingStub.java
The import javax.xml.rpc.encoding is never used     MIDadosPessoaisSyncBindingStub.java
The constructor BaseRuntimeException(ResourceAccessor, String, Throwable) is deprecated     MIDadosPessoaisSyncBindingStub.java
It is very similar with your problem, could you help me?
Thanks
Gustavo Freitas

Client code generation question

I am starting to use OEPE to develop JAX-WS services and my first exercise is the HelloService of the J2EE 6 tutorial. The client code of the example is the following:
import javax.xml.ws.WebServiceRef;
import helloservice.endpoint.HelloService;
import helloservice.endpoint.Hello;
public class HelloClient {
public static void main(String[] args) {
try {
HelloClient client = new HelloClient();
client.doTest(args);
} catch(Exception e) {
e.printStackTrace();
public void doTest(String[] args) {
try {
System.out.println("Retrieving the port from the following service: " + service);
HelloService service = new HelloService();
Hello port = service.getHelloPort();
System.out.println("Invoking the sayHello operation on the port.");
String name;
if (args.length > 0) {
name = args[0];
} else {
name = "No Name";
String response = port.sayHello(name);
System.out.println(response);
} catch(Exception e) {
e.printStackTrace();
I have create a web service project and added a web service client for the Hello Service. The above code does not work because the code generated for HelloService is an interface and not as a class. In order to get the example working, I had to use the HelloServiceLocator instead of the HelloService one.
HelloServiceLocator helloSvcLocator = new HelloServiceLocator();
Hello port = helloSvcLocator.getHelloPort();
Did I miss something ?
Fred

Fred,
Sorry for the slow response.
Just to confirm, you're using this URL?
http://java.sun.com/webservices/docs/2.0/tutorial/doc/.
I'm going through the tutorial and most of this seems like it should work through OEPE with some caveats.
Some initial thoughts:
In OEPE we don't support java web service clients without using WLS directly or build tools built on top of WLS.
WLS builds on top of Glassfish web service API calls with its own API calls or ANT tasks.
For Hello you can deploy this web service from a web service enabled project to a running WLS instance and test through Test Client by right clicking on the file and choosing Run As.
For HelloClient to work some libraries need to be adjusted if you're using projects within OEPE and WLS since it's initial grammar doesn't allow it to run on WLS.
Regards,
Andrew

Problem while invoking webservice-method in client-code

Hi,
I had written webservice-client-code (using uddi-ext.jar, as i am using uddi for publishing webservices.) which is invoking webservice method successfully with complex datatypes(both for return type and input paramters).
But while calling following webservice-method from my client-code:
public ComplexType[] getData(String[] p_str1, String[] p_str2)
it is throwing exception
The Exception is:
[ERROR] - 27 Mar 2007 12:34:38 -failed to invoke operation 'getData' due to an error in the soap layer (SAAJ); nested exception is: Message[failed to deserialize xml:weblogic.xml.schema.binding.DeserializationException: mapping lookup failure. type=['java:language_builtins.lang']:ArrayOfString schema context=TypedSchemaContext{javaType=[Ljava.lang.String;}]
Although I had done correct registration of mapping of ArrayOfString in client-code:
registry = m_Service.getTypeMappingRegistry();
m_TypeMapping = registry.getTypeMapping(SOAPConstants.URI_NS_SOAP_ENCODING );
m_TypeMapping.register( ArrayOfStringHolder.class,
new QName( "java:language_builtins.lang", "ArrayOfString" ),
new ArrayOfStringCodec(),
new ArrayOfStringCodec());
But some how it doesnt works.
I had searched on google as well but didnt find any reliable solutions.
Please advice.
Edited by meetmrdeepak at 03/27/2007 2:43 AM
Edited by meetmrdeepak at 03/27/2007 2:45 AM

See item A.1 of the [RMI FAQ|http://java.sun.com/j2se/1.5.0/docs/guide/rmi/faq.html].

Need Help With NetBeans (Java Studio Enterprise 8)'s code generation

Hi!
I am using Java Studio Enterprise 8 with NetBeans 4.1 IDE bundled together with it. When trying to create GUI out from NetBeans Form Designer, I don't like the way it generates the code. When I try to use a JTextField, it uses "Fully Qualifed Class Names" (e.g: javax.swing.JTextField) on the code. How do I set NetBeans not to use it but rather use only the class name and generate import lines on top of the code? Also, how do I set it up that it will generate the variable declarations (which is on the uneditable blue portion of the code) on top rather than the default which is placed at the bottom of the class code body. I have tried tweaking the Options menu of this IDE but haven't got any luck...
Hope you could help, and thanks in advance!

To address the location of the var decl codegen section (or any codegen location issues), there is a workaround, admittedly, it is a bit tedious.
Once the form code is generated, as Kris mentioned, open the class in an external editor so that you can edit the generated code.
Then cut the entire var declaration section along with the begin/end gen-code markers and paste it to the section of the file you desire.
When you add more components to your form, the codegen will find this section wherever it is and add to it.
Alternatively, you could just move the non-protected code around the protected within the NB editor, but you would not be able to rearrange the order of the actual code-genned sections.
craig

Problem with a Webservice's proxy client re-generation...

Hi all,
I have a problem. I'm trying to re-generate a proxy client for a Web service and, when i'm about to finish WAS server ask me for an user. it shows me a window such as the window it shows when you launch (verify) a web app. standalone. Do i have to have a special permission for re-generate (generate) a proxy client for an enterprise service?. I tried to enter the user that i have in the server...and it doesn't work...please help

This proxy is based on a .NET Webservice. This Webservice is on a intranet server. When i launch the wsdl in a regular browser...it asks me enter an intranet user... (not was)...but the prompt that the WAS shows me when it is just about to regenerate...is an enter data logon of WAS, When i put my WAS User...doesnt work...ask me again for an user.... that is a bummer that you couldnt simulate my exact problem....

Error while generating java client code from wsdl file

I am trying to generate a java client code from WSDL file um_workflowSaveCreateProfile.wsdl which includes um_workflowSaveCreateProfile_interface.wsdl file, so I am keeping both the files in the same folder and trying to generate the client code but it is showing me the below error highlighted .
um_workflowSaveCreateProfile.wsdl
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:xsd="E:/DIPPWF/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:oblix="http://www.oblix.com/" xmlns:obinterface="http://www.oblix.com/wsdl/um_workflowSaveCreateProfile_interface" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://www.oblix.com/wsdl/um_workflowSaveCreateProfile" targetNamespace="http://www.oblix.com/wsdl/um_workflowSaveCreateProfile">
     <import namespace="D:/DIPP/WSDL/um_workflowSaveCreateProfile_interface" location="um_workflowSaveCreateProfile_interface.wsdl"/>
     <service name="OblixIDXML_um_workflowSaveCreateProfile_Service">
          <port name="OblixIDXML_um_workflowSaveCreateProfile_Port" binding="obinterface:OblixIDXML_um_workflowSaveCreateProfile_Binding">
               <soap:address location="http://localhost:7777/identity/oblix/apps/userservcenter/bin/userservcenter.cgi"/>
          </port>
     </service>
</definitions>
um_workflowSaveCreateProfile_interface.wsdl
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:oblix="http://www.oblix.com/" xmlns:oblixxmllocalschema="http://www.oblix.com/OblixXMLLocalSchema" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://www.oblix.com/wsdl/um_workflowSaveCreateProfile_interface" targetNamespace="http://www.oblix.com/wsdl/um_workflowSaveCreateProfile_interface">
     <types>
          <xsd:schema targetNamespace="http://www.oblix.com/" elementFormDefault="qualified"
               xmlns="http://www.oblix.com/"
               xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                    <xsd:include schemaLocation="../XMLSchema/common_parameters.xsd" />
                    <xsd:include schemaLocation="../XMLSchema/common_authentication.xsd" />
                    <xsd:include schemaLocation="../XMLSchema/workflowSaveCreateProfile.xsd" />
          </xsd:schema>
          <xsd:schema targetNamespace="http://www.oblix.com/OblixXMLLocalSchema" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
               <xsd:element name="request">
                    <xsd:complexType>
                         <xsd:sequence>
                              <xsd:element name="params">
                                   <xsd:complexType>
                                        <xsd:sequence>
                                             <xsd:element ref="oblix:ObWorkflowName"/>
                                             <xsd:element ref="oblix:ObDomainName"/>
                                             <xsd:element ref="oblix:ObWfComment" minOccurs="0"/>
                                             <xsd:element ref="oblix:noOfFields"/>
                                             <xsd:element ref="oblix:AttributeParams"/>
                                        </xsd:sequence>
                                   </xsd:complexType>
                              </xsd:element>
                         </xsd:sequence>
                         <xsd:attribute name="version" type="xsd:string" use="optional"/>
                         <xsd:attribute name="application" type="xsd:string" use="required" />
                         <xsd:attribute name="function" type="xsd:string" use="required" />
                         <xsd:attribute name="mode" type="xsd:string" use="optional"/>
                    </xsd:complexType>
               </xsd:element>
          </xsd:schema>
     </types>
     <message name="OblixIDXMLInput">
          <part name="authentication" element="oblix:authentication"/>
          <part name="request" element="oblixxmllocalschema:request"/>
     </message>
     <message name="OblixIDXMLOutput">
          <part name="body" element="oblix:Oblix"/>
     </message>
     <portType name="OblixIDXMLPortType">
          <operation name="OblixIDXML_um_workflowSaveCreateProfile">
               <input message="tns:OblixIDXMLInput"/>
               <output message="tns:OblixIDXMLOutput"/>
          </operation>
     </portType>
     <binding name="OblixIDXML_um_workflowSaveCreateProfile_Binding" type="tns:OblixIDXMLPortType">
          <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
          <operation name="OblixIDXML_um_workflowSaveCreateProfile">
               <soap:operation soapAction="http://www.oblix.com/"/>
               <input>
                    <soap:body use="literal"/>
               </input>
               <output>
                    <soap:body use="literal"/>
               </output>
          </operation>
     </binding>
</definitions>
I am using WSDL2 Java for generating the client code .
Please suggest where am I wrong .
E:\axis2-1.4\bin>WSDL2Java -uri E:\DIPPWF\um_workflowSaveCreateProfile.wsdl -p R
ND -d adb -s -o build\client--http-proxy-host 10.74.93.35 --http-proxy-port 80
Using AXIS2_HOME: E:\axis2-1.4
Using JAVA_HOME: C:\Program Files\Java\jdk1.6.0_02
Retrieving document at 'E:\DIPPWF\um_workflowSaveCreateProfile.wsdl'.
Retrieving document at 'um_workflowSaveCreateProfile_interface.wsdl', relative t
o 'file:/E:/DIPPWF/um_workflowSaveCreateProfile.wsdl'.
Retrieving schema at 'E:/DIPPWF/XMLSchema/common_parameters.xsd', relative to 'f
ile:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
Retrieving schema at 'E:/DIPPWF/XMLSchema/common_authentication.xsd', relative t
o 'file:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
Retrieving schema at 'E:/DIPPWF/XMLSchema/workflowSaveCreateProfile.xsd', relati
ve to 'file:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
Retrieving schema at 'navbar.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/workfl
owSaveCreateProfile.xsd'.
Retrieving schema at 'searchform.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/wo
rkflowSaveCreateProfile.xsd'.
Retrieving schema at 'component_basic.xsd', relative to 'file:/E:/DIPPWF/XMLSche
ma/workflowSaveCreateProfile.xsd'.
Retrieving schema at 'displaytype.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/c
omponent_basic.xsd'.
Retrieving schema at 'error.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/compone
nt_basic.xsd'.
Retrieving schema at 'component_workflowTicket.xsd', relative to 'file:/E:/DIPPW
F/XMLSchema/workflowSaveCreateProfile.xsd'.
Retrieving document at 'E:\DIPPWF\um_workflowSaveCreateProfile.wsdl'.
Retrieving document at 'um_workflowSaveCreateProfile_interface.wsdl', relative t
o 'file:/E:/DIPPWF/um_workflowSaveCreateProfile.wsdl'.
Retrieving schema at 'E:/DIPPWF/XMLSchema/common_parameters.xsd', relative to 'f
ile:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
Retrieving schema at 'E:/DIPPWF/XMLSchema/common_authentication.xsd', relative t
o 'file:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
Retrieving schema at 'E:/DIPPWF/XMLSchema/workflowSaveCreateProfile.xsd', relati
ve to 'file:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
Retrieving schema at 'navbar.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/workfl
owSaveCreateProfile.xsd'.
Retrieving schema at 'searchform.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/wo
rkflowSaveCreateProfile.xsd'.
Retrieving schema at 'component_basic.xsd', relative to 'file:/E:/DIPPWF/XMLSche
ma/workflowSaveCreateProfile.xsd'.
Retrieving schema at 'displaytype.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/c
omponent_basic.xsd'.
Retrieving schema at 'error.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/compone
nt_basic.xsd'.
Retrieving schema at 'component_workflowTicket.xsd', relative to 'file:/E:/DIPPW
F/XMLSchema/workflowSaveCreateProfile.xsd'.
*[ERROR] More than one part for message OblixIDXMLInput*
org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessingException:
More than one part for message OblixIDXMLInput
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.addQNameRefer
ence(WSDL11ToAxisServiceBuilder.java:1162)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.addQNameRefer
ence(WSDL11ToAxisServiceBuilder.java:1085)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateBindi
ng(WSDL11ToAxisServiceBuilder.java:686)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpo
int(WSDL11ToAxisServiceBuilder.java:538)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpo
ints(WSDL11ToAxisServiceBuilder.java:489)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateServi
ce(WSDL11ToAxisServiceBuilder.java:363)
at org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateA
llServices(WSDL11ToAllAxisServicesBuilder.java:107)
at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.<init>(CodeGenerat
ionEngine.java:147)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
Exception in thread "main" org.apache.axis2.wsdl.codegen.CodeGenerationException
: Error parsing WSDL
at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.<init>(CodeGenerat
ionEngine.java:153)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
Caused by: org.apache.axis2.AxisFault: More than one part for message OblixIDXML
Input
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateServi
ce(WSDL11ToAxisServiceBuilder.java:397)
at org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateA
llServices(WSDL11ToAllAxisServicesBuilder.java:107)
at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.<init>(CodeGenerat
ionEngine.java:147)
... 2 more
Caused by: org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessin
gException: More than one part for message OblixIDXMLInput
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.addQNameRefer
ence(WSDL11ToAxisServiceBuilder.java:1162)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.addQNameRefer
ence(WSDL11ToAxisServiceBuilder.java:1085)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateBindi
ng(WSDL11ToAxisServiceBuilder.java:686)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpo
int(WSDL11ToAxisServiceBuilder.java:538)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpo
ints(WSDL11ToAxisServiceBuilder.java:489)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateServi
ce(WSDL11ToAxisServiceBuilder.java:363).
Thanks in advance.
akshay

Hello,
Were you able to resolve this issue ?
I am seeing the same issue and at my wits end.
regards
Amit

JMS, Help needed in writing a client code with .bindings file

Some one is keeping a message in MQSeries in their environment. We need to develop a client code, probably a JMSClient, which will consume the messages from the MQSeries. They have given us a ".bindings" file. The following lines of code is used and we are not able to connect to it. Can somebody help us in completing this task?
env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.fscontext.RefFSContextFactory");
env.put(Context.PROVIDER_URL, "file:///c:/Temp");
String QCF = "CPS.ECOMM.QCF";
String TEST_QUEUE_S = "SYSTEM.JMS.D.CPSI.ECOMM";
initialContext = new InitialContext(env);
queueConnectionFactory = (QueueConnectionFactory)initialContext.lookup(QCF);
queueConnection = queueConnectionFactory.createQueueConnection();
queueConnection.start();
queueSession = queueConnection.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
queue = (Queue)initialContext.lookup(TEST_QUEUE_S);
QueueReceiver receiver = queueSession.createReceiver(queue);
Message msg = receiver.receive();
TextMessage txtMsg = (TextMessage)msg;
String result1 = txtMsg.getText();
....

The .bindings file is part of the structure expected by the RefFSContextFactory in the directory that provider.utl points to.
Create a directory containing only the .bindings file and point the PROVIDER_URL at the directory.

Where to find example code referenced in Java WebServices Tutorial, v1.5_01

Java WebServices Tutorial, v1.5_01 refenced a lot of code examples, which are supposed to be in <JWSDP_HOME>/docs/tutorial/examples.
I have downloaded and installed "Java Web Services Developer Pack v1.5" and "Java WebServices Tutorial, v1.5_01" from http://java.sun.com/webservices/downloads/webservicespack.html
But none of these downloads includes the code examples.
Thanks for any hitns.

Thanks.
But you were talking about a different set of examples referenced in a different document. You can get these examples when you install downloaded file:jwsdp-1_5-windows-i586.exe
The code examples I am looking for are referenced in:
"Java WebServices Tutorial, v1.5_01"
and this document can be downloaded at:
http://java.sun.com/webservices/downloads/webservicespack.html

Problem using VB Client with a JAVA Webservice

Hi people!
I'm using JDeveloper (9.0.3) to create a JAVA Webservice on OC4J container. I followed tutorial of Oracle and I got to execute my webservice, including I can invoke my methods by HTTP using HTML forms.
I need to invoke my methods using a VB Client with MIcrosoft SOAP ToolKit. My VB code is:
Function autenticar(login As String, senha As String)
Dim ObjWS As New MSSOAPLib30.SoapClient30
Dim retorno As Variant
Call ObjWS.MSSoapInit("http://10.71.200.40:8888/iSimp-Web-Root/br.gov.anp.isimp.controleVersao.ControleVersaoEJB?WSDL")
retorno = ObjWS.autentica(login, senha)
autenticar = retorno
End Function
My webservice publish a method called autentica that receives two parameters (a login and a password) and authenticates to obtain access to my system.
When I try to execute this function, I got this message error:
No deserializer found to deserialize a ":login" using encoding style "http://schemas.xmlsoap.org/soap/encoding/". [java.lang.illegalArgumentException]
Anyone knows what is this error?

If you could post what solved your problem that would be useful for others that run into the same issue. Thanks if possible!
Mike.

Problems using a VB Client to access a JAVA Webservice

Hi people!
I'm using JDeveloper (9.0.3) to create a JAVA Webservice on OC4J container. I followed tutorial of Oracle and I got to execute my webservice, including I can invoke my methods by HTTP using HTML forms.
I need to invoke my methods using a VB Client with MIcrosoft SOAP ToolKit. My VB code is:
Function autenticar(login As String, senha As String)
    Dim ObjWS As New MSSOAPLib30.SoapClient30
    Dim retorno As Variant
    Call ObjWS.MSSoapInit("http://10.71.200.40:8888/iSimp-Web-Root/br.gov.anp.isimp.controleVersao.ControleVersaoEJB?WSDL")
    retorno = ObjWS.autentica(login, senha)
    autenticar = retorno
End FunctionMy webservice publish a method called autentica that receives two parameters (a login and a password) and authenticates to obtain access to my system.
When I try to execute this function, I got this message error:
No deserializer found to deserialize a ":login" using encoding style "http://schemas.xmlsoap.org/soap/encoding/". [java.lang.illegalArgumentException]Anyone knows what is this error?

Thanks guys! I'm already solve my problem.

Java Web Services Developer Pack, where is jwsdp.home defined?

Hi.
I am trying out the Web Services Developer Pack, and so far so good, a really nice package of tools, tutorials and examples.
But there is one thing I do not understand regarding the Ant scripts for building the various examples.
In most of the scripts, the ${jwsdp.home} is used, but where is it defined? I have looked everywhere, and the only place where I have seen it defined, is in the server.xml file that is used by Tomcat. And it seems somewhat strange that Ant should be dependant on Tomcat on this particular issue, so surely that cannot be it.
It may seem like a unimportant question, but it is not, as I am purely beginning to use Ant, and need this information for when I'll begin writing my own scripts. Sure, I could just hardcode my app home path into the scripts, but that would be a ugly hack.
Thanks in advance
/Gabriel

In the path c:\jwsdp-1.1\conf of my installation, the file server.xml includes this code:
    
    <Environment
              name="jwsdp.home"
       description="Absolute Pathname of the JWSDP Installation"
              type="java.lang.String"
             value="C:\jwsdp-1.1"/>.. is that what are you looking for, is'n it?

Java Web Services Developer Pack 1.3 now available

All,
The Java Web Services Developer Pack 1.3 is now available for
download from http://java.sun.com/webservices. This release of JWSDP includes the fcs release of JAXRPC 1.1 and SAAJ 1.2 based on the WS-I basic profile 1.0 in addition to bug fixes /maintenance relases of the other components that have been in there in the previous releases. Feel free to download and send us comments at [email protected]
- Rajiv
:wq

I was pumped when I saw this post, then deflated when I read what was new...
No new JSF. I'm sooo ready for an update :-)
TTFN,
-bd-
http://bill.dudney.net/roller/page/bill

How to use Delphi Client in Java WEBSERVICE

I am building a Webservice Application. In client side I use Delphi to import WSDL from a Java Webservice Server ( literal WSDL ). By using WSDL Importer Control I successfully imported the WSDL file but when I called the impoted method the system returned an error :
"Project sendEmail.exe raise exception class ERemotableException with message ' Unable to find a matching Operation for this remote invocation <SOAP-ENV: send xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> </SOAP-ENV:send>.Please check your Operation Name.'
I think when i call send method in Client side the request is sent to Webservice Server but in server side ( build in Java ) that method doesn't match with the original method ( although the method in client side is imported from Webservice Server )
( When I use Delphi client to invoke methods from Delphi Webservice Server ( with rpc WSDL ) the result is OK and Java client also sucessfully invoke that method from Java Webservice )
Can you show me how i resolve this problem. Thanks

Hi Robin,
At some point, you can expect that the Web services frameworks will be implementing some of the plumbing related to WS-* for you. For example, you can rely on the framework to deal with WS-sec for you with the current Developer Preview of OC4J. For WS-Adressing specifically, you have to handle this in the application layer today, and there is very little the framework can do for you, other than converting the WS-Addressing SOAP header into some java object model for you. The business logic related to the use of the ws-addressing headers has to be implemented at the application level, with some handler. The same applies today for any JAX-RPC based Web services framework, including Axis. Now, if you are using some 'advance' framework like BPEL PM, they can do a lot of heavy lifting for you, under the cover.
Hope this helps,
Eric

Java Webservice Developer Pack client code generation

Similar Messages

Maybe you are looking for