Windows Communcation Foundation - JSR 172 Web Stub - interoperability

Hi! I am just playing with WCF -Windows Communication Foundation and JSR 172 Web Stub generation utility of WTK 2.5beta - is there a known problem with the import-expression i XML?
WCF generates:
?wsdl -> web service descrption that has import- references to
<?xml version="1.0" encoding="utf-8" ?>
- <wsdl:definitions name="EchoService" targetNamespace="http://tempuri.org/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://tempuri.org/" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:i0="http://schemas.microsoft.com/ws/2005/02/mex/bindings" xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:wsa10="http://www.w3.org/2005/08/addressing" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex">
<wsdl:import namespace="http://schemas.microsoft.com/ws/2005/02/mex/bindings" location="http://localhost:8080/echo?wsdl=wsdl0" />
- <wsdl:types>
- <xsd:schema targetNamespace="http://tempuri.org/Imports">
<xsd:import schemaLocation="http://localhost:8080/echo?xsd=xsd0" namespace="http://tempuri.org/" />
<xsd:import schemaLocation="http://localhost:8080/echo?xsd=xsd1" namespace="http://schemas.microsoft.com/2003/10/Serialization/" />
</xsd:schema>
</wsdl:types>
+ <wsdl:message name="IEchoService_Echo_InputMessage">
<wsdl:part name="parameters" element="tns:Echo" />
</wsdl:message>
- <wsdl:message name="IEchoService_Echo_OutputMessage">
<wsdl:part name="parameters" element="tns:EchoResponse" />
</wsdl:message>
- <wsdl:portType name="IEchoService">
- <wsdl:operation name="Echo">
<wsdl:input wsaw:Action="http://tempuri.org/IEchoService/Echo" message="tns:IEchoService_Echo_InputMessage" />
<wsdl:output wsaw:Action="http://tempuri.org/IEchoService/EchoResponse" message="tns:IEchoService_Echo_OutputMessage" />
</wsdl:operation>
</wsdl:portType>
- <wsdl:service name="EchoService">
- <wsdl:port name="MetadataExchangeHttpBinding_IEchoService" binding="i0:MetadataExchangeHttpBinding_IEchoService">
<soap12:address location="http://localhost:8080/echo" />
- <wsa10:EndpointReference>
<wsa10:Address>http://localhost:8080/echo</wsa10:Address>
</wsa10:EndpointReference>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>?wsdl=wsdl0
?xsd=xsd0
?xsd=xsd1Anyone experienced the same problem and knows a solution ?
Henning

I have gotten a step futher! The emulator had to be configured to run in the "secure" domain (as mentioned by some other people here), otherwise a http response "400 bad request (invalid header name)" was produced. J2ME web service is interoperable with WCF basichttpbinding (without debugging becuase it inserts unparseable soap-code into the http response)

Similar Messages

A JSR 172 (Web services) tutorial

Hi,
Some mobile phones already include JSR 172 api. There are some tools that already allow the automatic generation of stubs. I have written an article on how to access the API without the use of this tools, maybe somebody will find it useful
http://mobile.liveshere.net/articles/viewarticle.php?id=15

I have written a dot net/ c# Web Services doesn't fully work with J2ME client - it too throws the same exception, with the exception text being "Missing SOAP Body or Envelope"
a) c# web service works with c# WIndows Client (local & remote web service)
b) c# web service works with J2ME client - when the Web Service is local
c) c# web service FAILS with J2ME client - when the Web Service is remote
error/exception:
"Missing SOAP Body or Envelope" -- This occurs at the point of invoking the remote Web Service
Speculation:
a) dot net Web Services are "different" from Java Web services - yet it works fine in local mode
b) error is a misnomer & there is some other problem, perhaps fixable thru Web.config changes remotely??
- changed Web.Config authentication (from Windows to none), but this made no difference
- changed back to default web service namespace of tempuri.org, but this made no difference

[JSR-172 Web Services] Error with some web services

hello
I m trying to use jsr172 with multiple services find at Xmethods.com
- I choice only doc/litteral wsdl types ----> OK
- use of the J2ME Wireless Toolkit Stubs Generator ---> OK
- use the service stub generated to invoke the service -------> NOT OK
Some services runs correctly, but lots of service methods throw a java.rmi.MarshalException: Missing SOAP Body or Envelope
i.e: http://www.closerfar.com/dic2.asmx?WSDL
--> this has a method which return a definition of a word by a complex type
When I use the TryIt function in Xmethods.com, it's run!...
.... but not in my midlet
Can you help me
thanks
ludo

I have written a dot net/ c# Web Services doesn't fully work with J2ME client - it too throws the same exception, with the exception text being "Missing SOAP Body or Envelope"
a) c# web service works with c# WIndows Client (local & remote web service)
b) c# web service works with J2ME client - when the Web Service is local
c) c# web service FAILS with J2ME client - when the Web Service is remote
error/exception:
"Missing SOAP Body or Envelope" -- This occurs at the point of invoking the remote Web Service
Speculation:
a) dot net Web Services are "different" from Java Web services - yet it works fine in local mode
b) error is a misnomer & there is some other problem, perhaps fixable thru Web.config changes remotely??
- changed Web.Config authentication (from Windows to none), but this made no difference
- changed back to default web service namespace of tempuri.org, but this made no difference

"JSR 172 Web Service Timeout"

I have successfully used JSR172 and Sun's stub generator to access my web services and it works very nicely. The only hitch I see is that if for some reason ( not very likely but I'd like to handle it anyway ) the Blackberry client connects to the service by never receives a response, it appears to hang indefinitely.
Is there a way to set a time out, since it doesn't seem to fall through normal error trapping
I suppose I could kill the thread after a certain amount of time but that seems rude and would likely cause other problems
This is at the point where the JSR172 Invoke api is called.
thnx in advance...

Hi,
Check parameters *icm/server_port_<xx> *
In my CRM system, I have setup :
icm/server_port_0 = PROT=HTTP,PORT=80,TIMEOUT=90,PROCTIMEOUT=600
The PROCTIMEOUT is the one interesting for you.
I have set up it to 600 seconds to get the same timeout as with the sapgui.
Check also rdisp/plugin_auto_logout but it is more useful for the webui than for web services.
Regards,
Olivier

How to use Web Serivce for not jsr 172 phone

Hi:
Is anyone know, how to use web service for phones that only have standard J2ME package installed (without jsr 172 web service packagenstalled)?
thank you

Hi,
I think you need to write the code for this from scratch (built on top of existing HTTP functionality). There may be open-source J2ME code you could use. I've never tried this so I'm afraid I don't know any more. But maybe that is what you were asking... i.e. does anyone have code that does this already...
Tx,
Sam

2 Java ME Web Service Errors of "Not Compliant with JSR-172"

This happened when I use Microsoft's ASMX-based WSDL file on a Java ME WS client.
Say I had a test.asmx WSDL. Then I use NetBeans, and I go to New > Java ME Web Service Client
I tried to import from running web service, URL "http://www.testhost.com/wspackage/test.asmx?WSDL"
and then the popup validation error told me "Reference in element is not supported by this version of stub compiler"
also the X logo error told me "testasmx.wsdl is not compliant with Java ME Web Services specification (JSR-172)"
I wondered what's going on? Is there any data types not supported by JSR-172? Which is it?
When I "Validate XML" this ASMX file, it pops this:
"Error: src-resolve: Cannot resolve the name 's:schema' to a(n) 'element declaration' component."
The "types" section of my WSDL are like this:
<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://tempuri.org/MMWebServices/Coverage"
xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
targetNamespace="http://tempuri.org/MMWebServices/Coverage" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<wsdl:types>
<s:schema elementFormDefault="qualified" targetNamespace="http://tempuri.org/MMWebServices/Coverage">
<s:import namespace="http://www.w3.org/2001/XMLSchema" />
<s:element name="ViewListDoctor">
<s:complexType>
<s:sequence>
<s:element minOccurs="1" maxOccurs="1" name="iUserId" type="s:int" />
<s:element minOccurs="1" maxOccurs="1" name="iASchId" type="s:int" />
<s:element minOccurs="0" maxOccurs="1" name="sSearchKeyword" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="dsView">
<s:complexType>
<s:sequence>
<s:element ref="s:schema" /> // <<error occured on this line, and every time the ref="s:schema" shows up <<
Anyone have experienced this?

Yes, thx u. I didn't realized I was posting on the wrong section (Enterprise) so I posted again to the J2ME/MIDP section since it was all about mobility. Please delete the first post.

Developing JSR 172 compliant Web Service

Hi Experts,
I am trying to develop a web service in NWDI (Java), but it should be JSR 172 (J2ME) compliant. The web services developed with NWDI are not getting parsed and results in failure.
Could anyone please share some inputs on the same?
Regards, Kathirvel

Hi Sam,
I haven't worked with this before but I did some quick reading and it looks like you have your work cut out for you, you can't just use the WSDL as is for J2ME...Refer to the "Stub Generation and Invocation" section of the document below:
[http://developers.sun.com/mobility/midp/articles/webservices/?feed=DSC]
Regards, Trevor

How can I trust Firefox as a reliable web browser when you allow companys like Microsoft install plugins like Windows Presentation Foundation with out permissio

Microsoft had installed Windows Presentation Foundation without my permission and I smoking mad. This is bull crap I don't need. My web browser is personal to me and when companies stick their dirty little fingers in my computer without my permission it really PISS ME OFF. I don't kneed a web browser that allows this CRAP!!!!!

Hi,
The people who answer questions here, for the most part, are other Firefox users volunteering their time (like me), not Mozilla employees or Firefox developers.
If you want to leave feedback for Firefox developers, you can go to the Firefox ''Help'' menu and select ''Submit Feedback...'' or use [https://input.mozilla.org/feedback this link]. (You'll need to be on the latest version of Firefox to submit feedback). Your feedback gets collected at http://input.mozilla.org/, where a team of people read it and gather data about the most common issues.
Sorry!
Curtis

Web Services support-JSR-172 implementation

Are there specific devices which supports Web-Services or all the devices supports JSR-172 ?
Thanks in advance.
Krishan

simple google search will do.... http://www.j2mepolish.org/devices/devices-webservice.html

Using WebServices (JSR 172) on actual phones ?

hi,
I am trying to access web services with J2ME and JSR 172 on actual phone.
(For example a Nokia 7610 (Midp 2.0/CDLC1.0))
I use "J2ME Wireless Toolkit 2.2 Beta" it work's ok with the emulator.
But is it possible to insert the JSR172.jar (j2me-ws.jar) in the real phone or mix the used classes with my owned Midlet. ?
thanks,
Marc.

Hi,
Why not? Why shouldn't it work to inlcude in the program JAR the JSR172 classes for a device that has no support for JSR172?
I tried the following:
- Used WTK2.1 Stub generator to generate the client classes for a Web Service.
- Put these classes into the src of a WTK1.0.4 project.
- And put j2me-ws.jar into that project's lib.
And, running on WTK1.0.4 emulator, it works!
However, we are still talking about emulators...
After this emulator test, I loaded the project package on a SonyEricsson P900 device and tried to test the program. But, I am getting a SAXException on the device. I suppose it's having some problem while parsing the response.
Monitoring the server, I can see that the device is able to communicate with the server. It sends a request and the server sends a response back to the client. I am using Apacha Axis on the server side.
I also tried a implementation to access the same Web Service, but using KSoap2 instead of this JSR172 approach. It does not work as well.
I really have no idea of what could be wrong, since both versions of the Web Service client work fine while running in any emulator (I tried using both the Sun's and SonyEricsson's emulator, with MIDP1.0 and MIDP2.0).
Any help would be very appreciated.
Regards,
Anderson

JSR-172 J2ME Webservice

Hi,
I have search the Internet for reasons to why not support rpc/literal in JSR-172, but I haven't found any good explanations yet.
I have also read the entire JSR-172 specification, and the only thing mentioned about style and use are chapters 3.2.2 and 6.2:
3.2.2 Operation mode
"Implementations MUST generate stubs that use the document style and literal use (document/literal). See section 6.2, 'Operation Style attribute'.
Note - this does restrict the web services that can be interacted with but greatly simplifies implementation. SOAP 1.2 [9] is moving away from the SOAP encoding [SOAP 1.2 Part 2 Section 4.1]."
6.2 Operation Style attribute
"The style attribute (specified per soap:operation element or as a default in the soap:binding element) indicates whether an operation is rpc or document oriented. In the JAX-RPC Subset programming model, document style operations are mapped to the corresponding remote methods on a service endpoint interface. The rpc operation style is not supported.
A JAX-RPC subset client side implementation MUST support the use of services that
follow the JAX-RPC (refer to the beginning of this section) specified document
operation style requirements. Note that the WSDL 1.1 specification does not require
a wrapper element for the document style operations and assumes the use of
SOAPAction.
The JAX-RPC specification requires that the above requirements based on the
operation style should be hidden from the JAX-RPC programming model. A JAX-
RPC implementation should take the responsibility for the appropriate
representation of a SOAP message based on the operation style."
Questions:
1. What is negative about supporting rpc/literal in J2ME?
2. What would be the preferred strategy when you have an environment where you expose you internal business services by generating WSDL's from the Java interfaces and you have several methods in the same interface with same signature? As far as I can see, document/literal binding will have trouble deciding what remote method to call when there is nothing in the SOAP message indicating it.

I googled a little bit for RPC/literal vs Document/literal
Maybe it helps...
http://dev.eclipse.org/mhonarc/lists/alf-dev/msg00650.html
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/c018da90-0201-0010-ed85-d714ff7b7019
http://susanduncan.blogspot.com/2006/05/rpc-document-bare-wrapped-literal-get.html
http://www-128.ibm.com/developerworks/webservices/library/ws-whichwsdl/

JSR 172 marshal exception for complex type

Hi,
Im trying to run a JSR 172 webservice but i always get marshall exception for complex types, below is my code:
WSDL:
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://newsletter.kp/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://newsletter.kp/" name="NewsService">
    <ns1:Policy xmlns:ns1="http://www.w3.org/ns/ws-policy" wsu:Id="NewsPortBinding_getNewslettersRemote_WSAT_Policy">
        <ns1:ExactlyOne>
            <ns1:All>
                <ns2:ATAlwaysCapability xmlns:ns2="http://schemas.xmlsoap.org/ws/2004/10/wsat"></ns2:ATAlwaysCapability>
                <ns3:ATAssertion xmlns:ns4="http://schemas.xmlsoap.org/ws/2002/12/policy" xmlns:ns3="http://schemas.xmlsoap.org/ws/2004/10/wsat" ns1:Optional="true" ns4:Optional="true"></ns3:ATAssertion>
            </ns1:All>
        </ns1:ExactlyOne>
    </ns1:Policy>
    <types>
        <xsd:schema>
            <xsd:import namespace="http://newsletter.kp/" schemaLocation="http://localhost:8080/NewsService/News?xsd=1"></xsd:import>
        </xsd:schema>
    </types>
    <message name="getNewslettersRemote">
        <part name="parameters" element="tns:getNewslettersRemote"></part>
    </message>
    <message name="getNewslettersRemoteResponse">
        <part name="parameters" element="tns:getNewslettersRemoteResponse"></part>
    </message>
    <portType name="News">
        <operation name="getNewslettersRemote">
            <ns5:PolicyReference xmlns:ns5="http://www.w3.org/ns/ws-policy" URI="#NewsPortBinding_getNewslettersRemote_WSAT_Policy"></ns5:PolicyReference>
            <input message="tns:getNewslettersRemote"></input>
            <output message="tns:getNewslettersRemoteResponse"></output>
        </operation>
    </portType>
    <binding name="NewsPortBinding" type="tns:News">
        <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"></soap:binding>
        <operation name="getNewslettersRemote">
            <ns6:PolicyReference xmlns:ns6="http://www.w3.org/ns/ws-policy" URI="#NewsPortBinding_getNewslettersRemote_WSAT_Policy"></ns6:PolicyReference>
            <soap:operation soapAction="getNews"></soap:operation>
            <input>
                <soap:body use="literal"></soap:body>
            </input>
            <output>
                <soap:body use="literal"></soap:body>
            </output>
        </operation>
    </binding>
    <service name="NewsService">
        <port name="NewsPort" binding="tns:NewsPortBinding">
            <soap:address location="http://localhost:8080/NewsService/News"></soap:address>
        </port>
    </service>
</definitions>Stub:
public class NewsService_Stub implements NewsService, javax.xml.rpc.Stub {
    private String[] _propertyNames;
    private Object[] _propertyValues;
    public NewsService_Stub() {
        _propertyNames = new String[] { ENDPOINT_ADDRESS_PROPERTY };
        _propertyValues = new Object[] { "http://localhost:8080/NewsService/News" };
    public void _setProperty( String name, Object value ) {
        int size = _propertyNames.length;
        for (int i = 0; i < size; ++i) {
            if( _propertyNames.equals( name )) {
_propertyValues[i] = value;
return;
String[] newPropNames = new String[size + 1];
System.arraycopy(_propertyNames, 0, newPropNames, 0, size);
_propertyNames = newPropNames;
Object[] newPropValues = new Object[size + 1];
System.arraycopy(_propertyValues, 0, newPropValues, 0, size);
_propertyValues = newPropValues;
_propertyNames[size] = name;
_propertyValues[size] = value;
public Object _getProperty(String name) {
for (int i = 0; i < _propertyNames.length; ++i) {
if (_propertyNames[i].equals(name)) {
return _propertyValues[i];
if (ENDPOINT_ADDRESS_PROPERTY.equals(name) || USERNAME_PROPERTY.equals(name) || PASSWORD_PROPERTY.equals(name)) {
return null;
if (SESSION_MAINTAIN_PROPERTY.equals(name)) {
return new Boolean(false);
throw new JAXRPCException("Stub does not recognize property: " + name);
protected void _prepOperation(Operation op) {
for (int i = 0; i < _propertyNames.length; ++i) {
op.setProperty(_propertyNames[i], _propertyValues[i].toString());
public newsletter[] getNewslettersRemote() throws java.rmi.RemoteException {
Object inputObject[] = new Object[] {
Operation op = Operation.newInstance( qnameoperation_getNewslettersRemote, typegetNewslettersRemote, typegetNewslettersRemoteResponse );
_prepOperation( op );
op.setProperty( Operation.SOAPACTION_URI_PROPERTY, "getNews" );
Object resultObj;
try {
resultObj = op.invoke( inputObject );
} catch( JAXRPCException e ) {
Throwable cause = e.getLinkedCause();
if( cause instanceof java.rmi.RemoteException ) {
throw (java.rmi.RemoteException) cause;
throw e;
return newsletter_ArrayfromObject((Object[])((Object[]) resultObj)[0]);
private static newsletter[] newsletter_ArrayfromObject( Object obj[] ) {
if(obj == null) return null;
newsletter result[] = new newsletter[obj.length];
for( int i = 0; i < obj.length; i++ ) {
result[i] = new newsletter();
Object[] oo = (Object[]) obj[i];
result[i].setBody((String )oo[0]);
result[i].setId((Long )oo[1]);
result[i].setImageLocation((String )oo[2]);
result[i].setTitle((String )oo[3]);
return result;
protected static final QName qnameoperation_getNewslettersRemote = new QName( "http://newsletter.kp/", "getNewslettersRemote" );
protected static final QName qnamegetNewslettersRemote = new QName( "http://newsletter.kp/", "getNewslettersRemote" );
protected static final QName qnamegetNewslettersRemoteResponse = new QName( "http://newsletter.kp/", "getNewslettersRemoteResponse" );
protected static final Element typegetNewslettersRemote;
protected static final Element typegetNewslettersRemoteResponse;
static {
typegetNewslettersRemote = new Element( qnamegetNewslettersRemote, _complexType( new Element[] {
}), 1, 1, false );
typegetNewslettersRemoteResponse = new Element( qnamegetNewslettersRemoteResponse, _complexType( new Element[] {
new Element( new QName( "", "return" ), _complexType( new Element[] {
new Element( new QName( "", "body" ), Type.STRING, 0, 1, false ),
new Element( new QName( "", "id" ), Type.LONG, 0, 1, false ),
new Element( new QName( "", "imageLocation" ), Type.STRING, 0, 1, false ),
new Element( new QName( "", "title" ), Type.STRING, 0, 1, false )}), 0, Element.UNBOUNDED, true )}), 1, 1, false );
private static ComplexType _complexType( Element[] elements ) {
ComplexType result = new ComplexType();
result.elements = elements;
return result;
}I tested the web service with the following xml
input:<?xml version="1.0" encoding="UTF-8"?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Header/>
<S:Body>
<ns2:getNewslettersRemote xmlns:ns2="http://newsletter.kp/"/>
</S:Body>
</S:Envelope>
output:bq. <?xml version="1.0" encoding="UTF-8"?> \\ <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> \\ <S:Body> \\ <ns2:getNewslettersRemoteResponse xmlns:ns2="http://newsletter.kp/"> \\ <return> \\ <body>teste</body> \\ <id>1</id> \\ <imageLocation>testes</imageLocation> \\ <title>teste</title> \\ </return> \\ <return> \\ <body>mau</body> \\ <id>2</id> \\ <imageLocation>mau</imageLocation> \\ <title>mau</title> \\ </return> \\ <return> \\ <body>mau</body> \\ <id>3</id> \\ <imageLocation>mau</imageLocation> \\ <title>mau</title> \\ </return> \\ <return> \\ <body>mau</body> \\ <id>4</id> \\ <imageLocation>mau</imageLocation> \\ <title>teste</title> \\ </return> \\ <return> \\ <body>2</body> \\ <id>5</id> \\ <imageLocation>2</imageLocation> \\ <title>2</title> \\ </return> \\ <return> \\ <body>corpo</body> \\ <id>6</id> \\ <imageLocation>imagem</imageLocation> \\ <title>Titulo</title> \\ </return> \\ <return> \\ <body>corpos</body> \\ <id>7</id> \\ <imageLocation>imagem</imageLocation> \\ <title>Titulo</title> \\ </return> \\ <return> \\ <body>teste</body> \\ <id>8</id> \\ <imageLocation>teste</imageLocation> \\ <title>teste</title> \\ </return> \\ <return> \\ <body>rweqrrq</body> \\ <id>9</id> \\ <imageLocation>rwe</imageLocation> \\ <title>rewq</title> \\ </return> \\ </ns2:getNewslettersRemoteResponse> \\ </S:Body> \\ </S:Envelope> \\ but i always get a:
java.rmi.MarshalException: Invalid URI From Server: , expected: http://schemas.xmlsoap.org/soap/envelope/
        at news.NewsService_Stub.getNewslettersRemote(NewsService_Stub.java:73)
        at hello.HelloMIDlet.getTextField(HelloMIDlet.java:168)
        at hello.HelloMIDlet.getForm(HelloMIDlet.java:132)
        at hello.HelloMIDlet.startMIDlet(HelloMIDlet.java:56)
        at hello.HelloMIDlet.startApp(HelloMIDlet.java:205)
        at javax.microedition.midlet.MIDletProxy.startApp(MIDletProxy.java:43)
        at com.sun.midp.midlet.Scheduler.schedule(Scheduler.java:374)
        at com.sun.midp.main.Main.runLocalClass(Main.java:466)
        at com.sun.midp.main.Main.main(Main.java:120)
Can you please help me find the problem?
Thanks in advance.

Hello,
A bit late, but I'm sure others will use this answers. We encountered the same problem in our development and after some hours playing with our WSDL we found the source of the problem.
The problem is having a field named "body" in the Object this apparently doesn't work well with SOAP we guess because of the Envelope having also a Body.
So the solution is changing the field body to something like msgBody.
Regards,
Raanan Nevet

Windows Communication Foundation .svc versus .asmx

.NET 3.5 and above allow programmer to create Windows Communication Foundation that has the .svc file. I can use this WCF like a Web services on .Net C# and VB.NET without issues. I can also access what has been created on the browser (http://server1/DemoWebServices/Demo.svc?wsdl).
However, when I go to LabView 8.6.1, it can only allowed import of asmx?wsdl Web services.
Does that mean labview does not play with .svc?wsdl ?
If not supported, would other Labview version allowed that support.

Unfortunately, at this point it appears only asmx?wsdl Web Services are supported. If you can convert between formats, that may be your best solution.
Regards,
Mike S
NI AE

Netbeans 4.1: JSR-109 web services are only supported in j2ee 1.4 apps

There is no way to create web services in NetBeans 4.1 with Tiger (jdk 1.5).
Because when you try to create a web service in NB4.1, you will straight away get an message in the New Web Service window:
JSR-109 web services are only supported in j2ee 1.4 applications.

JSR-109 web services are only supported in j2ee 1.4
applications.Do you have J2EE 1.4 SDK installed?

Unable to consume a simple SAPWebService error "not JSR 172 Compliant"

Hi,
Am trying to consume a simple webservice which was created by exposing a function module. The consumer of this WS is a J2ME application.
Usually we the framework(or IDE or other tools) will help us in creating the stubs(proxy classes) when provided the WS wsdl URL .I tried in C#.dotnet and i was able to create the stubs and consume it. Now when i try it J2ME ->NetBeans IDE-> STub generator->same wsdl url, i get an error "not JSR 172 compliant". FYI, JSR 172 is the spec for WS consumption by a Java 2 MicroEdition(J2ME) applications[http://jcp.org/en/jsr/detail?id=172].
My question: How can i make or what are the other settings that i have to do in SOAManager to make this JSR 172 compliant.
FYI, i just created a helloworld function module in ABAP and created a enter. service. In soamanager i have not done anyother setting other the default settings the comes.
Any inputs on this would be really helpful.
Thanks,
Sam.

Hi Sam,
I haven't worked with this before but I did some quick reading and it looks like you have your work cut out for you, you can't just use the WSDL as is for J2ME...Refer to the "Stub Generation and Invocation" section of the document below:
[http://developers.sun.com/mobility/midp/articles/webservices/?feed=DSC]
Regards, Trevor

Windows Communcation Foundation - JSR 172 Web Stub - interoperability

Similar Messages

Maybe you are looking for