Soapbuilders:

I don't know about you, but I am continually impressed with the awesome
range of new functionality people are discovering for their Web
Services.  Viva la SOAP! :)

--Glen (yes, moderating this away in a moment)

sexysingles98743 wrote:
> I'm a hot single, looking for better SEX partner. Check my live
> webcams and sexy photos here:
> http://findsexysingle.com/sex
>
>
>
>
>
>
> -----------------------------------------------------------------
> This group is a forum for builders of SOAP implementations to discuss
implementation and interoperability issues.  Please stay on-topic.
> Yahoo! Groups Links
>
>
>
>
>
>
>

Anyone interested in doin somethin new on the net. Come over here and add me
http://www.makeitgreat.info/ainb

i have a .net 2 service and am using NuSoap to send requests to it as
follows

require_once("nusoap/nusoap.php");

$soapclient = new
soapclient("http://mysite.com/Service.asmx?wsdl",true,'ServiceSoap');

$args = array(
	 "guid" 	 => "",
	 "strTitle"  =>  "Mr",
	 "strFirstName"  => "greg",
	 "strLastName"  => "Brant",
	 "strEmail"  => "greg@".$email.".com",
	 "strGender"  => "m",
	 "strDob"  => "12/12/1982",
	 "strAddress1"  => "36 xxxxxxxx Mount",
	 "strAddress2"  => "blahh ",
	 "strTown"  => "Leeds",
	 "strRegion"  => "west yorks",
	 "strPostCode"  => "ls1 1ls",
	 "intCountry"  => 120,
	 "intLanguage"  => 8,
	 "strPhoneNumber" => "0114 123456",
	 "strMobileNumber" => "0044 7908 123546",
	 "bitBrandOI"  => true,
	 "bitAGOI"  => true,
	 "intCompetitionID" => 0,
	 "intSiteID"  => 1,
	 "strGoldens"  => "1:1,0,0,0,0|2:0,1,1,0,1",
	 "intCardCount"  => 1
);

$result = $soapclient->call("personalRequest",$args);

print_r($result);

on the return all my strings are null/empty

On 4/18/06, greg_brant <greg_brant@...> wrote:
> i have a .net 2 service and am using NuSoap to send requests to it as
> follows
>
> require_once("nusoap/nusoap.php");
>
> $soapclient = new
> soapclient("http://mysite.com/Service.asmx?wsdl",true,'ServiceSoap');
>
> $args = array(
>         "guid"                  =>      "",
>         "strTitle"              =>  "Mr",
>         "strFirstName"          =>      "greg",
>         "strLastName"           =>      "Brant",
>         "strEmail"              =>      "greg@".$email.".com",
>         "strGender"             =>      "m",
>         "strDob"                =>      "12/12/1982",
>         "strAddress1"           =>      "36 xxxxxxxx Mount",
>         "strAddress2"           =>      "blahh ",
>         "strTown"               =>      "Leeds",
>         "strRegion"             =>      "west yorks",
>         "strPostCode"           =>      "ls1 1ls",
>         "intCountry"            =>      120,
>         "intLanguage"           =>      8,
>         "strPhoneNumber"        =>      "0114 123456",
>         "strMobileNumber"       =>      "0044 7908 123546",
>         "bitBrandOI"            =>      true,
>         "bitAGOI"               =>      true,
>         "intCompetitionID"      =>      0,
>         "intSiteID"             =>      1,
>         "strGoldens"            =>      "1:1,0,0,0,0|2:0,1,1,0,1",
>         "intCardCount"          =>      1
> );
>
> $result = $soapclient->call("personalRequest",$args);
>
> print_r($result);
>
> on the return all my strings are null/empty
>
>
>

Have you used a SOAP trace tool to see what gets sent over the wire?

no, this is my first time using soap.

where could i get one?

preferably a free one ;)

--- In soapbuilders@yahoogroups.com, "Steve Loughran"
<steve.loughran.soapbuilders@...> wrote:
>
> On 4/18/06, greg_brant <greg_brant@...> wrote:
> > i have a .net 2 service and am using NuSoap to send requests to it as
> > follows
> >
> > require_once("nusoap/nusoap.php");
> >
> > $soapclient = new
> > soapclient("http://mysite.com/Service.asmx?wsdl",true,'ServiceSoap');
> >
> > $args = array(
> >         "guid"                  =>      "",
> >         "strTitle"              =>  "Mr",
> >         "strFirstName"          =>      "greg",
> >         "strLastName"           =>      "Brant",
> >         "strEmail"              =>      "greg@".$email.".com",
> >         "strGender"             =>      "m",
> >         "strDob"                =>      "12/12/1982",
> >         "strAddress1"           =>      "36 xxxxxxxx Mount",
> >         "strAddress2"           =>      "blahh ",
> >         "strTown"               =>      "Leeds",
> >         "strRegion"             =>      "west yorks",
> >         "strPostCode"           =>      "ls1 1ls",
> >         "intCountry"            =>      120,
> >         "intLanguage"           =>      8,
> >         "strPhoneNumber"        =>      "0114 123456",
> >         "strMobileNumber"       =>      "0044 7908 123546",
> >         "bitBrandOI"            =>      true,
> >         "bitAGOI"               =>      true,
> >         "intCompetitionID"      =>      0,
> >         "intSiteID"             =>      1,
> >         "strGoldens"            =>      "1:1,0,0,0,0|2:0,1,1,0,1",
> >         "intCardCount"          =>      1
> > );
> >
> > $result = $soapclient->call("personalRequest",$args);
> >
> > print_r($result);
> >
> > on the return all my strings are null/empty
> >
> >
> >
>
> Have you used a SOAP trace tool to see what gets sent over the wire?
>

ok,

so done some pokin around

this is the soap message

<?xml version="1.0" encoding="ISO-8859-1"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns4316="http://tempuri.org">
<SOAP-ENV:Body>
<personalRequest xmlns="http://cmwnorth.com/webservices"/>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>


and as you can see, the <personalRequest> is empty ( closed with a />)
so im guessing its a problem with the nusoap lib

anybody got any experiance with this?


--- In soapbuilders@yahoogroups.com, "greg_brant" <greg_brant@...> wrote:
>
> no, this is my first time using soap.
>
> where could i get one?
>
> preferably a free one ;)
>
> --- In soapbuilders@yahoogroups.com, "Steve Loughran"
> <steve.loughran.soapbuilders@> wrote:
> >
> > On 4/18/06, greg_brant <greg_brant@> wrote:
> > > i have a .net 2 service and am using NuSoap to send requests to
it as
> > > follows
> > >
> > > require_once("nusoap/nusoap.php");
> > >
> > > $soapclient = new
> > >
soapclient("http://mysite.com/Service.asmx?wsdl",true,'ServiceSoap');
> > >
> > > $args = array(
> > >         "guid"                  =>      "",
> > >         "strTitle"              =>  "Mr",
> > >         "strFirstName"          =>      "greg",
> > >         "strLastName"           =>      "Brant",
> > >         "strEmail"              =>      "greg@".$email.".com",
> > >         "strGender"             =>      "m",
> > >         "strDob"                =>      "12/12/1982",
> > >         "strAddress1"           =>      "36 xxxxxxxx Mount",
> > >         "strAddress2"           =>      "blahh ",
> > >         "strTown"               =>      "Leeds",
> > >         "strRegion"             =>      "west yorks",
> > >         "strPostCode"           =>      "ls1 1ls",
> > >         "intCountry"            =>      120,
> > >         "intLanguage"           =>      8,
> > >         "strPhoneNumber"        =>      "0114 123456",
> > >         "strMobileNumber"       =>      "0044 7908 123546",
> > >         "bitBrandOI"            =>      true,
> > >         "bitAGOI"               =>      true,
> > >         "intCompetitionID"      =>      0,
> > >         "intSiteID"             =>      1,
> > >         "strGoldens"            =>      "1:1,0,0,0,0|2:0,1,1,0,1",
> > >         "intCardCount"          =>      1
> > > );
> > >
> > > $result = $soapclient->call("personalRequest",$args);
> > >
> > > print_r($result);
> > >
> > > on the return all my strings are null/empty
> > >
> > >
> > >
> >
> > Have you used a SOAP trace tool to see what gets sent over the wire?
> >
>

Just jumped on board at this place     http://www.lookatthatnow.info/uodz and
have to    say its        a riot. Lots of awesome things to   do to do on there.
Check it out.

Hi wats new with everyone? Just wanted to give u all a nice tip. Have a peak
over here http://www.makeitgreat.info/iavx and add me on there. Wanna get
everyone over and have some fun.

On 2/18/06, Steve Loughran <steve.loughran.soapbuilders@...> wrote:

> At the same time, F2Fs can be good. I note that ApacheCon Europe 2006
> has just been announced: "ApacheCon Europe 2006 will be held in
> Dublin, Ireland, at the Burlington Hotel, June 26-30."  this will no
> doubt be preceeded by a hackathon in which apache projects get worked
> on; there is nothing to stop us doing an interop session in the
> corner. For those who have not attended an apachecon, they have a bit
> of a developer flavour, but as they serve alcohol from the 10am break
> (at least in Germany), its not too dull. There will no doubt be a big
> axis2 presence, but we would extend an open hand to all other dev
> teams, open or closed source. I could also put in for a talk "web
> service interop, where we are now", or a panel "next generation WS
> stacks" to tie everything together during the main conf.
>
> regardless of where or when, this would effectively constitute
> SOAPBuilders round 6, if I am not mistaken. Let's do longstanding and
> emergent troublespots
>
> -SOAP1.2
>
> -doc/lit. All of it. Let's echo xsd:any back; maybe have some
> equals(xsd:any,xsd:any) to see if two different representations of the
> same thing match.
>
> -WS-A. Addressing, mapping from WS-A address elements ina message to
> stack addresses., equality tests.
>
> -timezones in xsd:dateTime (echoing it doesnt verify the far end
> actually took it; we need something better like
>   boolean equals(xsd:dateTime date, int year,
>          int month,int day, int hour, int min, int s, int millis,
>         long tzGmtOffsetMinutes)
>
> -Attachments in the many flavours (SwA, Dime, MTOM). Something to
> checksum the results to verify losslessness and correct understanding.
>
> -Faulting. All that fancy new SOAP1.2 stuff.
>
> -statefulness. So we can see that when an mustUnderstand header is
> rejected, a side-effecing far end has not actually been called.
>
> HTTP things:
> -multiple cookies in a response being repeated next time
> -error code handling
> -no attempt to parse the HTML response coming from an error page
> unless the content-type is correct (yes, we've all seen that one :)
>
> Oh, we could have so much fun. So many things have gone wrong out
> there since Round 5, things we can test for.
>
> -Steve

I am now at the point in my soap stack works, and where I have some
intra-operability between Axis1+Muse for WSA/WSRF support, enough to
meet my short term goals. The WCF endpoints for simple types, faults
and the many, many versions of WSA out there.

ApacheCon Europe is coming up (http://www.eu.apachecon.com/), and
there will presumably be Axis developers as well as myself. If anyone
else is interested in getting together for some interop testing and
fixing then we could do it on the monday/tuesday of the week, at the
invitation-only hackathon part of the conference.

Question is: what are we going to test? what will SOAPBuilders round
six consist of?

I propose the following test areas

-HTTP: bits and bobs underneath the SOAP layer
-SOAP12: envelope, MU headers, faults
-WSA1.0 (how much is optional here?)
-doc/lit XSD

In particular, I want endpoints to generate interesting failures.
endpoints that return text/html to a POST, or return HTML content
after a text+xml header. soapfaults with big complex datasets coming
back, endpoints that return stack traces in the Axis1 namespace, etc,
etc. The kind of thing you get out there, even if you dont want to see
them.

-steve

All,

Does anyone have any pointers to documentation/best practices that
capture the lowest common denominator of schema construct support in
major platforms?  i.e., it is colloquially known that xsd:union does
not have wide spread support in J2EE app servers, but has this been (in)
formally captured anywhere (besides per-platform READMEs).  Has anyone
taken a stab at producing this laundry list?  I'm not looking for a ws-
i rant here... ;)

Tim Julien

On 26 Apr 2006, at 00:49, timastaJ wrote:

> Does anyone have any pointers to documentation/best practices that
> capture the lowest common denominator of schema construct support in
> major platforms?  i.e., it is colloquially known that xsd:union does
> not have wide spread support in J2EE app servers, but has this been
> (in)
> formally captured anywhere (besides per-platform READMEs).  Has anyone
> taken a stab at producing this laundry list?  I'm not looking for a
> ws-
> i rant here... ;)

The W3C XML Schema Patterns for Databinding Working Group is
currently trying to address this task in its "Basic Patterns"
document. The result will be a W3C Recommendation and a validation
tool which will indicate if a given XML Schema or WSDL is likely
to give "a good user experience with databinding tools".

We're also working on an "Advanced Patterns" document which
are a set of XML Schema patterns in common use which should
be better supported by databinding tools (but typically aren't).

This work is progressing slowly, thanks in no small part to
a lack of participation. In particular we've seen very little
interest from vendors, many of whom still claim to support
"the whole of schema" when they evidently don't, or
"the latest version of foobar works with xs:union" when the
current version of foobar has been in the wild for 3 or so
years and plainly doesn't.

The Working Group is conducting technical discussions in public,
and you are all welcome to contribute patterns and experiences
with toolkits:

http://www.w3.org/2002/ws/databinding/

Identifying the aspects of schema which doesn't work with
tools hasn't been the approach taken so far, but I continue
to wonder if "naming and shaming" tools which purport
to abstract away XML using an XML Schema as an IDL and yet
fail to map 'xs:choice', etc be a more fruitful activity.

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

On 4/26/06, Paul Downey <paul.downey@...> wrote:

> Identifying the aspects of schema which doesn't work with
> tools hasn't been the approach taken so far, but I continue
> to wonder if "naming and shaming" tools which purport
> to abstract away XML using an XML Schema as an IDL and yet
> fail to map 'xs:choice', etc be a more fruitful activity.
>

go for it :)

http://ws.apache.org/commons/axiom

After nearly 2 years of development and numerous incremental releases,
we are proud to announce the release of Version 1.0 of Apache AXIOM!
(Download : http://ws.apache.org/commons/axiom/download.cgi )

Apache AXIOM is a StAX-based, XML Infoset compliant object model which
supports on-demand building of the object tree. It supports a novel
"pull-through" model which allows one to turn off the tree building and
directly access the underlying pull event stream. It also has built in
support for XML Optimized Packaging (XOP) and MTOM, the combination of
which allows XML to carry binary data efficiently and in a transparent
manner. The combination of these is an easy to use API with a very
high performant architecture!

Developed as part of Apache Axis2, Apache AXIOM is the core of Apache
Axis2. However, it is a pure standalone XML Infoset model with novel
features and can be used independently of Apache Axis2.

Key Features
============

     * Full XML Infoset compliant XML object model
     * StAX based builders with on-demand building and pull-through
     * XOP/MTOM support offering direct binary support
     * Convenient SOAP Infoset API on top of AXIOM
     * Two implementations included:
           o Linked list based implementation
           o W3C DOM supporting implementation
     * High performant


Thanks for your interest in Apache AXIOM!


-The Apache AXIOM Development Team

Hi everybody,

                                   I am very new to SOAP, can anybody
provide me some example package of SOAP with PHP server and only XML for
client.  Actually i have downloaded the NuSoap Package, but i have to
create a webservice and have to provide only xml to my customers, In
Nusoap the client uses the package ( Class File  nusoap.php ) , and in
this case only customers who are using PHP as there enviournment can use
it. I need somthing(Only With XML) at client side which is plateform
Independent.

If any body uses NuSoap with only XML at client Please Help Me !!!!!!

thanks In Advance !!!!!!!!!!!!!!!

Best Regards

Vikas

vikas_mdu writes

> Hi everybody,
>
>                                   I am very new to SOAP, can anybody
> provide me some example package of SOAP with PHP server and only XML for
> client.  Actually i have downloaded the NuSoap Package, but i have to
> create a webservice and have to provide only xml to my customers, In
> Nusoap the client uses the package ( Class File  nusoap.php ) , and in
> this case only customers who are using PHP as there enviournment can use
> it. I need somthing(Only With XML) at client side which is plateform
> Independent.

As Anne responded, you can use any software you like at either end of a
SOAP connection.  I think the real question is: how robust do you want
your SOAP support to be.  If you know, for example, that the SOAP messages
sent to your clients will have no headers, or at least no headers for
which mustUnderstand="true", then you can just write a bit of code to
ensure that those aren't there in any responses you receive, raising an
error if they do show up.  If there are headers you want to process, then
to be a compliant SOAP implementation you have to follow some rules about
what order to do certain things, and it's much more likely you'll get them
right by using someone's package than trying to hack it yourself.  Either
approach is really OK, as long as you're building what you need for your
customers.  Of course, you can also build noncompliant software that may
work a lot of the time by just ignoring the official SOAP rules and
grepping through the responses for what appears to be the data you need.
Whether doing that is robust enough for your purposes is up to you, but
certainly there are applications that take this approach (at their own
risk, of course.)

In short, I wouldn't try to build up your own fully general purpose SOAP
support by hand, but you may very well find that you can easily build
robust support for just the part of SOAP you expect your applications to
use (e.g. no headers, or certain particular headers that you are
expecting.)  Certainly the code to send out a simple, compliant SOAP
request is straightforward.

--------------------------------------
Noah Mendelsohn
IBM Corporation
One Rogers Street
Cambridge, MA 02142
1-617-693-4036
--------------------------------------

Thanks To Noah and Anne for Response,

I got waht Anne and Noah want to say but I think my problem is little
misunderstood, Ok Let me clear..., As i told, i am using the NuSoap
package, currently what i seen that for the client side a script is
given in which client have to pass some parameters and have to use a
function '$soapclient->Call' to send the request to the server, if we
put the 'URL?wsdl' script makes its own wsdl depends on providing
parameters and ofcourse uses the 'nusoap.php' Class , but i want that
client script should request with only XML (complete Soap Envelope)
to the server through 'fsockopen' or 'cURL', and should use the
external wsdl (unlike as it currently create its own) file. So that
server should got an SOAP/XML envelope to process with an external
wsdl. As i told i am a newbie in SOAP, so didn't find such example of
NuSoap on the net. If anybody can help me, please
respond !!

One more question : If it is necessary to use the WSDL, and i seen
somwhere xsd file also can anybody tell me why these files are used
with SOAP messages and how Important are these ?

Best Regards
Vikas Sheoran


--- In soapbuilders@yahoogroups.com, "Anne Thomas Manes"
<atmanes@...> wrote:
>
> Using the NuSoap package to build a service does not require that
you use
> the same NuSoap package on the client. NuSoap will generate an XML
message
> packaged in a SOAP envelope, and any client can interpret the
message using
> only XML or using any other SOAP client package (for any programming
> language).
>
> Anne
>
> On 5/12/06, vikas_mdu <vikas_mdu@...> wrote:
> >
> >
> > Hi everybody,
> >
> >                                   I am very new to SOAP, can
anybody
> > provide me some example package of SOAP with PHP server and only
XML for
> > client.  Actually i have downloaded the NuSoap Package, but i
have to
> > create a webservice and have to provide only xml to my customers,
In
> > Nusoap the client uses the package ( Class File  nusoap.php ) ,
and in
> > this case only customers who are using PHP as there enviournment
can use
> > it. I need somthing(Only With XML) at client side which is
plateform
> > Independent.
> >
> > If any body uses NuSoap with only XML at client Please Help
Me !!!!!!
> >
> > thanks In Advance !!!!!!!!!!!!!!!
> >
> > Best Regards
> >
> > Vikas
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > -----------------------------------------------------------------
> > This group is a forum for builders of SOAP implementations to
discuss
> > implementation and interoperability issues.  Please stay on-topic.
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
> >
> >
> >
>

If you want to build the SOAP message programmatically, just do so and then POST it to the URL specified in the "location" attribute in the <soap:address> element in the <service> definition in the WSDL.

The WSDL provides important information that you need to know in order to construct the SOAP envelope correctly. If the service binding is defined as style="document" and use="literal", then you should be able to construct the message based on the XML Schema, and you shouldn't need to reference the WSDL. If the service binding is defined as style="rpc" and use="literal" or use="encoded", then you will need to reference the WSDL to construct the message properly.

Anne

On 5/13/06, vikas_mdu <vikas_mdu@...> wrote:

Thanks To Noah and Anne for Response,

I got waht Anne and Noah want to say but I think my problem is little
misunderstood, Ok Let me clear..., As i told, i am using the NuSoap
package, currently what i seen that for the client side a script is
given in which client have to pass some parameters and have to use a
function '$soapclient->Call' to send the request to the server, if we
put the 'URL?wsdl' script makes its own wsdl depends on providing
parameters and ofcourse uses the 'nusoap.php' Class , but i want that
client script should request with only XML (complete Soap Envelope)
to the server through 'fsockopen' or 'cURL', and should use the
external wsdl (unlike as it currently create its own) file. So that
server should got an SOAP/XML envelope to process with an external
wsdl. As i told i am a newbie in SOAP, so didn't find such example of
NuSoap on the net. If anybody can help me, please
respond !!

One more question : If it is necessary to use the WSDL, and i seen
somwhere xsd file also can anybody tell me why these files are used
with SOAP messages and how Important are these ?

Best Regards
Vikas Sheoran


--- In soapbuilders@yahoogroups.com, "Anne Thomas Manes"
<atmanes@...> wrote:
>
> Using the NuSoap package to build a service does not require that
you use
> the same NuSoap package on the client. NuSoap will generate an XML
message
> packaged in a SOAP envelope, and any client can interpret the
message using
> only XML or using any other SOAP client package (for any programming
> language).
>
> Anne
>
> On 5/12/06, vikas_mdu <vikas_mdu@...> wrote:
> >
> >
> > Hi everybody,
> >
> >                                   I am very new to SOAP, can
anybody
> > provide me some example package of SOAP with PHP server and only
XML for
> > client.  Actually i have downloaded the NuSoap Package, but i
have to
> > create a webservice and have to provide only xml to my customers,
In
> > Nusoap the client uses the package ( Class File   nusoap.php ) ,
and in
> > this case only customers who are using PHP as there enviournment
can use
> > it. I need somthing(Only With XML) at client side which is
plateform
> > Independent.
> >
> > If any body uses NuSoap with only XML at client Please Help
Me !!!!!!
> >
> > thanks In Advance !!!!!!!!!!!!!!!
> >
> > Best Regards
> >
> > Vikas
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > -----------------------------------------------------------------
> > This group is a forum for builders of SOAP implementations to
discuss
> > implementation and interoperability issues.  Please stay on-topic.
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
> >
> >
> >
>






------------------------ Yahoo! Groups Sponsor --------------------~-->
You can search right from your browser? It's easy and it's free.  See how.
http://us.click.yahoo.com/_7bhrC/NGxNAA/yQLSAA/W6uqlB/TM
--------------------------------------------------------------------~->

-----------------------------------------------------------------
This group is a forum for builders of SOAP implementations to discuss implementation and interoperability issues.  Please stay on-topic.
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/soapbuilders/

<*> To unsubscribe from this group, send an email to:
    soapbuilders-unsubscribe@yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Hi All,

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

Key Features

    1. AXIOM, an XML object model optimized for SOAP 1.1/1.2 messages.
This has complete XML infoset support.
    2. Support for One-Way Messaging (In-Only) and Request Response
Messaging (In-Out)
    3. Module architecture, mechanism to extend the SOAP processing model
    4. Context hierarchy
    5. Directory based deployment model
    6. Raw XML providers
    7. WS-Addressing, both the submission (2004/08) and final (2005/08)
versions
    8. Transports: HTTP
           * Both simple axis server and Apache2 httpd module
           * SSL client transport - New
    9. Service Groups - New
   10. Service client and operation client APIs - New
   11. REST support (POST case) - New
   12. Module version support - New
   13. MTOM support - New

Other notes

    1. Interoperability tested with Axis2/Java for XML in/out client and
services
    2. Addressing 1.0 interoperability

Major changes since last release

    1. Full Addressing 1.0 support
    2. Improved fault handling model
    3. SSL client transport
    4. MTOM implementation
    5. Implementation of easy to use service client and operation client
APIs for client side programming
    6. REST support (POST case)
    7. Module version support
    8. Service groups
    9. Numerous bug fixes since last release

Un-Implemented Architecture Features (TBD in 1.0)

    1. Sessions scoping for application, SOAP, transport and request levels
    2. Different character encoding support
    3. Dynamic invocation
    4. Archive based deployment Model

Un-Implemented Architecture Features (TBD post 1.0)

    1. WSDL code generation tool for stub and skeletons (based on Java tool)
    2. Security module
    3. REST (REpresentational State Transfer) support (GET case)
    4. Web Services policy support
    5. Axis2 Web application (Web App)

We welcome your early feedback on this implementation.
Thanks for your interest in Axis2C

-- Apache Axis2C Team --

 


Note: Forwarded message attached

-- Original Message --

From: "DIPAK GADHAVI" <dipakgadhavi009@...>
To: "Parmar Amit" <amit_518@...>, "darshak sureshbhai shah" <darshak40@...>, "malay pankhania" <malaypan@...>, bhavumech98@..., dhadkan@...
Subject: Fwd: REMEMBER : SEPTEMBER 22nd 2006

KDD-2006 Workshop on
    Data Mining Standards, Services and Platforms (DM-SSP 06)
    August 20, 2006


    A Workshop at KDD-2006
    The Twelfth ACM SIGKDD International Conference on
    Knowledge Discovery and Data Mining
    August 20-23, 2006
    Philadelphia, PA

-----------------------------------------------------------------

Web Site: http://www.ncdm.uic.edu/dm-ssp-06.htm
Workshop Submission Deadline: June 18, 2006


IMPORTANT DATES

June 18, 2006        Deadline for electronic submission papers or
abstracts
July 10, 2006        Notification of accepted presentations
July 20, 2006        Camera Ready Copies Due
August 20, 2006      DM-SSP Workshop

SUBMIT PAPERS TO: connelly@... with the subject line "DM-SSP 06
Workshop submission".

------------------------------------------------------------------


WORKSHOP DESCRIPTION

DM-SSP '06 is the sixth KDD workshop focusing on standards, services,
and platforms for data mining.  Motivating this workshop are a number
of trends, including:

      1. A number of standards have matured, including PMML, SQL-based
         standards for Data Mining, JDM, CRISP, and OMG CWM for Data
         Mining. It is timely to expose these standards to the
         community and to gather requirements through position papers
         and panels for new versions of these standards.

      2. Web services, as well as maturing and emerging data mining
         standards, will enable standards-based data mining services
         for scoring, modeling, and exploration of data.  This workshop
         will also include this timely topic.

      3. Work in related fields, including data grids, data webs, and
         semantic webs is very relevant to data mining but often not
         included in KDD per se.  This workshop will also provide an
         opportunity for work on data mining standards and services in
         these areas to be included.

If you are using standards and services to build production data
mining and scoring systems, we encourage you to submit a paper or
abstract to DM-SSP 06.  To encourage presentations from industry, we
will accept abstracts for presentations, as well as papers, for
consideration.


WORKSHOP FORMAT

The workshop will consist of both invited and contributed talks.  Some
of the invited talks will provide an update on PMML and emerging web
service standards for data mining.

All papers should be submitted by email in pdf format to
connelly@... with the subject line "DM-SSP 06 Workshop submission"
by June 18, 2006. Please use the prescribed formatting guidelines of
KDD (Springer LNCS).  The workshop proceedings will be published by
the ACM and distributed during the workshop. They will also be
available on the workshop's home page. The full version of the
accepted papers will be considered for publication in an edited
proceedings after a second round of reviews, pending approval.

Papers should be no longer than 12 pages (or 5,000 words) inclusive of
all references and figures. All papers must be submitted in either PDF
(preferred) or postscript. Please ensure that any special fonts used
are included in the submitted documents. All papers must be original,
and have not been published elsewhere.

For questions, please email connelly@... with the subject line
"DM-SSP 06 Workshop question".


WORKSHOP TOPICS

Topics appropriate for the workshop include the following topics and
closely related topics.

Standards Based Data Mining Services:

    * Scoring services
    * Analysis services
    * Data exploration services
    * Statistical modeling services

Maturing Standards:

    * Predictive Model Markup Language (PMML)
    * XML for Analysis
    * SQL-based standards for data mining
    * Java Data Mining (JDM) - Java Specification Request 73 (JSR-73)
    * CRoss Industry Standard Process for Data Mining (CRISP-DM)
    * OMG Common Warehouse Metadata (CWM) for Data Mining

Related Standards:

    * Web services (SOAP/XML, WSRF, etc)
    * Grid services (OGSA, etc.)
    * Semantic Web Standards (RDF, OWL, etc.)

Emerging Standards:

    * Standards for KDD workflow
    * Standards for data transformations
    * Standards for real time data mining
    * Standards for data webs

Open Source Data Mining Platforms:

    * R
    * Weka
    * GNU Octave


ORGANIZING COMMITTEE:

Dave Selinger, FortisForge.com
Robert Grossman, Open Data Group and University of Illinois at Chicago
Rick Pechter, MicroStrategy
Stefan Raspl, IBM
Shirley Connelly, University of Illinois at Chicago

HAI FRIENDS

           I AM NEWLY ENTERED INTO THIS PLATFORM . I HAVE LOT OF
REQUIREMENT FOR THIS JAVAWEBSERVICES .. BUT I DONOT KNOW ABOUT
JAVAWEBSERVICES ..PLEASE HELP ME...

           HOW TO RUN AND HOW TO INSTALL ALL THESE INFORMATION...


BY
SRIDHAR.VALLURU

We are pleased to announce the Final Release of the reference
implementation of the Java API for XML Web Services 2.0 (JAX-WS).
JAX-WS is the standard Java API for doing web services. JAX-WS was
approved by Apache, BEA, Fujitsu,  HP, IBM,  Intel, JBOSS, Oracle, SAP
and more.  The reference implementation is a product quality
implementation of the spec and is used in Glassfish application server
(http://glassfish.dev.java.net) as well as Sun's Java System Application
Server PE 9 (http://java.sun.com/javaee/downloads/index.jsp).  JAX-WS
2.0 is being developed as an open source project on java.net at
http://jax-ws.dev.java.net.

Key Features:
     1. Ease of use by utilizing annotations: deployment descriptors are
no longer necessary.
     2. Portability:  All Java artifacts that the spec. mandates are
portable.  This means that you can confidently write an application
using one vendor's implementation of JAX-WS and it will run on any other
version.
     3.  JAXB (http://jaxb.dev.java.net) is used for databinding:  JAXB
provides 100% schema support and bi-directional mapping between schema
and Java.
     4.  REST support: Not just POST, but also GET, PUT and  DELETE
     5.  Layered architecture which allows the developer to either
program to a strongly typed interface or they can choose to use the
Dispatch and Provider APIs to have direct access to the message.
     6.  JAX-WS uses a dynamic annotation driven runtime, no more static
marshallers/unmarshallers are generated as in JAX-RPC
     7.  JAX-WS is part of Java 6:  JAX-WS is already part of Mustang
(http://mustang.dev.java.net) which means that JAX-WS applications no
longer have to ship library code.


We have already started working on version JAX-WS 2.0.1 of the reference
implementation. 2.0.1 does not change the API's that the developer uses,
but only improves the implementation.  The main goals of 2.0.1 are to
improve performance over 2.0 and to allow for greater extensibility and
modularity.  The WSIT (Web Services Interoperability Technologies:
http://wsit.dev.java.net) uses the new extension framework included in
JAX-WS 2.0.1.  WSIT will provide support for a number of the WS-*
specifications including
WS-Addressing, WS-Reliable Messaging,  WS-Secure Conversation, WS-Trust,
WS-SecurityPolicy, WS-Security, WS-Policy, WS-MetaDataExchange,
WS-Coordination and WS-AtomicTransactions.  WSIT is also being developed
as an open source project.

Download JAX-WS and give it a try.  If you are familiar with JAX-RPC I
believe you will be pleasantly surprised.

CALL FOR PAPERS

4th International Conference on Service-Oriented Computing (ICSOC'06)
Chicago, USA, December 4-7, 2006


Full conference information: http://www.icsoc.org/


Important Dates:

Workshop proposal submission:   May 30, 2006
Paper abstract submission:      June 12, 11:59pm, PST
Full paper submission:          June 19, 11:59pm, PST
Tutorial and panel submission:  July 6, 2006
Notification of acceptance:     September 12, 2006
Final manuscript due:           September 25, 2006
Main conference:                December 4-7, 2006



The 4th International Conference of Service Oriented Computing (ICSOC'06)
follows on the success of three previous editions in Amsterdam (2005), New
York City (2004), and Trento (2003). Today ICSOC is recognized as the main
conference for service oriented computing research and covers the entire
spectrum from theoretical and foundational results to empirical
evaluations as well as practical and industrial experiences.

ICSOC'06 seeks original papers in the field of service oriented computing,
from theoretical and foundational results to empirical evaluations as well
as practical and industrial experiences, with an emphasis on contributions
to solve the many still open research problems that are of significant
impact to the field of service oriented applications. Topics include but
are not limited to the following:

* Business Service Modeling: Methods and tools for capturing business
goals
   and requirements, Decomposition into business services, Business
   processes, Business policies, Modeling, analysis, and simulation,
   Specification of functional and non-functional quality requirements;

* Service Assembly: Development and Discovery: Model-driven development,
   Service composition architectures, Service registries, Service discovery
   mechanisms, Semantic matching, Methods and tools for service
development,
   Governance, Verification and validation, Deployment strategies;

* Service Management: Instrumentation and service related data
aggregation,
   end-to-end Measurement, Analysis, Modeling and Capacity planning,
   Definition of deployment topology, Infrastructure configuration,
   Problem determination for SOAs, ITIL processes, Change management in
   live systems.

* SOA Runtime: Service Bus for mediation, transformation and routing,
   Runtime registry, Integration of legacy applications, Information
   services for data access and data integration, Scalability, Topology
   and Optimization, Service oriented middleware, Policy-based
   configuration & Workload management

* Quality of Service: Reliable Service-Oriented Computing, Security and
   Privacy in Service-Oriented Computing, SLA and Policy specification,
   QoS Negotiation, Autonomic management of service levels, Empirical
   Studies and Benchmarking of QoS, Performance and Dependability
prediction
   in SOA;

* Grid Services: Services and architecture for management of
infrastructural
   resources, Data and Compute intensive applications, Execution and
resource
   allocation services for job scheduling, Protocols for coordination
across
   multiple resource managers, Business value based allocation, Innovative
   Strategies for Creation and Management of Virtual Enterprises and
   Organizations, Prototype systems and Toolkits.


There will be two independent tracks for Research and Industrial papers,
each managed by a different program committee and with a different set of
evaluation criteria. The authors must clearly indicate the track to which
the paper is being submitted.

* Research Papers: The conference is soliciting original research papers
on
   all aspects of web services and service-oriented computing. The
   submissions should contain results which advance the state of the art in
   service-oriented systems, either through theoretical analysis or
   experimental analysis. They should clearly establish the research
   contribution, the relevance to service-oriented computing and the
relation
   to prior research. Submitted papers will be judged according to their
   scientific merit and evaluated on significance, originality, technical
   quality, and presentation.

* Industrial and Application Papers: ICSOC'06 places a strong emphasis on
   its industrial program and encourages submissions covering the
application
   of service-oriented computing in practice, including papers describing
   innovative service-based implementations, novel applications of service
   oriented technology, and major improvements to the state-of-practice.
   Actual case studies from practitioners emphasizing applications, service
   technology, system deployment, organizational ramifications, or business
   impact are especially welcomed. Industrial and application papers should
   give sufficient details on the application domain, on the service
oriented
   techniques that have been used, on the issues surrounding actual
   implementations and applications, and on the lessons learned in
developing
   service oriented applications. The papers submitted to this track can
   range from a few page extended abstract to a full paper. The track will
   also include a small number of invited visionary papers.


All papers should be submitted electronically in PDF and in Springer/LNCS
format. Research and industrial papers are not to exceed 12 pages.
Abstracts for research and application papers - not exceeding 200 words -
need to be submitted one week prior to the paper submission deadline. All
submissions should include title, authors, full contact information, and
references.
Submissions should indicate at least two main topics and the scientific
area (or areas) that best fit the paper. For selected papers, authors will
be given the opportunity to submit a one-page reply, within one week, to
answer to the reviewers' concerns.  This is done in the effort to improve
the paper selection process and make sure that papers are not rejected
based on some misunderstanding or erroneous interpretation by the
reviewers that is easy to correct in preparing the final version. All
accepted papers will appear in the ICSOC'06 archival proceedings,
published by Springer.

For the complete information please visit the conference website:
http://www.icsoc.org


CONFERENCE ORGANIZATION

General Chairs:           Ian Foster (ANL & The University of Chicago),
                           Carlo Ghezzi (Politecnico di Milano)
Program Chairs:           Asit Dan (IBM),
                           Winfried Lamersdorf (Hamburg University)
Industrial Track Chairs:  Robert Johnson (IBM),
                           Jeff Mischkinsky (Oracle)
Workshop Coordination     Dimitrios Georgakopoulos (Telcordia
Technologies)
                   Chairs: Norbert Ritter (Hamburg University)
Tutorial Chairs:          Frank Leymann (University of Stuttgart)
                           Heiko Ludwig (IBM Research)
Local Organization Chair: Julie Wulf-Knoerzer (Univa)
Financial Chair:          Vincenzo D'andrea, (University of Trento)
Registration Chair:   Martin Swany (University of Delaware)
Publication Chair:        Boualem Benatallah (UNSW)
Publicity Chair:          Matei Ripeanu (University of British Columbia)

STEERING COMMITTEE

Fabio Casati (Hewlett-Packard Labs, USA)
Paco Curbera (IBM Research, USA)
Mike Papazoglou (Tilburg University, The Nederland)
Paolo Traverso (ITC-IRST, Italy)


PROGRAM COMMITTEE

Area Coordinators

Service Modeling:   Wolfgang Emmerich (University College London)
                     Mathias Weske (University of Potsdam)
Service Assembly:   Barbara Pernici (Politecnico di Milano)
                     Munindar Singh (North Carolina State University)
Service Management: Luciano Baresi (Politecnico di Milano)
                     Hiro Kishimoto (Fujitsu)
SOA Runtime:        Douglas Schmidt (Vanderbilt University)
                     Steve Vinoski (Iona)
Quality of Service: Priya Narasimhan (CMU)
                     Jim Pruyne (HP)
Grid Services:      Dennis Gannon (Indiana University)
                     Paul Watson (University of Newcastle upon Tyne)


Program Committee Members - Research Track

Nabil R. Adam (Rutgers University)
Jose Luis Ambite (USC)
Mikio Aoyama (NISE)
Boualem Benatallah (University of New South Wales)
Elisa Bertino (Purdue University)
Walter Binder (EPFL)
Athman Bouguettaya (Virginia Tech)
Sjaak Brinkkemper (Utrecht Univ.)
Tevfik Bultan (UCSB)
Fabio Casati (HP)
Malu Castellanos (HP)
Bruno Crispo (Vrije University)
Paco Curbera (IBM Research)
Vincenzo D'Andrea (Universita di Trento)
Umesh Dayal (HP)
Flavio De Paoli (Universita di Milano)
Tommaso Di Noia (University of Bari)
Jens-Peter Dittrich (ETH Zurich)
John Domingue (KMI)
Schahram Dustdar (University of Technology Vienna)
Kim Elms (SAP)
Boi Faltings (EPFL)
Dieter Fensel (Deri Innsbruck)
Gianluigi Ferrari (University of Pisa)
George Feuerlicht (University of Technology Sydney)
Ioannis Fikouras (Ericsson)
Daniela Florescu (INRIA)
Geoffrey Fox (Indiana University)
Dimitrios Georgakopoulos (Telcordia)
Paolo Giorgini (University of Trento)
Claude Godart (LORIA)
Paul Grefen (Eindhoven)
John Grundy (University of Auckland)
Mohand-Said Hacid (Université Lyon)
Hakan Hacigumus (Almaden IBM)
Richard Hull (Lucent)
Kate Keahey (Argonne National Laboratory)
Alfons Kemper (Technische Universität München)
Roger Kilian-Kehr (SAP Karlsruhe)
Jana Koehler (IBM Zurich Research Lab)
Bernd Kraemer (Fernuniversitaet Hagen)
Brian LaMacchia (Microsoft)
Frank Leymann (University of Stuttgart)
Ling Liu (Georgia Institute of Technology)
Pierluigi Lucchese (ITC-IRST Trento)
Heiko Ludwig (IBM Research)
Neil Maiden (City University London)
Ioana Manolescu (INRIA)
David Martin (SRI)
Eugene M. Maximilien (IBM Almaden)
Massimo Mecella (Universita di Roma)
Brahim Medjahed (Michigan University)
Toshi Nakata (NEC)
Steve Newhouse (Univ. of Southampton)
Christos Nikolaou (University of Crete)
David O'hallaron (CMU)
Guadalupe Ortiz (Univ. de Extremadura)
Mike Papazoglou (Tilburg University)
Anna Perini (ITC-IRST Trento)
Marco Pistore (Universita di Trento)
Axel Polleres (Univ. Rey Juan Carlos)
Jean Pierre Prost (IBM Montpellier)
Omer Rana (Cardiff University)
Thomas Risse (Fraunhofer Gesellschaft)
Norbert Ritter (Hamburg University)
Colette Rolland (Universite de Paris I)
Rainer Ruggaber (SAP)
Akhil Sahai (HP)
Volker Sander (Julich Research Centre)
Vladimiro Sassone (Univ. of Southampton)
Dimitrios N. Serpanos (Univ. of Patras)
Jun Shen (Univ. of Wollongong)
Santosh Srivastava (Univ. of New Castle)
Maarten Steen (Telematica Enschede)
Tony Storey (IBM)
Jianwen Su (UCSB)
Ravi Subramaniam (Intel)
Angelo Susi (ITC-IRST Trento)
Katia Sycara (CMU)
Stefan Tai (IBM New York)
Kian-Lee Tan (National Univ. of Singapore)
Margaria Tiziana (Potsdam University)
Paolo Tonella (ITC-IRST Trento)
Farouk Toumani (ISIMA Aubiere)
Don Towsley (UMass)
Paolo Traverso (ITC-RST)
Aphrodite Tsalgatidou (Univ. of Athens)
Karthikeyan Umapathy (Penn State Univ.)
Will van der Aalst (Eindhoven University of Technology)
Jos van Hillegersberg (University of Twente)
Aad Van Moorsel (Univ. of Newcastle)
Vijay Varadharajan (Macquire University)
John Wilkes (HP Labs Palo Alto)
Martin Wirsing (University of Munich)
Raymond Wong (Univ. of New South Wales)
Jian Yang (Macquire University)
Yelena Yesha (University of Maryland)
Arkady Zaslavsky (Monash University)
Gianluigi Zavattaro (University of Bologna)
Yanchun Zhang (Victoria University)
Christian Zirpins (Univ. College London)


Program Committee Members - Industry Track

Anne Anderson (Sun)
Paul Freemantle (WSO2)
Steve Graham (IBM)
Kerrie Holley (IBM)
Robert Johnson (IBM)
Philippe Le Hegaret (W3)
Mark Little (NCL)
Jeff Mischinsky (Oracle)
Andy Mulholland (Gemini Consulting)
Mark Nottingham (Yahoo)
Sanjay Patil (SAP)
Greg Pavlik (Oracle)
Sanjeeva Weerawarana (WSO2)
Bobbi Young (Unisys)

On 5/30/06, Doug Kohlert <doug.kohlert@...> wrote:
> We are pleased to announce the Final Release of the reference
> implementation of the Java API for XML Web Services 2.0 (JAX-WS).
> JAX-WS is the standard Java API for doing web services. JAX-WS was
> approved by Apache, BEA, Fujitsu,  HP, IBM,  Intel, JBOSS, Oracle, SAP
> and more.  The reference implementation is a product quality
> implementation of the spec and is used in Glassfish application server
> (http://glassfish.dev.java.net) as well as Sun's Java System Application
> Server PE 9 (http://java.sun.com/javaee/downloads/index.jsp).  JAX-WS
> 2.0 is being developed as an open source project on java.net at
> http://jax-ws.dev.java.net.


> Key Features:
>     1. Ease of use by utilizing annotations: deployment descriptors are
> no longer necessary.

I'm not convinced that hard coding deployment options in source is any
better than coding them into XML descriptors, but that is a separate
topic.

What I am curious about is the fact that Java EE mandates both
JAXRPC1.1 and JAXWS. Does glassfish run the old and the new side by
side? Or does the stack merge a few methods down?

-steve

Steve,
First, deployment options do not need to be encoded in sources, 109 has
just defined resonable defaults that a DD is no longer necessary.  You
have the choice of adding some deployment characteristics to code but
the DD can always override what is in the code so you should have no
concernes there.
Second, yes both JAX-RPC and JAX-WS run side-by-side and in Glassfish,
they do not share any code.

Steve Loughran wrote:

> On 5/30/06, Doug Kohlert <doug.kohlert@...
> <mailto:doug.kohlert%40sun.com>> wrote:
> > We are pleased to announce the Final Release of the reference
> > implementation of the Java API for XML Web Services 2.0 (JAX-WS).
> > JAX-WS is the standard Java API for doing web services. JAX-WS was
> > approved by Apache, BEA, Fujitsu, HP, IBM, Intel, JBOSS, Oracle, SAP
> > and more. The reference implementation is a product quality
> > implementation of the spec and is used in Glassfish application server
> > (http://glassfish.dev.java.net <http://glassfish.dev.java.net>) as
> well as Sun's Java System Application
> > Server PE 9 (http://java.sun.com/javaee/downloads/index.jsp
> <http://java.sun.com/javaee/downloads/index.jsp>). JAX-WS
> > 2.0 is being developed as an open source project on java.net at
> > http://jax-ws.dev.java.net. <http://jax-ws.dev.java.net.>
>
> > Key Features:
> > 1. Ease of use by utilizing annotations: deployment descriptors are
> > no longer necessary.
>
> I'm not convinced that hard coding deployment options in source is any
> better than coding them into XML descriptors, but that is a separate
> topic.
>
> What I am curious about is the fact that Java EE mandates both
> JAXRPC1.1 and JAXWS. Does glassfish run the old and the new side by
> side? Or does the stack merge a few methods down?
>
> -steve
>
>

On 6/6/06, Doug Kohlert <doug.kohlert@...> wrote:
> Steve,
> First, deployment options do not need to be encoded in sources, 109 has
> just defined resonable defaults that a DD is no longer necessary.  You
> have the choice of adding some deployment characteristics to code but
> the DD can always override what is in the code so you should have no
> concernes there.

seems good.

> Second, yes both JAX-RPC and JAX-WS run side-by-side and in Glassfish,
> they do not share any code.

How do they reconcile the need for JAXRPC to depend upon one version
of SAAJ and the JAXWS needing a different version?

-steve

Steve,
I believe that JAX-RPC and JAX-WS in glassfish both use the same version
of SAAJ.

Steve Loughran wrote:

> On 6/6/06, Doug Kohlert <doug.kohlert@...
> <mailto:doug.kohlert%40sun.com>> wrote:
> > Steve,
> > First, deployment options do not need to be encoded in sources, 109 has
> > just defined resonable defaults that a DD is no longer necessary. You
> > have the choice of adding some deployment characteristics to code but
> > the DD can always override what is in the code so you should have no
> > concernes there.
>
> seems good.
>
> > Second, yes both JAX-RPC and JAX-WS run side-by-side and in Glassfish,
> > they do not share any code.
>
> How do they reconcile the need for JAXRPC to depend upon one version
> of SAAJ and the JAXWS needing a different version?
>
> -steve
>
>