Web Service XML Input Arguments Schema Validation

I'm new to web services, but we are currently implementing a number of Web Services that all take as arguments a single parameter which is an XMLBean, which has been generated by a XML Schema.
What I find surprising is that when I submit a SOAP message to the Web Service (through the http Web Service Tester inside eclipse), I can send any valid XML without getting a SOAP fault. Is there a way on the Web Service that I want the XML submitted to be validated against the XML Schema for that parameter?
Bit surprised I have to implement my own input argument validation, and there doesn't appear to be a standard way to do this. I must be missing soemthing surely? Why else would the Schema be in the WSDL?
Cheers
John

I'm new to web services, but we are currently
implementing a number of Web Services that all take
as arguments a single parameter which is an XMLBean,
which has been generated by a XML Schema.
What I find surprising is that when I submit a SOAP
message to the Web Service (through the http Web
Service Tester inside eclipse), I can send any valid
XML without getting a SOAP fault. Is there a way on
the Web Service that I want the XML submitted to be
validated against the XML Schema for that parameter?
Bit surprised I have to implement my own input
argument validation, and there doesn't appear to be a
standard way to do this. I must be missing soemthing
surely? Why else would the Schema be in the WSDL?
Cheers
JohnHas anyone found an answer to this, we have the same issue?

Similar Messages

  • Web service XML use with Schema

    Hi!
    I have a Webservice working ok and a can see the xml, but, the after process for read this data(I do it trought pbl) take too time, then i go to try use of schema, as follow structure:
    <?xml version="1.0" encoding="UTF-8" ?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
         <xsd:simpleType name="nombres" type="xsd:string"/>
         <xsd:simpleType name="paterno" type="xsd:string"/>
         <xsd:simpleType name="materno" type="xsd:string"/>
         <xsd:simpleType name="email" type="xsd:string"/>
         <xsd:simpleType name="codigo" type="xsd:string"/>
         <xsd:simpleType name="vigencia" type="xsd:string"/>
         <xsd:simpleType name="fecIni" type="xsd:string"/>
         <xsd:simpleType name="fecTer" type="xsd:string"/>
         <xsd:simpleType name="codCargo" type="xsd:string"/>
         <xsd:simpleType name="codGrado" type="xsd:string"/>
         <xsd:simpleType name="codPuesto" type="xsd:string"/>
         <xsd:simpleType name="codRepart" type="xsd:string"/>
         <xsd:simpleType name="codOrganismo" type="xsd:string"/>
         <xsd:simpleType name="descCargo" type="xsd:string"/>
         <xsd:simpleType name="descEscalafon" type="xsd:string"/>
         <xsd:simpleType name="descReparticion" type="xsd:string"/>
         <xsd:simpleType name="descEstamento" type="xsd:string"/>
         <xsd:simpleType name="descJerarquia" type="xsd:string"/>
         <xsd:group name="nombramientos">
              <xsd:sequence>
                   <xsd:element name="codigo" type="codigo"/>
                   <xsd:element name="vigencia" type="vigencia"/>
                   <xsd:element name="fecIni" type="fecIni"/>
                   <xsd:element name="fecTer" type="fecTer"/>
                   <xsd:element name="codCargo" type="codCargo"/>
                   <xsd:element name="codGrado" type="codGrado"/>
                   <xsd:element name="codPuesto" type="codPuesto"/>
                   <xsd:element name="codRepart" type="codRepart"/>
                   <xsd:element name="codOrganismo" type="codOrganismo"/>
                   <xsd:element name="descCargo" type="descCargo"/>
                   <xsd:element name="descEscalafon" type="descEscalafon"/>
                   <xsd:element name="descReparticion" type="descReparticion"/>
                   <xsd:element name="descEstamento" type="descEstamento"/>
                   <xsd:element name="descJerarquia" type="descJerarquia"/>
              </xsd:sequence>
         </xsd:group>
         <xsd:complexType name="Usuario">
              <xsd:sequence>
                   <xsd:choice>
                        <xsd:element name="nombres" type="nombres"/>
                        <xsd:element name="paterno" type="paterno"/>
                        <xsd:element name="materno" type="materno"/>
                        <xsd:element name="email" type="email"/>
                        <xsd:group ref="nombramientos"/>
                   </xsd:choice>
              </xsd:sequence>
         </xsd:complexType>
         <xsd:element name="usuario" type="Usuario"/>
    </xsd:schema>
    ... and the xml i using as the next:
    <usuario>
         <nombres>Oscar Hernan</nombres>
         <paterno>Pozo</paterno>
         <materno>Ortiz</materno>
         <email>[email protected]</email>
         <nombramientos class="list">
              <nombramiento>
                   <codigo>A110401412002</codigo>
                   <vigencia>1</vigencia>
                   <fecIni>2002-01-01 00:00:00.0</fecIni>
                   <fecTer>2002-12-31 00:00:00.0</fecTer>
                   <codCargo>N3A075</codCargo>
                   <codGrado>13</codGrado>
                   <codPuesto>A22004</codPuesto>
                   <codRepart>11040501</codRepart>
                   <codOrganismo>11040000</codOrganismo>
                   <descCargo>ANALISTA COMPUTACIONAL</descCargo>
                   <descEscalafon>N3A</descEscalafon>
                   <descReparticion>Dirección de Servicios de Tecnologías de Información</descReparticion>
                   <descEstamento>A</descEstamento>
                   <descJerarquia>Técnica</descJerarquia>
              </nombramiento>
              <nombramiento>
                   <codigo>A120200011978</codigo>
                   <vigencia>1</vigencia>
                   <fecIni>1978-09-15 00:00:00.0</fecIni>
                   <fecTer>2099-12-31 00:00:00.0</fecTer>
                   <codCargo>A2A001</codCargo>
                   <codGrado>05</codGrado>
                   <codPuesto>001767</codPuesto>
                   <codRepart>19012061</codRepart>
                   <codOrganismo>12060000</codOrganismo>
                   <descCargo>Académico Prof. Asociado</descCargo>
                   <descEscalafon>A2A</descEscalafon>
                   <descReparticion>Aporte Institucional Ciencias Físicas </descReparticion>
                   <descEstamento>A</descEstamento>
                   <descJerarquia>Prof. Asociado - Categ. Academica Ord.</descJerarquia>
              </nombramiento>
         </nombramientos>
    </usuario>
    As you see, i'm try retrieve data "nombramientos" in a group, but que schema is not charging in albpm with this structure.
    A need let "nombramientos" tag in a group to use it as correct.
    Please.. if any body can help me.
    Nathan Bernal

    I'm new to web services, but we are currently
    implementing a number of Web Services that all take
    as arguments a single parameter which is an XMLBean,
    which has been generated by a XML Schema.
    What I find surprising is that when I submit a SOAP
    message to the Web Service (through the http Web
    Service Tester inside eclipse), I can send any valid
    XML without getting a SOAP fault. Is there a way on
    the Web Service that I want the XML submitted to be
    validated against the XML Schema for that parameter?
    Bit surprised I have to implement my own input
    argument validation, and there doesn't appear to be a
    standard way to do this. I must be missing soemthing
    surely? Why else would the Schema be in the WSDL?
    Cheers
    JohnHas anyone found an answer to this, we have the same issue?

  • Web-services.xml, dtd or xml schema?

    Hi there!
    I'm just curious to know whether there exists any dtd or schema
    for wls 7.x web-services.xml file?
    The diagram in
    http://e-docs.bea.com/wls/docs70/webserv/wsp.html#1001373
    shows one order for the contents of the web-service element,
    whereas the examples reflect another (being types,
    type-mapping, components, operations).
    Why are the example web-services.xml not tagged with the
    information of the location of the schema?
    Of course building web-services.xml manually is not the first
    thing to try, but since the contents are documented and since
    it gives the best control over the process, it makes sense.

    Hello,
    There's not one. The primary vision for the web-services.xml file
    was/is to be a linkage between wsdl/soap and the j2ee environment. It
    was not intended to be a starting point for building an application, but
    a semi-private intermediary.
    HTHs,
    Bruce
    Toni Nykanen wrote:
    >
    Hi there!
    I'm just curious to know whether there exists any dtd or schema
    for wls 7.x web-services.xml file?
    The diagram in
    http://e-docs.bea.com/wls/docs70/webserv/wsp.html#1001373
    shows one order for the contents of the web-service element,
    whereas the examples reflect another (being types,
    type-mapping, components, operations).
    Why are the example web-services.xml not tagged with the
    information of the location of the schema?
    Of course building web-services.xml manually is not the first
    thing to try, but since the contents are documented and since
    it gives the best control over the process, it makes sense.

  • Web-services.xml, why is security not enforced (format improved)

    <pre>
    Hi,
    Sorry about the lack of formatting in previous post.
    Running weblogic 8.1SP5.
    Im having problems with the message style security, it doesn't seem to be enforced by weblogic.
    The intention of web-services.xml (below) is that weblogic should authenticate the user according to credential info in the request header.
    The console webservice testpage seem OK, it has user and password input boxes. But invocations fail with an obscure message involving
    AssertionError: Bad password type: wsse:PasswordText
    A simple Axis based client (see below) with no security tags in the header can invoke the service with no problems, would expect it to fail on athentication.
    Did I miss something in web-services.xml or does something general need to be set up in the server for this to work as intended?
    I am pulling my hair out on this one so any help will be greatly appreciated.
    Rgds.
    web-services.xml looks like this:
    <security>
    <user>
    <name>test_user</name>
    <password>test_password</password>
    </user>
    <spec:SecuritySpec xmlns:spec="http://www.openuri.org/2002/11/wsse/spec"
    Namespace="http://schemas.xmlsoap.org/ws/2002/07/secext"
    Id="_mySpec">
    <spec:UsernameTokenSpec xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/07/secext"
    PasswordType="wsse:PasswordText">
    </spec:UsernameTokenSpec>
    </spec:SecuritySpec>
    </security>
    <components>
    <stateless-ejb name="CaseConverter">
    <jndi-name path="CaseConverter"></jndi-name>
    </stateless-ejb>
    </components>
    <operations xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <operation
    component="CaseConverter"
    name="convertToUpper"
    method="convertToUpper"
    in-security-spec="_mySpec"
    >
    The client looks like this (Axis based):
    URL endpoint = new URL("http://127.0.0.1:7001/WebModule/CaseConverter");
    Service service = new Service();
    Call call = (Call)service.createCall();
    call.setTargetEndpointAddress(endpoint);
    call.setOperationName("convertToUpper");
    call.addParameter("inputString",XMLType.XSD_STRING,ParameterMode.IN);
    call.setReturnType(XMLType.XSD_STRING);
    String result = (String) call.invoke(new Object[] { "hello!" });
    System.out.println("Result: " + result);
    </pre>

    Hi
    I am also getting the same error. if anybody has some solution, pl. tell us

  • Web-services.xml, why is security not enforced

    Hi,
    Running weblogic 8.1SP5.
    Im having problems with the message style security, it doesn't seem to be enforced by weblogic.
    The intention of web-services.xml (below) is that weblogic should authenticate the user according to credential info in the request header.
    The console webservice testpage seem OK, it has user and password input boxes. But invocations fail with an obscure message involving
    <b>AssertionError: Bad password type: wsse:PasswordText</b>
    A simple Axis based client (see below) with no security tags in the header can invoke the service with no problems, would expect it to fail on athentication.
    Did I miss something in web-services.xml or does something general need to be set up in the server for this to work as intended?
    I am pulling my hair out on this one so any help will be greatly appreciated.
    Rgds.
    web-services.xml looks like this:
    <security>
    <user>
    <name>test_user</name>
    <password>test_password</password>
    </user>
    <spec:SecuritySpec xmlns:spec="http://www.openuri.org/2002/11/wsse/spec"
    Namespace="http://schemas.xmlsoap.org/ws/2002/07/secext"
    Id="_mySpec">
    <spec:UsernameTokenSpec xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/07/secext"
    PasswordType="wsse:PasswordText">
    </spec:UsernameTokenSpec>
    </spec:SecuritySpec>
    </security>
    <components>
    <stateless-ejb name="CaseConverter">
    <jndi-name path="CaseConverter"></jndi-name>
    </stateless-ejb>
    </components>
    <operations xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <operation
    component="CaseConverter"
    name="convertToUpper"
    method="convertToUpper"
    in-security-spec="_mySpec"
    >
    The client looks like this (Axis based):
    URL endpoint = new URL("http://127.0.0.1:7001/WebModule/CaseConverter");
    Service service = new Service();
    Call call = (Call)service.createCall();
    call.setTargetEndpointAddress(endpoint);
    call.setOperationName("convertToUpper");
    call.addParameter("inputString",XMLType.XSD_STRING,ParameterMode.IN);
    call.setReturnType(XMLType.XSD_STRING);
    String result = (String) call.invoke(new Object[] { "hello!" });
    System.out.println("Result: " + result);
    .......

    Hi
    I am also getting the same error. if anybody has some solution, pl. tell us

  • Error while inluding xsd:whiteSpace in web-services.xml

    Hi,
    i am trying to allow the xml attribute values to preserve the whiteSpace characters(tabs, line feeds, carriage returns etc...)
    In web-services.xml i am adding
    <xsd:complexContent>
    <xsd:restriction base="xsd:string">
    <xsd:attribute name="address">
    <xsd:whiteSpace value="preserve"/>
    </xsd:attribute>
    </xsd:restriction>
    </xsd:complexContent>
    But i am getting a run time exception as
    [weblogic.xml.schema.model.parser.XSDParseException: invalid element "xsd:whiteSpace" AT line 0, column 0: <['http://www.w3.org/2001/XMLSchema']:xsd:whiteSpace value="preserve">]
    am i doing in a correct way?
    Please suggest me.
    Thanks
    subba.

    weblogic server doesn't support some of the xsd features.
    WebLogic Server does not support the following XML Schema features:
    ?     Complex data type inheritance by restriction
    ?     Union simple data types
    ?     References to named model groups
    ?     Nested content models in a single complex type
    ?     Redefinition of declarations
    ?     Identity constraints (key, keyref, unique)
    ?     Nested XSD model groups with other content models at the same level.
    There cannot be a modelgroup (say sequence) that contains another nested modelgroup (say choice), and a content element (say element). So, if a nested modelgroup is required, make sure that it contains only another model group and no other content element.
    ?     Wildcards
    but i didn't understand why its giving error for whiteSpace.
    Can someone reply to this please,, its urgent for me.
    thanks
    subba.

  • Generate web-service.xml

    I need to configure the deployment descriptor web-services.xml, but I don't know where or how to generate it. I use version 8.1 of weblogic. Someone can help me? thanks!

    I have an XML input in my transaction. I was able to generate the WSDL without problems. But need to know how to test it by sendig in some XML data. Probably, we could both be helping each other in the process.
    Regards,
    Chanti.

  • Web-services.xml

    I'm implementing WS-SECURITY for my web service. The only service that I am enabling is the soap encryption. Furthermore, I only want to encrypt the request. I in the web-services.xml the operations specify the security spec to use for both the request and the response...
    in-security-spec
    out-security-spec
    The docs say "If you do not specify this attribute, the default security specification, if it exists, is applied to the SOAP response. If there is no default security specification, then no message-level security is applied to the SOAP response."
    My question is how do you disable the response if there is a default security spec.
    thx

    xmllint is correct. Here's what the 1.1.3 XSD says (I put in the leading periods to fool the discussion board into preserving structure ):
    . <xsd:element name="ITunesUDocument">
    . . <xsd:complexType>
    . . . <xsd:sequence>
    . . . . <xsd:element ref="Version" minOccurs="1" maxOccurs="1"/>
    . . . . <xsd:element ref="AddCourse" minOccurs="0"/>
    . . . </xsd:sequence>
    . . </xsd:complexType>
    . </xsd:element>
    If "minOccurs" or "maxOccurs" aren't specified in sequence elements, then they both default to "1". So the "minOccurs" and "maxOccurs" specifiers are redundant in the "Version" element specification…they'd be "1" anyway. Setting "minOccurs" to "0" means that you can omit the element in XML…but unless "maxOccurs" is set, than the most any element can appear in the sequence is once to be valid. "unbounded" can be used in "maxOccurs" to set no limit on the number of times it can appear in the sequence.
    Recall that XML doesn't necessarily have to validate to "work". An XML validation is a contract between us and Apple…Apple promises that we can put at least one "AddCourse" in an "ITunesUDocument" and that is going to work, or our money back. But if we don't submit valid XML, it might still work…but there is no promise there either. It might work today, it might fail tomorrow. The iTunes U people have said, in various venues, that we should expect Apple to validate our XML…but nobody's perfect. It could be that Apple just missed this one…but we should still write code under the assumption that the XSD is being correctly applied and that our XML is being validated on Apple's end. That way, our code can never be "wrong".

  • How to generate param-prefix in web-services.xml

    Hello I am using source2wsdd to generate my WSDL and my web-services.xml. For sake
    of interoperability I would like to have the type param-prefix in the web-services.xml
    file. From my Bean class what kind of javadoc comments would help me generate
    the type param-prefix ?
    I also would like the location="header" in the param list.
    Thanks,
    Aswin.
    <param xmlns:param-prefix="http://tempuri.org/"
    type="param-prefix:SOAPCredentials"
    location="header"
    class-name="com.xyz.webservices.SOAPCredentials"
    name="SOAPCredentials"
    style="in">
    </param>
    <return-param xmlns:param-prefix="http://tempuri.org/"
    type="param-prefix:GetFileProfileInformationResponse"
    class-name="com.xyz.webservices.GetFileProfileInformationResponse"
    name="parameters">
    </return-param>
    </params>

    Please try this:
    * @wlws:part p_SOAPAuthToken location="header"
    * type="typeNS:p_SOAPAuthToken"
    * class-name="com.xyz.webservices.SOAPAuthToken"
    * style="inout"
    * xmlns:typeNS=http://namespace/of/the/type
    * @wlws:part p_SOAPCredentials location="header"
    * type="typeNS:p_SOAPCredentials"
    * class-name="com.xyz.webservices.SOAPCredentials"
    * style="in"
    * xmlns:typeNS=http://namespace/of/the/type
    * @ejbgen:remote-method
    public void login(SOAPAuthToken p_SOAPAuthToken,
    SOAPCredentials p_SOAPCredentials)
    I did not try this one out. So i can only hope that it works.
    Regards,
    -manoj
    http://manojc.com
    "Aswin Dinakar" <[email protected]> wrote in message
    news:40aeeb5d$1@mktnews1...
    >
    I tried this
    * @wlws:part p_SOAPAuthToken location="header"
    * @wlws:part p_SOAPAuthToken type="param-prefix:p_SOAPAuthToken"
    * @wlws:part p_SOAPAuthTokenclass-name="com.xyz.webservices.SOAPAuthToken"
    * @wlws:part p_SOAPAuthToken style="inout"
    * @wlws:part p_SOAPCredentials location="header"
    * @wlws:part p_SOAPCredentials type="param-prefix:p_SOAPCredentials"
    * @wlws:part p_SOAPCredentialsclass-name="com.xyz.webservices.SOAPCredentials"
    * @wlws:part p_SOAPCredentials style="in"
    * @ejbgen:remote-method
    public void login(SOAPAuthToken p_SOAPAuthToken,
    SOAPCredentials p_SOAPCredentials)
    and I got the following error -
    [source2wsdd] source2wsdd: In doclet classweblogic.webservice.tools.ddgen.Servi
    ceGen, method start has thrown an exceptionjava.lang.reflect.InvocationTargetE
    xception
    [source2wsdd] weblogic.xml.stream.XMLStreamException: Attribute QNamevalue "par
    am-prefix:p_SOAPAuthToken" does not map to a prefix that is in scope
    [source2wsdd] atweblogic.webservice.dd.NSAttribute.getValueAsXMLName(NSAttrib
    ute.java:45)
    [source2wsdd] atweblogic.webservice.dd.DDLoader.processParamElement(DDLoader.
    java:1252)
    "manoj cheenath" <[email protected]> wrote:
    Check out this example:
    http://manojc.com/?sample3
    You can find more details regarding the tags here:
    http://manojc.com/tutorial/sample3/source2wsdd.html
    Regards,
    -manoj
    http://manojc.com
    "Aswin D" <[email protected]> wrote in message
    news:[email protected]...
    Hello I am using source2wsdd to generate my WSDL and my
    web-services.xml.
    For sake
    of interoperability I would like to have the type param-prefix inthe
    web-services.xml
    file. From my Bean class what kind of javadoc comments would help megenerate
    the type param-prefix ?
    I also would like the location="header" in the param list.
    Thanks,
    Aswin.
    <param xmlns:param-prefix="http://tempuri.org/"
    type="param-prefix:SOAPCredentials"
    location="header"
    class-name="com.xyz.webservices.SOAPCredentials"
    name="SOAPCredentials"
    style="in">
    </param>
    <return-param xmlns:param-prefix="http://tempuri.org/"
    type="param-prefix:GetFileProfileInformationResponse"
    class-name="com.xyz.webservices.GetFileProfileInformationResponse"
    name="parameters">
    </return-param>
    </params>

  • Fault elt in web-services.xml NOT WORKING

    We are trying to capture an invalid message coming into our service before our
    service actually processes it. Per WLS7 documentation, it provides the ability
    to add a <fault> elt under the <params> elt in web-services.xml to perform that.
    Here's how the operations portion of our web-services.xml looks like:
    <operations>
    <operation method="echo(java.lang.String)" component="jcComp0" name="echo"
    handler-chain="diagnosticChain">
    <params>
    <param location="body" class-name="java.lang.String" style="in" name="echoString"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema" type="xsd:string">
    </param>
    <return-param location="body" class-name="java.lang.String" name="Result"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema" type="xsd:string">
    </return-param>
         <fault name="InvalidMessageException" class-name="com.gmacfs.routeone.diagnostic.InvalidMessageException"/>
    </params>
    </operation>
    </operations>
    However, when we tried doing that, we got a BIG set of exception while trying
    to build our client. It looks as follows:
    client:
    [clientgen] Generating client jar for diagnostic.ear ...
    [clientgen] Could not read Web Service deployment descriptor
    [clientgen] at weblogic.ant.taskdefs.webservices.clientgen.EARClientGen.run(EARClientGen.java:112)
    [clientgen] at weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenTask.java:270)
    [clientgen] at org.apache.tools.ant.Task.perform(Task.java:217)
    [clientgen] at org.apache.tools.ant.Target.execute(Target.java:164)
    [clientgen] at org.apache.tools.ant.Target.performTasks(Target.java:182)
    [clientgen] at org.apache.tools.ant.Project.executeTarget(Project.java:601)
    [clientgen] at org.apache.tools.ant.Project.executeTargets(Project.java:560)
    [clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
    [clientgen] at org.apache.tools.ant.Main.start(Main.java:153)
    [clientgen] at org.apache.tools.ant.Main.main(Main.java:176)
    [clientgen] --- Nested Exception ---
    [clientgen] Could not read Web Service deployment descriptor
    [clientgen] at weblogic.ant.taskdefs.webservices.clientgen.EARClientGen.getWebServiceDD(EARClientGen.java:332)
    [clientgen] at weblogic.ant.taskdefs.webservices.clientgen.EARClientGen.run(EARClientGen.java:110)
    [clientgen] at weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenTask.java:270)
    [clientgen] at org.apache.tools.ant.Task.perform(Task.java:217)
    [clientgen] at org.apache.tools.ant.Target.execute(Target.java:164)
    [clientgen] at org.apache.tools.ant.Target.performTasks(Target.java:182)
    [clientgen] at org.apache.tools.ant.Project.executeTarget(Project.java:601)
    [clientgen] at org.apache.tools.ant.Project.executeTargets(Project.java:560)
    [clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
    [clientgen] at org.apache.tools.ant.Main.start(Main.java:153)
    [clientgen] at org.apache.tools.ant.Main.main(Main.java:176)
    [clientgen] --- Nested Exception ---
    [clientgen] weblogic.webservice.dd.DDProcessingException: Could not find required
    attribute "type" for element <fault> (Line 28, Column 8)
    [clientgen] at weblogic.webservice.dd.ParsingHelper.getRequiredAttribute(ParsingHelper.java:287)
    [clientgen] at weblogic.webservice.dd.DDLoader.processFaultElement(DDLoader.java:1195)
    [clientgen] at weblogic.webservice.dd.DDLoader.processFaultElements(DDLoader.java:1166)
    [clientgen] at weblogic.webservice.dd.DDLoader.processParamsElement(DDLoader.java:1004)
    [clientgen] at weblogic.webservice.dd.DDLoader.processOperationElement(DDLoader.java:977)
    [clientgen] at weblogic.webservice.dd.DDLoader.processOperationElements(DDLoader.java:853)
    [clientgen] at weblogic.webservice.dd.DDLoader.processOperationsElement(DDLoader.java:841)
    [clientgen] at weblogic.webservice.dd.DDLoader.processWebServiceElement(DDLoader.java:378)
    [clientgen] at weblogic.webservice.dd.DDLoader.processWebServiceElements(DDLoader.java:283)
    [clientgen] at weblogic.webservice.dd.DDLoader.processWebServicesElement(DDLoader.java:271)
    [clientgen] at weblogic.webservice.dd.DDLoader.load(DDLoader.java:249)
    [clientgen] at weblogic.webservice.util.WebServiceWarFile.getWSDD(WebServiceWarFile.java:79)
    [clientgen] at weblogic.ant.taskdefs.webservices.clientgen.EARClientGen.getWebServiceDD(EARClientGen.java:330)
    [clientgen] at weblogic.ant.taskdefs.webservices.clientgen.EARClientGen.run(EARClientGen.java:110)
    [clientgen] at weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenTask.java:270)
    [clientgen] at org.apache.tools.ant.Task.perform(Task.java:217)
    [clientgen] at org.apache.tools.ant.Target.execute(Target.java:164)
    [clientgen] at org.apache.tools.ant.Target.performTasks(Target.java:182)
    [clientgen] at org.apache.tools.ant.Project.executeTarget(Project.java:601)
    [clientgen] at org.apache.tools.ant.Project.executeTargets(Project.java:560)
    [clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
    [clientgen] at org.apache.tools.ant.Main.start(Main.java:153)
    [clientgen] at org.apache.tools.ant.Main.main(Main.java:176)
    [clientgen] --------------- nested within: ------------------
    [clientgen] weblogic.webservice.util.WebServiceJarException: Could not load deployment
    descriptor - with nested exception:
    [clientgen] [weblogic.webservice.dd.DDProcessingException: Could not find required
    attribute "type" for element <fault> (Line 28, Column 8)]
    [clientgen] at weblogic.webservice.util.WebServiceWarFile.getWSDD(WebServiceWarFile.java:81)
    [clientgen] at weblogic.ant.taskdefs.webservices.clientgen.EARClientGen.getWebServiceDD(EARClientGen.java:330)
    [clientgen] at weblogic.ant.taskdefs.webservices.clientgen.EARClientGen.run(EARClientGen.java:110)
    [clientgen] at weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenTask.java:270)
    [clientgen] at org.apache.tools.ant.Task.perform(Task.java:217)
    [clientgen] at org.apache.tools.ant.Target.execute(Target.java:164)
    [clientgen] at org.apache.tools.ant.Target.performTasks(Target.java:182)
    [clientgen] at org.apache.tools.ant.Project.executeTarget(Project.java:601)
    [clientgen] at org.apache.tools.ant.Project.executeTargets(Project.java:560)
    [clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
    [clientgen] at org.apache.tools.ant.Main.start(Main.java:153)
    [clientgen] at org.apache.tools.ant.Main.main(Main.java:176)
    BUILD FAILED
    Anybody has any ideas?
    Thanks much,
    sami

    Manoj,
    Thanks a lot, THAT DID IT... two very helpful hints from you in a row.
    By the way, one thing worth mentioning is that the Weblogic documentation that
    we explored did not have enough information about that issue.
    Thanks again.
    sami
    "manoj cheenath" <[email protected]> wrote:
    Buried deep in the stack trace, is this little
    detail:
    Could not find required
    attribute "type" for element <fault> (Line 28, Column 8)
    So the correct DD should look something like:
    <fault type="typeNS:string"
    xmlns:typeNS="http://www.w3.org/2001/XMLSchema"
    class-name="tutorial.sample9.HelloWorldException"
    name="HelloWorldException">
    </fault>
    Also, check out this example:
    http://manojc.com/?sample9
    There is a know problem: WLS can not handle
    exceptions that contain complex data types.
    This will be fixed in SP1.
    Regards,
    -manoj
    http://manojc.com
    "sami titi" <[email protected]> wrote in message
    news:[email protected]...
    We are trying to capture an invalid message coming into our servicebefore
    our
    service actually processes it. Per WLS7 documentation, it providesthe
    ability
    to add a <fault> elt under the <params> elt in web-services.xml toperform
    that.
    Here's how the operations portion of our web-services.xml looks like:
    <operations>
    <operation method="echo(java.lang.String)" component="jcComp0"name="echo"
    handler-chain="diagnosticChain">
    <params>
    <param location="body" class-name="java.lang.String" style="in"name="echoString"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema" type="xsd:string">
    </param>
    <return-param location="body" class-name="java.lang.String"name="Result"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema" type="xsd:string">
    </return-param>
    <fault name="InvalidMessageException"class-name="com.gmacfs.routeone.diagnostic.InvalidMessageException"/>
    </params>
    </operation>
    </operations>
    However, when we tried doing that, we got a BIG set of exception whiletrying
    to build our client. It looks as follows:
    client:
    [clientgen] Generating client jar for diagnostic.ear ...
    [clientgen] Could not read Web Service deployment descriptor
    [clientgen] atweblogic.ant.taskdefs.webservices.clientgen.EARClientGen.run(EARClientGen.ja
    va:112)
    [clientgen] atweblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenT
    ask.java:270)
    [clientgen] at org.apache.tools.ant.Task.perform(Task.java:217)
    [clientgen] at org.apache.tools.ant.Target.execute(Target.java:164)
    [clientgen] atorg.apache.tools.ant.Target.performTasks(Target.java:182)
    [clientgen] atorg.apache.tools.ant.Project.executeTarget(Project.java:601)
    [clientgen] atorg.apache.tools.ant.Project.executeTargets(Project.java:560)
    [clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
    [clientgen] at org.apache.tools.ant.Main.start(Main.java:153)
    [clientgen] at org.apache.tools.ant.Main.main(Main.java:176)
    [clientgen] --- Nested Exception ---
    [clientgen] Could not read Web Service deployment descriptor
    [clientgen] atweblogic.ant.taskdefs.webservices.clientgen.EARClientGen.getWebServiceDD(EAR
    ClientGen.java:332)
    [clientgen] atweblogic.ant.taskdefs.webservices.clientgen.EARClientGen.run(EARClientGen.ja
    va:110)
    [clientgen] atweblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenT
    ask.java:270)
    [clientgen] at org.apache.tools.ant.Task.perform(Task.java:217)
    [clientgen] at org.apache.tools.ant.Target.execute(Target.java:164)
    [clientgen] atorg.apache.tools.ant.Target.performTasks(Target.java:182)
    [clientgen] atorg.apache.tools.ant.Project.executeTarget(Project.java:601)
    [clientgen] atorg.apache.tools.ant.Project.executeTargets(Project.java:560)
    [clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
    [clientgen] at org.apache.tools.ant.Main.start(Main.java:153)
    [clientgen] at org.apache.tools.ant.Main.main(Main.java:176)
    [clientgen] --- Nested Exception ---
    [clientgen] weblogic.webservice.dd.DDProcessingException: Could notfind
    required
    attribute "type" for element <fault> (Line 28, Column 8)
    [clientgen] atweblogic.webservice.dd.ParsingHelper.getRequiredAttribute(ParsingHelper.java
    :287)
    [clientgen] atweblogic.webservice.dd.DDLoader.processFaultElement(DDLoader.java:1195)
    [clientgen] atweblogic.webservice.dd.DDLoader.processFaultElements(DDLoader.java:1166)
    [clientgen] atweblogic.webservice.dd.DDLoader.processParamsElement(DDLoader.java:1004)
    [clientgen] atweblogic.webservice.dd.DDLoader.processOperationElement(DDLoader.java:977)
    [clientgen] atweblogic.webservice.dd.DDLoader.processOperationElements(DDLoader.java:853)
    [clientgen] atweblogic.webservice.dd.DDLoader.processOperationsElement(DDLoader.java:841)
    [clientgen] atweblogic.webservice.dd.DDLoader.processWebServiceElement(DDLoader.java:378)
    [clientgen] atweblogic.webservice.dd.DDLoader.processWebServiceElements(DDLoader.java:283)
    [clientgen] atweblogic.webservice.dd.DDLoader.processWebServicesElement(DDLoader.java:271)
    [clientgen] at weblogic.webservice.dd.DDLoader.load(DDLoader.java:249)
    [clientgen] atweblogic.webservice.util.WebServiceWarFile.getWSDD(WebServiceWarFile.java:79
    [clientgen] atweblogic.ant.taskdefs.webservices.clientgen.EARClientGen.getWebServiceDD(EAR
    ClientGen.java:330)
    [clientgen] atweblogic.ant.taskdefs.webservices.clientgen.EARClientGen.run(EARClientGen.ja
    va:110)
    [clientgen] atweblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenT
    ask.java:270)
    [clientgen] at org.apache.tools.ant.Task.perform(Task.java:217)
    [clientgen] at org.apache.tools.ant.Target.execute(Target.java:164)
    [clientgen] atorg.apache.tools.ant.Target.performTasks(Target.java:182)
    [clientgen] atorg.apache.tools.ant.Project.executeTarget(Project.java:601)
    [clientgen] atorg.apache.tools.ant.Project.executeTargets(Project.java:560)
    [clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
    [clientgen] at org.apache.tools.ant.Main.start(Main.java:153)
    [clientgen] at org.apache.tools.ant.Main.main(Main.java:176)
    [clientgen] --------------- nested within: ------------------
    [clientgen] weblogic.webservice.util.WebServiceJarException: Couldnot
    load deployment
    descriptor - with nested exception:
    [clientgen] [weblogic.webservice.dd.DDProcessingException: Could not
    find>required>> attribute "type" for element <fault> (Line 28, Column 8)
    [clientgen] atweblogic.webservice.util.WebServiceWarFile.getWSDD(WebServiceWarFile.java:81
    [clientgen] atweblogic.ant.taskdefs.webservices.clientgen.EARClientGen.getWebServiceDD(EAR
    ClientGen.java:330)
    [clientgen] atweblogic.ant.taskdefs.webservices.clientgen.EARClientGen.run(EARClientGen.ja
    va:110)
    [clientgen] atweblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenT
    ask.java:270)
    [clientgen] at org.apache.tools.ant.Task.perform(Task.java:217)
    [clientgen] at org.apache.tools.ant.Target.execute(Target.java:164)
    [clientgen] atorg.apache.tools.ant.Target.performTasks(Target.java:182)
    [clientgen] atorg.apache.tools.ant.Project.executeTarget(Project.java:601)
    [clientgen] atorg.apache.tools.ant.Project.executeTargets(Project.java:560)
    [clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
    [clientgen] at org.apache.tools.ant.Main.start(Main.java:153)
    [clientgen] at org.apache.tools.ant.Main.main(Main.java:176)
    BUILD FAILED
    Anybody has any ideas?
    Thanks much,
    sami

  • What web service & xml will be used for deleting the packged epub/pdf file from Admin Console

    What web service & xml will be used for deleting the packged epub/pdf file from Admin Console?
    I am able to delete the files from Admin console directy but not able to get which web service is calling on deleting the file from admin console:
    Mangal

    Hi Jim,
    I tired following web service and xml to delete the packaged ebook but it is giving me error instead of response:
    Web Service & XML
    http://myserver_url/admin/ManageResourceKey
    <request action="delete" auth="builtin" xmlns="http://ns.adobe.com/adept">
    <nonce>" . $nonce . "</nonce>
    <expiration>'. $expiration .'</expiration>
    <resourceKey>
    <resource>resource_id</resource>
    <resourceItem>1</resourceItem>
    </resourceKey>
    </request>
    Error Message
    <error xmlns="http://ns.adobe.com/adept"
    data="E_ADEPT_DATABASE http://myserver_url/admin/ManageResourceKey
    Cannot%20delete%20or%20update%20a%20parent%20row:%20a%20foreign%20key%20constraint%20fails %20(`adept`.`distributionrights`,%20CONSTRAINT%20`distributionrights_ibfk_2`%20FOREIGN%20K EY%20(`resourceid`)%20REFERENCES%20`resourcekey`%20(`resourceid`))"/>
    Magal Varshney

  • Web-services.xml for EJB component and SOAP Message Handler Chain

    I have used the following example for my own web service with EJB component and SOAP
    Message Handler Chain:
    http://e-docs.bea.com/wls/docs70/webServices/dd.html#1058208
    I have a deployment error:
    javax.naming.NameNotFoundException: Unable to resolve 'app/ejb/DocumentService.j
    ar#DocumentService/home' Resolved: 'app/ejb' Unresolved:'DocumentService.jar#Doc
    umentService' ; remaining name 'DocumentService.jar#DocumentService/home'
    In attachement is the ear file.
    Is there a problem in web-services.xml?
    Thanks
    [ws_dox_sdi.ear]

    It works. Thanks,
    Ioana
    "Neal Yin" <[email protected]> wrote:
    The error means your EJB is not deployed.
    Adding a EJB module to your application.xml file of the ear should fixe
    it.
    <application>
    <display-name />
    <module>
    <web>
    <web-uri>dox_sdi.war</web-uri>
    </web>
    </module>
    <module>
    <ejb>DocumentService.jar</ejb>
    </module>
    </application>
    "Ioana Meissner" <[email protected]> wrote in message
    news:3cf640cc$[email protected]..
    I have used the following example for my own web service with EJBcomponent and SOAP
    Message Handler Chain:
    http://e-docs.bea.com/wls/docs70/webServices/dd.html#1058208
    I have a deployment error:
    javax.naming.NameNotFoundException: Unable to resolve'app/ejb/DocumentService.j
    ar#DocumentService/home' Resolved: 'app/ejb'Unresolved:'DocumentService.jar#Doc
    umentService' ; remaining name 'DocumentService.jar#DocumentService/home'
    In attachement is the ear file.
    Is there a problem in web-services.xml?
    Thanks

  • Changing web-services.xml for handler

    I have been using the servicegen task to generate the .ear file for my webservice.
    Among other things, it took care of generating the web-services.xml file for me.
    I have a need to write a handler and thus it requires changes in the web-services.xml.
    I generated the web-services.xml file the first time and made the handler related
    changes and it's working fine.
    But now, I loose the auto-generation facility (since I have hand-edited it for
    handler changes). Any time, I change the interface of the webservice, I would
    have to manually change the web-services.xml file to reflect the new interface.
    Is there a better way of doing this so that I can auto-generate the webservices.xml
    file plus make my handler changes. Anything in the ant to do it smartly, rather
    than doing it manually. I would imagine that anyone who writes a handler would
    run into similar situation.
    thanks for help.
    John

    Here is an example of ejb and source2wsdd.
    "manoj cheenath" <[email protected]> wrote in message
    news:[email protected]...
    It works with EJBs too. You should use ejbLink attribute
    to point to the ejb link. Something like:
    <source2wsdd
    javaSource="${sourcecode.for.the.ejb.interface}"
    ddFile="${webss.output.dir}/WEB-INF/web-services.xml"
    typesInfo="${webss.output.dir}/WEB-INF/classes/types.xml"
    serviceURI="${webss.service.url}"
    ejbLink="${webss.ejb.link}" >
    "John" <[email protected]> wrote in message
    news:[email protected]...
    Thanks for the response. But the source2wsdd task only works with javacomponents
    whereas we have ejbs. Any other clues/suggestions.
    Thks,
    - John.
    "manoj cheenath" <[email protected]> wrote:
    Here you go.
    regards,
    -manoj
    "John" <[email protected]> wrote in message
    news:[email protected]...
    Thanks for the response. I'll appreciate if you could share the
    workaround
    in 7.0.
    I'm okay with it even if it's unofficial and might go away.
    thks,
    - John.
    "manoj cheenath" <[email protected]> wrote:
    Hi John,
    This is a know problem with WLS 7.0 and WLS 8.1. The
    DD file (web-services.xml) is much more expressive than
    the servicegen ant task. So one needs to modify the DD
    to use some features. But, if one modifies the DD then it
    is difficult to use the ant tasks again for iterative developemnt.
    JSR 181 [1] and JSR 175 [2] tries to address this
    problem by providing metadata (markup) in source code.
    Unfortunately these JSRs are in the early stages and
    will be completed around JDK 1.5 timeframe. There
    is an internal implementation of a similar beast in WLS
    since 7.0 SP2, but it is not officially supported or
    documented. Mainly because the above said JSRs are
    supposed to address iterative development problem
    in a standard way.
    So, if you cannot wait for the JSRs and dont mind using
    a non standard implementation that may not be supported
    or may change in the next major release (~WLS 9.0),
    let me know. I can send you details.
    Regards,
    -manoj
    [1] http://www.jcp.org/en/jsr/detail?id=181
    [2] http://www.jcp.org/en/jsr/detail?id=175
    "John" <[email protected]> wrote in message
    news:[email protected]...
    I have been using the servicegen task to generate the .ear file
    for
    my
    webservice.
    Among other things, it took care of generating the
    web-services.xml
    file
    for me.
    I have a need to write a handler and thus it requires changes in
    the
    web-services.xml.
    I generated the web-services.xml file the first time and made the
    handler
    related
    changes and it's working fine.
    But now, I loose the auto-generation facility (since I have
    hand-edited
    it
    for
    handler changes). Any time, I change the interface of the
    webservice,
    I
    would
    have to manually change the web-services.xml file to reflect the
    new
    interface.
    Is there a better way of doing this so that I can auto-generate
    the
    webservices.xml
    file plus make my handler changes. Anything in the ant to do it
    smartly,
    rather
    than doing it manually. I would imagine that anyone who writes a
    handler
    would
    run into similar situation.
    thanks for help.
    John
    begin 666 handler.zip
    M4$L#!!0`" `(`#V&D2X````````````````)``0`345402U)3D8O_LH```,`
    M4$L'" `````"`````````%!+`P04``@`" `]AI$N````````````````% ``
    M`$U%5$$M24Y&+TU!3DE&15-4+DU&\TW,RTQ++2[1#4LM*L[,S[-2,-0SX.5R
    M+DI-+$E-T76J! D8ZQG&&Y@I: 27YBGX9B87Y1=7%I>DYA8K>.8EZVGR<O%R
    M`0!02P<(<UT-_$<```!'````4$L#!!0`" `(`/V"D2X````````````````4
    M````=VQS-S O<')O<&5R=&EE<RYT>'2%4$UKPS ,O0?R'P3==5-W&@1Z&AD4
    M!BL[]1;<1&T]',O(RMHR]M]G)RNL'6PZV4_O0]+L]L\JBQF,%80#B5J*"?I/
    MDRA*?8#."K7*<@)EX$'#H+ C3V*4.MA:E]TRLTG,!6H?<!2;$)QMC5KV,9L`
    M;T'W!)'DG>3NDC%JNPHW9'!(C":-^I9B(^J0LJUQ^-.O+*ZU8^[!'2*V[+=V
    MA_VIX]Y8?Z5+L1L3"09QOP::'DUJ+?:JH4)TW!JWYZC5PWQ^/^V5L6QVEF^$
    M#TD)=*2R^/XL'BM<">_$]/"4+X1+KR2>%.IC<"PDN*S7J^>7U_JN7M?9>#KM
    MN,S-Q_F>GSC!9=$Z2UZ;UID8*5Y0+EME\0502P<(3D:RZ!$!```/`@``4$L#
    M! H```````V&D2X````````````````.````=VQS-S O<V%M<&QE-"]02P,$
    M% `(``@`^X21+@```````````````!T```!W;',W,"]S86UP;&4T+V%P<&QI
    M8V%T:6]N+GAM;%6/36_", R&[TC\!Z^77M9X5#M,4P!MT&E,^T "A'9"(;6V
    MH#2IDI2/?[^*`BLW^_7[O+;Y<%]HV)+SRII^U&-W$0`9:7-E?OK18OZ2/$3#
    M0;?3[?";\==H_CW-0)2E5E*$&H'IXOE],H(X09Q5!CZ4=-8??*#"W\+$2(8X
    MGH_A+<TR>&IQ/98B9I\QQ+\AE(^(&[$5S%>&25O@)B7"/.0>6[M6O57*:C%N
    MSFE-:@& Y\J76AP2(PH:O)+6=FF=SF?DMDH2QZMY0Y"73I7'B",`2V=U#DM:
    MPS_6,AVIPN:5;A+J;D?K4]DT2>74P(NBU'3/=L)Q/(L7E[0FT#XDSMIPMG*\
    M4D_A>$[G>-G*\?KS/U!+!PBT=FQ0$0$``,,!``!02P,$% `(``@`RX61+@``
    M`````````````!<```!W;',W,"]S86UP;&4T+V)U:6QD+GAM;*5726_;.!2^
    M%^A_8(6>"DL"!CW:';33%I-!$Q1-!SD&M/1L,Z5%@:3B&(7_>Q\WB5J\-/4A
    M",FWO^\MFM=2/$"A246WL$@4W=8<WB:DA!5MN%XDRX;Q,GGW\L7+%X3,7Z4I
    M*<1V*RJ"C#5(S4"1-'UG7_W5GJP81V%9EG=$F7[2"<EC09$$54/!5JP@6A"]
    M87@!\I$5,!;M[73/"7FDO,'SO\"YN!.2E[?A)3_%>%_3X@===P)THX5DE&=M
    M!$[S[ZAL>7LLQYA WA><*@6JY7O]4S2Z;O1]R>0AO_OT(;VZ^9RW5)TTJC>$
    ME8NDX PJG5F*S-PFUD9/`ARV^$S,_T:XHPY:#\&C(]2Q*:]_>C</J5?Y8-P]
    MR?] 'VED6:MNGINC=<4>-95K"'!SX$*PU5"5RC@(M)HIT$T]0YC5"*/,!6^V
    M@Z4W*K-<,V?+J1^*Y6+?"G*N1''MF6)5&U-4(5FMF:@628E.:B!KJ$!2#251
    MNEFM$A+BX-\Q9H,(1K'JTQS)R3QWMDQ:9L,QL*R0@ 81I]((QQ)&_!K8!,7;
    M'W@=]/81&-O7(WN.>?T\)<3)[5OK2(B72RJ $J.)301Q1!PC4:S$<B1>!VHQ
    MB"J(DH4U+DL(JPK>H.!%\B8SCPF!IW#C+,_?)"TL\%H?\SXXGUL=YWT<@B^9
    M<M*E!$G;YA7>A9R1G2JY[8NS'DD`9><VQ4ZD]S60X(FQ\1^,H*B04@5_HB9V
    MR+J";?TW[G\<`7/<90*]EW5C_1VK")T&#;2LOJA#J?5:`A<%=3&YH,,]2P)G
    MRQ/<YUJ22_W0C7D>(A]R,5>BD07\A:DK0YPN3SFA5>FS+L66.%D6`2%'QKY;
    M>QU%_."A'?25G^TLG8X#:DX]G\J>MCQ(-EZHJVHESJ0@MX0QIY?V_[>K19*/
    M8;5!ISA()WICAFZZ,U,W]0\IPQ<K+]38)%[^&"Y_A);?!<L(*_,\0D8WVB[I
    MDJ'>HS*]M$\Z5M\G6XRZ6QQ1IQ!*)WJ.@Z41;$ :$NS>_J.CQC&]$W@N</2T
    MKCESN1@PF7WID$''@>>;>./,=MW;F5848AAA_>MO<30*O@JI#?5[=0UZ(TK'
    MJ64#W7YP>@2%@>/+-9HVHR$ZT3J)A-7T1M=-YG8XG0676W1&RXNY;).^W./B
    M7N]9M3:Q-WOV^07*_J*DMHO&/NG-:8FM3(8^U<NX79.75,%X%/4"?<DFU=M4
    M8FA>?_K^WA1Z3"L>P7^%3%FDQ3%[7)HP4)X[\MZUM2G6@073<;FD.+J<G(O9
    M23PLI=@I&.#!71*-0,4*6V-X<$;%WUIQ3N$)"F+^-)HNG?V.7_;PC$H)9Q5$
    M2U8C^="U>(Y$\#;BSZ]>LAENY7@SL3:98G&-LSK=!;)KRJKG%N5S?/[[[O;C
    MEV%=CQV?Y_Y3'$^_`%!+!PCTFH+3( 0``)8/``!02P,$"@``````$8:1+@``
    M`````````````!4```!W;',W,"]S86UP;&4T+V-L:65N="]02P,$% `(``@`
    M[X*1+@```````````````"<```!W;',W,"]S86UP;&4T+V-L:65N="]#;&EE
    M;G1(86YD;&5R+FIA=F'M55%/VS 0?D?B/YSZE*C,8M+>NCY A0;3QAA%TZ1I
    M#ZY[:;TY=F8[4(3ZWV?'3NN4%/JPQZ$JQ+[OOCO?=^=4E/VF"P1;6Z4Y%<30
    MLA+XCC#!4=K1\='Q$2\KI2W\HO>4U)8+<F514X??M:[(JA1$TA)-11F2K]?N
    MM1^D*T8^GGV_O9E<K!A6EBLYV@-;4CD7J,D'E*@YNPS+U] 1=B4+]1KT,QKC
    M:C!1TN+*OH8VBE9D^N7LYIE;CV,#CE7H-WJF<S5_?!%P(; ,:KR >:F.NTGO
    MQ=SMJ4 XB)H'.:MZ)C@#)J@Q,&DZ)=8;G#_*N8&N6D_>"Z#2_)Y:A$0<8$H6
    M?#&*@$!\K_@<N.0VZX%"_N2A`';)#8E[XRT/P+I#UG3ACY^P0'N)=([:9"V#
    M1EMK&5U)"NCPQ*R;K(1:-(I+:S)(M $,_T]<WA8$WJ/8).H3:.W-^QAD+<0H
    M6+N&N/+)7&P-,2& Z:.Q6!)56^+2DE;(S!_LDX^7-5%S&,)@.'#/E#B/!09H
    MAQ?8DHNY1MD-.O&[,7*H0W![</L(6>ODQL%<.ZVS/(=X2G=.UQ\@_6,,F5_D
    M&[ALL!LV`%YD`<JEL50R5$6GG/F&%3K[#:/G3S9S&1JSQ:<:-?B3*,@0WN8;
    MW!J%P22*;_TMO5_M\AY8_#>^^ V1+^@W*FJG'^3]1(6HS3)+L@HOZY[^<W6R
    MKI^GUL5>; /W-%R G-=%X2;2S'R_X4-G-]&B4#IP\/'I"/C[ALJ]#(>)"&9&
    M:%6YR<Y@`.[7)KQN6>(H.9Q5(=#.$(5AG"DED$H(M^DM_JG1V*Q[E4+)-@?I
    MJ?B@XPL3*@3.@:1_@Z3?K7[<G.+YM0W,KMINZEKRDHUZ_-Q!0]RQ=_4"1T.B
    M87NGN].ZQ[AU\6!ONJ':S4(SX=*56E485MXE8>G<-)[I!$ZW=6?4LF6\@=J;
    M'S!1#$/%IM9]X>^T^QPGU':IU4/3$SO?X SW"6MUC0?H:2HE#6;P3%$X2-+@
    M?HBF\%_4?RNJ^_T%4$L'"&S_=^_[`@``#0H``%!+`P04``@`" #O@I$N````
    M````````````'@```'=L<S<P+W-A;7!L930O8VQI96YT+TUA:6XN:F%V8;54
    M2VO<,!"^!_(?!I]LNFA;Z"G+'D)(R4+21Y;00PA%D6=MM6/)2/(^*/GOE>7W
    M9DM[B3&6F/DT\VGF&Y=<_.(9@JN<-I(3L[PH"3\R01*56YR?G9_)HM3&P4^^
    MY:QRDMBMM+7GE?W2&'YHG5.WU&SUY7HOL'12JV/WGNT+8HH7:$LND'W[[+>G
    M0:84;(UF*P7^(UR-S+E*"0V[:=:5VNC%_T'O,?/W,(<0NZR>20H0Q*V%.R[5
    M[]H*T-JMX\XO6RU3*+PWAK4S4F6/3\!-9B%IX0!R$P<3(U29RV&YA _!#>%1
    MN OA&]#C^R=(%HWO!<EBCW.YT;N 7A%AQNG29%7AV]67)(;HX?X6],9C$6Q3
    M,%#:@2U1R(W$-!J"U\O+Y$IWHVO SJ;T8*@GZLO24[E!(OU=&TK;KO3)EH'@
    M*_^/E==7/,1<_#72U[I)H5/++BC+T)W$Q<FBJS% D$\X&38-D6#T9<F=*R_F
    M\T[O\U;O\V@&W7F Z&22:)SD2"=@NLV4[!0UH5D/"K2R"_N&:#]$\5";$8KQ
    M-(V;T@ZBCN$JC&MK8D&I,U 54?.%!,:I.[+,]A2O\M#RKFJS";.!R?I@'19,
    M5XZ57AR.VC,L[RL6)X.R!'<BCV$T^X CP9^*%GWBDC %IT$8Y YAA\^]JIK?
    MTD4$[^I 1VF.?PQODJL=%O_^`5!+!PC/*:Y>! (``#P%``!02P,$% `(``@`
    M[X*1+@```````````````"H```!W;',W,"]S86UP;&4T+VAE;&QO+7=O<FQD
    M+6AA;F1L97(M:6YF;RYX;6QMD+$.@C 0AG<3W^'2O; X5A<7=@?GDUZDR;60
    M'I#X]H(%4HC=^OWW];_4-!@L4]1U@R[([7P",#L&`3U=547,[;.-;*N4WN=0
    M_83YK!+4C"(Z2?W0M]$A%X*^8[H4#XHCQ>4%!9L]^2ZX7G<8T4N&=\&RRKJ>
    M)Q%\DX)\'&!$'J8IT!K06K+P^L"AM\R+RW_-IEQ:$MFNZ4\F>""S^0502P<(
    M&/JK'I\```!,`0``4$L#!!0`" `(`.^"D2X````````````````D````=VQS
    M-S O<V%M<&QE-"](96QL;U=O<FQD4V5R=FEC92YJ879A18TQRP(Q#(;W0O]#
    M[*0'VN6;%$%P<7)Q<(XUW!5C6]*>-XC_7>OY*00">=Z\3T)WP9:@]"6*1UYD
    MO":FOY566MFFT0H:V P\Y.5 ITQR\^Z51FFI[/%*.:&CM>E*24MK_UOLI\6:
    M^F^U2OV)O0/'F#/LB#D>H_#Y,/;=JPQ@U,%7&!,)%A\#=!C.3#)W'?JP-K^"
    MW0BV]6[&9UO7QW<HXD,+W3<_G=W?*1 JO00P;S2!H4*SJNRAU6N>4$L'"/O]
    MA9:Z````& $``%!+`P04``@`" `,AI$N````````````````&0```'=L<S<P
    M+W-A;7!L930O<F5A9&UE+FAT;6R%5DMOVS ,O@_H?R!\7F)LQ2Z#:Z"/%=VP
    M=L4RH+TJ-E.KE25/DI,8V(\?];!C+VYW262:Y/?Q)3JK;"WRDW<G[P"R"EF9
    MNQ.=+;<"\V_GCXN?]Y=PPV0I4)LL#?*H)+A\`8WB+#&V$V@J1)N [1H\2RSN
    M;5H8DT"-)6>D4FA$F013@$KCYBQ9+M-2%:EMK=*<B:4W\.ZS--+Q#VM5=CUJ
    M]6&&%PF#*L"OBAO /:L;@6 JM3- /V 5M 8'$]AQ6\$.UV!0;WF!R\.K@LG@
    M2A.%E.A;L!7"ZL?Y/8E^MVALJM$T2I+#&HUA3V0^@[M6M@J>"L%16C"\1" 8
    M#XHZ/%<1=QE48YC-$-#*8F. RZT26RSI`#O-+9=/Q.H`^;E7SY3(^RQ3B?('
    M4D98L^(%"?B9;1FQ8<; 1FD?UR@)L(#!E,4:W: 0ZD%I4:YBIIR/))^79RG+
    MLY1@>SIC$JOCJ.<0@UHL1T0[EKV)%!4I61L%C[??8</%;'25BV*Q<V$L(J6%
    M,UKN:Y'D;[U]$Y]1L=<M%V4`IN8K5-VXHZM^>.-R/S3?$3&O$U@,1P<Y*([*
    M') 'B/G*>.3C-,+!";%4K6U:FSY\N5A\O;M.?:.@@1CG!$VW$A@-KIMW9_J$
    M$C6CV%U<A2JQ.+285#(&3=WK#,QK'HUJ=8$?=Z8L)TZI21<Q6<:E`DILA.IJ
    M-U4NQ7/^*!*/?G45JD#8_\0')==8T.73O<8G#"[1``K!.4.FAYI.0PXC_LST
    MG"\20]M$_ ,L, -L\#EGV!=U!.'GQV5X5+MI\P3%])9Q&>=G.+H>\JWP']M+
    M_S<=PF/9N"-AMDU"G3Q]UC2"%XQ;UPT=1=!TX18;995+RJN3'-Q$,\OIOAUE
    M3FV&"<)IRK-T? 7V(SH>TFM%$[+S]EP:J]LB>!^2$!<3W>*$U<JEVY/N.M#H
    M\]?[(JZ^K=^'::"L6EH.D\D^XC%B&-;N:;_91N#&W^F?4K>!:HSP=[13/?R?
    MUPQ.IP87=.D'`SBV</%Q6>(^*M^H&OMRTD(][?FE<?F2+'PL_ 502P<(9EEH
    M_0\#```U" ``4$L#!!0`" `(`.^"D2X````````````````@````=VQS-S O
    M<V%M<&QE-"]397)V97)(86YD;&5R+FIA=F&-5;%NVS 0W0/D'PZ9*!35U*E&
    MAM1(VQ1HFL9!4:#HP%!GFRU%JN3)<6#DWTN*I"W9<A(-LD6^]^[XCD<V7/SE
    M"P1JR5C)5>EXW2A\-SD].3V1=6,LP1^^XF5+4I57A)9[X/[LNES7JM2\1M=P
    M@>7W:_]W'&0;47ZY^'E[,[U<"VQ(&CTY`EMR72FTY2?4:*7X'#]?0B?8E9Z;
    MEZ!?T3F_^*G1A&MZ">T,;\K9MXN;`]H(L0,G%\8G@]('4ST^"[A46*,>36V'
    M><['_:2/8NZ..! 78JI8SJ:]5U* 4-PYF*%=H4U^@^>CKAP,J[4)+(#&RA4G
    MA%YQ0!@]EXM)?WI&5NH%),=W*7>8&'IE9 522V(C8E!L`A2 EM*5:>R\'PD@
    MOH<A/(;%V$7$E@ND)#_M!E@1AE@DA^<L*;RMH\09%%V IT&V72/\^@U!#GF%
    MUK&<HD5JK89>O P8T;DW1B'7*>U;_->B(S;<B%"+K#U[=(1U:5HJO;6:E&8Y
    MX<2%*5<**RC[3U[#-CFR+;XB&]<8[9#!03[PJH0B_9F,4DWM(VQR`0[[$ 2M
    MNSH>S!2UF(SP_"*C%>>!&BJ0)E@Q@(<F]4OVK_-,"> P=<,MQ9UQJ5>H3(/Q
    M*U#V5%(G@\?X(]1WJU?SR(_2.IHNI:I8C#'.LNA:18>4G5J/-^;U;120#MZ?
    MP9ND%U+]P57KL^[QTQROJG FA-9G^^V2P4^"DU@R&!Q#@-NR`V#,84;^GKFS
    M_F[HV4)+:QY XP/L70@,MP%R\8]MR'QP]+S:LZ@_A>FWV&3=?*.!"&B+H2P)
    M%=SI-!([=F:D/?AQ!)9)_HYPU]XL5A2[+1J<`QU>?E>&CV(+UQUVJP8@YRQ"
    MI7;$M4 S'R2^,W2X+SK%O.O38*'C:9WQ^: )T.WPT[B_NE5JYZ]__0=02P<(
    M)86WEK("```@" ``4$L!`A0`% `(``@`/8:1+@`````"``````````D`! ``
    M`````````````````$U%5$$M24Y&+_[*``!02P$"% `4``@`" `]AI$N<UT-
    M_$<```!'````% `````````````````]````345402U)3D8O34%.249%4U0N
    M34902P$"% `4``@`" #]@I$N3D:RZ!$!```/`@``% ````````````````#&
    M````=VQS-S O<')O<&5R=&EE<RYT>'102P$""@`*```````-AI$N````````
    M````````#@`````````````````9`@``=VQS-S O<V%M<&QE-"]02P$"% `4
    M``@`" #[A)$NM'9L4!$!``##`0``'0````````````````!%`@``=VQS-S O
    M<V%M<&QE-"]A<'!L:6-A=&EO;BYX;6Q02P$"% `4``@`" #+A9$N])J"TR $
    M``"6#P``%P````````````````"A`P``=VQS-S O<V%M<&QE-"]B=6EL9"YX
    M;6Q02P$""@`*```````1AI$N````````````````%0`````````````````&
    M" ``=VQS-S O<V%M<&QE-"]C;&EE;G0O4$L!`A0`% `(``@`[X*1+FS_=^_[
    M`@``#0H``"<`````````````````.0@``'=L<S<P+W-A;7!L930O8VQI96YT
    M+T-L:65N=$AA;F1L97(N:F%V85!+`0(4`!0`" `(`.^"D2[/*:Y>! (``#P%
    M```>`````````````````(D+``!W;',W,"]S86UP;&4T+V-L:65N="]-86EN
    M+FIA=F%02P$"% `4``@`" #O@I$N&/JK'I\```!,`0``*@``````````````
    M``#9#0``=VQS-S O<V%M<&QE-"]H96QL;RUW;W)L9"UH86YD;&5R+6EN9F\N
    M>&UL4$L!`A0`% `(``@`[X*1+OO]A9:Z````& $``"0`````````````````
    MT X``'=L<S<P+W-A;7!L930O2&5L;&]7;W)L9%-E<G9I8V4N:F%V85!+`0(4
    M`!0`" `(``R&D2YF66C]#P,``#4(```9`````````````````-P/``!W;',W
    M,"]S86UP;&4T+W)E861M92YH=&UL4$L!`A0`% `(``@`[X*1+B6%MY:R`@``
    M( @``" `````````````````,A,``'=L<S<P+W-A;7!L930O4V5R=F5R2&%N
    ?9&QE<BYJ879A4$L%!@`````-``T`K@,``#(6````````
    `
    end
    [sample10.zip]

  • Nice parameter names generation in web-services.xml

    Hi
    My session bean has explicit parameter names such as:
    public void createCustomer(String name, String address, String telephoneNumber);
    But inside web-services.xml for his operation, 'servicegen' generates parameters
    name 'string, string0, string1'. Composing the xml becomes a tedious job!
    Is there a way to have this file generated automatically but with the original
    parameter names?
    Thanks for the help,
    guy

    Can source2wsdd be applied to an EJB implementation - the doc mentions only Java class-implemented web service - has this been
    fixed or being fixed in the next wls 7 service pack.
    http://edocs.bea.com/wls/docs70/webserv/assemble.html#1056639
    Thanks.
    Darma
    Shridhar Mysore wrote:
    In WLS 7.0.1 onwards, using "source2wsdd" ant task (quo vide http://e-docs.bea.com/wls/docs70/webserv/anttasks.html#1080421)
    you would be able to preserve the parameter names.
    For instance, if you do :
    <source2wsdd
    javaSource="MyService.java"
    ddFile="web-services.xml"
    typesInfo="temp_dir/WEB-INF/classes/types.xml"
    serviceURI="/MyService" >
    <classpath>
    <pathelement path="temp_dir/WEB-INF/classes"/>
    <pathelement path="${java.class.path}"/>
    </classpath>
    </source2wsdd>
    Then, the signature of a method in the backend component,
    public void testMethod( int a, float fval, String name ){
    would get translated mapped inside web-services.xml as :
    - <operation component="MyService" name="testMethod" method="testMethod">
    - <params>
    <param name="a" class-name="int" type="parms:int" style="in" xmlns:parms="http://www.w3.org/2001/XMLSchema"
    location="body" />
    <param name="fval" class-name="float" type="parms:float" style="in" xmlns:parms="http://www.w3.org/2001/XMLSchema"
    location="body" />
    <param name="name" class-name="java.lang.String" type="parms:string" style="in"
    xmlns:parms="http://www.w3.org/2001/XMLSchema" location="body" />
    </params>
    </operation>
    where you would see that the parameter names are being preserved.
    Regards
    Shridhar
    "Guy Deffaux" <[email protected]> wrote:
    Hi
    My session bean has explicit parameter names such as:
    public void createCustomer(String name, String address, String telephoneNumber);
    But inside web-services.xml for his operation, 'servicegen' generates
    parameters
    name 'string, string0, string1'. Composing the xml becomes a tedious
    job!
    Is there a way to have this file generated automatically but with the
    original
    parameter names?
    Thanks for the help,
    guy

  • Updating the web-services.xml for WS-Security

    If I wanted to change my webservice from encryption of both the request and response to just encryption of the request how do I manually change the web-services.xml file ??? Do I have to un-archive the ear and re-archive the ear everytime I want to make security changes to the web-services.xml file ?

    It works. Thanks,
    Ioana
    "Neal Yin" <[email protected]> wrote:
    The error means your EJB is not deployed.
    Adding a EJB module to your application.xml file of the ear should fixe
    it.
    <application>
    <display-name />
    <module>
    <web>
    <web-uri>dox_sdi.war</web-uri>
    </web>
    </module>
    <module>
    <ejb>DocumentService.jar</ejb>
    </module>
    </application>
    "Ioana Meissner" <[email protected]> wrote in message
    news:3cf640cc$[email protected]..
    I have used the following example for my own web service with EJBcomponent and SOAP
    Message Handler Chain:
    http://e-docs.bea.com/wls/docs70/webServices/dd.html#1058208
    I have a deployment error:
    javax.naming.NameNotFoundException: Unable to resolve'app/ejb/DocumentService.j
    ar#DocumentService/home' Resolved: 'app/ejb'Unresolved:'DocumentService.jar#Doc
    umentService' ; remaining name 'DocumentService.jar#DocumentService/home'
    In attachement is the ear file.
    Is there a problem in web-services.xml?
    Thanks

Maybe you are looking for

  • HP Officejet pro 8610, wanting to print transparen​cy

    I have the HP Officejet Pro 8610 all in one printer, and want to attempt home screen printing some shirts for my 9 year old's hockey team. My friend lent me her YuDu home screen printing machine. I am needing to print the design on a transparency she

  • Upgrade Weblogic Server Issue

    Hi, I have an installation of oracle weblogic server 10.3.5.0 with ADF 11.1.1.5.0. I can upgrade weblogic server to 12.1.3.0 ?

  • 8i Enterprise Edition

    Is the recently released "815ship.tgz" Oracle 8i the Enterprise Edition or the Standard Edition? I need to use fine grained access control. Thanks, Jeff null

  • Matching words

    Hi all, i have this table , i want to retrieve words that match my word that i used it for search not all characters should match i mean how can i match words without match end of words by 3 or 4 characters that in case of my word more that 5 charact

  • Sync calendars with out usb cable

    I have searched the apple site and forums but I am still confused. Should I be able to sync my calendars over .mac. I have only been able to do it so far by usb in itunes. I think that I have my .mac set up on my iphone. I want it to sync in the back