Hi all:

The Apache Axis2 team is pleased to announce the release of Axis2 version 1.5.

Major Changes Since 1.4.1:
- Refactored, pluggable transports (separate jars, with deployer)
- Clustering improvements (works with EC2)
- Over 100 JIRA issues resolved

You can find the new version at the usual location:
   http://ws.apache.org/axis2

Please report any issues via JIRA:
   http://issues.apache.org/jira/browse/AXIS2.

As always, we welcome any and all feedback at:
   axis-dev@... - for developer-related questions/concerns
   axis-user@... - for general questions, usage, etc.

Thanks for your interest in Apache Axis2!

--Glen Daniels

> When: Wednesday, April 30, 2008 5:00 PM-8:00 PM (GMT-05:00) Eastern Time
> (US & Canada).
> Where: The Hartford, 690 Asylum Street, Hartford CT: Tower Building
>
> *~*~*~*~*~*~*~*~*~*
>
> At the core, OWASP is just a community of people passionate about software
> development and making sure the applications we create are done with
> security in mind. We all share a vision of a world where you can
> confidently trust the software you use. Unfortunately, the current
> software market doesn't encourage security - that's something we are
> trying to change. One of our primary missions is to make application
> security visible so that people can make informed decisions about risk.
> All of our events are free to attend and materials are available under an
> open source license...
> Agenda: Wednesday, April 30th, 2008
> Food and Networking: 5:30 - 5:45 PM: Sponsored by Ounce Labs
> (<http://www.ouncelabs.com>)
> Opening Remarks: 5:45 - 6:00 PM James McGovern, Chapter Lead
> Session One: 6:00 - 6:45 PM: The idiots guide to developing bad enterprise
> applications and worst logging practices
> Anton Chuvakin, Chief Logging Evangelist, LogLogic
> Session Two: 6:45- 7:30 PM: Keeping Secrets - Application Security is a
> Business Imperative
> Jack Danahy, CTO and Founder, Ounce Labs
> Closing: 7:30- 7:45 PM: Raffles and Door Prizes
>
> Next Meeting: Wednesday, June 11th, 2008
> Session One: 6:00 - 6:45 PM: Identity Governance Framework
> Prateek Mishra, Director of Security Standards at Oracle. Pioneered
> development of the SAML specification and brains behind Netegrity
> Siteminder
> Session Two: 6:45 - 7:30 PM: CardSpace and User-Centric Identity
> Chris Winn, Security Evangelist, Microsoft
> To join the chapter mailing list, please visit our mailing list homepage
> at <https://lists.owasp.org/mailman/listinfo/owasp-hartford>. Please check
> the mailing list before coming to a meeting to confirm the location and
> time and to catch any last minute notes.
> Future Meetings
> * Jeffrey Margolies, Partner at Accenture (<http://www.accenture.com>)
>
> * Nick Selby, Industry Analyst at the 451 Group
> (<http://www.the451group.com/>)
> * Jim Routh, CISO of Depository Trust and Clearing Corporation
> (<http://www.dtcc.com>)
> * Grady Summers, CISO of General Electric (<http://www.ge.com/>)
> * Peter Lindstrom, Industry Analyst at the Burton Group
> (<http://www.burtongroup.com/>)
>
> Directions: The Hartford, Tower Building 22nd Floor
> From East (via Route 84):
> * Approaching Hartford, follow Route 84 West to Exit 48 (Asylum Ave.
> Exit
> * At light, take a right onto Asylum Avenue
> * Turn into entrance on right near Home Office
> * Proceed to the Ramp Garage and park
> * Enter the Tower Building using the West Entrance
> From West (via Route 84):
> * Approaching downtown Hartford, follow Route 84 East to Exit 48A
> (Asylum Ave. Exit)
> * At light, take a left onto Asylum Avenue
> * Turn into entrance on right near Home Office
> * Proceed to the Ramp Garage and park
> * Enter the Tower Building using the West Entrance
> Sponsors:
> * Artec Group: <http://www.arctecgroup.net/>
> * Ounce Labs: <http://www.ouncelabs.com/>
> * The Hartford: <http://www.thehartford.com/>
> * White Hat Security: <http://www.whitehatsec.com/>
> * LogLogic:<http://www.loglogic.com/>
> * Forrester Research: <http://www.forrester.com/>
> * Cigital: <http://www.cigital.com/>
>

httprio component makes an alive connection. how can I close the
connection after the server response?

Hi builders,

About a year ago, RC1 of the SOAP over Java Message Service spec was
released. See http://mail-archives.apache.org/mod_mbox/ws-axis-dev/
200701.mbox/raw/%
3C80A43FC052CE3949A327527DCD5D6B27020FB65C@...
%3E/3

I wonder what the current status of this spec is. Is there a more
recent version? Is the spec implemented by any SOAP Stack?

Thanks,

Arjen Poutsma
---
Interface21
E: apoutsma@...
W: www.interface21.com
B: blog.interface21.com/arjen

Apache Axis2/C Team is pleased to announce the release of Apache Axis2/C
version 1.1.0
You can download this release from:
     http://ws.apache.org/axis2/c/download.cgi

Key Features

    1. Support for one-way messaging (In-Only) and request response
messaging (In-Out)
    2. Client APIs: Easy to use service client API and more advanced
operation client API
    3. Transports supported: HTTP
           * Inbuilt HTTP server called simple axis server
           * Apache2 httpd module called mod_axis2 for server side
           * IIS module for server side
           * Client transport with ability to enable SSL support
           * Basic HTTP Authentication
           * libcurl based client transport
    4. Module architecture, mechanism to extend the SOAP processing model
    5. WS-Addressing support, both the submission (2004/08) and final
(2005/08) versions, implemented as a module
    6. MTOM/XOP support
    7. AXIOM, an XML object model optimized for SOAP 1.1/1.2 messages;
This has complete XML infoset support
    8. XML parser abstraction
           * Libxml2 wrapper
           * Guththila pull parser support
    9. Both directory based and archive based deployment models for
deploying services and modules
   10. Description hierarchy providing access to static data of Axis2/C
runtime
       (configuration, service groups, services, operations and messages)
   11. Context hierarchy providing access to dynamic Axis2/C runtime
information
       (corresponding contexts to map to each level of description hierarchy)
   12. Message receiver abstraction
           * Inbuilt raw XML message receiver
   13. Code generation tool for stub and skeleton generation for a given
WSDL
       (based on Java tool)
           * Axis Data Binding (ADB) support
   14. Transport proxy support
   15. REST support (more POX like) using both HTTP POST and GET
   16. Comprehensive documentation
           * Axis2/C Manual
   17. WS-Policy implementation called Neethi/C, with WS-SecurityPolicy
extension
   18. TCP Transport, for both client and server side

Major Changes Since Last Release

    1. WS-Policy implementation
    2. TCP Transport
    3. Improvements to Guththila parser to improve performance
    4. Improvements to Java tool, WSDL2C, that generates C code
    5. Basic HTTP Authentication
    6. Memory leak fixes
    7. Many bug fixes

We welcome your early feedback on this implementation.
Thank you for your interest in Axis2/C

-- Apache Axis2/C Team --





--
Samisa Abeysinghe - Apche Axis2/C
"http://ws.apache.org/axis2/c/?Apache Axis2/C The Web Servic\
es Engine"

Hi Ian,

Once you have the WSDL of the Web Service you can use any of the
available tools which allow you to parse the WSDL and create a SOAP
message. Once you have a handle on the SOAP message you can send the
same through to your web site.

The tools that I know of are AXIS (java and C++ support), XFire (java
support as far as I know) and gSOAP (C++ support)

Hope that helps you.


Regards

Nilesh


--- In soapbuilders@yahoogroups.com, "its_mba" <its_mba@...> wrote:
>
> Hello Group
>
> I am a true newbie, new to this group and new to SOAP technology. I've
> developed an application with Btrieve 6.15 and have a few XML files as
> a result.
>
> I need to connect to a website via a SOAP message. I also have a WSDL
> file but do not know how to proceed. I understand that I may have to
> send the information as a data stream through a socket?
>
> My clients would have to upload information to this site regularly, so
> I'd like a solution which can be integrated with my application.
>
> Any assistance would be greatly appreciated.
>
> Ian
>

Hi,

I'm a new developer in VB + SOAP 3.0 SDK, I would like to sending out
a header of message like this:

POST /mm7extadapter HTTP/1.1
Content-Type: multipart/related; boundary="soap-border"; type="text/
xml"; start="mm7-submit"
Authorization: Basic Og==
User-Agent: Java/1.4.2_08
Host: 10.23.48.130:9500
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection: keep-alive
Content-Length: 2205

--soap-border
Content-Type: text/xml; charset="utf-8"
Content-ID: <mm7-submit>

but when my application trying to sent out, to become like this:

POST /mm7extadapter HTTP/1.1
Content-Type: text/xml
Host: 203.78.116.52
SOAPAction: ""
Content-Length: 2551

Could u give me an advice?
How to configure or how to set the properties of header?

Thanks a lot.

regards,
JohanWijaya

Apache Axis2/C Team is pleased to announce the release of Apache Axis2/C
version 1.0.0
You can download this release from
http://ws.apache.org/axis2/c/download.cgi

Key Features

   1. Support for one-way messaging (In-Only) and request response
messaging (In-Out)
   2. Client APIs: Easy to use service client API and more advanced
operation client API
   3. Transports supported: HTTP
         a. Inbuilt HTTP server called simple axis server
         b. Apache2 httpd module called mod_axis2 for server side
         c. IIS module for server side
         d. Client transport with ability to enable SSL support
         e. libcurl based client transport
   4. Module architecture, mechanism to extend the SOAP processing model
   5. WS-Addressing support, both the submission (2004/08) and final
(2005/08) versions, implemented as a module
   6. MTOM/XOP support
   7. AXIOM, an XML object model optimized for SOAP 1.1/1.2 messages;
This has complete XML infoset support
   8. XML parser abstraction
         a. Libxml2 wrapper
         b. Guththila pull parser support
   9. Both directory based and archive based deployment models for
deploying services and modules
10. Description hierarchy providing access to static data of Axis2/C
runtime (configuration, service groups, services, operations and messages)
11. Context hierarchy providing access to dynamic Axis2/C runtime
information(corresponding contexts to map to each level of description
hierarchy)
12. Message receiver abstraction
         a. Inbuilt raw XML message receiver
13. Code generation tool for stub and skeleton generation for a given
WSDL (based on Java tool)
         a. Axis Data Binding (ADB) support
14. Transport proxy support
15. REST support (more POX like) using both HTTP POST and GET
16. Comprehensive documentation
         a. Axis2/C Manual

Major Changes Since Last Release

   1. Many Bug Fixes
   2. IIS module for server side
   3. libcurl based client transport
   4. Improvements to overall API to make it more user friendly, stable
and binary compatible
   5. Transport proxy support
   6. Memory leak fixes We welcome your early feedback on this
implementation.
Thank you for your interest in Axis2/C.

-- Apache Axis2/C Team --

--
Samisa Abeysinghe : http://www.bloglines.com/blog/samisa

Hello Group

I am a true newbie, new to this group and new to SOAP technology. I've
developed an application with Btrieve 6.15 and have a few XML files as
a result.

I need to connect to a website via a SOAP message. I also have a WSDL
file but do not know how to proceed. I understand that I may have to
send the information as a data stream through a socket?

My clients would have to upload information to this site regularly, so
I'd like a solution which can be integrated with my application.

Any assistance would be greatly appreciated.

Ian

For people who implement web services.
Webswell Connect provides open source technological infrastructure
that enables companies to take part in documents interchange based on
the ebXML, WS web services and AS2 standards.
It contains:
- EbXML, WS web services and AS2-compliant messaging system
- A Registry and Repository for business objects
- Demonstration, simulation and testing utilities
- Multiplatform java installer

Changes in latest version:
- Added support of Windows services for Tomcat
- Dispatcher 1.1.1 , improved error handling
- Major bug fix in installer for Windows systems

More information at:
http://www.webswell.com

Download at:
http://sourceforge.net/project/showfiles.php?group_id=167017

Hi,

I want to consume an Apache Webservice with a C# .NET Client.
Everything works fine, but I'm having problem with the deserialization
of the complex type "Item" that is included in the response of the web
service, what seems so be the type "hashtable" in .NET. Every "Item"
consists of two fields "key" and "value".

I read a lot about SOAP/Apache/.NET/Complex Types/etc. and somewhere I
read that there is no automatic deserialization possible of such a type.
Does anyone know a HowTo-Example or Codesnippet? Or can somebody
explain how to consume Complex Types from Apache?
I didn't find any helpful postings or Code Examples…

I'm looking forward to your replies!

Best regards,
Gregor

Looks like many QName links are broken.  You have to link port to
binding to portType to messages using QNames.  Thats a namespace
qualified name.  The first example I found was the link from the
service port to the binding.  Notice the value of the binding
attribute: "ratings:SampleServiceSoapBinding"  The ratings namespace
prefix is bound to the wrong namespace
(http://schemas.wamu.com/2006/07/LoanSampleRequest).  The binding you
want is the one in the file, but it is defined in
"http://com/wamu/Sample" - the targetNamespace for the document.

In short figure out your namespaces and links.  If you like grab a
copy of SOAPscope[1] (my company) to validate your WSDL and find this
error.

Hope this Helps,

Jim Murphy
Mindreef, Inc.

[1] http://www.mindreef.com/


On 2/18/07, Karr, David <david.karr@...> wrote:
> I have a WSDL that was originally generated from a service in WebLogic
> Workshop.  It isn't validating, and I don't understand why.  I'll attach
> a slightly modified version of it at the end of this.
>
> Line 76 (I mark that line below) has an error that says this:
>
> "The input element is referencing an undefined message
> 'overrideRequest'. Check that the message name and namespace are correct
> and that the message has been defined."
>
> There are similar errors on lines 77, 80, and 81, and other errors
> further on, because of these errors.
>
> I'm sure that I'm making some mistake with namespaces or wsdl, but I'm
> not sure what I'm doing wrong.
>
> ----------------
> <?xml version='1.0' encoding='UTF-8'?>
> <s0:definitions name="SampleServiceDefinitions"
>                 targetNamespace="http://com/wamu/Sample"
>                 xmlns=""
>                 xmlns:s0="http://schemas.xmlsoap.org/wsdl/"
>                 xmlns:tns="http://schemas.wamu.com/Sample.wsdl"
>
> xmlns:ratings="http://schemas.wamu.com/2006/07/LoanSampleRequest"
>
> xmlns:questions="http://schemas.wamu.com/2006/07/QuestionsRequest"
>                 xmlns:s2="http://schemas.xmlsoap.org/wsdl/soap/">
>   <s0:types>
>     <xs:schema
> targetNamespace="http://schemas.wamu.com/2006/07/LoanSampleRequest"
>
> xmlns:ratings="http://schemas.wamu.com/2006/07/LoanSampleRequest"
>                xmlns:xs="http://www.w3.org/2001/XMLSchema">
>       <xs:element name="loanSampleRequest">
>         <xs:complexType>
>           <xs:sequence>
>             <xs:element ref="ratings:loanProperties"/>
>           </xs:sequence>
>           <xs:attribute name="modelVersion" type="xs:integer"
> use="optional"/>
>         </xs:complexType>
>       </xs:element>
>       <xs:element name="loanSampleResponse">
>         <xs:complexType>
>           <xs:sequence>
>             <xs:element ref="ratings:loanProperties"/>
>             <xs:element ref="ratings:messages"/>
>           </xs:sequence>
>         </xs:complexType>
>       </xs:element>
>       <xs:element name="loanProperties">
>         <xs:complexType>
>           <xs:sequence>
>             <xs:element maxOccurs="unbounded" ref="ratings:property"/>
>           </xs:sequence>
>         </xs:complexType>
>       </xs:element>
>       <xs:element name="property">
>         <xs:complexType>
>           <xs:sequence>
>             <xs:element ref="ratings:key"/>
>             <xs:element ref="ratings:value"/>
>           </xs:sequence>
>         </xs:complexType>
>       </xs:element>
>       <xs:element name="key" type="xs:string"/>
>       <xs:element name="value" type="xs:string"/>
>       <xs:element name="messages">
>         <xs:complexType>
>           <xs:sequence>
>             <xs:element maxOccurs="unbounded" minOccurs="0"
> ref="ratings:message"/>
>           </xs:sequence>
>         </xs:complexType>
>       </xs:element>
>       <xs:element name="message">
>         <xs:complexType mixed="true">
>           <xs:attribute name="level" type="xs:string"/>
>           <xs:attribute name="fieldName" type="xs:string"/>
>         </xs:complexType>
>       </xs:element>
>     </xs:schema>
>   </s0:types>
>   <s0:message name="overrideRequest">
>     <s0:part element="ratings:loanSampleRequest" name="parameters"/>
>   </s0:message>
>   <s0:message name="overrideRequestResponse">
>     <s0:part element="ratings:loanSampleResponse" name="parameters"/>
>   </s0:message>
>   <s0:message name="ratingsRequest">
>     <s0:part element="ratings:loanSampleRequest" name="parameters"/>
>   </s0:message>
>   <s0:message name="ratingsRequestResponse">
>     <s0:part element="ratings:loanSampleRequest" name="parameters"/>
>   </s0:message>
>   <s0:portType name="Sample">
>     <s0:operation name="overrideRequest" parameterOrder="parameters">
>       <s0:input message="overrideRequest"/> <!--  76 -->
>       <s0:output message="tns:overrideRequestResponse"/>
>     </s0:operation>
>     <s0:operation name="ratingsRequest" parameterOrder="parameters">
>       <s0:input message="ratings:loanSampleRequest"/>
>       <s0:output message="ratings:loanSampleResponse"/>
>     </s0:operation>
>   </s0:portType>
>   <s0:binding name="SampleServiceSoapBinding" type="ratings:Sample">
>     <s2:binding style="document"
> transport="http://schemas.xmlsoap.org/soap/http"/>
>     <s0:operation name="overrideRequest">
>       <s2:operation soapAction="" style="document"/>
>       <s0:input>
>         <s2:body parts="parameters" use="literal"/>
>       </s0:input>
>       <s0:output>
>         <s2:body parts="parameters" use="literal"/>
>       </s0:output>
>     </s0:operation>
>     <s0:operation name="ratingsRequest">
>       <s2:operation soapAction="" style="document"/>
>       <s0:input>
>         <s2:body parts="parameters" use="literal"/>
>       </s0:input>
>       <s0:output>
>         <s2:body parts="parameters" use="literal"/>
>       </s0:output>
>     </s0:operation>
>   </s0:binding>
>   <s0:service name="SampleService">
>     <s0:port binding="ratings:SampleServiceSoapBinding"
> name="SampleSoapPort">
>       <s2:address location="http://localhost:7001/Sample/Sample"/>
>     </s0:port>
>   </s0:service>
> </s0:definitions>
> ----------------
>
>
> -----------------------------------------------------------------
> This group is a forum for builders of SOAP implementations to discuss
implementation and interoperability issues.  Please stay on-topic.
> Yahoo! Groups Links
>
>
>
>

I have a WSDL that was originally generated from a service in WebLogic
Workshop.  It isn't validating, and I don't understand why.  I'll attach
a slightly modified version of it at the end of this.

Line 76 (I mark that line below) has an error that says this:

"The input element is referencing an undefined message
'overrideRequest'. Check that the message name and namespace are correct
and that the message has been defined."

There are similar errors on lines 77, 80, and 81, and other errors
further on, because of these errors.

I'm sure that I'm making some mistake with namespaces or wsdl, but I'm
not sure what I'm doing wrong.

----------------
<?xml version='1.0' encoding='UTF-8'?>
<s0:definitions name="SampleServiceDefinitions"
                 targetNamespace="http://com/wamu/Sample"
                 xmlns=""
                 xmlns:s0="http://schemas.xmlsoap.org/wsdl/"
                 xmlns:tns="http://schemas.wamu.com/Sample.wsdl"

xmlns:ratings="http://schemas.wamu.com/2006/07/LoanSampleRequest"

xmlns:questions="http://schemas.wamu.com/2006/07/QuestionsRequest"
                 xmlns:s2="http://schemas.xmlsoap.org/wsdl/soap/">
   <s0:types>
     <xs:schema
targetNamespace="http://schemas.wamu.com/2006/07/LoanSampleRequest"

xmlns:ratings="http://schemas.wamu.com/2006/07/LoanSampleRequest"
                xmlns:xs="http://www.w3.org/2001/XMLSchema">
       <xs:element name="loanSampleRequest">
         <xs:complexType>
           <xs:sequence>
             <xs:element ref="ratings:loanProperties"/>
           </xs:sequence>
           <xs:attribute name="modelVersion" type="xs:integer"
use="optional"/>
         </xs:complexType>
       </xs:element>
       <xs:element name="loanSampleResponse">
         <xs:complexType>
           <xs:sequence>
             <xs:element ref="ratings:loanProperties"/>
             <xs:element ref="ratings:messages"/>
           </xs:sequence>
         </xs:complexType>
       </xs:element>
       <xs:element name="loanProperties">
         <xs:complexType>
           <xs:sequence>
             <xs:element maxOccurs="unbounded" ref="ratings:property"/>
           </xs:sequence>
         </xs:complexType>
       </xs:element>
       <xs:element name="property">
         <xs:complexType>
           <xs:sequence>
             <xs:element ref="ratings:key"/>
             <xs:element ref="ratings:value"/>
           </xs:sequence>
         </xs:complexType>
       </xs:element>
       <xs:element name="key" type="xs:string"/>
       <xs:element name="value" type="xs:string"/>
       <xs:element name="messages">
         <xs:complexType>
           <xs:sequence>
             <xs:element maxOccurs="unbounded" minOccurs="0"
ref="ratings:message"/>
           </xs:sequence>
         </xs:complexType>
       </xs:element>
       <xs:element name="message">
         <xs:complexType mixed="true">
           <xs:attribute name="level" type="xs:string"/>
           <xs:attribute name="fieldName" type="xs:string"/>
         </xs:complexType>
       </xs:element>
     </xs:schema>
   </s0:types>
   <s0:message name="overrideRequest">
     <s0:part element="ratings:loanSampleRequest" name="parameters"/>
   </s0:message>
   <s0:message name="overrideRequestResponse">
     <s0:part element="ratings:loanSampleResponse" name="parameters"/>
   </s0:message>
   <s0:message name="ratingsRequest">
     <s0:part element="ratings:loanSampleRequest" name="parameters"/>
   </s0:message>
   <s0:message name="ratingsRequestResponse">
     <s0:part element="ratings:loanSampleRequest" name="parameters"/>
   </s0:message>
   <s0:portType name="Sample">
     <s0:operation name="overrideRequest" parameterOrder="parameters">
       <s0:input message="overrideRequest"/> <!--  76 -->
       <s0:output message="tns:overrideRequestResponse"/>
     </s0:operation>
     <s0:operation name="ratingsRequest" parameterOrder="parameters">
       <s0:input message="ratings:loanSampleRequest"/>
       <s0:output message="ratings:loanSampleResponse"/>
     </s0:operation>
   </s0:portType>
   <s0:binding name="SampleServiceSoapBinding" type="ratings:Sample">
     <s2:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
     <s0:operation name="overrideRequest">
       <s2:operation soapAction="" style="document"/>
       <s0:input>
         <s2:body parts="parameters" use="literal"/>
       </s0:input>
       <s0:output>
         <s2:body parts="parameters" use="literal"/>
       </s0:output>
     </s0:operation>
     <s0:operation name="ratingsRequest">
       <s2:operation soapAction="" style="document"/>
       <s0:input>
         <s2:body parts="parameters" use="literal"/>
       </s0:input>
       <s0:output>
         <s2:body parts="parameters" use="literal"/>
       </s0:output>
     </s0:operation>
   </s0:binding>
   <s0:service name="SampleService">
     <s0:port binding="ratings:SampleServiceSoapBinding"
name="SampleSoapPort">
       <s2:address location="http://localhost:7001/Sample/Sample"/>
     </s0:port>
   </s0:service>
</s0:definitions>
----------------

slideware :)

On 2/16/07, Paul Downey <paul.downey@...> wrote:
>
> On 16 Feb 2007, at 13:59, Davanum Srinivas wrote:
> > FYI, For a while now, we've been building up a Stack comparison page
> > at the Apache WS Wiki site:
> > http://wiki.apache.org/ws/StackComparison
>
> Hmm.. I've no idea what an X means:
> proven interoperability,
> or a claim to support the spec on some slideware.
>
> --
> http://blog.whatfettle.com
>
>
>
>
> -----------------------------------------------------------------
> This group is a forum for builders of SOAP implementations to discuss
implementation and interoperability issues.  Please stay on-topic.
> Yahoo! Groups Links
>
>
>
>


--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

On 16 Feb 2007, at 13:59, Davanum Srinivas wrote:
> FYI, For a while now, we've been building up a Stack comparison page
> at the Apache WS Wiki site:
> http://wiki.apache.org/ws/StackComparison

Hmm.. I've no idea what an X means:
proven interoperability,
or a claim to support the spec on some slideware.

--
http://blog.whatfettle.com

Folks,

FYI, For a while now, we've been building up a Stack comparison page
at the Apache WS Wiki site:
http://wiki.apache.org/ws/StackComparison

Yes, You can edit it and update existing information on that page.
Just click on the link at the top right corner and create an account
for yourself. Any discussion on the page contents can be on general AT
ws.apache.org (subscribe first by sending an email to
general-subscribe AT ws.apache.org). Since that's where the wiki
update notifications are directed to. You can also subscribe to the
wiki notifications by clicking on the subscribe link.

thanks,
dims

--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

Paul,

SOAP is very much alive, and I agree with your point that when
considering web services that are doing any type of real work, you
cannot simply assume away things like addressing and security.

Having said that, there is also a tendency, especially from platform and
toolkit builders, to assume that all of that expensive processing is
going to be done at the endpoint; in the software.

I would argue that, that particular view is... Limiting.

I personally am a firm believer in separating, to the greatest extent
possible, the business logic (the stuff that travels in the SOAP body)
from the infrastructure functionality (the stuff that travels in the
SOAP header). And current technology capabilities allow one to just
this. As an example, security processing of SOAP messages (digital
signatures, xml encryption/decryption etc.) is an expensive process that
I would normally outsource to something like a hardware box like an XML
Security Gateway which can do that processing at wire speed.

Which to a great extent reinforces the view that one needs to look at
performance engineering end to end and should seek to optimize where you
can get the biggest bang for the buck. And that very well may not be at
the SOAP layer, but in the business logic processing.

And taking away databinding does not in any way shape or form take away
from the usefulness of SOAP. I am coming more and more to the viewpoint
that moving away from databinding allows one to focus on the core of
what SOA and web services are about, the exchange of messages.  And not
the issues dealing with the "object-ification" of XML.

Regards,

- Anil

:-
:- Anil John
:- http://www.aniltj.com/blog
:-




> -----Original Message-----
> From: soapbuilders@yahoogroups.com
> [mailto:soapbuilders@yahoogroups.com] On Behalf Of Paul Downey
> Sent: Wednesday, February 14, 2007 8:49 AM
> To: soapbuilders@yahoogroups.com
> Subject: Re: [soapbuilders] [ANN]JAX-WS 2.1 FCS released
>
> Dims
>
>
> > Use AXIOM, See even the REST guys are using it :)
> > http://blog.chanezon.com/articles/2006/05/31/apache-abdera-and-rome-
> > alea-jacta-est
> >
>
> Yup, I see no SOAP!
>
>
> > Just look at the performance numbers for processing a huge feed that
> > they posted. Yes, adding soap headers won't slow us (Axis2) down :)
> >
>
>
> unless you're mad enough to use Addressing and WSSec, apparently:
>
> http://tech.groups.yahoo.com/group/service-orientated-architecture/
> message/7316
>
> Sorry, when you remove databinding, and dismiss headers as being
> heavyweight, I wonder what I'm being asked to get excited about not
> being slow: <xsl:copy-of
> select="document()/soap:Envelope/soap:Body" /
>  > ?
>
> Paul
>
>
>
>
>
> -----------------------------------------------------------------
> This group is a forum for builders of SOAP implementations to
> discuss implementation and interoperability issues.  Please
> stay on-topic.
> Yahoo! Groups Links
>
>
>
>
>

Dims


> Use AXIOM, See even the REST guys are using it :)
> http://blog.chanezon.com/articles/2006/05/31/apache-abdera-and-rome-
> alea-jacta-est
>

Yup, I see no SOAP!


> Just look at the performance numbers for processing a huge feed that
> they posted. Yes, adding soap headers won't slow us (Axis2) down :)
>


unless you're mad enough to use Addressing and WSSec, apparently:

http://tech.groups.yahoo.com/group/service-orientated-architecture/
message/7316

Sorry, when you remove databinding, and dismiss headers as being
heavyweight, I wonder what I'm being asked to get excited about not
being slow: <xsl:copy-of select="document()/soap:Envelope/soap:Body" /
  > ?

Paul

Please, can we stop the product plugging on this list? It's getting
rather pathetic.

Thanks,

Arjen

On 14-feb-2007, at 13:28, Davanum Srinivas wrote:

> Paul,
>
> Use AXIOM, See even the REST guys are using it :)
> http://blog.chanezon.com/articles/2006/05/31/apache-abdera-and-rome-
> alea-jacta-est
>

Paul,

Use AXIOM, See even the REST guys are using it :)
http://blog.chanezon.com/articles/2006/05/31/apache-abdera-and-rome-alea-jacta-e\
st

Just look at the performance numbers for processing a huge feed that
they posted. Yes, adding soap headers won't slow us (Axis2) down :)

thanks,
dims

On 2/14/07, Paul Downey <paul.downey@...> wrote:
>
> On 13 Feb 2007, at 21:25, Davanum Srinivas wrote:
>
>
> > Sure. Just press the off button :)
>
> >
> thread killed :)
>
>
> > Did you see this already?
> >
> > http://www.bloglines.com/blog/sanjiva?id=180
>
>
> Ah, so we learnt earlier how SOAP headers
> aren't the 80 case, and now should just use
> just use XML because databinding is evil.
>
> I wonder where the baby is now we've tossed out
> the SOAP bath water.
>
> Paul
> --
> http://blog.whatfettle.com
>
>
>
> -----------------------------------------------------------------
> This group is a forum for builders of SOAP implementations to discuss
implementation and interoperability issues.  Please stay on-topic.
> Yahoo! Groups Links
>
>
>
>


--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

On 13 Feb 2007, at 21:25, Davanum Srinivas wrote:


> Sure. Just press the off button :)

>
thread killed :)


> Did you see this already?
>
> http://www.bloglines.com/blog/sanjiva?id=180


Ah, so we learnt earlier how SOAP headers
aren't the 80 case, and now should just use
just use XML because databinding is evil.

I wonder where the baby is now we've tossed out
the SOAP bath water.

Paul
--
http://blog.whatfettle.com

Sure. Just press the off button :) Did you see this already?

http://www.bloglines.com/blog/sanjiva?id=180

-- dims

On 2/13/07, Paul Downey <paul.downey@...> wrote:
> > That's why i am very interested in seeing the relative performances of
> > the two data bindings under JDK6 using woodstox running under tomcat.
> > (Since kohsuke hinted at possible problem in GlassFish and we prefer
> > woodstox, since we haven't spent any time with SJSXP).
>
> I'm quite frankly bored by this performance peeing contest:
>
> 1) Make it run.
> 2) make it right.
> 3) make it fast.
>
> Axis2, XFire, Glassfish, etc all need to try harder at (2).
>
> Paul
> --
> http://blog.whatfettle.com
>
>
>
>
> -----------------------------------------------------------------
> This group is a forum for builders of SOAP implementations to discuss
implementation and interoperability issues.  Please stay on-topic.
> Yahoo! Groups Links
>
>
>
>


--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers