Apache WSS4J's WS Security Implementation - WSS Licensing Requirements?

Hi, It seems that WS Security requires licensing arrangements from Microsoft, Verisign, and IBM based on OASIS WS Security TC IPR statement http://www.oasis-open.org/committees/wss/ipr.php So, can someone please clarify: 1)if the users who to develop and deploy AXIS clients(using WS Security

Re: Attachments - AXIS Server, .NET Client

Hi, 1) What level of support currently there is inAXIS 1.2 for message attachments. E.g., does it support both DIME and and SwA? 2) WS-I has SOAP attachment profile finalized in August 2004. Does AXIS support SOAP attachment profile:

axis 1.2

do u know where latest axis is available also can we build custom de-serializers in axis that would handle request message from client that send payloads with different namespace yet we want to use same generated code since the schema structure is same. Do you Yahoo!? Yahoo! Mail is new and

Fwd: AXIS De-serialization/Serialization w/ and w/o namespace

Do you Yahoo!? Yahoo! Mail is new and improved - Check it out!---BeginMessage--- Is it possible to use one WSDL/XSD definition for a web service implementation in AXIS 1.1 or 1.2such that we can de-serialize and serialize request and response payloads from and to 2 different types of clients:

Extending Abstract Data Types for XML Payloads in SOAP Doc/Lit Messages

I am using AXIS 1.1 to develop web services that require interoperation with .NET 1.1 and Java clients (that may run ondifferent Java/SOAP client run-times using Doc/Lit SOAP binding. The message payload that is used to instantiaite the particular payload instances for the SOAP message actually

Re: Axis and Basic Profile 1.0a

1. Which WS-I testing tools can be used toensure that the WSDL/XSDare clean? 2. What kinds of test coverage does the WS-I testing tools have for checking SOAP request and response messages? -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED]Sent: Wednesday, January 21,

Re: Regarding importing XML Schema files...

I don't see any requirement inWS-I BP 1.0a that specifies that imported XSDs can not import additional XSDs. However, it is reasonable to allow WSDL to import other .wsdl's. BTW, I believe .NET 1.1 Framework/VS.NET 2003 WSDL processor does not resolve multiple imported XSDs, hence you have to

WSDL Generated Code produce 100% Schema Conformant Document Style Payloads

In AXIS 1.1 if we use Doc/Lit option then will the XSD schemas based WSDL generated Java server-side skeleton code alwaysproduce schema conforming XML instances in response messages and always be able detect invalid request message payloads when the corresponding (schema-based) generated code

Can AXIS 1.1 Web Services have operations sharing same Requests/Responses?

In AXIS using the WSDL2Java tool it seems that for Document style SOAP messages, i.e., Doc/Lit messaging option, there is a limitation that if we have more than two or more operations for a given web service then each of those web services have to have different (i.e., unique) Request and

Re: Can AXIS 1.1 Web Services have operations sharing same Requests/Responses?

Hi Anne, Thanks for your clarification. So, if the WS-I BP 1.0 requirement is to ensure that each operation have a unique input message for (Doc/Lit based SOAP messaging) then it seems we can possibly satisfy that requirement by allowing theone operation's input message be

AXIS 1.2 Release Plan (Was: RE: Moving toward Axis 1.2 beta and release)

I think it is extremely important that we release: 0)AXIS 1.2 Beta by early Jan. '04 1) AXIS 1.2 Final Release by mid-Jan. '04 2) AXIS 1.3 Release by mid-Feb to mid-March '04 AXIS 1.2 should be bug-fix release of AXIS 1.1 such that we have minimal code changes in AXIS 1.1-based web services

Custom Serializer and Deserializer

Is it possible to use with AXIS custom serializer and de-serializer in the handler framework? E.g. will employing such serializer and de-serializer be portable/interoperable with multiple client run-times? Thanks Rupesh Sharma wrote: Can I modify the BeanSerializer.java used by Axis to do bean

Difference between SOAP 1.1 vs 1.2 SOAPAction Support in AXIS 1.1

Hi, In SOAP 1.1 SOAPAction: is a HTTP Header that corresponds with soapbind:operation soapAction="...". How is the functionality of SOAPAction Header element different in SOAP 1.2? DoesAXIS support both SOAP 1.1 and SOAP 1.2 and if it does then what are the guidelines to use SOAPAction w.r.t.

Re: Fwd: WSS4J - WS-Security Implementation (was Re: axis-wsse)

1) Any plans to develop a SAML tokenas an enhancement to current WS-Security implementation? 2) Any idea when the currently available WS-Security PasswordToken support will beome part ofan official AXIS 1.x release? ThanksDavanum Srinivas [EMAIL PROTECTED] wrote: FYI.--- Davanum Srinivas

Support for xml:lang in XSD/WSDL documentation element

Does AXIS support language identifier for XSD schema documentation such that the WSDL2Java compiler will be able to process the WSDL docs correctly even if the XSD schema that it imports includes: xs:annotation xs:documentation xml:lang="en" . Thanks Do you Yahoo!? Yahoo! SiteBuilder - Free,

Re: XML Schama message validation.

Isn't there an approach to include XSD Schema Validation Interceptor to support validation of incoming and outgoing SOAP message payload document instances? Thanks. Marcin Okraszewski [EMAIL PROTECTED] wrote: But in this way I can only parse some input stream. Axis provides already built DOM

AXIS 1.1 Support for xsd:duration type

Does AXIS 1.1 support the xsd:duration type. If it does not when can we expect support for it? What kind of workaround option exists in support for xsd:duration? Thanks. Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software

RE: xmlns= in the doc\literal SOAP message

Since elementFormDefault is "qualified" -- then one could safely assume that since Axis generated this wsdl, it should also be serializing local elements in the appropriate namespace...NOT adding xmlns="". Is there anyworkaround for this currently? That is exactly the problem I was identifying

RE: xmlns= in the doc\literal SOAP message

paces used by the document. Is there any workaround to this problem? Thanks Cory Wilkerson [EMAIL PROTECTED] wrote: See: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19524 -Original Message-From: Tony Opatha [mailto:[EMAIL PROTECTED]Sent: Friday, September 05, 2003 12:13 PMTo: [

RE: xmlns= in the doc\literal SOAP message

Name + "Return");+ returnQName = new QName(methodName + "Return"); } RPCParam param = new RPCParam(returnQName, objRes); -Original Message-From: Tony Opatha [mailto:[EMAIL PROTECTED] Sent: Friday, September 05, 2003 1:45 PMTo: [EMAIL PROTECTED]Subject: RE: xmlns="

RE: xmlns= in the doc\literal SOAP message

According to: Mike Perham [EMAIL PROTECTED] his patch for RPCService provider works for RPC/lit case, so will the same patch work with Doc/Lit style SOAP message. Any reason why anyone can think it will NOT? Thanks. -Original Message-From: Cory Wilkerson [mailto:[EMAIL PROTECTED]Sent:

Namespace handling in AXIS 1.1 using Doc/Lit style SOAP messages

Is there a way in AXIS to support only inclusion of namespace prefix for elements that are defined in a namespace that is not the default namespace rather than explcitly including the complete i.e., fully qualified namespace for each sub-element of the document instance that is included in the

Re: encoding.ser.castor

Thanks for clarifyin the types of message styles supported in AXIS. It seems then there are three different message styles for doc/literal: - Wrapped - Document - Message It seems that Wrapped and Document styles of messaging both require AXIS serialization. Is Wrapped thye more commonly used

Re: AXIS serialization/deserialization of XML payloads without SOAP/WSDL processing

only thing it doesn't do is convert the XML into Java for you. You might want to do some benchmark comparisons between Axis serialization and JAXB serialization.I'd look atperformance, scalability, and footprintdifferences. Anne - Original Message ----- From: Tony Opatha To: [EMAIL PROT

AXIS serialization/deserialization of XML payloads without SOAP/WSDL processing

1. Is there a way to use AXIS to process and generate XML payload streams using the XML schema (in .xsd) specifications of the payloads such that the payload streams are not serialized or deserialized to/from a SOAP message envelope? 2. If AXIS has general schema-driven XML payload

IDREF/IDREFs support in AXIS 1.1

Does the AXIS 1.1 WSDL2WebService tool support XML Schema types IDREF and IDREFs? It seems that a XSD used with WSDL is results in following error when used with WSD2WebService tool: Error found in the WSDL document: The XML Schema type 'IDREF' is not currently supported. Any ideas why this

RE: Does Doc/Literal allows users to directly work with language constructs (classes, structures etc..)?

Most importantly Doc/Lit allows end users to process payloads using the corresponding XML Schema for the payload that is packaged in the SOAP Body. This is quite important when the WSDL2Java compiler creates the stubs and skeletons it is basically creating serializable beans that produce XML

Re: Simple MessageContext problem...

1) Is this the username/password for the HTTP Basic Authentication header or for a SOAP security header? 2) how can we extract the userid password for SOAP security header in AXIS handler? "Chen, Li (Research, YOH)" [EMAIL PROTECTED] wrote: Hi All,There seems to be a problem with using

RE: doc/literal method names

From Anne's comments below it seems that SOAPAction should be equal to addNumbers if you want to interoperate with other web service engines. Also should there be any corresponding HTTP header?? ThanksCory Wilkerson [EMAIL PROTECTED] wrote: So should Axis be generating the soapAction element

Re: FW: another doc/literal issue

ByDEFAULT does not .NET/WSE based SOAP client send Doc/Lit request in bare format rather than wrapped format. Wrapped format is being discouraged and probably nopt very well documented by Microsoft. Shouldn't .NET developers and AXIS applications that interface with .NET NOT use wrapped

Re: Exception handling strategy question

Therefore you need to define a fault message for each of your exceptions, and then tell Axis to map the exceptions to the faults accordingly. So, this means that AXIS supports application-specific Faults for both document-style and RPC-style so long as the .xsd schema for the custom Fault

Re: Exception handling strategy question

Therefore you need to define a fault message for each of your exceptions, and then tell Axis to map the exceptions to the faults accordingly. So, this means that AXIS supports application-specific Faults for both document-style and RPC-style so long as the .xsd schema for the custom Fault

Re: accessing .net webservices which needs client authentication

.NET 1.1 Web services supports WS-Security which means that you also have the option of passing from AXIS client a WS-Security PasswordToken as part of the SOAP Security header. However, AXIS does not support the ability for applications to set the Password token and add it to the SOAP header. I

Re: accessing .net webservices which needs client authentication

.NET 1.1 Web services supports WS-Security which means that you also have the option of passing from AXIS client a WS-Security PasswordToken as part of the SOAP Security header. However, AXIS does not support the ability for applications to set the Password token and add it to the SOAP header.

AXIS 1.1 Performance comparisons between Document-Style vs RPC-Style

Hello, I wrote a simple web service client in.NET 1.1 (using Visual Studio .NET 2003) that consumed a document-style SOAP Web Service in AXIS 1.1. The document size that was transmitted ranged from 0.1 - 0.5 MB. I also tested a simple web service client in .NET 1.1 that consumed a RPC-sty;e SOAP

AXIS 1.1 Performance comparisons between Document-Style vs RPC-Style

Hello, I wrote a simple web service client in.NET 1.1 (using Visual Studio .NET 2003) that consumed a document-style SOAP Web Service in AXIS 1.1. The document size that was transmitted ranged from 0.1 - 0.5 MB. I also tested a simple web service client in .NET 1.1 that consumed a RPC-sty;e

RE: accessing .net webservices which needs client authentication

release and makes no statements regarding long term support. Be sure to check out MSDN and IBM AlphaWorks. I seem to recall an article on the subject. If you get an example working, please forward so others may benefit from your experiences. Thanks, Rick Kellogg -Original Message-From: Tony

RE: accessing .net webservices which needs client authentication

release and makes no statements regarding long term support. Be sure to check out MSDN and IBM AlphaWorks. I seem to recall an article on the subject. If you get an example working, please forward so others may benefit from your experiences. Thanks, Rick Kellogg -Original Message-From: Tony

RE: accessing .net webservices which needs client authentication

ns and new specification breakthroughs. Future versions of the WSE may not be backward compatible. Just be aware of the installation requirement and potential upgrade cycle you might be getting yourself into. Take care, Rick -Original Message-From: Tony Opatha [mailto:[EMAIL PROTECTED]Se

RE: accessing .net webservices which needs client authentication

ns and new specification breakthroughs. Future versions of the WSE may not be backward compatible. Just be aware of the installation requirement and potential upgrade cycle you might be getting yourself into. Take care, Rick -Original Message-From: Tony Opatha [mailto:[EMAIL PROTECTED]Se

Re: AXIS 1.1 Performance comparisons between Document-Style vs RPC-Style

Thanks for the analysis. However, has anyone tested AXIS with large messages ( 0.1 MB)? It seems that RPC data argument streaming has larger impact on the performance when you have large size messages because it allows overlap between AXIS communication and deserialization that would otherwise

Re: AXIS 1.1 Performance comparisons between Document-Style vs RPC-Style

Thanks for the analysis. However, has anyone tested AXIS with large messages ( 0.1 MB)? It seems that RPC data argument streaming has larger impact on the performance when you have large size messages because it allows overlap between AXIS communication and deserialization that would otherwise

RE: passing xml file as a parameter to a web-service

Does AXIS and SOAP w/Attachments allow passing in the XML file by reference i.e. a URI that points to the physical location of the said XML instance. Obviously, size should matter when we talk about "attacments" in a web service invocation. Also, how does AXIS deal with the processing of an

Re: Authentication

Why not use with AXIS SOAP Message Handler the WS-Security Password-based Authentication mechanism and/or WS-Security with SAML Assertion. Are there any plans to support WS-Security for AXIS SOAP Message exchanges either by Apache/AXIS or by IBM? Benjamin Tomasini [EMAIL PROTECTED] wrote: