How to get a doc//literal web service with JWSDP1.3

I can build a rpc/encoded service (based the tutorial),
but I need a doc/literal.
Because I have a J2ME client.
How can I do it?
thanks

Do you want to see if Arun's white paper helps you? I checked and he talkks about this at the end of his first scenario, at https://jax-rpc.dev.java.net/whitepaper/1.1/index-part2.html#Scenario1.
- eduard/o

Similar Messages

How to create document/literal web services with WLS7

How do you create document/literal web services with WLS7 ( not workshop)
- Is it possible with servicegen and stateless EJBs as the backend component?
The default is RPC/Soap-encoded is there anyway to craft the web-services.xml
to make it document/literal
- Is it possible with the JMS-implemented web services - have not tried this yet
- Is there another mechanism?

That would be the <web-service> element in the web-services.xml file, of course.
"Michael Wooten" <[email protected]> wrote:
>
Hi Rich,
Try adding a style="document" attribute to the starting <web-service>
element.
The might be a way to get <servicegen> to do this for you, but I haven't
found
it yet :-)
Regards,
Mike Wooten
"Rich Muth" <[email protected]> wrote:
How do you create document/literal web services with WLS7 ( not workshop)
- Is it possible with servicegen and stateless EJBs as the backend component?
The default is RPC/Soap-encoded is there anyway to craft the web-services.xml
to make it document/literal
- Is it possible with the JMS-implemented web services - have not tried
this yet
- Is there another mechanism?

Document/literal web service with WSDL

Hi
I is so hard to get an easily written example of how to do a Document/literal web service in java, to generate a WSDL descripbing it and then deploying it on Apache.
I first belived that I should use JAXM. But I think it is just SOAP and there is no way to generate a WSDL file for the JAXM service, or??
It seems that u can to document/literal style using JAX-RPC, but this is VERY strange since RPC style is the direct opposite of Document style.
well, well
I would be very greatful for information here.
regards
/Rassol

JWSDP 1.2 includes the WS-I sample application in JWSDP_HOME/wsi-sampleapp. Several components of
this application use document-literal operations. The architecture of the application is described
here http://ws-i.org/SampleApplications/SupplyChainManagement/2003-04/SCMArchitecture1.0-BdAD.pdf
The WSDL for the services is availabe from URLs in the document.
As you say, the trick is generating the WSDL for a new service. You have two options: 1. Modify
existing WSDL yourself. This might be fairly easy, since the only major changes will be in the
schema. Then use a tool to generate Java source code from the WSDL. 2. Use a tool to generate WSDL
from source files.
I prefer option 1 myself, since that gives me total control over the schema. It allows me to
serialize certain parts of the SOAP message as body elements, others as attributes, and others as
header elements. Then I use the Apache Axis tool WSDL2Java with the "-s" option to generate skeleton
service files. One big advantage to this approach is that WSDL2Java generates JavaBean class for the
types in the WSDL schema, so I don't need to build the SOAP message with SAAJ. A service client
generates stubs and calls the service exactly as it would for an rpc/encoded service.
wscompile also generates service files from WSDL if you give the "-gen:server" option, but I've only
used Axis for my services.
Here's a sample WSDL for a document/literal service you can modify as you need. I checked it with
the WS-I testing tools to be sure it conforms to the WS-I Basic Profile 1.0a (available at www.ws-
i.org). Notice that the processPo operation is a request-response type operation, even though it has
a document/literal style. This follows the recommendations in the Basic Profile.
Cheers,
Mike
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="http://www.ltree.com/wsdl/po" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:impl="http://www.ltree.com/wsdl/po" xmlns:intf="http://www.ltree.com/wsdl/po" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns1="http://www.ltree.com/types/po" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
          xmlns:tns1="http://www.ltree.com/types/po"
          xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
          targetNamespace="http://www.ltree.com/types/po"
          elementFormDefault="qualified">
     <xsd:import namespace="http://schemas.xmlsoap.org/soap/envelope/"
                 location="http://schemas.xmlsoap.org/soap/envelope/"/>
     <xsd:complexType name="LineItem">
         <xsd:sequence>
             <xsd:element name="itemId" type="xsd:string"/>
             <xsd:element name="quantity" type="xsd:int"/>
         </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="PurchaseOrder">
         <xsd:sequence>
             <xsd:element name="customerName" type="xsd:string"/>
             <xsd:element name="lineItem" type="tns1:LineItem"
                      minOccurs="1" maxOccurs="unbounded" />
         </xsd:sequence>
         <xsd:attribute name="purchaseOrderId" type="xsd:string" use="required"/>
     </xsd:complexType>
     <xsd:element name="purchaseOrder" nillable="true" type="tns1:PurchaseOrder"/>
     <xsd:complexType name="CallbackEndpoint">
         <xsd:attribute name="location" type="xsd:anyURI" use="required"/>
     </xsd:complexType>
     <xsd:element name="callbackEndpoint" nillable="false" type="tns1:CallbackEndpoint"/>
     <xsd:complexType name="PurchaseOrderAck">
         <xsd:sequence>
             <xsd:element name="poId" type="xsd:string"/>
         </xsd:sequence>
     </xsd:complexType>
     <xsd:element name="purchaseOrderAck" nillable="true" type="tns1:PurchaseOrderAck"/>
     <xsd:complexType name="InvalidCustomerNameException">
      <xsd:sequence>
       <xsd:element name="message" nillable="true" type="xsd:string"/>
       <xsd:element name="customerName" type="xsd:string"/>
      </xsd:sequence>
     </xsd:complexType>
     <xsd:element name="invalidCustomerNameException" nillable="true"
                  type="tns1:InvalidCustomerNameException"/>
</xsd:schema>
</wsdl:types>
   <wsdl:message name="processPoRequest">
      <wsdl:part name="callbackEndpoint" element="tns1:callbackEndpoint"/>
      <wsdl:part name="purchaseOrder" element="tns1:purchaseOrder"/>
   </wsdl:message>
   <wsdl:message name="processPoResponse">
      <wsdl:part name="purchaseOrderAck" element="tns1:purchaseOrderAck"/>
   </wsdl:message>
   <wsdl:message name="invalidCustomerNameException">
      <wsdl:part name="fault" element="tns1:invalidCustomerNameException"/>
   </wsdl:message>
   <wsdl:portType name="PurchaseOrderHandler">
      <wsdl:operation name="processPo">
         <wsdl:input message="impl:processPoRequest" name="processPoRequest"/>
         <wsdl:output message="impl:processPoResponse" name="processPoResponse"/>
         <wsdl:fault message="impl:invalidCustomerNameException" name="invalidCustomerNameException"/>
      </wsdl:operation>
   </wsdl:portType>
   <wsdl:binding name="PurchaseOrderHandlerPortSoapBinding" type="impl:PurchaseOrderHandler">
      <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
      <wsdl:operation name="processPo">
         <wsdlsoap:operation soapAction="" style="document"/>
         <wsdl:input name="processPoRequest">
            <wsdlsoap:header message="impl:processPoRequest" part="callbackEndpoint" use="literal"/>
            <wsdlsoap:body parts="purchaseOrder" use="literal"/>
         </wsdl:input>
         <wsdl:output name="processPoResponse">
            <wsdlsoap:body use="literal"/>
         </wsdl:output>
         <wsdl:fault name="invalidCustomerNameException">
            <wsdlsoap:fault name="invalidCustomerNameException" use="literal"/>
         </wsdl:fault>
      </wsdl:operation>
   </wsdl:binding>
   <wsdl:service name="PurchaseOrderHandlerService">
      <wsdl:port binding="impl:PurchaseOrderHandlerPortSoapBinding" name="PurchaseOrderHandlerPort">
         <wsdlsoap:address location="http://localhost:8080/po/services/PurchaseOrderHandlerService"/>
      </wsdl:port>
   </wsdl:service>
</wsdl:definitions>

How to get, handle and check web service response?

Hello All!
We test web services and try to use e-Tester for this.
We have some problems with validation of service response. Maybe somebody can help or advice us?
Service method returns the list of Cards (total is about 300 items) with attributes.
Below is the sample of one card properties.
- <Cards>
- <UserCard>
- <characteristics>
- <item>
<Name>ARM</Name>
<Value>78</Value>
</item>
- <item>
<Name>BAT</Name>
<Value>40</Value>
</item>
- <item>
<Name>SPD</Name>
<Value>30</Value>
</item>
- <item>
<Name>STR</Name>
<Value>40</Value>
</item>
</characteristics>
<ID>1</ID>
<FirstName>A.J.</FirstName>
<LastName>Burnett</LastName>
<PlayerName>A.J. Burnett</PlayerName>
- <Team>
<Name>Blue Jays</Name>
<City>Toronto</City>
</Team>
<cardid>1</cardid>
- <Flags>
<IsFavorite>false</IsFavorite>
<IsForPosters>false</IsForPosters>
<IsForTrade>false</IsForTrade>
<IsToppCard>false</IsToppCard>
</Flags>
<Count>0</Count>
</UserCard>
+ <UserCard>
+ <UserCard>
+ <UserCard>
In one test case we need to check the state of Count property (0 or 1) for all cards, count the quantity of cards with Count=1 and check that it equals to 8.
So the question is how to get the service request to the VBA for analyzing and verification?
Thanks a lot!

Have any other ideas?

Doc/Literal Web Services in OmniPortlet

Hi I was wondering if OmniPortlet has a problem calling Document/Literal type of Web Services? Because I tried calling 2 such WS, one of which is .NET, the other is developed in JDeveloper.
In both cases, OminPortlet sends the encodingStyle attribute in its SOAP body, which shouldn't occur for doc/lit types right? The .NET WS can accept the request though, while the JDev one can't.

This is the WSDL for the .NET service:
<wsdl:definitions targetNamespace="http://tempuri.org/">
     <wsdl:types>
     <s:schema elementFormDefault="qualified" targetNamespace="http://tempuri.org/">
     <s:element name="HelloWorld">
<s:complexType/>
</s:element>
     <s:element name="HelloWorldResponse">
     <s:complexType>
     <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="HelloWorldResult" type="s:string"/>
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
     <wsdl:message name="HelloWorldSoapIn">
<wsdl:part name="parameters" element="tns:HelloWorld"/>
</wsdl:message>
     <wsdl:message name="HelloWorldSoapOut">
<wsdl:part name="parameters" element="tns:HelloWorldResponse"/>
</wsdl:message>
     <wsdl:portType name="ServiceSoap">
     <wsdl:operation name="HelloWorld">
<wsdl:input message="tns:HelloWorldSoapIn"/>
<wsdl:output message="tns:HelloWorldSoapOut"/>
</wsdl:operation>
</wsdl:portType>
     <wsdl:binding name="ServiceSoap" type="tns:ServiceSoap">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http"/>
     <wsdl:operation name="HelloWorld">
<soap:operation soapAction="http://tempuri.org/HelloWorld" style="document"/>
     <wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
     <wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
     <wsdl:binding name="ServiceSoap12" type="tns:ServiceSoap">
<soap12:binding transport="http://schemas.xmlsoap.org/soap/http"/>
     <wsdl:operation name="HelloWorld">
<soap12:operation soapAction="http://tempuri.org/HelloWorld" style="document"/>
     <wsdl:input>
<soap12:body use="literal"/>
</wsdl:input>
     <wsdl:output>
<soap12:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
     <wsdl:service name="Service">
     <wsdl:port name="ServiceSoap" binding="tns:ServiceSoap">
<soap:address location="http://137.132.1.150:83/service.asmx"/>
</wsdl:port>
     <wsdl:port name="ServiceSoap12" binding="tns:ServiceSoap12">
<soap12:address location="http://137.132.1.150:83/service.asmx"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

How to get original message in web service implementation and proxy

Hi,
We have a java web service and its client (proxy) generated from WSDL by JDev wizards. All the parameters are mapped to classes, but we need a way to get the original message we send and receive in order to log it.
Is there any way to get the SOAP message that is being sent/received?
Thank you

If you are using 10.1.3 or later releases, you can use the JAX-RPC handler to gain access to the message. Your SOAP payload can then been manipulated using the SAAJ APIs. You have also the option to log messages directly from OWSM.
Best,
-Eric

How to start a process via web service with automatically run first screen

Hi guys,
we want to start the process via web service and skip the inbox presentation of the first human activity of the process. It means that the first activity should start automatically by clicking the link (wsdl link).
Is there any opportunity to realize this thought?
THX
Regrads
Phil

Hi Phil,
You may refer to my blog series for steop by step procedure on how to initiate a BPM workflow through webservice. Below are the links:
/people/arafat.farooqui/blog/2009/08/13/introduction-to-sap-netweaver-bpm-part-4
/people/arafat.farooqui/blog/2010/06/23/introduction-to-sap-netweaver-bpm-part-5
Hope this helps!!
Regards,
Arafat

Get a URL for web service with HTTPS

Hi,
After deploying all required configuration for secure WS, I'm trying to generate a wsdl to give to the third party. I m using the Despay WSDL in Integration Directoryb but that WSDL containt a like staring with the HTTP instead of HTTPS! My question is how to generate a wsdl file with an HTTPS url tot he web service,
Thanks in advance,
Fred.

Hi,
>>>WSDL in Integration Directoryb but that WSDL containt a like staring with the HTTP instead of HTTPS! My question is how to generate a wsdl file with an HTTPS url tot he web service,
you don't use the URL from ID - you need to create one yourself and put it there in the generator
Regards,
Michal Krawczyk

How to implement the security in web service with Weblogic 9.2

I've generated web service by Web Logic 9.2 using existing WSDL (as per client requirement) and want to add security policy for authentications.
I have used following annotation in service class.
@Policies({
@Policy(uri="policy:Auth.xml" , direction=Policy.Direction.inbound)
But it gives compilation time error with following message.
The Policy and Policies annotations are not allowed on jws file when compiledWsdl option is specified
I've also tried to modify the WSDL to accommodate policy configuration and again generate the web service but problem is being as it is.
If anybody has solution of this issue then please let me know ASAP.

Did you get an answer to your question? I have the same problem with WebLogic 10.0.

Getting error in cxf web service with spring 3.0.

I developed a web service using cxf. Implemented the client codes to invoke the web service.
The client codes running fine through JUnit test case but whenever I try to invoke the client through another service (after actual UI integration),
its throwing error while initializing the service. I'm using cxf 2.2.7 with spring 3.0
     // configuration stuffs
     public static final QName SERVICE_NAME = new QName("http://perksplus.com/WebServices/HealthPrize/Rewards/", "Rewards");
     //@Value("@{perks.api.wsdl.location}")
     private String wsdlLocation="https://www.perksplus.com/WebServices/HealthPrize/Rewards.asmx?wsdl";
     protected Rewards loadWSDL(){
        URL wsdlURL = null;
          try {
              setApplicationContext(applicationContext);
              Resource lResource = getApplicationContext().getResource(wsdlLocation);
               wsdlURL = lResource.getURL();
          } catch (MalformedURLException e) {
               LOG.error("Invalid wsdl URL"+e);
          } catch (IOException e) {
               LOG.error("Error while loading the file"+e);
          this.rewards = new Rewards(wsdlURL, SERVICE_NAME); *// ERROR THROWING AT THIS LINE*
          return this.rewards;
     }Error stacktrace
javax.servlet.ServletException: org.springframework.web.util.NestedServletException: Handler processing failed; nested exception is java.lang.LinkageError: loader constraint violation: when resolving overridden method "org.apache.cxf.bus.spring.ControlledValidationXmlBeanDefinitionReader.doLoadBeanDefinitions(Lorg/xml/sax/InputSource;Lorg/springframework/core/io/Resource;)I" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, org/apache/cxf/bus/spring/ControlledValidationXmlBeanDefinitionReader, and its superclass loader (instance of org/apache/catalina/loader/StandardClassLoader), have different Class objects for the type org/springframework/core/io/Resource used in the signature
Can someone please help me here, to figure out whats wrong I'm doing or if I' m missing anything which causing this error?
(Thanks in adv).

My understanding of exception stack trace is that the two class loader are unable to match the argument type org/springframework/core/io/Resource in original method and its overridden method. And original method class loader and overridden method class loader are different.
This normally happens due to class clashes.

How to get JSON item in web service workflow?

Im tried to get json item in workflow,But was unable to obtain "RtnCode",how to do it?
This my JSON,
"MerchantID": "1032017",
"RtnCode": "2",
"RtnMsg": "Get Succeeded",
My workflow :
Get RtnCodefrom
Variable: DealItems
Error code:
RequestorId: f85b0795-6682-fde7-0000-000000000000.
Details: An unhandled exception occurred during the execution of the workflow instance.
Exception details: System.InvalidOperationException: Looking up a value using a key is not supported on an instance of 'Microsoft.Activities.Dynamic.DynamicPrimitive'. at Microsoft.Activities.Dynamic.DynamicItem.TryGetValue(String key, DynamicItem&
value) at Microsoft.Activities.Dynamic.DynamicValueBuilder.PathSegmentFactory.ObjectPathSegment.Get(DynamicItem obj) at Microsoft.Activities.GetDynamicValueProperty`1.Execute(CodeActivityContext context) at System.Activities.CodeActivity`1.InternalExecute(ActivityInstance
instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation) Exception from activity
GetDynamicValueProperty<String> Start Sequence Flowchart Sequence Pay.WorkflowXaml_07f732da_c82a_4234_abd5_34c32c637413

Hi Felaray,
I have a similar issue and what I tried to do is to install JSON.NET in my project and used the "Assign" activity (under "Primitives" category on the toolbox) to assign the string to an object:
Newtonsoft
.Json.JsonConvert.DeserializeObject(resultFromCustomActivity)
but unfortunately did not work. I am getting this exception:
Visual Studio 2013 Workflow: Failed to translate expression because of the following error: Translating the method or one of its overloads to an activity is not supported
If you cannot really change the source header, you might need to create a code custom activity and pass in your string and use JSON.NET, parse it and return what you want.
Another "easier" option might involve doing some nasty parsing (using the Assign Activity) by finding the index of your "RntCode:" and getting the next set of characters before the comma. Since the .NET classes to utilize are limited
it would be worth trying to use a RegEx
resultFromCustomActivity
.Substring(0,
10)

Securing single point of entry doc-lit web services

I am designing doc-lit web services with a single point of entry, but the doc can contain requests of various types, with varying levels of authorization on the 'methods' being called by the web service as a result of the passed requests. I'm looking for a standards-compliant means of accomplishing this, or at least some method that will not be insanely difficult to move to a standards-based security implementation when they become available. I do not want to use SSL/TLS, but do want to stick to standards including WS-Security, XML-Encryption and XML-DSig. I would also like to use OID/SSO with certificate-based authentication.
What are my options as far as existing tools, techniques, etc for this in a Java/Oracle environment? Is there anything in Oracle BPEL that could help me in this quest?
Appreciate any advice, pointers, shared experiences, etc on this - I'm a little lost in the trees right now!
Thanks Much,
Jim Stoll

Eric - appreciate the tip. The link to the JDev files for the OBE article doesn't work though (ie, in the article, there is a link to download the source for the project) - is there an alternate way that I could get hold of that code? Even something as simple as someone emailing it to me would work - I desperately need to move forward on this stuff. (There's another sample at http://www.oracle.com/technology/products/jdev/101/howtos/securews/index.html, but that one throws exceptions and I can't seem to get any help on it via the forum or Oracle Support, either...)
Thanks for your assistance!
Jim

Web services with XFire.

Hi,
I am completely new to web service with XFire topic and want to work on any sample application to get some idea on web services with XFire.

check your Tomcat documentation and try to test with relative path
Edited by: RezaRavasizadeh on Sep 2, 2008 5:40 PM

Problem Generating Document/Literal Web Service

Hi folks..
I am currently using JDeveloper 10.1.3 (Preview Edition) and I am having trouble getting the Create Java Web Service wizard to work correctly when generating a document/literal web service. After going through the wizard selecting the appropriate settings to generate a document/literal web service from my implementation I get the following error during generation.
oracle.j2ee.ws.common.tools.api.SeiValidationException
oracle.j2ee.ws.common.processor.modeler.rmi.RmiModeler.modelPort(RmiModeler.java:587)
oracle.j2ee.ws.common.processor.modeler.rmi.RmiModeler.buildModel(RmiModeler.java:455)
oracle.j2ee.ws.common.processor.config.ModelInfo.buildModel(ModelInfo.java:160)
oracle.j2ee.ws.common.processor.Processor.runModeler(Processor.java:76)
oracle.j2ee.ws.common.tools.wscompile.CompileTool.run(CompileTool.java:510)
oracle.j2ee.ws.tools.wsa.JavaToWsdlTool.createWSDL(JavaToWsdlTool.java:234)
oracle.j2ee.ws.metadata.JavaWebServiceCompiler.processAnnotations(JavaWebServiceCompiler.java:313)
oracle.j2ee.ws.metadata.JavaWebServiceCompiler.processAnnotations(JavaWebServiceCompiler.java:205)
oracle.j2ee.ws.metadata.JavaWebServiceCompiler.processAnnotations(JavaWebServiceCompiler.java:131)
oracle.j2ee.ws.tools.wsa.Util.processAnnotations(Util.java:77)
oracle.jdeveloper.webservices.model.java.JavaGenerator.generateWSDLFromAnnotations(JavaGenerator.java:1188)
oracle.jdeveloper.webservices.model.java.JavaGenerator.doGeneration(JavaGenerator.java:362)
oracle.jdeveloper.webservices.model.Generator.generateImpl(Generator.java:330)
oracle.jdeveloper.webservices.model.Generator.access$1000071(Generator.java:100)
oracle.jdeveloper.webservices.model.Generator$1$ReturningRunnable.run(Generator.java:250)
oracle.jdeveloper.webservices.model.GeneratorUI$GeneratorAction.run(GeneratorUI.java:344)
oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:526)
java.lang.Thread.run(Thread.java:534)
When I googled this error I actually get a hit for a thread here on this board, that looks VERY promising... but when I attempt to access it I get a message "Duscussion Forms Error" and I cant access it. (Very frustrating believe me.. :-)
Any help that you can give would be appreciated...
Thanks
Dave

Hi Dave,
One reason to have the SeiValidationException is when you do not follow the java bean convention for getter/setter or some of the public methods you want to expose are not throwing the right execption.
Using the command line utility genProxy [or the ant task] with the debug flag may give you some informations about the WSDL constructs WSA do not understand. Look at the following how-to to get started:
http://www.oracle.com/technology/tech/java/oc4j/1013/howtos/how-to-ws-bottomup/doc/how-to-ws-bottomup.html
If this does not help, can you share your WSDL with us ?
Thanks,
Eric

Problem with document/literal web services

Hi,
I need to publish a document\literal WSDL for a web service on my OC4J 10.1.2.2 because my app has an interface with a .NET system.
I generated the WSDL with JDEV 10.1.3.3 and tried to deploy it on an OC4J 10.1.2 using JDEV 10.1.2.
The deployment worked fine but when I'm trying to access the web service with the generated stub I'm getting the following message:
"These methods do not conform to the restrictions imposed by the web service implementation"
and then a list of these methods.
Later I tried to remove the parameters from the methods and regenerated the WSDL and it worked fine, but I need the methods with the parameters.
What can I do?
Thanks

Jason, have you made any progress with CF7 and WS Security?
It doesn't seem like enough information on this is available. Is it
even possible? and how?

How to get a doc//literal web service with JWSDP1.3

Similar Messages

Maybe you are looking for