You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by keith chapman <ke...@gmail.com> on 2007/12/13 07:34:00 UTC
[Axis2] Added option to control cookie policy on http Request
Hi,
I've added an option to the messagecontext to control the cookie policy on
http Request. This can be set as follows
options.setProperty(HTTPConstants.COOKIE_POLICY, CookiePolicy.IGNORE_COOKIES
);
Valid values for cookie policy are
public static final java.lang.String BROWSER_COMPATIBILITY =
"compatibility";
public static final java.lang.String NETSCAPE = "netscape";
public static final java.lang.String RFC_2109 = "rfc2109";
public static final java.lang.String IGNORE_COOKIES = "ignoreCookies";
public static final java.lang.String DEFAULT = "default";
These constants are located in
org.apache.commons.httpclient.cookie.CookiePolicy
Thanks,
Keith.
--
Keith Chapman
WSO2 Inc.
Oxygen for Web Services Developers.
http://wso2.org/
RE: Removing SOAP 1.2 and HTTP for POJO services
Posted by "Hoda, Nadeem [USA]" <ho...@bah.com>.
Thanks all.
Was it ever the intention of Axis 2 Java2WSDL to be WS-I BP Compliant?
My impression for a long time was that Axis2 was tailored for the
contract-first approach, but supported code-first if necessary or
desired, i.e., the strong emphasis is on contract-first.
Perhaps this can be a feature that can be added in the future, for
example using Axis2 tailored tools like jibx2wsdl for WSDL
auto-generation within the Axis2 codebase (jibx2wsdl WSDLs are WS-I BP
Compliant, though seems as though jibx2wsdl requires Java5). And
further, the method of WSDL generation could be selected, etc...
Thanks,
Nadeem
-----Original Message-----
From: Anne Thomas Manes [mailto:atmanes@gmail.com]
Sent: Tuesday, December 18, 2007 5:03 PM
To: axis-user@ws.apache.org
Subject: Re: Removing SOAP 1.2 and HTTP for POJO services
Nadir,
The generated WSDL is invalid -- and it's not just related to the
targetNamespaces.
Looking at the first WSDL the first inline schema ("impl") references
elements from the three following schemas ("delegate", "utils", and
"transferobjects"), but it neglects to import those namespaces.
The WSDL is also not WS-I BP compliant.
Again, looling at the first WSDL, the service has more than one request
message that contains no parts. WS-I states that each operation must
have a unique signature, where the signature is defined as the qname of
the child element of the SOAP Body. A message with no parts has no child
element in the SOAP Body. In a situation like this,
Axis2 uses the endpoint URL or the Action parameter to determine the
signature, but that approach is not WS-I BP compliant.
Anne
On Dec 17, 2007 7:29 PM, Nadir Amra <am...@us.ibm.com> wrote:
> Nadeem,
>
> I assume these WSDLs are generated by the AXIS2. There currently is a
> bug in how AXIS2 sets the target namespace for the schemas (see
> http://issues.apache.org/jira/browse/AXIS2-3301).
>
> However, we have gotten around the problem as follows. Assuming the
> package name for the POJO is: wsbeans.converttemp, then add the
> following line in services.xml:
>
> <schema schemaNamespace="http://converttemp.wsbeans/xsd" />
>
> You rmileage may vary, but this worked for me.....
>
>
> Nadir K. Amra
>
>
> "Hoda, Nadeem [USA]" <ho...@bah.com> wrote on 12/17/2007
> 04:31:55
> PM:
>
>
> >
> >
> > Nadir,
> >
> > Thanks.
> >
> > Our services fail Basic Profile 1.1 compliance due to the following
> > WSDL
> > constructs:
> >
> > First Service WSDL:
> >
> > Fails BP2120
> >
> > No assertion from ws-i test tool.
> >
> > Fails BP2122
> >
> > Assertion: BP2122
> >
> > Result
> > failed
> > Failure Message
> > A wsdl:types element contained a data type definition that is not an
> > XML schema definition.
> > Failure Detail Message
> > Error: s4s-elt-schema-ns: The namespace of element 'import' must be
> > from the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
> > Error: s4s-elt-schema-ns: The namespace of element 'import' must be
> > from the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
> > Error: s4s-elt-schema-ns: The namespace of element 'import' must be
> > from the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
> > Error: s4s-elt-schema-ns: The namespace of element 'import' must be
> > from the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
> >
> >
> > Element Location:
> > lineNumber=4
> >
> >
> > Second Service WSDL:
> >
> > Fails BP2122
> >
> > Assertion: BP2122
> >
> > Result
> > failed
> > Failure Message
> > A wsdl:types element contained a data type definition that is not an
> > XML schema definition.
> > Failure Detail Message
> > Error: s4s-elt-schema-ns: The namespace of element 'import' must be
> > from the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
> > Error: s4s-elt-schema-ns: The namespace of element 'import' must be
> > from the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
> > Error: s4s-elt-schema-ns: The namespace of element 'import' must be
> > from the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
> >
> >
> > Element Location:
> > lineNumber=4
> >
> > Any pointers would be appreciated as compliance is a requirement for
> > our system. Since we have gone this far with POJO services,
> > reverting to contract-first would be time consuming and additional
work.
> >
> > I have attached the wsdls.
> >
> > Thanks,
> >
> > Nadeem
> >
> > -----Original Message-----
> > From: Nadir Amra [mailto:amra@us.ibm.com]
> > Sent: Sunday, December 16, 2007 7:02 PM
> > To: axis-user@ws.apache.org
> > Cc: axis-user@ws.apache.org
> > Subject: RE: Removing SOAP 1.2 and HTTP for POJO services
> >
> > Nadeem,
> >
> > Can you explain more about "WS-I Basic Profile 1.1 compliance from
> > POJO Services"? Why did it fail?
> >
> > As for excluding operations, you can add the following in
> > services.xml file for the service:
> >
> > <excludeOperations>
> > <operation>findcustomers</operation>
> > <operation>disablecustomers</operation>
> > </excludeOperations>
> >
> > The above excludes two operations....
> >
> > Nadir K. Amra
> >
> >
> > "Hoda, Nadeem [USA]" <ho...@bah.com> wrote on 12/16/2007
> > 03:20:12
> > AM:
> >
> > >
> > >
> > > Thank you Nadir. That worked perfectly.
> > >
> > > Two additional questions:
> > >
> > > - Is there a way to get WS-I Basic Profile 1.1 compliance from
> > > POJO Services?
> > > (currently, my particular service fails)
> > >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Removing SOAP 1.2 and HTTP for POJO services
Posted by Anne Thomas Manes <at...@gmail.com>.
Nadir,
The generated WSDL is invalid -- and it's not just related to the
targetNamespaces.
Looking at the first WSDL the first inline schema ("impl") references
elements from the three following schemas ("delegate", "utils", and
"transferobjects"), but it neglects to import those namespaces.
The WSDL is also not WS-I BP compliant.
Again, looling at the first WSDL, the service has more than one
request message that contains no parts. WS-I states that each
operation must have a unique signature, where the signature is defined
as the qname of the child element of the SOAP Body. A message with no
parts has no child element in the SOAP Body. In a situation like this,
Axis2 uses the endpoint URL or the Action parameter to determine the
signature, but that approach is not WS-I BP compliant.
Anne
On Dec 17, 2007 7:29 PM, Nadir Amra <am...@us.ibm.com> wrote:
> Nadeem,
>
> I assume these WSDLs are generated by the AXIS2. There currently is a bug
> in how AXIS2 sets the target namespace for the schemas (see
> http://issues.apache.org/jira/browse/AXIS2-3301).
>
> However, we have gotten around the problem as follows. Assuming the
> package name for the POJO is: wsbeans.converttemp, then add the following
> line in services.xml:
>
> <schema schemaNamespace="http://converttemp.wsbeans/xsd" />
>
> You rmileage may vary, but this worked for me.....
>
>
> Nadir K. Amra
>
>
> "Hoda, Nadeem [USA]" <ho...@bah.com> wrote on 12/17/2007 04:31:55
> PM:
>
>
> >
> >
> > Nadir,
> >
> > Thanks.
> >
> > Our services fail Basic Profile 1.1 compliance due to the following WSDL
> > constructs:
> >
> > First Service WSDL:
> >
> > Fails BP2120
> >
> > No assertion from ws-i test tool.
> >
> > Fails BP2122
> >
> > Assertion: BP2122
> >
> > Result
> > failed
> > Failure Message
> > A wsdl:types element contained a data type definition that is not an XML
> > schema definition.
> > Failure Detail Message
> > Error: s4s-elt-schema-ns: The namespace of element 'import' must be from
> > the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
> > Error: s4s-elt-schema-ns: The namespace of element 'import' must be from
> > the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
> > Error: s4s-elt-schema-ns: The namespace of element 'import' must be from
> > the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
> > Error: s4s-elt-schema-ns: The namespace of element 'import' must be from
> > the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
> >
> >
> > Element Location:
> > lineNumber=4
> >
> >
> > Second Service WSDL:
> >
> > Fails BP2122
> >
> > Assertion: BP2122
> >
> > Result
> > failed
> > Failure Message
> > A wsdl:types element contained a data type definition that is not an XML
> > schema definition.
> > Failure Detail Message
> > Error: s4s-elt-schema-ns: The namespace of element 'import' must be from
> > the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
> > Error: s4s-elt-schema-ns: The namespace of element 'import' must be from
> > the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
> > Error: s4s-elt-schema-ns: The namespace of element 'import' must be from
> > the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
> >
> >
> > Element Location:
> > lineNumber=4
> >
> > Any pointers would be appreciated as compliance is a requirement for our
> > system. Since we have gone this far with POJO services, reverting to
> > contract-first would be time consuming and additional work.
> >
> > I have attached the wsdls.
> >
> > Thanks,
> >
> > Nadeem
> >
> > -----Original Message-----
> > From: Nadir Amra [mailto:amra@us.ibm.com]
> > Sent: Sunday, December 16, 2007 7:02 PM
> > To: axis-user@ws.apache.org
> > Cc: axis-user@ws.apache.org
> > Subject: RE: Removing SOAP 1.2 and HTTP for POJO services
> >
> > Nadeem,
> >
> > Can you explain more about "WS-I Basic Profile 1.1 compliance from POJO
> > Services"? Why did it fail?
> >
> > As for excluding operations, you can add the following in services.xml
> > file for the service:
> >
> > <excludeOperations>
> > <operation>findcustomers</operation>
> > <operation>disablecustomers</operation>
> > </excludeOperations>
> >
> > The above excludes two operations....
> >
> > Nadir K. Amra
> >
> >
> > "Hoda, Nadeem [USA]" <ho...@bah.com> wrote on 12/16/2007 03:20:12
> > AM:
> >
> > >
> > >
> > > Thank you Nadir. That worked perfectly.
> > >
> > > Two additional questions:
> > >
> > > - Is there a way to get WS-I Basic Profile 1.1 compliance from POJO
> > > Services?
> > > (currently, my particular service fails)
> > >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Removing SOAP 1.2 and HTTP for POJO services
Posted by Martin Gainty <mg...@hotmail.com>.
finally got LookupDataService service deployed
Unfortunately ./META-INF/services.xml was never created by wsdl2java utility
attaching a sample services.xml which I created
Martin-
GMT+5
----- Original Message -----
From: "Hoda, Nadeem [USA]" <ho...@bah.com>
To: <ax...@ws.apache.org>
Sent: Monday, December 17, 2007 5:31 PM
Subject: RE: Removing SOAP 1.2 and HTTP for POJO services
Nadir,
Thanks.
Our services fail Basic Profile 1.1 compliance due to the following WSDL
constructs:
First Service WSDL:
Fails BP2120
No assertion from ws-i test tool.
Fails BP2122
Assertion: BP2122
Result
failed
Failure Message
A wsdl:types element contained a data type definition that is not an XML
schema definition.
Failure Detail Message
Error: s4s-elt-schema-ns: The namespace of element 'import' must be from
the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
Error: s4s-elt-schema-ns: The namespace of element 'import' must be from
the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
Error: s4s-elt-schema-ns: The namespace of element 'import' must be from
the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
Error: s4s-elt-schema-ns: The namespace of element 'import' must be from
the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
Element Location:
lineNumber=4
Second Service WSDL:
Fails BP2122
Assertion: BP2122
Result
failed
Failure Message
A wsdl:types element contained a data type definition that is not an XML
schema definition.
Failure Detail Message
Error: s4s-elt-schema-ns: The namespace of element 'import' must be from
the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
Error: s4s-elt-schema-ns: The namespace of element 'import' must be from
the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
Error: s4s-elt-schema-ns: The namespace of element 'import' must be from
the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
Element Location:
lineNumber=4
Any pointers would be appreciated as compliance is a requirement for our
system. Since we have gone this far with POJO services, reverting to
contract-first would be time consuming and additional work.
I have attached the wsdls.
Thanks,
Nadeem
-----Original Message-----
From: Nadir Amra [mailto:amra@us.ibm.com]
Sent: Sunday, December 16, 2007 7:02 PM
To: axis-user@ws.apache.org
Cc: axis-user@ws.apache.org
Subject: RE: Removing SOAP 1.2 and HTTP for POJO services
Nadeem,
Can you explain more about "WS-I Basic Profile 1.1 compliance from POJO
Services"? Why did it fail?
As for excluding operations, you can add the following in services.xml
file for the service:
<excludeOperations>
<operation>findcustomers</operation>
<operation>disablecustomers</operation>
</excludeOperations>
The above excludes two operations....
Nadir K. Amra
"Hoda, Nadeem [USA]" <ho...@bah.com> wrote on 12/16/2007 03:20:12
AM:
>
>
> Thank you Nadir. That worked perfectly.
>
> Two additional questions:
>
> - Is there a way to get WS-I Basic Profile 1.1 compliance from POJO
> Services?
> (currently, my particular service fails)
>
> - Is there a way to exclude certain public methods from the WSDL for a
> POJO Service?
> (e.g., excluding public getters/setters)
>
> Thanks,
>
> Nadeem
>
>
>
> -----Original Message-----
> From: Nadir Amra [mailto:amra@us.ibm.com]
> Sent: Thursday, December 13, 2007 10:19 PM
> To: axis-user@ws.apache.org
> Subject: Re: Removing SOAP 1.2 and HTTP for POJO services
>
> Nadeem
>
> You will need to get the latest code (a nightly build) to use these,
> but in axis2.xml config file, you can do the following:
>
> <!-- Following parameter will completely disable REST handling in
Axis2-->
> <parameter name="disableREST" locked="true">true</parameter>
>
> <!-- Following parameter will suppress generation of SOAP 1.2
> bindings in auto-generated WSDL files -->
> <parameter name="disableSOAP12" locked="true">true</parameter>
>
> This will disable it for all services...there currently no way to
> selectively do this on a per service basis. There is a JIRA for this
> enhancement.
>
> Nadir K. Amra
>
>
> "Hoda, Nadeem [USA]" <ho...@bah.com> wrote on 12/13/2007
> 05:17:49
> AM:
>
> >
> >
> > In a simple POJO service with no WSDL file (only relying on the
> > ServiceClass in services.xml), how do you disable/get rid of SOAP 1.
> > 2 and HTTP bindings and ports if you only want the SOAP 1.1 port and
> binding?
> >
> > Is there a simple config/options/parameter for this?
> >
> > Thanks,
> >
> > Nadeem
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
----------------------------------------------------------------------------
----
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
RE: Removing SOAP 1.2 and HTTP for POJO services
Posted by Nadir Amra <am...@us.ibm.com>.
Nadeem,
I assume these WSDLs are generated by the AXIS2. There currently is a bug
in how AXIS2 sets the target namespace for the schemas (see
http://issues.apache.org/jira/browse/AXIS2-3301).
However, we have gotten around the problem as follows. Assuming the
package name for the POJO is: wsbeans.converttemp, then add the following
line in services.xml:
<schema schemaNamespace="http://converttemp.wsbeans/xsd" />
You rmileage may vary, but this worked for me.....
Nadir K. Amra
"Hoda, Nadeem [USA]" <ho...@bah.com> wrote on 12/17/2007 04:31:55
PM:
>
>
> Nadir,
>
> Thanks.
>
> Our services fail Basic Profile 1.1 compliance due to the following WSDL
> constructs:
>
> First Service WSDL:
>
> Fails BP2120
>
> No assertion from ws-i test tool.
>
> Fails BP2122
>
> Assertion: BP2122
>
> Result
> failed
> Failure Message
> A wsdl:types element contained a data type definition that is not an XML
> schema definition.
> Failure Detail Message
> Error: s4s-elt-schema-ns: The namespace of element 'import' must be from
> the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
> Error: s4s-elt-schema-ns: The namespace of element 'import' must be from
> the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
> Error: s4s-elt-schema-ns: The namespace of element 'import' must be from
> the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
> Error: s4s-elt-schema-ns: The namespace of element 'import' must be from
> the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
>
>
> Element Location:
> lineNumber=4
>
>
> Second Service WSDL:
>
> Fails BP2122
>
> Assertion: BP2122
>
> Result
> failed
> Failure Message
> A wsdl:types element contained a data type definition that is not an XML
> schema definition.
> Failure Detail Message
> Error: s4s-elt-schema-ns: The namespace of element 'import' must be from
> the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
> Error: s4s-elt-schema-ns: The namespace of element 'import' must be from
> the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
> Error: s4s-elt-schema-ns: The namespace of element 'import' must be from
> the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
>
>
> Element Location:
> lineNumber=4
>
> Any pointers would be appreciated as compliance is a requirement for our
> system. Since we have gone this far with POJO services, reverting to
> contract-first would be time consuming and additional work.
>
> I have attached the wsdls.
>
> Thanks,
>
> Nadeem
>
> -----Original Message-----
> From: Nadir Amra [mailto:amra@us.ibm.com]
> Sent: Sunday, December 16, 2007 7:02 PM
> To: axis-user@ws.apache.org
> Cc: axis-user@ws.apache.org
> Subject: RE: Removing SOAP 1.2 and HTTP for POJO services
>
> Nadeem,
>
> Can you explain more about "WS-I Basic Profile 1.1 compliance from POJO
> Services"? Why did it fail?
>
> As for excluding operations, you can add the following in services.xml
> file for the service:
>
> <excludeOperations>
> <operation>findcustomers</operation>
> <operation>disablecustomers</operation>
> </excludeOperations>
>
> The above excludes two operations....
>
> Nadir K. Amra
>
>
> "Hoda, Nadeem [USA]" <ho...@bah.com> wrote on 12/16/2007 03:20:12
> AM:
>
> >
> >
> > Thank you Nadir. That worked perfectly.
> >
> > Two additional questions:
> >
> > - Is there a way to get WS-I Basic Profile 1.1 compliance from POJO
> > Services?
> > (currently, my particular service fails)
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: Removing SOAP 1.2 and HTTP for POJO services
Posted by "Hoda, Nadeem [USA]" <ho...@bah.com>.
Nadir,
Thanks.
Our services fail Basic Profile 1.1 compliance due to the following WSDL
constructs:
First Service WSDL:
Fails BP2120
No assertion from ws-i test tool.
Fails BP2122
Assertion: BP2122
Result
failed
Failure Message
A wsdl:types element contained a data type definition that is not an XML
schema definition.
Failure Detail Message
Error: s4s-elt-schema-ns: The namespace of element 'import' must be from
the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
Error: s4s-elt-schema-ns: The namespace of element 'import' must be from
the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
Error: s4s-elt-schema-ns: The namespace of element 'import' must be from
the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
Error: s4s-elt-schema-ns: The namespace of element 'import' must be from
the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
Element Location:
lineNumber=4
Second Service WSDL:
Fails BP2122
Assertion: BP2122
Result
failed
Failure Message
A wsdl:types element contained a data type definition that is not an XML
schema definition.
Failure Detail Message
Error: s4s-elt-schema-ns: The namespace of element 'import' must be from
the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
Error: s4s-elt-schema-ns: The namespace of element 'import' must be from
the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
Error: s4s-elt-schema-ns: The namespace of element 'import' must be from
the schema namespace, 'http://www.w3.org/2001/XMLSchema'.
Element Location:
lineNumber=4
Any pointers would be appreciated as compliance is a requirement for our
system. Since we have gone this far with POJO services, reverting to
contract-first would be time consuming and additional work.
I have attached the wsdls.
Thanks,
Nadeem
-----Original Message-----
From: Nadir Amra [mailto:amra@us.ibm.com]
Sent: Sunday, December 16, 2007 7:02 PM
To: axis-user@ws.apache.org
Cc: axis-user@ws.apache.org
Subject: RE: Removing SOAP 1.2 and HTTP for POJO services
Nadeem,
Can you explain more about "WS-I Basic Profile 1.1 compliance from POJO
Services"? Why did it fail?
As for excluding operations, you can add the following in services.xml
file for the service:
<excludeOperations>
<operation>findcustomers</operation>
<operation>disablecustomers</operation>
</excludeOperations>
The above excludes two operations....
Nadir K. Amra
"Hoda, Nadeem [USA]" <ho...@bah.com> wrote on 12/16/2007 03:20:12
AM:
>
>
> Thank you Nadir. That worked perfectly.
>
> Two additional questions:
>
> - Is there a way to get WS-I Basic Profile 1.1 compliance from POJO
> Services?
> (currently, my particular service fails)
>
> - Is there a way to exclude certain public methods from the WSDL for a
> POJO Service?
> (e.g., excluding public getters/setters)
>
> Thanks,
>
> Nadeem
>
>
>
> -----Original Message-----
> From: Nadir Amra [mailto:amra@us.ibm.com]
> Sent: Thursday, December 13, 2007 10:19 PM
> To: axis-user@ws.apache.org
> Subject: Re: Removing SOAP 1.2 and HTTP for POJO services
>
> Nadeem
>
> You will need to get the latest code (a nightly build) to use these,
> but in axis2.xml config file, you can do the following:
>
> <!-- Following parameter will completely disable REST handling in
Axis2-->
> <parameter name="disableREST" locked="true">true</parameter>
>
> <!-- Following parameter will suppress generation of SOAP 1.2
> bindings in auto-generated WSDL files -->
> <parameter name="disableSOAP12" locked="true">true</parameter>
>
> This will disable it for all services...there currently no way to
> selectively do this on a per service basis. There is a JIRA for this
> enhancement.
>
> Nadir K. Amra
>
>
> "Hoda, Nadeem [USA]" <ho...@bah.com> wrote on 12/13/2007
> 05:17:49
> AM:
>
> >
> >
> > In a simple POJO service with no WSDL file (only relying on the
> > ServiceClass in services.xml), how do you disable/get rid of SOAP 1.
> > 2 and HTTP bindings and ports if you only want the SOAP 1.1 port and
> binding?
> >
> > Is there a simple config/options/parameter for this?
> >
> > Thanks,
> >
> > Nadeem
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: Removing SOAP 1.2 and HTTP for POJO services
Posted by Nadir Amra <am...@us.ibm.com>.
Nadeem,
Can you explain more about "WS-I Basic Profile 1.1 compliance from POJO
Services"? Why did it fail?
As for excluding operations, you can add the following in services.xml
file for the service:
<excludeOperations>
<operation>findcustomers</operation>
<operation>disablecustomers</operation>
</excludeOperations>
The above excludes two operations....
Nadir K. Amra
"Hoda, Nadeem [USA]" <ho...@bah.com> wrote on 12/16/2007 03:20:12
AM:
>
>
> Thank you Nadir. That worked perfectly.
>
> Two additional questions:
>
> - Is there a way to get WS-I Basic Profile 1.1 compliance from POJO
> Services?
> (currently, my particular service fails)
>
> - Is there a way to exclude certain public methods from the WSDL for a
> POJO Service?
> (e.g., excluding public getters/setters)
>
> Thanks,
>
> Nadeem
>
>
>
> -----Original Message-----
> From: Nadir Amra [mailto:amra@us.ibm.com]
> Sent: Thursday, December 13, 2007 10:19 PM
> To: axis-user@ws.apache.org
> Subject: Re: Removing SOAP 1.2 and HTTP for POJO services
>
> Nadeem
>
> You will need to get the latest code (a nightly build) to use these, but
> in axis2.xml config file, you can do the following:
>
> <!-- Following parameter will completely disable REST handling
> in
Axis2-->
> <parameter name="disableREST" locked="true">true</parameter>
>
> <!-- Following parameter will suppress generation of SOAP 1.2
> bindings in auto-generated WSDL files -->
> <parameter name="disableSOAP12" locked="true">true</parameter>
>
> This will disable it for all services...there currently no way to
> selectively do this on a per service basis. There is a JIRA for this
> enhancement.
>
> Nadir K. Amra
>
>
> "Hoda, Nadeem [USA]" <ho...@bah.com> wrote on 12/13/2007 05:17:49
> AM:
>
> >
> >
> > In a simple POJO service with no WSDL file (only relying on the
> > ServiceClass in services.xml), how do you disable/get rid of SOAP 1.
> > 2 and HTTP bindings and ports if you only want the SOAP 1.1 port and
> binding?
> >
> > Is there a simple config/options/parameter for this?
> >
> > Thanks,
> >
> > Nadeem
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: Removing SOAP 1.2 and HTTP for POJO services
Posted by "Hoda, Nadeem [USA]" <ho...@bah.com>.
Thank you Nadir. That worked perfectly.
Two additional questions:
- Is there a way to get WS-I Basic Profile 1.1 compliance from POJO
Services?
(currently, my particular service fails)
- Is there a way to exclude certain public methods from the WSDL for a
POJO Service?
(e.g., excluding public getters/setters)
Thanks,
Nadeem
-----Original Message-----
From: Nadir Amra [mailto:amra@us.ibm.com]
Sent: Thursday, December 13, 2007 10:19 PM
To: axis-user@ws.apache.org
Subject: Re: Removing SOAP 1.2 and HTTP for POJO services
Nadeem
You will need to get the latest code (a nightly build) to use these, but
in axis2.xml config file, you can do the following:
<!-- Following parameter will completely disable REST handling in
Axis2-->
<parameter name="disableREST" locked="true">true</parameter>
<!-- Following parameter will suppress generation of SOAP 1.2
bindings in auto-generated WSDL files -->
<parameter name="disableSOAP12" locked="true">true</parameter>
This will disable it for all services...there currently no way to
selectively do this on a per service basis. There is a JIRA for this
enhancement.
Nadir K. Amra
"Hoda, Nadeem [USA]" <ho...@bah.com> wrote on 12/13/2007 05:17:49
AM:
>
>
> In a simple POJO service with no WSDL file (only relying on the
> ServiceClass in services.xml), how do you disable/get rid of SOAP 1.
> 2 and HTTP bindings and ports if you only want the SOAP 1.1 port and
binding?
>
> Is there a simple config/options/parameter for this?
>
> Thanks,
>
> Nadeem
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Removing SOAP 1.2 and HTTP for POJO services
Posted by Nadir Amra <am...@us.ibm.com>.
Nadeem
You will need to get the latest code (a nightly build) to use these, but
in axis2.xml config file, you can do the following:
<!-- Following parameter will completely disable REST handling in
Axis2-->
<parameter name="disableREST" locked="true">true</parameter>
<!-- Following parameter will suppress generation of SOAP 1.2 bindings
in auto-generated WSDL files -->
<parameter name="disableSOAP12" locked="true">true</parameter>
This will disable it for all services...there currently no way to
selectively do this on a per service basis. There is a JIRA for this
enhancement.
Nadir K. Amra
"Hoda, Nadeem [USA]" <ho...@bah.com> wrote on 12/13/2007 05:17:49
AM:
>
>
> In a simple POJO service with no WSDL file (only relying on the
> ServiceClass in services.xml), how do you disable/get rid of SOAP 1.
> 2 and HTTP bindings and ports if you only want the SOAP 1.1 port and
binding?
>
> Is there a simple config/options/parameter for this?
>
> Thanks,
>
> Nadeem
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Removing SOAP 1.2 and HTTP for POJO services
Posted by "Hoda, Nadeem [USA]" <ho...@bah.com>.
In a simple POJO service with no WSDL file (only relying on the
ServiceClass in services.xml), how do you disable/get rid of SOAP 1.2
and HTTP bindings and ports if you only want the SOAP 1.1 port and
binding?
Is there a simple config/options/parameter for this?
Thanks,
Nadeem