GetBytes() - Encoding Style problem

Hi people,
I need to encrypt a password using SHA algorithm through the MessageDigest object. Initially, I need obtain the bytes of the password String in order to pass it to the update() method of the mentioned object.
The problem is that the getBytes() method return different values on different platforms. I am using Windows and Sun Solaris OSs. I also noticed that even on the same OS, changing the jdk version will return in different result for the same String.
Could you please help me with this issue because it is getting very frustrating.
Regards George

The code is very simple.
System.out.println("TEST".getBytes("UTF-8"));
I am using jvm 1.5.0_04 both on Windows and Unix. On Windows, the above statement is returning [B@6b97fd while on Unix it is returning [B@e48e1b.
I don't know what's wrong with this. Maybe I have a misconception of some principles.
Thanks for your support
Regards
George

Similar Messages

Re: SOAP Fault: unexpected encoding style

Hi Oliver,
Have you tried using the Test XML tab in the test harness to test the
external web service. By using that, you can check the SOAP request sent to
the service.
Could you please send us the WSDL file and a sample SOAP request sent to the
external web service. Will it be possible for us to connect to the service
from here?
I look forward to your response.
Regards,
Anurag
Workshop Support
"Oliver Strassberger" <[email protected]> wrote in
message news:3d7e0abf$[email protected]..
>
Hello,
I added a service control in my project from the wsdl file of a webservice. If
try to invoke this external web service, I get a soap response with thefollowing
fault message:
Internal Server Error (unexpected encoding style:expected=http://schemas.xmlsoap.org/soap/encoding/,
actual=)
But the soap header of the request contains the following lines:
<SOAP-ENV:Envelopexmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
The external service runs in Tomcat 4 Servlet Container from SunMicrosystems
WSDP.
What could be wrong? Is it possible to edit the request header withWorkshop?

I'm having the same problem and was wondering if/how it was resolved. I'm using
BEA 8.1 and Apache tomcat 4.1
"Oliver Strassberger" <[email protected]> wrote:
>
>
>
Hello,
the "external" Web Service also runs on my local machine, but on a apache
tomcat
server. It is not possible for you to connect to it.
I have attached a .zip file, containing the SOAP request/response message
from
two tests and the wsdl of the externel web service.
First, I invoked the externel service from a client running with apache
axis -
it works.
Then I tried to invoke the same service from Weblogic Workshop, without
success.
With best regards,
Oliver

SOAP Fault: unexpected encoding style

Hello,
I added a service control in my project from the wsdl file of a web service. If
try to invoke this external web service, I get a soap response with the following
fault message:
Internal Server Error (unexpected encoding style: expected=http://schemas.xmlsoap.org/soap/encoding/,
actual=)
But the soap header of the request contains the following lines:
<SOAP-ENV:Envelope xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
The external service runs in Tomcat 4 Servlet Container from Sun Microsystems
WSDP.
What could be wrong? Is it possible to edit the request header with Workshop?

I'm having the same problem and was wondering if/how it was resolved. I'm using
BEA 8.1 and Apache tomcat 4.1
"Oliver Strassberger" <[email protected]> wrote:
>
>
>
Hello,
the "external" Web Service also runs on my local machine, but on a apache
tomcat
server. It is not possible for you to connect to it.
I have attached a .zip file, containing the SOAP request/response message
from
two tests and the wsdl of the externel web service.
First, I invoked the externel service from a client running with apache
axis -
it works.
Then I tried to invoke the same service from Weblogic Workshop, without
success.
With best regards,
Oliver

How to handle rpc/encoded style messages using BizTalk?

I am integrating with a lot of services and one of our customers has a service with rpc/encoded style
I could consume and generate schema from their wsdl file via BizTalk consume WCF wizard.
Once I am trying to call the service with request message that generated from the schema, it is giving an error that can not desterilize the first element of the message.
No Deserializer found to deserialize a 'FieldName' using encoding style 'null'
I compared the stub xml request message from SaopUI and I noticed that the xml expecting the data type with the element like this .
<soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsb="WSBanka">
<soapenv:Header/>
<soapenv:Body>
<wsb:bnkBorcsorgulama soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<sozlesmeNo xsi:type="xsd:string">?</sozlesmeNo>
<bankaKodu xsi:type="xsd:string">?</bankaKodu>
<anahtar xsi:type="xsd:string">?</anahtar>
</wsb:bnkBorcsorgulama>
</soapenv:Body>
</soapenv:Envelope>
On the other hand, I got the request of the message from Fiddler using the BizTalk , and the generate xml of the BizTalk schema without the data type.
<soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsb="WSBanka">
<soapenv:Header/>
<soapenv:Body>
<wsb:bnkBorcsorgulama>
<sozlesmeNo>?</sozlesmeNo>
<bankaKodu>?</bankaKodu>
<anahtar>?</anahtar>
</wsb:bnkBorcsorgulama>
</soapenv:Body>
</soapenv:Envelope>
In SoapUi, if I remove a datatype from the message, I will get same error from the BizTalk request.
I read some articles that rpc/encoded style are not supported but I am not sure and these articles are not clear.
I also read that it was supported with Soap adapter but now it is deprecated.
So, Is there any one has an experience in rpc/encoded style messages and how to handle these message in BizTalk or is there any work around to handle these messages?
Your inputs really appreciate it.
Thanks in advance,
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer

Hi,
Please refer to the document which might help you:
#RPC/Encoded Style
http://www.c-sharpcorner.com/UploadFile/martinkropp/DesigningInteroperableWebService11232005044847AM/DesigningInteroperableWebService.aspx

Web Service Client encoding style error

Hi all,
I have a created a java static stub client (created with wscompile from the wsdp). If I run the client I receive the following error
"unexpected encoding style: expected=http://schemas.xmlsoap.org/soap/encoding/..."
I am using a delphi web service server, the encoding style is set to "http://schemas.xmlsoap.org/soap/encoding/"
My server simply echos a string with the method name "echoString"
Where do I go from here?
Does the xmlns tag in the "config-wsdl.xml" have anything to do with it?
Complete error :
java.rmi.RemoteException: Runtime exception; nested exception is:
unexpected encoding style: expected=http://schemas.xmlsoap.org/soap/encoding/, actual=
at com.sun.xml.rpc.client.StreamingSender._handleRuntimeExceptionInSend(StreamingSender.java:248)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:230)
at staticstub.IMyEmailWebService_Stub.echoString(IMyEmailWebService_Stub.java:68)
at DelphiClass.main(DelphiClass.java:25)
Caused by: unexpected encoding style: expected=http://schemas.xmlsoap.org/soap/encoding/, actual=
at com.sun.xml.rpc.encoding.SOAPDeserializationContext.verifyEncodingStyle(SOAPDeserializationContext.java:159)
at com.sun.xml.rpc.encoding.ObjectSerializerBase.deserialize(ObjectSerializerBase.java:150)
at com.sun.xml.rpc.encoding.ReferenceableSerializerImpl.deserialize(ReferenceableSerializerImpl.java:134)
at staticstub.IMyEmailWebService_Stub._deserialize_echoString(IMyEmailWebService_Stub.java:173)
at staticstub.IMyEmailWebService_Stub._readFirstBodyElement(IMyEmailWebService_Stub.java:157)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:158)
Thank you in advance
Garth

Looks like the server is not using the correct encoding. I suggest using a packet sniffer so you can actually see the SOAP message to verify that. Apache Axis has a tcpmon utility that works very nicely.

Unexpected encoding style

Hi all. I'm new to Oracle and Web Services in general, so do pardon me in advance.
I followed the example here: http://www.oracle.com/technology/obe/obe1013jdev/ws/wsandascontrol.htm and deployed the web service to the external OC4J server.
Subsequently, I tried calling the web service using the OmniPortlet in OracleAS but it gives this error:
Call to Web Service Failed. [env:Client : caught exception while handling request: unexpected encoding style: expected=, actual=http://xml.apache.org/xml-soap/literalxml]
Any help is appreciated.

Jose,
When you work with Web Services, the common development flow is as follow:
1) develop your service endpoint. You can start from JAVA code or PL/SQL package (bottom-up) or from a WSDL (top-down). In your case, you need to start from the Store Procedures.
2) deploy your service endpoint. As the result of the deployment step, you will have a WSDL available on your application server, that advertise the service interface.
3) generate the static client proxy from the WSDL (service contract).
4) invoke the service using the proxy from step 3 or use dynamic invocation APIs to make direct call, without to use a static proxy.
Bypassing step 3) usually requires a dipper understanding of SOAP linguana, so it's not the easiest way to get started.
Based on the statement you made, it looks like you are starting from step 3)
From the error message, it seams that you are trying to invoke a Web service that was deployed using 'literal' encoding (either document/literal or RPC/literal) with a client generated for RPC-encoded message format. In the JDeveloper Wizard, you have an option to change the message format to RPC/Encoded.
Hope this helps,
eric

DII unexpected encoding style with SharePoint Web Service

I am trying to call a dynamic sharepoint web service in Java using DII (Dynamic Invocation Interface)
but I kept getting error:unexpected encoding style: after the invoke expected=http://schemas.xmlsoap.org/soap/encoding/, actual=
I am trying to call web service - GetWebCollection()
String endPoint="http://%SPSERVER/_vti_bin/Webs.asmx";
String nameSpaceUri = "xmlns:xsi";
String serviceName = "Webs";
String porttype="WebsSoap";
String NS_XSD = "http://www.w3.org/2001/XMLSchema";
ServiceFactory factory =
ServiceFactory.newInstance();
Service service =factory.createService(new QName(serviceName));
QName qport = new QName(porttype);
hpsharepoint.Webs webs = new hpsharepoint.Webs_Impl();
Call call = (Call) webs.createCall(qport);
call.setProperty(call.USERNAME_PROPERTY,kuser);
call.setProperty(call.PASSWORD_PROPERTY,password);
call.setProperty(Call.ENCODINGSTYLE_URI_PROPERTY, "http://schemas.xmlsoap.org/soap/encoding/");
call.setProperty(Call.SOAPACTION_USE_PROPERTY,
new Boolean(true));
call.setProperty(Call.SOAPACTION_URI_PROPERTY,"http://schemas.microsoft.com/sharepoint/soap/GetWebCollection");
call.setTargetEndpointAddress(endPoint);
call.setOperationName(
new QName(nameSpaceUri,"GetWebCollection"));
String[] params = {};
NodeList list=(NodeList)call.invoke(params);
==========================
This is the soap 1.1
==========================
POST /_vti_bin/Webs.asmx HTTP/1.1 Host: <server> Content-Type: text/xml; charset=utf-8 Content-Length: length SOAPAction: "http://schemas.microsoft.com/sharepoint/soap/GetWebCollection" <?xml version="1.0" encoding="utf-8"?> <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <GetWebCollection xmlns="http://schemas.microsoft.com/sharepoint/soap/" /> </soap:Body> </soap:Envelope>

Jose,
When you work with Web Services, the common development flow is as follow:
1) develop your service endpoint. You can start from JAVA code or PL/SQL package (bottom-up) or from a WSDL (top-down). In your case, you need to start from the Store Procedures.
2) deploy your service endpoint. As the result of the deployment step, you will have a WSDL available on your application server, that advertise the service interface.
3) generate the static client proxy from the WSDL (service contract).
4) invoke the service using the proxy from step 3 or use dynamic invocation APIs to make direct call, without to use a static proxy.
Bypassing step 3) usually requires a dipper understanding of SOAP linguana, so it's not the easiest way to get started.
Based on the statement you made, it looks like you are starting from step 3)
From the error message, it seams that you are trying to invoke a Web service that was deployed using 'literal' encoding (either document/literal or RPC/literal) with a client generated for RPC-encoded message format. In the JDeveloper Wizard, you have an option to change the message format to RPC/Encoded.
Hope this helps,
eric

RPC/encoded style

Hi Experts,
I have read it in some forum thread stating that, we can't use RPC/encoded style in XI. Even if we get RPC style wsdl files from other platforms we have to first convert it into Document style to access XI.
Question:
When we create wsdl thro' XI also, it automatically creates with document style. Do we have any option to create a wsdl file with RPC style? If it is not possible with XI then, is there any other way to create RPC style wsdl file for the XI service.
Regards
Sara

Yes its possible,
Please check following :-
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c018da90-0201-0010-ed85-d714ff7b7019
RPC WSDL in XI
Vishal
Reward points for useful Help

No Serializer found to serialize a 'org.w3c.dom.Element' using encoding style ...

I use oc4j903 and win2k. I write a document style web service following Demo for Stateless Java Document Web Services.
I Create an EAR file using WebServicesAssembler and deploy it .and my config.xml:
<web-service>
<display-name>Stateful Java Document milkdemo Web Service</display-name>
<description>Stateful Java Document milkdemo Web Service Example</description>

<destination-path>./milkdemo.ear</destination-path>

<temporary-directory>./temp</temporary-directory>

<context>/milkdemo</context>

<stateful-java-service>
<interface-name>com.brightdairy.client.sync.SyncServerDoc</interface-name>
<class-name>com.brightdairy.client.sync.SyncServerDocImpl</class-name>

<uri>/milkdemo</uri>

<java-resource>./classes</java-resource>

<message-style>doc</message-style>
</stateful-java-service>

<wsdl-gen>
     <wsdl-dir>wsdl</wsdl-dir>

     <option name="force">true</option>
     <option name="httpServerURL">http://localhost:8888</option>
</wsdl-gen>

<proxy-gen>
     <proxy-dir>proxy</proxy-dir>
     <option name="include-source">true</option>
</proxy-gen>
</web-service>
my webservice java file:
* Title: BrightDairy SOAP demo
* Description:
* Copyright: Copyright (c) 2002
* Company: ufoasia
* @author
* @version 1.0
package com.brightdairy.client.sync;
import java.sql.*;
import java.util.Vector;
import java.util.Iterator;
import org.w3c.dom.Element;
import org.w3c.dom.Document;
import org.w3c.dom.NodeList;
import oracle.xml.parser.v2.XMLDocument;
import oracle.xml.parser.v2.XMLElement;
//import com.brightdairy.client.object.Product;
import com.brightdairy.client.sync.SyncServerDoc;
public class SyncServerDocImpl implements SyncServerDoc {
public SyncServerDocImpl() {
public Element getProductIDList() {
Connection connServer = null;
PreparedStatement stmtServerProduct = null;
ResultSet rsServerProduct = null;
Document doc = new XMLDocument();
Element elProduct = doc.createElement("product");
doc.appendChild(elProduct);
long m_msec;
m_msec = System.currentTimeMillis();
try {
connServer = makeConnection();
System.out.println("1");
stmtServerProduct = connServer.prepareStatement(
"SELECT ID FROM " + SERVER_TABLE_PRODUCT );
System.out.println("");
rsServerProduct = stmtServerProduct.executeQuery();
System.out.println("2");
while(rsServerProduct.next()) {
Element elID = doc.createElement("id");
elID.appendChild(doc.createTextNode(rsServerProduct.getString("ID")));
elProduct.appendChild(elID);
System.out.println("3");;
System.out.println("4");
return doc.getDocumentElement();
} catch(SQLException e) {
e.printStackTrace();
System.out.println("SQL exception has occured");
System.out.println(e.getMessage());
return doc.getDocumentElement();
}finally {
try {
rsServerProduct.close();
stmtServerProduct.close();
connServer.close();
m_msec = System.currentTimeMillis() - m_msec;
System.out.println("6");
System.out.println("getProductIDList:It take time:" m_msec/1000 "s");
} catch(Exception e1) {}
Now my firts question: when i generate the proxy WebServicesAssembler will failure (couldn't import jar.....) and i had imported all jar files,But if i commented proxy-gen , no error.
and my second question: I commented proxy-gen and deployed ite and success. when i invoked it through web page , then error:
java.lang.IllegalArgumentException: No Serializer found to serialize a 'org.w3c.
dom.Element' using encoding style 'http://schemas.xmlsoap.org/soap/encoding/'.
at org.apache.soap.util.xml.XMLJavaMappingRegistry.querySerializer(XMLJa
vaMappingRegistry.java:157)
at org.apache.soap.encoding.soapenc.ParameterSerializer.marshall(Paramet
erSerializer.java:106)
at org.apache.soap.rpc.RPCMessage.marshall(RPCMessage.java:265)
at org.apache.soap.Body.marshall(Body.java:148)
at org.apache.soap.Envelope.marshall(Envelope.java:203)
at org.apache.soap.Envelope.marshall(Envelope.java:161)
at oracle.j2ee.ws.InvocationWrapper.invoke(InvocationWrapper.java:309)
at oracle.j2ee.ws.RpcWebService.doGetRequest(RpcWebService.java:540)
at oracle.j2ee.ws.BaseWebService.doGet(BaseWebService.java:1106)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletReque
stDispatcher.java:721)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(Ser
vletRequestDispatcher.java:306)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpReques
tHandler.java:767)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.ja
va:259)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.ja
va:106)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExec
utor.java:803)
at java.lang.Thread.run(Thread.java:484)
I took much time and couln't get answer ,please help me!!!!!!!!!!!!

Yeah!
I have resolved it .
It take me one day time!
my error is 1: Element which I used is no namespace.
2: no import enough jar files
just so so .
sorry! I am poor in English

RPC/encoded style webservice

Hi Experts,
How to expose RPC/encoded style webservices from XI? As far as I know, we can expose Document literal style webservice from PI7.0.
Could you please tell me, for this question where I can get the exact answer?
Regards
Sara

Hi,
please go through below links
Using XML-RPC in NetWeaver
/people/sap.user72/blog/2004/09/23/using-xml-rpc-in-netweaver
External Data Loads for CRM 4.0 using XIF adapter
/people/stephen.johannes/blog/2005/08/18/external-data-loads-for-crm-40-using-xif-adapter
XML-RPC protocol and XIF Adapter
XML-RPC protocol and XIF Adapter
Thanks
Swarup

SOAP Encoding styles

Hi Experts,
Other than Document/Literal, PI7.0 supports any other SOAP Encoding styles?
Need document proof please.
Regards
Sara

Hi,
Pls refer the following encoding styles.
http://www.sapag.co.in/SAP-XI-SOAP-Adapter-FAQ'S.html

(261229964) Q MSGC-7 Can you give an example of chosing different encoding styles?

Q <MSGC-7> Can you give an example of chosing different encoding styles?
A <MSGC-7> I will refer you to the online documentation for the encoding information
at:
http://e-docs.bea.com/wls/docs61/webServices/develop.html#1036286
And the JavaDocs for the weblogic.soap.codec.CodecFactory class which describes the
register method you must use to identify which encoding style you want:
http://edocs.bea.com/wls/docs61/javadocs/weblogic/soap/codec/SoapEncodingCodec.html

What is that post supposed to be?

Weblogic 7.0 and encoding styles

All,
Does anyone of you know if Weblogic 7.0 supports following two encoding
styles?
http://schemas.xmlsoap.org/soap/encoding/
http://xml.apache.org/xml-soap/literalxml
In the WLS 6.1 documentation, I see that the above two encoding styles
are
supported but not in 7.0!
Your input to this...is greatly appretiated.
Thanks,
Sanjay

Hi Sanjay,
WLS 7.0 only supports the SOAP encoding described in section 5 of the SOAP 1.1
spec. This is represented by the "http://schemas.xmlsoap.org/soap/encoding/" namespace.
"Literal encoding" is actually an oxymoron, because why would you want to "encode
something" that was intended to be "interpreted literally" :-)
When you want to use "literalxml" with WLS 7.0, just add a style="document" attribute
to the <service> element of the <servicegen> Ant task.
Regards,
Mike Wooten
Sanjay Ungarala <[email protected]> wrote:
All,
Does anyone of you know if Weblogic 7.0 supports following two encoding
styles?
http://schemas.xmlsoap.org/soap/encoding/
http://xml.apache.org/xml-soap/literalxml
In the WLS 6.1 documentation, I see that the above two encoding styles
are
supported but not in 7.0!
Your input to this...is greatly appretiated.
Thanks,
Sanjay

Document style Problem

We have three issues when trying to implement a document-style service. I will
document them all but I'd suggest you go through them all before attempting to
answer any of them.
We are trying to implement a service that has the following signature:
public void echoDom(Document doc)
We want the delivery of our message to be of style ("document"). Therefore, we
modified our servicegen entry to include the style="document" under the service.
It looks like the following:
<servicegen
destEar="${appDir}/dom.ear"
warName="dom.war">
<service
javaClassComponents="examples.dom.EchoDom"
targetNamespace="http://examples.org"
serviceName="dom"
serviceURI="/EchoDomService"
generateTypes="True"
expandMethods="True"
style="document">
<client
packageName="examples.dom"
clientJarName="client.jar"
/>
</service>
<classpath>
<pathelement path="${temp_dir}"/>
<pathelement path="${java.class.path}"/>
</classpath>
</servicegen>
1. FIRST PROBLEM:
The first problem we're having is that it does not compile with the combination
of our signature being of type void (as shown above) and the style="document"
in build.xml.
The error is the following:
[servicegen] Generating service "dom" ...
[servicegen] Generating XML types and serializers from java classes (examples.do
m.EchoDom) ...
[servicegen] weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ void:
null ]
[servicegen] at weblogic.utils.Debug.assertion(Debug.java:84)
[servicegen] at weblogic.xml.schema.binding.internal.codegen.Compiler.compile
(Compiler.java:111)
[servicegen] at weblogic.xml.schema.binding.internal.XSDTypeMappingBuilder.ma
pClass(XSDTypeMappingBuilder.java:88)
[servicegen] at weblogic.xml.schema.binding.internal.TypeMappingBuilderBase.a
ddMapping(TypeMappingBuilderBase.java:183)
[servicegen] at weblogic.ant.taskdefs.webservices.autotype.ComponentAutoTyper
.mapComponent(ComponentAutoTyper.java:155)
[servicegen] at weblogic.ant.taskdefs.webservices.autotype.JavaAutoTyper.run(
JavaAutoTyper.java:80)
[servicegen] at weblogic.ant.taskdefs.webservices.autotype.AutoTypeTask.execu
te(AutoTypeTask.java:353)
[servicegen] at weblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.g
enerateService(ServiceGenTask.java:251)
[servicegen] at weblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.e
xecute(ServiceGenTask.java:146)
[servicegen] at org.apache.tools.ant.Task.perform(Task.java:217)
[servicegen] at org.apache.tools.ant.Target.execute(Target.java:164)
[servicegen] at org.apache.tools.ant.Target.performTasks(Target.java:182)
[servicegen] at org.apache.tools.ant.Project.executeTarget(Project.java:601)
[servicegen] at org.apache.tools.ant.Project.executeTargets(Project.java:560)
[servicegen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
[servicegen] at org.apache.tools.ant.Main.start(Main.java:153)
[servicegen] at org.apache.tools.ant.Main.main(Main.java:176)
2. SECOND PROBLEM
If we change the signature to become:
public Document echoDom(Document doc)
then the build works but when we try to test our service, it gives us the following:
[java] java.rmi.RemoteException: web service invoke failed; nested exceptio
n is:
[java] javax.xml.soap.SOAPException: failed to serialize xml:weblogic.
xml.schema.binding.SerializationException: type mapping lookup failure on class=
class weblogic.apache.xerces.dom.DocumentImpl TypeMapping=TYPEMAPPING SIZE=6
[java] ENTRY 1:
[java] class: org.w3c.dom.Document
[java] xsd_type: ['http://examples.org']:p3:echoDom
[java] ser: weblogic.xml.schema.binding.internal.builtin.DocumentCode
c@5973ea
[java] deser: weblogic.xml.schema.binding.internal.builtin.DocumentCode
c@49131c
[java] ENTRY 2:
[java] class: java.lang.Object
[java] xsd_type: ['http://examples.org']:p1:echoDomResponse
[java] ser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@
5b99f
[java] deser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@
3. THIRD PROBLEM:
Now, when we revert back to style="rpc" and everything works fine and dandy (although
not as we want it because, as I mentioned above, we want a void signature and
a document style), we get the following added tag around our body content, which
we did not add ourselves, nor are we sure yet why it shows up:
We pass it the following argument:
<those dummy="hi">
<this xmlns="mynamespace">
<f:that xmlns:f="yournamespace">
<or> a lot of random < </or>
<f:the>
</f:the>
<f:other> foo bar blaz</f:other>
</f:that>
</this>
</those>
We get the following (notice the <document> tag around it):
<env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<env:Body>
<m:echoDom xmlns:m="http://examples.org"
env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<document>
<those dummy="hi">
<this xmlns="mynamespace">
<f:that xmlns:f="yournamespace">
<or> a lot of random < </or>
<f:the>
</f:the>
<f:other> foo bar blaz</f:other>
</f:that>
</this>
</those>
</document>
</m:echoDom>
</env:Body>
</env:Envelope>
4. PROBLEM FOUR (just remembered this one):
If we use the standard test page (provided with WLS), with (3) above, it chops
off the "those" and it still wraps it within this new <document> element as show
below:

<env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<env:Header>
</env:Header>
<env:Body>
<m:echoDom xmlns:m="http://examples.org"
env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<document>
<this xmlns="mynamespace">
<f:that xmlns:f="yournamespace">
<or> a lot of random < </or>
<f:the>
</f:the>
<f:other> foo bar blaz</f:other>
</f:that>
</this>
</document>
</m:echoDom>
</env:Body>
</env:Envelope>
We're not so worried about the fourth because it seems like a bug but the first
three (especially the first) are most important. Any ideas would be appreciated.
Thanks
sami

Ok I tried it out, DOM with document style web
service is not working in WLS 7.0.2. I filed
CR104719. Please contact support with this case
number to get a patch.
Sorry for the trouble.
http://manojc.com
"sami titi" <[email protected]> wrote in message
news:[email protected]...
>
We're using WLS7 SP2, patch: CR102544_70sp2_v2.jar
thanks
"manoj cheenath" <[email protected]> wrote:
Quick question, before i try this out.
Which version of WLS? SP?
http://manojc.com
"sami titi" <[email protected]> wrote in message
news:[email protected]...
We have three issues when trying to implement a document-style service.I
will
document them all but I'd suggest you go through them all beforeattempting to
answer any of them.
We are trying to implement a service that has the following signature:
public void echoDom(Document doc)
We want the delivery of our message to be of style ("document").Therefore, we
modified our servicegen entry to include the style="document" underthe
service.
It looks like the following:
<servicegen
destEar="${appDir}/dom.ear"
warName="dom.war">
<service
javaClassComponents="examples.dom.EchoDom"
targetNamespace="http://examples.org"
serviceName="dom"
serviceURI="/EchoDomService"
generateTypes="True"
expandMethods="True"
style="document">
<client
packageName="examples.dom"
clientJarName="client.jar"
/>
</service>
<classpath>
<pathelement path="${temp_dir}"/>
<pathelement path="${java.class.path}"/>
</classpath>
</servicegen>
1. FIRST PROBLEM:
The first problem we're having is that it does not compile with thecombination
of our signature being of type void (as shown above) and thestyle="document"
in build.xml.
The error is the following:
[servicegen] Generating service "dom" ...
[servicegen] Generating XML types and serializers from java classes(examples.do
m.EchoDom) ...
[servicegen] weblogic.utils.AssertionError: ***** ASSERTION FAILED*****[ void:
null ]
[servicegen] at weblogic.utils.Debug.assertion(Debug.java:84)
[servicegen] atweblogic.xml.schema.binding.internal.codegen.Compiler.compile
(Compiler.java:111)
[servicegen] atweblogic.xml.schema.binding.internal.XSDTypeMappingBuilder.ma
pClass(XSDTypeMappingBuilder.java:88)
[servicegen] atweblogic.xml.schema.binding.internal.TypeMappingBuilderBase.a
ddMapping(TypeMappingBuilderBase.java:183)
[servicegen] atweblogic.ant.taskdefs.webservices.autotype.ComponentAutoTyper
mapComponent(ComponentAutoTyper.java:155)
[servicegen] atweblogic.ant.taskdefs.webservices.autotype.JavaAutoTyper.run(
JavaAutoTyper.java:80)
[servicegen] atweblogic.ant.taskdefs.webservices.autotype.AutoTypeTask.execu
te(AutoTypeTask.java:353)
[servicegen] atweblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.g
enerateService(ServiceGenTask.java:251)
[servicegen] atweblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.e
xecute(ServiceGenTask.java:146)
[servicegen] at org.apache.tools.ant.Task.perform(Task.java:217)
[servicegen] at org.apache.tools.ant.Target.execute(Target.java:164)
[servicegen] atorg.apache.tools.ant.Target.performTasks(Target.java:182)
[servicegen] atorg.apache.tools.ant.Project.executeTarget(Project.java:601)
[servicegen] atorg.apache.tools.ant.Project.executeTargets(Project.java:560)
[servicegen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
[servicegen] at org.apache.tools.ant.Main.start(Main.java:153)
[servicegen] at org.apache.tools.ant.Main.main(Main.java:176)
2. SECOND PROBLEM
If we change the signature to become:
public Document echoDom(Document doc)
then the build works but when we try to test our service, it givesus the
following:
[java] java.rmi.RemoteException: web service invoke failed; nestedexceptio
n is:
[java] javax.xml.soap.SOAPException: failed to serializexml:weblogic.
xml.schema.binding.SerializationException: type mapping lookup failureon
class=
class weblogic.apache.xerces.dom.DocumentImpl TypeMapping=TYPEMAPPINGSIZE=6
[java] ENTRY 1:
[java] class: org.w3c.dom.Document
[java] xsd_type: ['http://examples.org']:p3:echoDom
[java] ser:weblogic.xml.schema.binding.internal.builtin.DocumentCode
c@5973ea
[java] deser:weblogic.xml.schema.binding.internal.builtin.DocumentCode
c@49131c
[java] ENTRY 2:
[java] class: java.lang.Object
[java] xsd_type: ['http://examples.org']:p1:echoDomResponse
[java] ser:weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@
5b99f
[java] deser:weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@
3. THIRD PROBLEM:
Now, when we revert back to style="rpc" and everything works fine anddandy (although
not as we want it because, as I mentioned above, we want a void
signature
and
a document style), we get the following added tag around our body
content,
which
we did not add ourselves, nor are we sure yet why it shows up:
We pass it the following argument:
<those dummy="hi">
<this xmlns="mynamespace">
<f:that xmlns:f="yournamespace">
<or> a lot of random < </or>
<f:the>
</f:the>
<f:other> foo bar blaz</f:other>
</f:that>
</this>
</those>
We get the following (notice the <document> tag around it):
<env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<env:Body>
<m:echoDom xmlns:m="http://examples.org"
env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<document>
<those dummy="hi">
<this xmlns="mynamespace">
<f:that xmlns:f="yournamespace">
<or> a lot of random < </or>
<f:the>
</f:the>
<f:other> foo bar blaz</f:other>
</f:that>
</this>
</those>
</document>
</m:echoDom>
</env:Body>
</env:Envelope>
4. PROBLEM FOUR (just remembered this one):
If we use the standard test page (provided with WLS), with (3) above,it
chops
off the "those" and it still wraps it within this new <document>
element
as show
below:

<env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<env:Header>
</env:Header>
<env:Body>
<m:echoDom xmlns:m="http://examples.org"
env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<document>
<this xmlns="mynamespace">
<f:that xmlns:f="yournamespace">
<or> a lot of random < </or>
<f:the>
</f:the>
<f:other> foo bar blaz</f:other>
</f:that>
</this>
</document>
</m:echoDom>
</env:Body>
</env:Envelope>
We're not so worried about the fourth because it seems like a bug butthe
first
three (especially the first) are most important. Any ideas would beappreciated.
Thanks
sami

Please help with jce 1.2.1 encoding/decoding problem (urgent)

Hello,
env: jce 1.2.1,java 1.3,webstart. Server (Sun),client webstart
PBE encryption
The encryption done on client side, but problems become on some machines encryption comes diferent, we can not find where the problem is (encoding or locale seting)
please help
any help welcome
Nerijus Jasinskas

soure atached:
Provider sunJce = new com.sun.crypto.provider.SunJCE();
Security.addProvider(sunJce);
pbeParamSpec = new PBEParameterSpec(salt, count);
pbeKeySpec = new PBEKeySpec(password);
keyFac = SecretKeyFactory.getInstance("PBEWithMD5AndDES");
SecretKey pbeKey = keyFac.generateSecret(pbeKeySpec);
Cipher pbeCipher = Cipher.getInstance("PBEWithMD5AndDES");
pbeCipher.init(Cipher.ENCRYPT_MODE, pbeKey, pbeParamSpec);
byte[] cleartext = (new String(password)).getBytes();
ciphertext = pbeCipher.doFinal(cleartext);

GetBytes() - Encoding Style problem

Similar Messages

Maybe you are looking for