WLS 9: WebServices using XMLBeans

I'm attempting to implement a web service on WLS 9 (without workshop) that uses XMLbean types as parameters.
The docs for jwsc hint that XMLBeans are given special treatment when used as web service arguments, but I have had no luck creating a functional web service this way.
Does anyone have a functional example for this, or any other tips on how the get started?

Similar Messages

Returning Errors from a webservice using XMLBeans

I have a webservice that accepts XML as input and output parameters, and I'm using XMLBeans to handle this. I'm trying to work out how I can return error information from the webservice, so I created an Exception.xsd schema and 'include' it in the output XML Schema, so an exception xml element is valid in the output schema. The problem is, the XMLBean class generated from the output XML schema has no methods that allow me to create an Exception element. Is there some other way of handling the return of exceptions from webservices using XML?

The answer is just throw a SoapFaultException and put the exception.xsd XMLBean in the FaultDetail section of the SoapFaultException.

WLS 9.2 using XmlBeans error

Using WLS 9.2 MP1 and attempting to use XmlBean derived classes from a bean called from a JSP.
          Using XmlBeans v2.3.0.
          Server is WebLogic Server 9.2 MP1 Sun Jan 7 00:56:31 EST 2007 883308
          JSP version is 2.0
          Servlet API is 2.4
          An exception is thrown :
                    javax.servlet.jsp.el.ELException
               at javelin.jsp.el.ArrayRefEvaluator.evaluateBeanType(ArrayRefEvaluator.java:252)
               at javelin.jsp.el.ArrayRefEvaluator.evaluate(ArrayRefEvaluator.java:49)
               at javelin.jsp.el.ELNode$RefExpression.evaluate(ELNode.java:492)
               at javelin.jsp.el.ExpressionEvaluatorImpl$ELExpression.evaluate(ExpressionEvaluatorImpl.java:186)
               at javelin.jsp.el.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:124)
               at javelin.jsp.el.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:104)
               at jsp_servlet._order.__composeorder3._jsp__tag1(__composeorder3.java:229)
               at jsp_servlet._order.__composeorder3._jspService(__composeorder3.java:205)
               at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
               at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:223)
               at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
               at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
               at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
               at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3245)
               at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
               at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
               at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2003)
               at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1909)
               at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1359)
               at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
               at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
                    This corresponds to the declaration of the root document within the bean e.g.
          ======== JSP code extract ===========
                    <%@ include file="/html/doctypes/StrictDoctype.html" %>
          <%@ taglib uri="utilTLD" prefix="util" %>
          <%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
          <%@ taglib uri="http://java.sun.com/jsp/jstl/xml" prefix="x" %>
          <%@ page import="com.web.order.*" %>
          <%@ page language="java" session="false" %>
          <jsp:useBean id="composeXmlBean" scope="request" class="com.web.order.composeXmlBean">
          <jsp:setProperty name="composeXmlBean" property="*"/>
          </jsp:useBean>
          <c:set scope="page" var="xml" value="${composeXmlBean.myXmlString}"/>
                    ============End Jsp code =======
          ========Java code extract =======
                    public class ComposeXmlBean {
               public Document getMyXmlString() {
                         // Use XML Beans to construct the XML String
                     DDServiceDocument rootDoc = DDServiceDocument.Factory.newInstance();
                    ========End Java code ===========
          Anyone have any ideas about what could be causing this error. I have used XmlBeans without problem in WLS 8.1. Is this a WLS9.2 problem caused by Javelin ?
          regards,
          Chris

Chris,
          Firstly, I think your pasted jsp's line below is not correct:
          <jsp:useBean id="composeXmlBean" scope="request"
          class="com.web.order.composeXmlBean">
          Should it be <jsp:useBean id="composeXmlBean" scope="request"
          class="com.web.order.ComposeXmlBean"> ?
          I tried to reprodcue your issues locally, but fails (my testcase works fine)
          since I have not your customerized classes.
          My codes are listed below:
          1) Bean codes:
          package com.web.order;
          public class ComposeXmlBean {
          public String getMyXmlString() {
          return "100";
          public void setMyXmlString(String setV) {
          return;
          2) JSP codes:
          <%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
          <%@ taglib uri="http://java.sun.com/jsp/jstl/xml" prefix="x" %>
          <%@ page import="com.web.order.*" %>
          <%@ page language="java" session="false" %>
          <jsp:useBean id="composeXmlBean" scope="request"
          class="com.web.order.ComposeXmlBean">
          <jsp:setProperty name="composeXmlBean" property="*"/>
          </jsp:useBean>
          <c:set scope="page" var="xml" value="${composeXmlBean.myXmlString}"/>
          My sugegstions:
          1) is it a XML bean related issue?
          can you remove XML releated logic to verify whether JSP compiler could
          support this kind of EL ( "${composeXmlBean.myXmlString}") correctly?
          2) If possible, can you pasted a reproducer here(a .war)?
          3) As for WLS8.1, which only support JSP1.2 and dose not support JSP2.0's
          EL, while your failed points is at EL: "${composeXmlBean.myXmlString}" in
          fact, I think your testcases are different during these two tests(WLS 8.1
          and WLS 9.2), Or that EL dose not work at all in WLS8.1. Can you help to
          clarify this?
          Regards
          Leon
          <Chris Thorp> wrote in message news:[email protected]...
          Using WLS 9.2 MP1 and attempting to use XmlBean derived classes from a bean
          called from a JSP.
          Using XmlBeans v2.3.0.
          Server is WebLogic Server 9.2 MP1 Sun Jan 7 00:56:31 EST 2007 883308
          JSP version is 2.0
          Servlet API is 2.4
          An exception is thrown :
                    javax.servlet.jsp.el.ELException
          at
          javelin.jsp.el.ArrayRefEvaluator.evaluateBeanType(ArrayRefEvaluator.java:252)
          at javelin.jsp.el.ArrayRefEvaluator.evaluate(ArrayRefEvaluator.java:49)
          at javelin.jsp.el.ELNode$RefExpression.evaluate(ELNode.java:492)
          at
          javelin.jsp.el.ExpressionEvaluatorImpl$ELExpression.evaluate(ExpressionEvaluatorImpl.java:186)
          at
          javelin.jsp.el.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:124)
          at
          javelin.jsp.el.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:104)
          at jsp_servlet._order.__composeorder3._jsp__tag1(__composeorder3.java:229)
          at jsp_servlet._order.__composeorder3._jspService(__composeorder3.java:205)
          at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
          at
          weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:223)
          at
          weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
          at
          weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
          at
          weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
          at
          weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3245)
          at
          weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
          at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
          at
          weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2003)
          at
          weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1909)
          at
          weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1359)
          at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
          at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
                    This corresponds to the declaration of the root document within the bean
          e.g.
          ======== JSP code extract ===========
                    <%@ include file="/html/doctypes/StrictDoctype.html" %>
          <%@ taglib uri="utilTLD" prefix="util" %>
          <%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
          <%@ taglib uri="http://java.sun.com/jsp/jstl/xml" prefix="x" %>
          <%@ page import="com.web.order.*" %>
          <%@ page language="java" session="false" %>
          <jsp:useBean id="composeXmlBean" scope="request"
          class="com.web.order.composeXmlBean">
          <jsp:setProperty name="composeXmlBean" property="*"/>
          </jsp:useBean>
          <c:set scope="page" var="xml" value="${composeXmlBean.myXmlString}"/>
                    ============End Jsp code =======
          ========Java code extract =======
                    public class ComposeXmlBean {
          public Document getMyXmlString() {
                         // Use XML Beans to construct the XML String
                DDServiceDocument rootDoc =
          DDServiceDocument.Factory.newInstance();
                    ========End Java code ===========
          Anyone have any ideas about what could be causing this error. I have used
          XmlBeans without problem in WLS 8.1. Is this a WLS9.2 problem caused by
          Javelin ?
          regards,
          Chris

Invalid security error when invoking secure webservice using SAML tokens

I have deployed a JAX-WS webservice using a stateless session bean to wl 10.3.2 that uses a custom policy. The service deploys fine, but weblogic returns an HTTP error 500 with a SOAP fault. The fault states wsse:InvalidSecurity. The webservice security policy reqires SAML holder of key assertions and attributes. I have tried everything from running weblogic with Metro 1.5 to configuring SAML Identity Asserter Providers, etc with no luck. I even tried using the built in SAML 2.0 assymetric holder of key policy. What am I doing wrong? The XML of interest is attached.
Thanks;
-Dave.
*[Sample message from client]*
<?xml version="1.0" encoding="UTF-8"?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion" xmlns:wsse11="http://docs.oasis-open.org/wss/oasis-wss-wssecurity-secext-1.1.xsd" xmlns:exc14n="http://www.w3.org/2001/10/xml-exc-c14n#">
     <S:Header>
          <To xmlns="http://www.w3.org/2005/08/addressing">https://localhost:7002/NHINAdapterDocQuerySecured/AdapterDocQuerySecured</To>
          <Action xmlns="http://www.w3.org/2005/08/addressing">urn:gov:hhs:fha:nhinc:adapterdocquerysecured:RespondingGateway_CrossGatewayQueryRequestMessage</Action>
          <ReplyTo xmlns="http://www.w3.org/2005/08/addressing">
               <Address>http://www.w3.org/2005/08/addressing/anonymous</Address>
          </ReplyTo>
          <MessageID xmlns="http://www.w3.org/2005/08/addressing">uuid:fec656f8-a2be-4129-8412-34d9453e7cb2</MessageID>
          <wsse:Security S:mustUnderstand="1">
               <wsu:Timestamp xmlns:ns17="http://docs.oasis-open.org/ws-sx/ws-secureconversation/200512" xmlns:ns16="http://www.w3.org/2003/05/soap-envelope" wsu:Id="_1">
                    <wsu:Created>2010-02-24T21:38:56Z</wsu:Created>
                    <wsu:Expires>2010-02-24T21:43:56Z</wsu:Expires>
               </wsu:Timestamp>
               <saml2:Assertion xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:exc14n="http://www.w3.org/2001/10/xml-exc-c14n#" xmlns:saml2="urn:oasis:names:tc:SAML:2.0:assertion" xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" xmlns:xs="http://www.w3.org/2001/XMLSchema" ID="96cdfb70-91a3-4baf-9da1-3ff07d249926" IssueInstant="2010-02-24T21:38:56.671Z" Version="2.0">
                    <saml2:Issuer Format="urn:oasis:names:tc:SAML:1.1:nameid-format:X509SubjectName">CN=SAML User,OU=SU,O=SAML User,L=Los Angeles,ST=CA,C=US</saml2:Issuer>
                    <saml2:Subject>
                         <saml2:NameID Format="urn:oasis:names:tc:SAML:1.1:nameid-format:X509SubjectName">UID=kskagerb*DoD</saml2:NameID>
                         <saml2:SubjectConfirmation Method="urn:oasis:names:tc:SAML:2.0:cm:holder-of-key">
                              <saml2:SubjectConfirmationData>
                                   <ds:KeyInfo>
                                        <ds:KeyValue>
                                             <ds:RSAKeyValue>
                                                  <ds:Modulus>iwGksKFK2ZYDxftMa093TajW7V9TwHW7NiyT6bJ2p38zBwpehwMJ1ZO9V0hFihcz/BZ2MvQ1WA1l0KhUBSR/bMiu6WmZ0bJPjvXx41ewGw5YzTL2RbT1U2XXBHtPHjbkH5jqK5zk67F/NM26v+hw0fSZiqM1BAFp9F73hMHsNrc=</ds:Modulus>
                                                  <ds:Exponent>AQAB</ds:Exponent>
                                             </ds:RSAKeyValue>
                                        </ds:KeyValue>
                                   </ds:KeyInfo>
                              </saml2:SubjectConfirmationData>
                         </saml2:SubjectConfirmation>
                    </saml2:Subject>
                    <saml2:AuthnStatement AuthnInstant="2009-04-16T13:15:39.000Z" SessionIndex="987">
                         <saml2:SubjectLocality Address="158.147.185.168" DNSName="cs.myharris.net"/>
                         <saml2:AuthnContext>
                              <saml2:AuthnContextClassRef>urn:oasis:names:tc:SAML:2.0:ac:classes:X509</saml2:AuthnContextClassRef>
                         </saml2:AuthnContext>
                    </saml2:AuthnStatement>
                    <saml2:AttributeStatement>
                         <saml2:Attribute Name="urn:oasis:names:tc:xspa:1.0:subject:subject-id">
                              <saml2:AttributeValue xmlns:ns6="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns7="http://www.w3.org/2001/XMLSchema" ns6:type="ns7:string">Karl S Skagerberg</saml2:AttributeValue>
                         </saml2:Attribute>
                         <saml2:Attribute Name="urn:oasis:names:tc:xspa:1.0:subject:organization">
                              <saml2:AttributeValue xmlns:ns6="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns7="http://www.w3.org/2001/XMLSchema" ns6:type="ns7:string">InternalTest2</saml2:AttributeValue>
                         </saml2:Attribute>
                         <saml2:Attribute Name="urn:oasis:names:tc:xspa:1.0:subject:organization-id">
                              <saml2:AttributeValue xmlns:ns6="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns7="http://www.w3.org/2001/XMLSchema" ns6:type="ns7:string">2.16.840.1.113883.4.349</saml2:AttributeValue>
                         </saml2:Attribute>
                         <saml2:Attribute Name="urn:nhin:names:saml:homeCommunityId">
                              <saml2:AttributeValue xmlns:ns6="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns7="http://www.w3.org/2001/XMLSchema" ns6:type="ns7:string">2.16.840.1.113883.4.349</saml2:AttributeValue>
                         </saml2:Attribute>
                         <saml2:Attribute Name="urn:oasis:names:tc:xacml:2.0:subject:role">
                              <saml2:AttributeValue>
                                   <hl7:Role xmlns:hl7="urn:hl7-org:v3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" code="307969004" codeSystem="2.16.840.1.113883.6.96" codeSystemName="SNOMED_CT" displayName="Public Health" xsi:type="hl7:CE"/>
                              </saml2:AttributeValue>
                         </saml2:Attribute>
                         <saml2:Attribute Name="urn:oasis:names:tc:xspa:1.0:subject:purposeofuse">
                              <saml2:AttributeValue>
                                   <hl7:PurposeForUse xmlns:hl7="urn:hl7-org:v3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" code="TREATMENT" codeSystem="2.16.840.1.113883.3.18.7.1" codeSystemName="nhin-purpose" displayName="Use or disclosure of Psychotherapy Notes" xsi:type="hl7:CE"/>
                              </saml2:AttributeValue>
                         </saml2:Attribute>
                         <saml2:Attribute Name="urn:oasis:names:tc:xacml:2.0:resource:resource-id">
                              <saml2:AttributeValue xmlns:ns6="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns7="http://www.w3.org/2001/XMLSchema" ns6:type="ns7:string">500000000^^^&1.1&ISO</saml2:AttributeValue>
                         </saml2:Attribute>
                    </saml2:AttributeStatement>
                    <saml2:AuthzDecisionStatement Decision="Permit" Resource="https://158.147.185.168:8181/SamlReceiveService/SamlProcessWS">
                         <saml2:Action Namespace="urn:nhin:names:hl7:rbac:4.00:operation">EXECUTE</saml2:Action>
                         <saml2:Evidence>
                              <saml2:Assertion ID="40df7c0a-ff3e-4b26-baeb-f2910f6d05a9" IssueInstant="2009-04-16T13:10:39.093Z" Version="2.0">
                                   <saml2:Issuer Format="urn:oasis:names:tc:SAML:1.1:nameid-format:X509SubjectName">CN=SAML User,OU=Harris,O=HITS,L=Melbourne,ST=FL,C=US</saml2:Issuer>
                                   <saml2:Conditions NotBefore="2009-04-16T13:10:39.093Z" NotOnOrAfter="2010-12-31T12:00:00.000Z"/>
                                   <saml2:AttributeStatement>
                                        <saml2:Attribute Name="AccessConsentPolicy" NameFormat="http://www.hhs.gov/healthit/nhin">
                                             <saml2:AttributeValue xmlns:ns6="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns7="http://www.w3.org/2001/XMLSchema" ns6:type="ns7:string">Claim-Ref-1234</saml2:AttributeValue>
                                        </saml2:Attribute>
                                        <saml2:Attribute Name="InstanceAccessConsentPolicy" NameFormat="http://www.hhs.gov/healthit/nhin">
                                             <saml2:AttributeValue xmlns:ns6="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns7="http://www.w3.org/2001/XMLSchema" ns6:type="ns7:string">Claim-Instance-1</saml2:AttributeValue>
                                        </saml2:Attribute>
                                   </saml2:AttributeStatement>
                              </saml2:Assertion>
                         </saml2:Evidence>
                    </saml2:AuthzDecisionStatement>
                    <ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
                         <ds:SignedInfo>
                              <ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
                              <ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>
                              <ds:Reference URI="#96cdfb70-91a3-4baf-9da1-3ff07d249926">
                                   <ds:Transforms>
                                        <ds:Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>
                                        <ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
                                   </ds:Transforms>
                                   <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
                                   <ds:DigestValue>VnukKqb4Bt1KWDKfy8SDfk1Hp2s=</ds:DigestValue>
                              </ds:Reference>
                         </ds:SignedInfo>
                         <ds:SignatureValue>DUwjh/H3XSfUG250rTlLdihstDXY1+qkY9GaY81Iu7Ag4MgoGvGBrGjZOJ7YnssPdrqUGiURxf6k
IBH7vaeXk24XvXP3F85WP9nBm+2M4BvGTplgOmAo0yuwze+90FvwILzFNmmX/tvy3QKTDHlh1rEx
/Jqfm6q/56WW1suAbRY=</ds:SignatureValue>
                         <ds:KeyInfo>
                              <ds:KeyValue>
                                   <ds:RSAKeyValue>
                                        <ds:Modulus>iwGksKFK2ZYDxftMa093TajW7V9TwHW7NiyT6bJ2p38zBwpehwMJ1ZO9V0hFihcz/BZ2MvQ1WA1l
0KhUBSR/bMiu6WmZ0bJPjvXx41ewGw5YzTL2RbT1U2XXBHtPHjbkH5jqK5zk67F/NM26v+hw0fSZ
iqM1BAFp9F73hMHsNrc=</ds:Modulus>
                                        <ds:Exponent>AQAB</ds:Exponent>
                                   </ds:RSAKeyValue>
                              </ds:KeyValue>
                         </ds:KeyInfo>
                    </ds:Signature>
               </saml2:Assertion>
               <ds:Signature xmlns:ns17="http://docs.oasis-open.org/ws-sx/ws-secureconversation/200512" xmlns:ns16="http://www.w3.org/2003/05/soap-envelope" Id="_2">
                    <ds:SignedInfo>
                         <ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#">
                              <exc14n:InclusiveNamespaces PrefixList="wsse S"/>
                         </ds:CanonicalizationMethod>
                         <ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>
                         <ds:Reference URI="#_1">
                              <ds:Transforms>
                                   <ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#">
                                        <exc14n:InclusiveNamespaces PrefixList="wsu wsse S"/>
                                   </ds:Transform>
                              </ds:Transforms>
                              <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
                              <ds:DigestValue>oo99UrPhAcwla4Qbkdd9jAPn0cE=</ds:DigestValue>
                         </ds:Reference>
                    </ds:SignedInfo>
                    <ds:SignatureValue>ds4vqts8uCdJcNGo0uTPzId5UBX+GVrdztQPv823c1Zy9ZZGSfQC/GsBPM/EMbFInDPFsyT4e1QYZMCzmqLYnifWHlDQJb7oMJBokafavAqZda1B55Zzh3TSm6BqKWtB/DX17d6rLx/HPiLNZ9qsBfuGn3aTlUCpNsYA8ObBtp8=</ds:SignatureValue>
                    <ds:KeyInfo>
                         <wsse:SecurityTokenReference wsse11:TokenType="http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV2.0">
                              <wsse:KeyIdentifier ValueType="http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLID">96cdfb70-91a3-4baf-9da1-3ff07d249926</wsse:KeyIdentifier>
                         </wsse:SecurityTokenReference>
                    </ds:KeyInfo>
               </ds:Signature>
          </wsse:Security>
     </S:Header>
     <S:Body>
          <ns3:AdhocQueryRequest xmlns:ns2="urn:gov:hhs:fha:nhinc:gateway:samltokendata" xmlns:ns3="urn:oasis:names:tc:ebxml-regrep:xsd:query:3.0" xmlns:ns4="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0" xmlns:ns5="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0" xmlns:ns6="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:3.0" maxResults="-1" startIndex="0" federated="false">
               <ns3:ResponseOption returnComposedObjects="true" returnType="LeafClass"/>
               <ns4:AdhocQuery home="urn:oid:2.16.840.1.113883.4.349" id="urn:uuid:14d4debf-8f97-4251-9a74-a90016b0af0d">
                    <ns4:Slot name="$XDSDocumentEntryStatus">
                         <ns4:ValueList>
                              <ns4:Value>('urn:oasis:names:tc:ebxml-regrep:StatusType:Approved')</ns4:Value>
                         </ns4:ValueList>
                    </ns4:Slot>
                    <ns4:Slot name="$XDSDocumentEntryPatientId">
                         <ns4:ValueList>
                              <ns4:Value>'1012581676V377802^^^&2.16.840.1.113883.4.349&ISO'</ns4:Value>
                         </ns4:ValueList>
                    </ns4:Slot>
               </ns4:AdhocQuery>
          </ns3:AdhocQueryRequest>
     </S:Body>
</S:Envelope>
*[Response from server:]*
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
     <env:Body>
          <env:Fault xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
               <faultcode>wsse:InvalidSecurity</faultcode>
               <faultstring>weblogic.xml.crypto.api.MarshalException: weblogic.xml.dom.marshal.MarshalException: Failed to unmarshal {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}SecurityTokenReference, no SecurityTokenReference factory found for {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}KeyIdentifier ValueType: http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLID</faultstring>
          </env:Fault>
     </env:Body>
</env:Envelope>
*[webservice WSDL]*
<?xml version="1.0" encoding="UTF-8"?>

<definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="urn:gov:hhs:fha:nhinc:adapterdocquerysecured"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:query="urn:oasis:names:tc:ebxml-regrep:xsd:query:3.0"
xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype"
xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"
xmlns:wsaws="http://www.w3.org/2005/08/addressing"
xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"
xmlns:sc="http://schemas.sun.com/2006/03/wss/server"
xmlns:wspp="http://java.sun.com/xml/ns/wsit/policy"
xmlns:vprop="http://docs.oasis-open.org/wsbpel/2.0/varprop"
xmlns:sxnmp="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/NMProperty"
name="AdapterDocQuerySecured"
targetNamespace="urn:gov:hhs:fha:nhinc:adapterdocquerysecured">
<documentation>Adapter Document Query</documentation>
<types>
<xsd:schema>
<xsd:import namespace="urn:oasis:names:tc:ebxml-regrep:xsd:query:3.0"
schemaLocation="../schemas/ebRS/query.xsd"/>
<xsd:import namespace="urn:gov:hhs:fha:nhinc:gateway:samltokendata"
schemaLocation="../schemas/nhinc/gateway/SamlTokenData.xsd"/>
</xsd:schema>
</types>
<message name="RespondingGateway_CrossGatewayQueryRequestMessage">
<part name="body"
element="query:AdhocQueryRequest"/>
</message>
<message name="RespondingGateway_CrossGatewayQueryResponseMessage">
<part name="body"
element="query:AdhocQueryResponse"/>
</message>
<portType name="AdapterDocQuerySecuredPortType">
<operation name="RespondingGateway_CrossGatewayQuery">
<input name="RespondingGateway_CrossGatewayQueryRequest"
message="tns:RespondingGateway_CrossGatewayQueryRequestMessage"
wsaw:Action="urn:gov:hhs:fha:nhinc:adapterdocquerysecured:RespondingGateway_CrossGatewayQueryRequestMessage"/>
<output name="RespondingGateway_CrossGatewayQueryResponse"
message="tns:RespondingGateway_CrossGatewayQueryResponseMessage"
wsaw:Action="urn:gov:hhs:fha:nhinc:adapterdocquerysecured:RespondingGateway_CrossGatewayQueryResponseMessage"/>
</operation>
</portType>
<binding name="AdapterDocQuerySecuredBindingSoap11" type="tns:AdapterDocQuerySecuredPortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsp:PolicyReference URI="#RespondingGateway_Query_Binding_SoapPolicy"/>
<operation name="RespondingGateway_CrossGatewayQuery">
<soap:operation soapAction="urn:RespondingGateway_CrossGatewayQuery"/>
<input name="RespondingGateway_CrossGatewayQueryRequest">
<soap:body use="literal"/>
<wsp:PolicyReference URI="#RespondingGateway_Query_Binding_Soap_Input_Policy"/>
</input>
<output name="RespondingGateway_CrossGatewayQueryResponse">
<soap:body use="literal"/>
<wsp:PolicyReference URI="#RespondingGateway_Query_Binding_Soap_Output_Policy"/>
</output>
</operation>
</binding>
<service name="AdapterDocQuerySecured">
<port name="AdapterDocQuerySecuredPortSoap11"
binding="tns:AdapterDocQuerySecuredBindingSoap11">
<soap:address
location="https://localhost:7002/NHINAdapterDocQuerySecured" />
</port>
</service>

<vprop:property name="action" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:action"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>action</vprop:query>
</vprop:propertyAlias>

<vprop:property name="resource" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:resource"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>resource</vprop:query>
</vprop:propertyAlias>

<vprop:property name="purposeForUseRoleCode" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:purposeForUseRoleCode"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>purposeForUseRoleCode</vprop:query>
</vprop:propertyAlias>

<vprop:property name="purposeForUseCodeSystem" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:purposeForUseCodeSystem"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>purposeForUseCodeSystem</vprop:query>
</vprop:propertyAlias>

<vprop:property name="purposeForUseCodeSystemName" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:purposeForUseCodeSystemName"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>purposeForUseCodeSystemName</vprop:query>
</vprop:propertyAlias>

<vprop:property name="purposeForUseDisplayName" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:purposeForUseDisplayName"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>purposeForUseDisplayName</vprop:query>
</vprop:propertyAlias>

<vprop:property name="userFirstName" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:userFirstName"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>userFirstName</vprop:query>
</vprop:propertyAlias>

<vprop:property name="userMiddleName" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:userMiddleName"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>userMiddleName</vprop:query>
</vprop:propertyAlias>

<vprop:property name="userLastName" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:userLastName"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>userLastName</vprop:query>
</vprop:propertyAlias>

<vprop:property name="userName" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:userName"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>userName</vprop:query>
</vprop:propertyAlias>

<vprop:property name="userOrganization" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:userOrganization"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>userOrganization</vprop:query>
</vprop:propertyAlias>

<vprop:property name="userRoleCode" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:userRoleCode"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>userRoleCode</vprop:query>
</vprop:propertyAlias>

<vprop:property name="userRoleCodeSystem" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:userRoleCodeSystem"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>userRoleCodeSystem</vprop:query>
</vprop:propertyAlias>

<vprop:property name="userRoleCodeSystemName" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:userRoleCodeSystemName"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>userRoleCodeSystemName</vprop:query>
</vprop:propertyAlias>

<vprop:property name="userRoleCodeDisplayName" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:userRoleCodeDisplayName"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>userRoleCodeDisplayName</vprop:query>
</vprop:propertyAlias>

<vprop:property name="expirationDate" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:expirationDate"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>expirationDate</vprop:query>
</vprop:propertyAlias>

<vprop:property name="signDate" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:signDate"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>signDate</vprop:query>
</vprop:propertyAlias>

<vprop:property name="contentReference" type="xsd:string"/>
<vprop:propertyAlias propertyName="tns:contentReference"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>contentReference</vprop:query>
</vprop:propertyAlias>

<vprop:property name="content" type="xsd:base64Binary"/>
<vprop:propertyAlias propertyName="tns:content"
messageType="tns:RespondingGateway_CrossGatewayQueryRequestMessage" part="body"
sxnmp:nmProperty="org.glassfish.openesb.outbound.custom.properties">
<vprop:query>content</vprop:query>
</vprop:propertyAlias>
<wsp:Policy wsu:Id="RespondingGateway_Query_Binding_SoapPolicy">
<wsp:ExactlyOne>
<wsp:All>
<wsaws:UsingAddressing xmlns:wsaws="http://www.w3.org/2006/05/addressing/wsdl"/>
<sc:KeyStore wspp:visibility="private"
aliasSelector="gov.hhs.fha.nhinc.callback.KeyStoreServerAliasSelector"
callbackHandler="gov.hhs.fha.nhinc.callback.KeyStoreCallbackHandler"/>
<sc:TrustStore wspp:visibility="private"
callbackHandler="gov.hhs.fha.nhinc.callback.TrustStoreCallbackHandler"/>
<sp:TransportBinding>
<wsp:Policy>
<sp:TransportToken>
<wsp:Policy>
<sp:HttpsToken>
<wsp:Policy>
<sp:RequireClientCertificate/>
</wsp:Policy>
</sp:HttpsToken>
</wsp:Policy>
</sp:TransportToken>
<sp:Layout>
<wsp:Policy>
<sp:Strict/>
</wsp:Policy>
</sp:Layout>
<sp:IncludeTimestamp/>
<sp:AlgorithmSuite>
<wsp:Policy>
<sp:Basic128/>
</wsp:Policy>
</sp:AlgorithmSuite>
</wsp:Policy>
</sp:TransportBinding>
<sp:EndorsingSupportingTokens>
<wsp:Policy>
<sp:SamlToken
sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient">
<wsp:Policy>
<sp:WssSamlV20Token11/>
</wsp:Policy>
</sp:SamlToken>
</wsp:Policy>
</sp:EndorsingSupportingTokens>
<sp:Wss11>
<wsp:Policy>
<sp:MustSupportRefKeyIdentifier/>
<sp:MustSupportRefIssuerSerial/>
<sp:RequireSignatureConfirmation/>
</wsp:Policy>
</sp:Wss11>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
<wsp:Policy wsu:Id="RespondingGateway_Query_Binding_Soap_Input_Policy">
<wsp:ExactlyOne>
<wsp:All>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
<wsp:Policy wsu:Id="RespondingGateway_Query_Binding_Soap_Output_Policy">
<wsp:ExactlyOne>
<wsp:All>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
<plnk:partnerLinkType name="AdapterDocQuerySecured">

<plnk:role name="AdapterDocQuerySecuredPortTypeRole"
portType="tns:AdapterDocQuerySecuredPortType"/>
</plnk:partnerLinkType>
</definitions>
Edited by: dvazquez1027 on Feb 25, 2010 5:10 PM
Edited by: dvazquez1027 on Feb 25, 2010 5:22 PM

Hi
yes, I had the same issue and I found a solution.
You need to request a patch for BUG 9212862 (already corrected in WLS 10.3.3) and do the follwing:
javax.xml.ws.BindingProvider provider = (javax.xml.ws.BindingProvider)port;
java.util.Map context = provider.getRequestContext();
context.put(weblogic.wsee.jaxrpc.WLStub.POLICY_COMPATIBILITY_PREFERENCE, weblogic.wsee.jaxrpc.WLStub.POLICY_COMPATIBILITY_MSFT);
This will cause the SecurityMessageArchitect class of WLS to not send the SecurityTokenReference in the Soap security header.
Please note that is evidently a non-comformity to the specs of microsoft:
Please give a look at
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf (8.3 Signing Tokens)
and also at:
http://www.oasis-open.org/committees/download.php/16768/wss-v1.1-spec-os-SAMLTokenProfile.pdf
(3.4 Identifying and Referencing Security Tokens)
A SAML key identifier reference MUST be used for all (local and remote) references to SAML 1.1
assertions. [...]
All conformant implementations MUST be able to process SAML assertion references occurring in a
<wsse:Security> header or in a header element other than a signature to acquire the corresponding
assertion. A conformant implementation MUST be able to process any such reference independent of the
confirmation method of the referenced assertion.
It follows that the .NET 3.5 is a non conformat implementation: I would gladly know which is the position of Microsoft on that.
ciao
carlo

Webservices with xmlbeans fails during deploy.

Hi there,
I have created a webservices from an existing wsdl that uses xmlbeans. The xmlbeans are on the weblogic classpath, because they are used by several components, including the webservices I generated.
When I try to deploy the webservice I get the following error:
<Oct 19, 2007 9:47:18 AM CEST> <Info> <Deployer> <BEA-149038> <Initiating Task for LAWebServicesEAR : [Deployer:149026]distribute application LAWebServicesEAR on RendServer.>
<Oct 19, 2007 9:47:21 AM CEST> <Info> <WorkManager> <BEA-002903> <Creating WorkManager from "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "LAWebServicesEAR">
<Oct 19, 2007 9:47:29 AM CEST> <Info> <Deployer> <BEA-149059> <Module LAWebServices of application LAWebServicesEAR is transitioning from STATE_NEW to STATE_PREPARED on server RendServer.>
<Oct 19, 2007 9:47:30 AM CEST> <Info> <HTTP> <BEA-101363> <Application: LAWebServicesEAR, WebApp: LAWebServices has context-root specified in application.xml: "LAWebServices". The context-root specified in weblogic.xml: "LAWebServices" will be ignore
d.>
<Oct 19, 2007 9:47:45 AM CEST> <Info> <Deployer> <BEA-149060> <Module LAWebServices of application LAWebServicesEAR successfully transitioned from STATE_NEW to STATE_PREPARED on server RendServer.>
<Oct 19, 2007 9:47:45 AM CEST> <Info> <Deployer> <BEA-149074> <Successfully completed deployment task: [Deployer:149026]distribute application LAWebServicesEAR on RendServer.>
<Oct 19, 2007 9:47:46 AM CEST> <Info> <Deployer> <BEA-149038> <Initiating Task for LAWebServicesEAR : [Deployer:149026]start application LAWebServicesEAR on RendServer.>
<Oct 19, 2007 9:47:46 AM CEST> <Info> <Deployer> <BEA-149059> <Module LAWebServices of application LAWebServicesEAR is transitioning from STATE_PREPARED to STATE_ADMIN on server RendServer.>
<Oct 19, 2007 9:47:46 AM CEST> <Info> <Deployer> <BEA-149060> <Module LAWebServices of application LAWebServicesEAR successfully transitioned from STATE_PREPARED to STATE_ADMIN on server RendServer.>
<Oct 19, 2007 9:47:50 AM CEST> <Error> <HTTP> <BEA-101216> <Servlet: "PartyServiceServlethttp" failed to preload on startup in Web application: "LAWebServices".
java.lang.IllegalStateException: Could not find binding for QNameProperty Parameters : BindingTypeName[com.leanapps.businesslayer.xml.Body$Parameters;t|e=parameters|t=Body@http://www.leanapps.com/businesslayer/xml] Bean type :interface com.leanapps.b
usinesslayer.xml.Body XmlType {http://www.leanapps.com/businesslayer/xml}Body
at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.createQNameProps(Deploytime109MappingHelper.java:1506)
at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.processTypeMappings(Deploytime109MappingHelper.java:545)
at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.initBindingFileFrom109dd(Deploytime109MappingHelper.java:249)
at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.<init>(Deploytime109MappingHelper.java:161)
at weblogic.wsee.bind.runtime.internal.RuntimeBindingsBuilderImpl.createRuntimeBindings(RuntimeBindingsBuilderImpl.java:86)
at weblogic.wsee.ws.WsBuilder.createRuntimeBindingProvider(WsBuilder.java:691)
at weblogic.wsee.ws.WsBuilder.buildService(WsBuilder.java:201)
at weblogic.wsee.ws.WsFactory.createServerService(WsFactory.java:54)
at weblogic.wsee.deploy.ServletDeployInfo.createWsService(ServletDeployInfo.java:76)
at weblogic.wsee.deploy.DeployInfo.createWsPort(DeployInfo.java:325)
at weblogic.wsee.server.servlet.BaseWSServlet.init(BaseWSServlet.java:74)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:504)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1830)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1807)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1727)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2890)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:948)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:353)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:139)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:816)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1223)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:434)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
I think it has something to do with duplicate xmlbeans, but I'm not sure. Has anyone experienced the same problems?
Is it possible to suppress the xmlbeans generation when the webservice is deployed? I want to use the xmlbeans that are already on the classpath.
Thanks in advance,
Martijn Baels
Software Architect
www.leanapps.com

Hi
Does it all work fine when you remove the xmlbeans from the classpath? (Just to make sure its causing the issue)
I also found several known issue on the same error.
Could you please open a BEA support case at http://support.bea.com and request a patch for the issue?
Please refer to the Cr's : CR271358, CR297871, CR316819 in the support case.
Vimala-

Failure to generate WSDL from web service when use xmlbean

Hi, I have a web service that uses xmlbean generated by schema. The schema from 3rd party is in a separate project since it's used by another web app and ejb project. In wlw103 I have included the schema project in this web service project's Java Build Path. The web service compiles, but when I tried to generate WSDL a Error window shows and says "The WSDL cannot be generated from the web service due to unexpected runtime errors".
The following is the detail. What do I need to do to make the xmlbean available for my web service? Thanks
com.bea.workshop.webservices.core.gen.WebServicesException: weblogic.wsee.tools.jws.build.CompileException: Error compiling web service: C:\workspace\ws\src\myPackage\testWS.java
     at com.bea.workshop.webservices.core.compiler.WebServiceCompilerImpl$3.invoke(WebServiceCompilerImpl.java:335)
     at com.bea.workshop.webservices.core.compiler.WebServiceCompilerImpl.accessCompiler(WebServiceCompilerImpl.java:390)
     at com.bea.workshop.webservices.core.compiler.WebServiceCompilerImpl.compile0(WebServiceCompilerImpl.java:330)
     at com.bea.workshop.webservices.core.compiler.WebServiceCompilerImpl.compile(WebServiceCompilerImpl.java:275)
     at com.bea.workshop.webservices.ui.actions.GenerateWsdlFromJwsAction.run(GenerateWsdlFromJwsAction.java:169)
     at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:256)
     at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:546)
Caused by: weblogic.wsee.tools.jws.build.CompileException: Error compiling web service: C:\workspace\ws\src\myPackage\testWS.java
     at weblogic.wsee.tools.jws.build.JwsCompiler.buildWebServices(JwsCompiler.java:526)
     at weblogic.wsee.tools.jws.build.JwsCompiler.compile(JwsCompiler.java:483)
     at com.bea.workshop.webservices.core.compiler.WebServiceCompilerImpl$3.invoke(WebServiceCompilerImpl.java:333)
     ... 46 more
Caused by: weblogic.wsee.tools.WsBuildException: weblogic.wsee.bind.buildtime.BindingException: ERROR ! could not add Xml Schema Type for XmlBean named '\[com.domain.UserDocument\]'. This is completely unexpected and might be caused by missing *.xsb and *.xsd files in the build environment. The building and running of this Service is likely to FAIL.
     at weblogic.wsee.tools.jws.jaxrpc.JAXRPCWebServiceInfo.createBindings(JAXRPCWebServiceInfo.java:227)
     at weblogic.wsee.tools.jws.wsdl.WsdlBuilder.processImpl(WsdlBuilder.java:43)
     at weblogic.wsee.tools.jws.jaxrpc.JAXRPCProcessor.process(JAXRPCProcessor.java:27)
     at weblogic.wsee.tools.jws.process.CompositeProcessor.process(CompositeProcessor.java:47)
     at weblogic.wsee.tools.jws.build.JwsCompiler.buildWebServices(JwsCompiler.java:522)
     ... 48 more
Caused by: weblogic.wsee.bind.buildtime.BindingException: ERROR ! could not add Xml Schema Type for XmlBean named '\[com.domain.UserDocument\]'. This is completely unexpected and might be caused by missing *.xsb and *.xsd files in the build environment. The building and running of this Service is likely to FAIL.
     at weblogic.wsee.bind.buildtime.internal.SoapAwareJava2Schema.bindAsExplodedTylar(SoapAwareJava2Schema.java:1414)
     at weblogic.wsee.bind.buildtime.internal.TylarJ2SBindingsBuilderImpl.createBuildtimeBindings(TylarJ2SBindingsBuilderImpl.java:216)
     at weblogic.wsee.tools.jws.jaxrpc.JAXRPCWebServiceInfo.createBindings(JAXRPCWebServiceInfo.java:223)
     ... 52 more

HI,
I hope this issue can resolved by adding this patch CR349256
Try to contact weblogic support to get more details about this patch.
Regards,
Kal.

Consuming peoplesoft webservices using JSF application gives error

Hi,
I am using Jdeveloper 11g to consume a peoplesoft webservice which does the basic datbase operations.
I have been successful in creating a proxy using the wsdl file and using JAX-WS approach to achieve the same.
I can connect to the webservice using the proxy client.
But when i package the proxy( create a jar) and import in my web application (JSF application), i am running into following error.
<ActionListenerImpl><processAction> com.sun.xml.ws.streaming.XMLStreamReaderException: unexpected XML tag. expected: {http://peoplesoft.com/KCM_WEB_CASE_CI}Get__CompIntfc__KCM_WEB_CASE_CIResponse but found: {http://schemas.xmlsoap.org/ws/2002/xx/secext}Get__CompIntfc__KCM_WEB_CASE_CIResponse
javax.faces.el.EvaluationException: com.sun.xml.ws.streaming.XMLStreamReaderException: unexpected XML tag. expected: {http://peoplesoft.com/KCM_WEB_CASE_CI}Get__CompIntfc__KCM_WEB_CASE_CIResponse but found: {http://schemas.xmlsoap.org/ws/2002/xx/secext}Get__CompIntfc__KCM_WEB_CASE_CIResponse
     at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:102)
     at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102)
     at javax.faces.component.UICommand.broadcast(UICommand.java:387)
     at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:475)
     at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:756)
     at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:82)
     at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
     at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: com.sun.xml.ws.streaming.XMLStreamReaderException: unexpected XML tag. expected: {http://peoplesoft.com/KCM_WEB_CASE_CI}Get__CompIntfc__KCM_WEB_CASE_CIResponse but found: {http://schemas.xmlsoap.org/ws/2002/xx/secext}Get__CompIntfc__KCM_WEB_CASE_CIResponse
     at com.sun.xml.ws.streaming.XMLStreamReaderUtil.verifyTag(XMLStreamReaderUtil.java:214)
     at com.sun.xml.ws.streaming.XMLStreamReaderUtil.verifyTag(XMLStreamReaderUtil.java:222)
     at com.sun.xml.ws.client.sei.ResponseBuilder$DocLit.readResponse(ResponseBuilder.java:531)
     at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:127)
     at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:95)
     at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:135)
     at $Proxy135.getCompIntfcKCMWEBCASECI(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at weblogic.wsee.jaxws.spi.ClientInstance$ClientInstanceInvocationHandler.invoke(ClientInstance.java:363)
     at $Proxy136.getCompIntfcKCMWEBCASECI(Unknown Source)
     at project1.proxy.KCM_WEB_CASE_CISoapClient.getKCMMethod_final(KCM_WEB_CASE_CISoapClient.java:618)
     at login.view.Handler.CRMSearchHandler.getSearchResults(CRMSearchHandler.java:18)
     at login.view.backing.Login.search(Login.java:54)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.sun.el.parser.AstValue.invoke(AstValue.java:157)
     at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283)
     at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88)
I am not sure what else i need to import or rather how to package the proxy classes to get it working.
Any help will be highly appreciated.
I even tried creating a webservice proxy in the JSF project instead of importing the jar, yet i am getting the same error, but the irony is that when i run just the proxy class(standalone with main method) i can get access to the webservice.
Thanks
Ash
Edited by: [email protected] on Jun 8, 2010 2:38 PM

Well,
There is a issue with analyzer capturing SOAP traffic when using with secure proxies, so that is why you are not seeing any data there.
And I think if you will try your jax-rpc code again, it might work as there was nothing incorrect in your code, so might be that the whole config was corrupt which was throwing out incorrect error(s).
About a web service with credentials, you can quickly create one.
Have a java class like the following:
import javax.jws.WebService;
import weblogic.jws.Policy;
@WebService
@Policy(uri = "policy:Wssp1.2-2007-Https-UsernameToken-Plain.xml")
public class Class1 {
public Class1() {
super();
public String sayHello() {
return "Hi";
The procy code for this will be something like:
private static Class1Service class1Service;
public static void main(String[] args) {
try {
class1Service = new Class1Service();
Class1 class1 = class1Service.getClass1Port();
Map<String, Object> requestContext = ((BindingProvider) class1).getRequestContext();
setPortCredentialProviderList(requestContext);
// Add your code to call the desired methods.
System.out.println(class1.sayHello());
} catch (Exception ex) {
ex.printStackTrace();
public static void setPortCredentialProviderList(Map<String, Object> requestContext) throws Exception {
// TODO - Provide the required values
String username = "weblogic";
String password = "weblogic1";
List<CredentialProvider> credList = new ArrayList<CredentialProvider>();
// Add the necessary credential providers to the list
credList.add(getUNTCredentialProvider(username, password));
//credList.add(getBSTCredentialProvider(clientKeyStore, clientKeyStorePassword, clientKeyAlias, clientKeyPassword, serverKeyStore, serverKeyStorePassword, serverKeyAlias, requestContext));
//credList.add(getSAMLTrustCredentialProvider());
requestContext.put(WSSecurityContext.CREDENTIAL_PROVIDER_LIST, credList);
Thanks,
Vishal

Which protocol does weblogic7 webservice use?

hello
i know that the java webservice development use either axis or soap protocol,but
i don't know which protocol does the weblogic7 webservice use?
thank you

We have our own implementation of soap.
WebLogic Web services use Simple Object Access Protocol (SOAP) 1.1 and 1.2
as the message format and HTTP as the connection protocol. See SOAP 1.1 with
Attachments.
Note: WebLogic Web services accept both SOAP 1.1 and 1.2 incoming
requests, but produce only SOAP 1.1 outgoing responses.
http://e-docs.bea.com/wls/docs70/webserv/overview.html
Google.........
http://google.bea.com/search?q=soap+version&ie=&site=bea&output=xml_no_dtd&c
lient=bea&lr=&proxystylesheet=http%3A%2F%2Fdev2dev.bea.com%2Fimages%2Fdev2de
v.xsl&oe=
cheers
mbg
"zhebincong" <[email protected]> wrote in message
news:3e7d2ed3$[email protected]..
>
hello
i know that the java webservice development use either axis or soapprotocol,but
i don't know which protocol does the weblogic7 webservice use?
thank you

How can I use XMLBeans in a Web Services client?

How can I use XMLBeans in a standalone Java client with a Web Service?
I posted the message below earlier in the year, but have not yet been successful
in my
attempts.
regards
Eddie
Hi,
I'm trying to using XMLBeans to send a document to a web service from a standalone
Java client. I'm using the PurchaseOrder (easypo) example document, and the service
expects a parameter of type PurchaseOrderDocument. The client proxy class generated
by WebLogic Workshop, however, expects to send a parameter of type PurchaseOrder.
In the client, I can instantiate a PurchaseOrderDocument, and then obtain a PurchaseOrder
(e.g. pod.getPurchaseOrder() ), but the returned class is not compatible with
the PurchaseOrder type that the client proxy expects.
In a previous attempt (not using Workshop), the client would not compile because
it expected to send a non-abstract class with a public default constructor (presumably
a JAX-RPC requirement), and XMLBeans had generated an interface.
Any help would be greatly appreciated!
thanks & regards
Eddie

I have been experiencing similar problems with the HTML Editor and have managed to find an answer that should start to answer some of my questions. The Apex HTML Editor Standard is actually an HTML editor called FCKeditor. The FCKeditor has a Javascript API that can be found at http://docs.fckeditor.net/FCKeditor_2.x/Developers_Guide/JavaScript_API. Unfortuately this doesn't seem to give the whole answer and I found more at http://www.houseoffusion.com/groups/cf-talk/thread.cfm/threadid:49607.
I needed to get the text entered within my html editor standard (e.g. P1_MYTEXT) and use it within my javascript function. I did this by using the following script
<script language="JavaScript" type="text/javascript">
function showtext(){
var oEditor = FCKeditorAPI.GetInstance('P1_MYTEXT');
var editortext = escape(oEditor.GetXHTML(oEditor.FormatOutput));
alert(editortext);
</script>
Hope this helps.
Matthew

Error while testing webservice using SOAP

Hi,
While i was testing my published webservice using soap-ui it gave me following error,
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Body>
<soap:Fault>
<faultcode>soap:Server</faultcode>
<faultstring>Internal SOAP Processing Failure</faultstring>
<detail/>
</soap:Fault>
</soap:Body>
</soap:Envelope>
and in the event log i can see a event as follows and there is no warning or error
Upon investigation i got to know the following steps might solve the problem..i.e..
- Is the receive location for the SOAP webservice enabled? - YES
- Can you browse to (the WSDL of) the webservice? Is displayed correctly? -YES
- Is the webservice configured to run in the correct application pool? -YES
-The user under which application pool is running have the read/write permission on the %temp% folder.-Dont Know how to check
-In IIS,Check the identity of the application pool on which Web service is running and make sure that the user is the member of both “IIS_WPG” and “BizTalk Isolated host users”.
-DONT Know how to check
Please Help me in guiding me in the last two points
and if there are any other solutions for this..
Thanks,
Sarva.

You mentioned you checked that the webservice is configured under correct application pool. you can find the user under which the application pool is configured (open iis- > select application pools -> find out the "Identity column" to
know the user for your application pool.
-The user under which application pool is running have the read/write permission on the %temp% folder.-Dont Know how to check
Go to run -> type "%temp%" -> Go one step back -> Right click to the folder -> Properties -> Security -> check the application pool user is present under "Group or user names"
-In IIS,Check the identity of the application pool on which Web service is running and make sure that the user is the member of both “IIS_WPG” and “BizTalk Isolated host users”.
-DONT Know how to check
Refer How to Add Service Account to the IIS_WPG Group to add your application pool user under IIS_WPG. Also similar activity to add your service account to "BizTalk Isolated
host users" if it is local groups. Or Ask your network support team if "BizTalk Isolated host users" is domain group.
Please Help me in guiding me in the last two points
and if there are any other solutions for this..
Thanks,
Sarva.
Your event viewer might have more information pointing exactly what is causing "Internal SOAP processing failure".
Also refer this
which might be helpful for you.
If this answers your question please mark it as Answer and if this post is helpful, please vote as helpful. Thanks !

Error while posting to Webservice using WCF-BasicHttp adapter

Hi,
I am getting the below exception when i am posting a request to a .asmx webservice using the Wcf-BasicHttp adapter.
I am able to call the same service with the SOAP adapter successfully. Could you please let me know any resolutions for the same.
The adapter failed to transmit message going to send port "MySendPort" with URL "http://myservice.com/Web.Services/service1.asmx". It will be retransmitted after the retry interval specified for this Send Port. Details:"System.ServiceModel.ProtocolException:
The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (text/xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes
of the response were: '
<html>
    <head><link rel="alternate" type="text/xml" href="/Web.Services/Service1.asmx?disco" />
    <style type="text/css">
       BODY { color: #000000; background-color: white; font-family: Verdana; margin-left: 0px; margin-top: 0px; }
       #content { margin-left: 30px; font-size: .70em; padding-bottom: 2em; }
       A:link { color: #336699; font-weight: bold; text-decoration: underline; }
       A:visited { color: #6699cc; font-weight: bold; text-decoration: underline; }
       A:active { color: #336699; font-weight: bold; text-decoration: underline; }
       A:hover { color: cc3300; font-weight: bold; text-decoration: underline; }
       P { color: #000000; margin-top: 0px; margin-bottom: 12px; font-family: Verdana; }
       pre { background-color: #e5e5cc; padding: 5px; font-family: Courier New; font-size: x-small; margin-top: -5px; border: 1px #f0f0e0 solid; }
       td { color: #000000; font-family: Verdana; font-size: .7em; }
       h2 { font-size: 1.5em; font-weight: bold; margin-top: 25px; margin-bottom: 10px; border-to'.
Server stack trace:
   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndRequest(IAsyncResult result)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at System.ServiceModel.Channels.IRequestChannel.EndRequest(IAsyncResult result)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.RequestCallback(IAsyncResult result)".
Regards,
Ujjwal
-Ujjwal

Where does the HTML indicate that the Service is not running??
The error message " The content type text/html; charset=utf-8 of the response message does not match
the content type of the binding (text/xml; charset=utf-8)" points to a bug in the WCF-BasicHttp described here:
http://social.msdn.microsoft.com/Forums/en-US/11796bf5-ba6a-4878-977e-5c854642f67c/the-content-type-textxml-charsetiso88591-of-the-response-message-does-not-match-the-content?forum=biztalkgeneral
Although not 100% the same, the conclusion here was to still use the old Adapter :-(
Morten la Cour

Error while trying to access WebService using WSIF

Hi All,
I am a new developer to WebServices. I read up information on how to create the WSDL and stubs using JDev 10g (10.1.2) using the wsa.jar that ships with the download. After creating my WSDL and the necessary proxies, when I try to run my client application (which runs in the same covatiner, standalone OC4j), I get the below error :
06/09/29 13:42:21 org.apache.wsif.WSIFException: org.apache.wsif.providers.ejb.WSIFOperation_EJB@15b0c83 : Could not invoke 'getOrderList'; nested exception is:
org.apache.wsif.WSIFException: Error while determining signature of method getOrderList : The meta information is not consistent.; nested exception is:
org.apache.wsif.WSIFException: parameters
06/09/29 13:42:21 at org.apache.wsif.providers.ejb.WSIFOperation_EJB.executeRequestResponseOperation(WSIFOperation_EJB.java:1259)
06/09/29 13:42:21 at org.apache.wsif.base.WSIFClientProxy.invoke(WSIFClientProxy.java:339)
06/09/29 13:42:21 at $Proxy3.getOrderList(Unknown Source)
I am trying to expose a Stateless Session EJB as a WebService, which contains a method called getOrderList(). This method returns an array of a complex type (Java Bean).
I am, however, able to succesfully access the WebService using the SOAP/HTTP protocol.
My client code is as follows:
WSIFServiceFactory factory = WSIFServiceFactory.newInstance();
WSIFService service = factory.getService("<path to wsdl>", null, null, "http://sample.com/", "OrderService");
orderService = (OrderService) service.getStub("WsifEjb", OrderService.class);
Not sure what am I missing here. If any further information is required in order to resolve this, please let me know.
Thanks,

You are trying to get 2 databases connected... so, you need to insure that FDEV can find and connect to ABCD.
So, from your FDEV database server, you can do 2 things (from command prompt):
1* tnsping ABCD (this will validate that the entry exists in your tnsnames.ora on your FDEV server, and that a valid listener can be found on remote server)
when above command succeeds:
2* sqlplus apps/appsdev@ABCD;
when you have established the connection, then you are SURE that your can connect ABCD database from FDEV database server. It will also validate the username / password combination, create session privilige, account not locked, etc.....
Please check the above, and post here the results.
HTH,
Thierry

Creation of webservices using SOAMANAGER

Hi All,
Can someone let me know how to create web services using the new transaction SOAMANAGER. I have earlier used WSCONFIG & WSADMIN transactions but these seem to obsolete in the latest versions.
I have done the following steps so far
1. Create a function module with required parameters
2. Set the FM as RFC enabled and activated.
3. Created the webservice using the wizard in SE37
When i checked for the node for the webservice in SICF it was inactive. Hence i had right clicked and activated the service.
I have also checked the following blog,
/people/bv.pillai/blog/2008/01/27/new-service-definitions-in-the-abap-development-environment-soamanager-150-sap-nw-70-sp14
I navigated to the following path to test my webservice
Txn: SOAMANAGER->Business admin->web service admin-><Z* webservice>Apply selection->Open Web Service navigator for selected binding
When i try this i am getting an error "J2EE host or port not specified; define them under "System Settings"
Can someone let me know in identifying what i have missed out?
Also it would be great if someone can let me know the URL for SAP help documentation on SOAMANAGER. I am unable to locate it in SAP library.
Thanks,
Prasath N

hi,
you don't need the webservice navigator to activate a service or binding. it's just there to allow testing of the service if you have no other options. like the "webservice homepage" in WSADMIN the webservice navigator requires a J2EE instance up, running and configured.
the help pages for SOAMANAGER are to be found under [this general node|http://help.sap.com/saphelp_nw70/helpdata/EN/9b/dad1ae3908ee44a5caf57e10918be9/frameset.htm].

Error in consuming webservices using ABAP

Dear Gurus,
I am trying to consume webservices using ABAP. We dont have XI installed and no java instance installed.
I created a customer proxy through SE80 and generated a proxy class by giving a WSDL link and also defined logical port. Traditionally followed the steps. But while testing webservices , I get a ICF error.
The error is as follows:
SOAP : 1:023 SRT : Processing error in internet communication framework ("ICF error when recieving the response ICM_HTTP_CONNECTION_FAILED)
Please let me know the cause of this error and solution to be provided.
I also tried to call the method from an abap program, But I get CX_AI_SYSTEM_FAULT exception.
Awaiting your replies.
Thanks in advance for your support and valuable time.
Thanks
Gurushanthi

Hi Gurushanthi,
It could one of several problems, examples:
- A firewall setting
- http communication out disabled by Basis team or
- The logical port wasn't configured correctly.
Try the suggestions in this thread to narrow down the reason (particularly the telnet test from the server):
[Re: Error testing external web service ICM_HTTP_CONNECTION_FAILED;
Regards, Trevor

How to call the webservice using ADF Bindings

Hi,
I have created a Data control of the webservice using the WSDL Url. (Web Service is secured and so i have given the security configurations)
Webservice works fine when i drag and drop that in to a jspx page.
Now i want to call the service from a java class so that i can modify the data a bit. ( Tried with Webservice client and proxy and it is not working)
Please provide me with some link or solution as how to achieve this.
Thanks,
Hari

You need to have the method binding in the page that calls the Web service - otherwise you can't use the binding layer.
If you don't want to use the binding layer you can have your managed bean just call out to the Web service directly - you can use JDeveloper's Web service proxy creation wizard to get the code for this.
If you want to call the Web service through binding outside of the page you can also drag the method into a taskflow as a method call.

WLS 9: WebServices using XMLBeans

Similar Messages

Maybe you are looking for