You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by susae lee <su...@yahoo.com> on 2006/03/05 12:52:50 UTC
repost - error for soap
i just read through Axis user doc, but all sample app it mention doesn't show how to use the <HEADER> tag inside soap request / response.
1 -- is <HEADER> tag not much a use when doing 1 - 1 host to host request /response?
2 -- <HEADER> is only useful when soap massage need to pass multiple endpoints / hosts ?
3 -- Why most of the web services at www.xmethods.net don't use <HEADER> tag on request / response xml?
4 -- Is that in most cases, BODY tag in soap is enough? no HEADER needed?
5 -- Hosts in between web service client + provider process <HEADER> elements but not the content of BODY element? and the Ultimate SOAP receiver will process the BODY elements?
---------------------------------
Yahoo! Mail
Bring photos to life! New PhotoMail makes sharing a breeze.
Re: repost - error for soap
Posted by Shaoguang Cong <sc...@yahoo.com>.
Anne,
We know from your postings and examples in the Axis (I use 1.3) release that we can specify the SOAP <header> in the WSDL. But all examples I seen are not "wrapped" document/literal, thus not WS-I compliant. If I write the WSDL strictly follows the "wrapped" document/literal style and include the <header> in the input binding, Axis wsdl2java just ignores the <header> in the generated classes.
Similar questions are posted several times, including one by myself. Since this is very important, I really want to get an answer. Do you know if this is just not supported by Axis or is it a bug? Should we post this question to soap_dev?
Thanks.
Shaoguang
Anne Thomas Manes <at...@gmail.com> wrote:
Susae,
Most web services posted on xmethods.com are for demo purposes only. They don't require authentication, monitoring, auditing, routing, transformations, or any additional infrastructure functionality. As a best practice, business-oriented services should require authentication, and they should be monitored and audited. These functions don't require intermediation (you can use transport-level authentication [HTTP Auth or SSL mutual auth] for 1-to-1 connections), but many organizations choose to use an intermediary to implement this functionality.
Routing, transformations, and acceleration typically require an intermediary. When using intermediaries, you typically also need to shift to application-level security (WS-Security).
The "ultimate receiver" is the last SOAP node to receive the SOAP message. It comprises a SOAP engine and an application agent. The SOAP engine processes the SOAP message -- both Header and Body. Typically it uses handlers to processs the Header element, and serializers to convert the Body into language objects. The application agent is the application code that gets dispatched after the SOAP engine has processed the incoming message. If an response is required, the agent returns a language object return value to the SOAP engine, which then transforms it into a SOAP Response message, and then uses handlers to construct any necessary Header blocks.
A handler and an intermediary are different things. A handler runs within the SOAP node. An intermediary is a separate SOAP node.
Anne
On 3/7/06, susae lee <su...@yahoo.com> wrote: you mention routing - if you sent soap to a host for routing then it's not 1-to-1 and must be intermediated connection, correct ?
you mean most web services are very simple sample for demo only and commerical implementations are much more complex?
and you mention "application agent" are u mening Ultimate SOAP receiver?
you mention "intermediary" is meaning same as "handler with the hosting SOAP engine." correct?
Anne Thomas Manes < atmanes@gmail.com> wrote:
People typically use a SOAP Header to perform system-level functionality, such as authentication, session management, and routing. These functional requirements apply to both 1-to-1 and intermediated connections.
Most web services on xmethods.com do not require these system-level functions.
Typically header information is not passed to the application agent. Instead, the header is processed either by an intermediary or by a handler with the hosting SOAP engine.
Anne
On 3/5/06, susae lee <susae008@yahoo.com > wrote: i just read through Axis user doc, but all sample app it mention doesn't show how to use the <HEADER> tag inside soap request / response.
1 -- is <HEADER> tag not much a use when doing 1 - 1 host to host request /response?
2 -- <HEADER> is only useful when soap massage need to pass multiple endpoints / hosts ?
3 -- Why most of the web services at www.xmethods.net don't use <HEADER> tag on request / response xml?
4 -- Is that in most cases, BODY tag in soap is enough? no HEADER needed?
5 -- Hosts in between web service client + provider process <HEADER> elements but not the content of BODY element? and the Ultimate SOAP receiver will process the BODY elements?
---------------------------------
Yahoo! Mail
Bring photos to life! New PhotoMail makes sharing a breeze.
---------------------------------
Yahoo! Mail
Bring photos to life! New PhotoMail makes sharing a breeze.
---------------------------------
Yahoo! Mail
Use Photomail to share photos without annoying attachments.
Re: repost - error for soap
Posted by Anne Thomas Manes <at...@gmail.com>.
Susae,
Most web services posted on xmethods.com are for demo purposes only. They
don't require authentication, monitoring, auditing, routing,
transformations, or any additional infrastructure functionality. As a best
practice, business-oriented services should require authentication, and they
should be monitored and audited. These functions don't require
intermediation (you can use transport-level authentication [HTTP Auth or SSL
mutual auth] for 1-to-1 connections), but many organizations choose to use
an intermediary to implement this functionality.
Routing, transformations, and acceleration typically require an
intermediary. When using intermediaries, you typically also need to shift to
application-level security (WS-Security).
The "ultimate receiver" is the last SOAP node to receive the SOAP message.
It comprises a SOAP engine and an application agent. The SOAP engine
processes the SOAP message -- both Header and Body. Typically it uses
handlers to processs the Header element, and serializers to convert the Body
into language objects. The application agent is the application code that
gets dispatched after the SOAP engine has processed the incoming message. If
an response is required, the agent returns a language object return value to
the SOAP engine, which then transforms it into a SOAP Response message, and
then uses handlers to construct any necessary Header blocks.
A handler and an intermediary are different things. A handler runs within
the SOAP node. An intermediary is a separate SOAP node.
Anne
On 3/7/06, susae lee <su...@yahoo.com> wrote:
>
> you mention routing - if you sent soap to a host for routing then it's not
> 1-to-1 and must be intermediated connection, correct ?
>
> you mean most web services are very simple sample for demo only and
> commerical implementations are much more complex?
>
> and you mention "application agent" are u mening Ultimate SOAP receiver?
>
> you mention "intermediary" is meaning same as "handler with the hosting
> SOAP engine." correct?
>
>
> *Anne Thomas Manes <at...@gmail.com>* wrote:
>
> People typically use a SOAP Header to perform system-level functionality,
> such as authentication, session management, and routing. These functional
> requirements apply to both 1-to-1 and intermediated connections.
>
> Most web services on xmethods.com do not require these system-level
> functions.
>
> Typically header information is not passed to the application agent.
> Instead, the header is processed either by an intermediary or by a handler
> with the hosting SOAP engine.
>
> Anne
>
> On 3/5/06, susae lee <su...@yahoo.com> wrote:
> >
> > i just read through Axis user doc, but all sample app it mention
> > doesn't show how to use the <HEADER> tag inside soap request / response.
> >
> > 1 -- is <HEADER> tag not much a use when doing 1 - 1 host to host
> > request /response?
> >
> > 2 -- <HEADER> is only useful when soap massage need to pass multiple
> > endpoints / hosts ?
> >
> > 3 -- Why most of the web services at www.xmethods.net don't use <HEADER>
> > tag on request / response xml?
> >
> > 4 -- Is that in most cases, BODY tag in soap is enough? no HEADER
> > needed?
> >
> > 5 -- Hosts in between web service client + provider process <HEADER>
> > elements but not the content of BODY element? and the Ultimate SOAP receiver
> > will process the BODY elements?
> > ------------------------------
> > Yahoo! Mail
> > Bring photos to life! New PhotoMail
> > <http://pa.yahoo.com/*http://us.rd.yahoo.com/evt=39174/*http://photomail.mail.yahoo.com>makes
> > sharing a breeze.
> >
>
>
> ------------------------------
> Yahoo! Mail
> Bring photos to life! New PhotoMail
> <http://pa.yahoo.com/*http://us.rd.yahoo.com/evt=39174/*http://photomail.mail.yahoo.com>makes sharing a breeze.
>
>
Re: repost - error for soap
Posted by susae lee <su...@yahoo.com>.
Hi Anne
you mention routing - if you sent soap to a host for routing then it's not 1-to-1 \
and must be intermediated connection, correct ?
you mean most web services are very simple sample for demo only and commerical
implementations are much more complex?
and you mention "application agent" are u meaning Ultimate SOAP receiver?
you mention "intermediary" is meaning same as "handler with the hosting SOAP \
engine." correct?
Thanks again
>
> Anne Thomas Manes wrote:
> People typically use a SOAP Header to perform system-level functionality, such as authentication, session management, and routing. These functional requirements apply to both 1-to-1 and intermediated connections.
>
> Most web services on xmethods.com do not require these system-level functions.
>
> Typically header information is not passed to the application agent. Instead, the header is processed either by an intermediary or by a handler with the hosting SOAP engine.
>
> Anne
>
> On 3/5/06, susae lee wrote: i just read through Axis user doc, but all sample app it mention doesn't show how to use the tag inside soap request / response.
>
> 1 -- is tag not much a use when doing 1 - 1 host to host request /response?
>
> 2 -- is only useful when soap massage need to pass multiple endpoints / hosts ?
>
> 3 -- Why most of the web services at www.xmethods.net don't use tag on request / response xml?
>
> 4 -- Is that in most cases, BODY tag in soap is enough? no HEADER needed?
>
> 5 -- Hosts in between web service client + provider process elements but not the content of BODY element? and the Ultimate SOAP receiver will process the BODY elements?
---------------------------------
Yahoo! Mail
Bring photos to life! New PhotoMail makes sharing a breeze.
Re: repost - error for soap
Posted by Dies Koper <di...@jp.fujitsu.com>.
Hello Eric,
eric kong wrote:
> 1) one SEI = one stub --> map to --> one skeleton = one URL = one web service = 1 WSDL describe 1 web service
I never use skeletons but I suppose one SEI maps to one skeleton.
You could publish your SEI at several URLs (one <portType>, <binding>
tag, with two <port> tags (under <binding>) referring to them).
So one WSDL could define several SEIs at different locations, published
in different ways (SOAP over HTTP, or other ways).
> 2) but you said "You can define multiple web services (with all their URLs) in one WSDL" that means you have to manually edit the WSDL file?
Yes.
> 4) there is no way automatcally generate 1 WSDL multiple web services ?
If "automatically generate" does not include the Java2WSDL command (-i
option), then I suppose not.
> 5) since when we request to ?wsdl in axis we get a WSDL file describe 1 web service only. there is no way to autmatically generate a WSDL describe multiple web services, correct?
I suppose so.
Sorry, I never use ?wsdl so I'm not sure what it produces, but I guess
you confirmed already what it outputs.
Regards,
Dies
> Note SEI = Service Endpoint Interface
>
> susae lee <su...@yahoo.com> wrote:
> you mention routing - if you sent soap to a host for routing then it's not 1-to-1 and must be intermediated connection, correct ?
>
> you mean most web services are very simple sample for demo only and commerical implementations are much more complex?
>
> and you mention "application agent" are u mening Ultimate SOAP receiver?
>
> you mention "intermediary" is meaning same as "handler with the hosting SOAP engine." correct?
>
>
>
> Anne Thomas Manes <at...@gmail.com> wrote:
> People typically use a SOAP Header to perform system-level functionality, such as authentication, session management, and routing. These functional requirements apply to both 1-to-1 and intermediated connections.
>
> Most web services on xmethods.com do not require these system-level functions.
>
> Typically header information is not passed to the application agent. Instead, the header is processed either by an intermediary or by a handler with the hosting SOAP engine.
>
> Anne
>
> On 3/5/06, susae lee <su...@yahoo.com> wrote: i just read through Axis user doc, but all sample app it mention doesn't show how to use the <HEADER> tag inside soap request / response.
>
> 1 -- is <HEADER> tag not much a use when doing 1 - 1 host to host request /response?
>
> 2 -- <HEADER> is only useful when soap massage need to pass multiple endpoints / hosts ?
>
> 3 -- Why most of the web services at www.xmethods.net don't use <HEADER> tag on request / response xml?
>
> 4 -- Is that in most cases, BODY tag in soap is enough? no HEADER needed?
>
> 5 -- Hosts in between web service client + provider process <HEADER> elements but not the content of BODY element? and the Ultimate SOAP receiver will process the BODY elements?
Re: repost - error for soap
Posted by eric kong <ui...@yahoo.com>.
1) one SEI = one stub --> map to --> one skeleton = one URL = one web service = 1 WSDL describe 1 web service
2) but you said "You can define multiple web services (with all their URLs) in one WSDL" that means you have to manually edit the WSDL file?
4) there is no way automatcally generate 1 WSDL multiple web services ?
5) since when we request to ?wsdl in axis we get a WSDL file describe 1 web service only. there is no way to autmatically generate a WSDL describe multiple web services, correct?
Note SEI = Service Endpoint Interface
susae lee <su...@yahoo.com> wrote:
you mention routing - if you sent soap to a host for routing then it's not 1-to-1 and must be intermediated connection, correct ?
you mean most web services are very simple sample for demo only and commerical implementations are much more complex?
and you mention "application agent" are u mening Ultimate SOAP receiver?
you mention "intermediary" is meaning same as "handler with the hosting SOAP engine." correct?
Anne Thomas Manes <at...@gmail.com> wrote:
People typically use a SOAP Header to perform system-level functionality, such as authentication, session management, and routing. These functional requirements apply to both 1-to-1 and intermediated connections.
Most web services on xmethods.com do not require these system-level functions.
Typically header information is not passed to the application agent. Instead, the header is processed either by an intermediary or by a handler with the hosting SOAP engine.
Anne
On 3/5/06, susae lee <su...@yahoo.com> wrote: i just read through Axis user doc, but all sample app it mention doesn't show how to use the <HEADER> tag inside soap request / response.
1 -- is <HEADER> tag not much a use when doing 1 - 1 host to host request /response?
2 -- <HEADER> is only useful when soap massage need to pass multiple endpoints / hosts ?
3 -- Why most of the web services at www.xmethods.net don't use <HEADER> tag on request / response xml?
4 -- Is that in most cases, BODY tag in soap is enough? no HEADER needed?
5 -- Hosts in between web service client + provider process <HEADER> elements but not the content of BODY element? and the Ultimate SOAP receiver will process the BODY elements?
---------------------------------
Yahoo! Mail
Bring photos to life! New PhotoMail makes sharing a breeze.
---------------------------------
Yahoo! Mail
Bring photos to life! New PhotoMail makes sharing a breeze.
---------------------------------
Yahoo! Mail
Bring photos to life! New PhotoMail makes sharing a breeze.
Re: repost - error for soap
Posted by susae lee <su...@yahoo.com>.
you mention routing - if you sent soap to a host for routing then it's not 1-to-1 and must be intermediated connection, correct ?
you mean most web services are very simple sample for demo only and commerical implementations are much more complex?
and you mention "application agent" are u mening Ultimate SOAP receiver?
you mention "intermediary" is meaning same as "handler with the hosting SOAP engine." correct?
Anne Thomas Manes <at...@gmail.com> wrote:
People typically use a SOAP Header to perform system-level functionality, such as authentication, session management, and routing. These functional requirements apply to both 1-to-1 and intermediated connections.
Most web services on xmethods.com do not require these system-level functions.
Typically header information is not passed to the application agent. Instead, the header is processed either by an intermediary or by a handler with the hosting SOAP engine.
Anne
On 3/5/06, susae lee <su...@yahoo.com> wrote: i just read through Axis user doc, but all sample app it mention doesn't show how to use the <HEADER> tag inside soap request / response.
1 -- is <HEADER> tag not much a use when doing 1 - 1 host to host request /response?
2 -- <HEADER> is only useful when soap massage need to pass multiple endpoints / hosts ?
3 -- Why most of the web services at www.xmethods.net don't use <HEADER> tag on request / response xml?
4 -- Is that in most cases, BODY tag in soap is enough? no HEADER needed?
5 -- Hosts in between web service client + provider process <HEADER> elements but not the content of BODY element? and the Ultimate SOAP receiver will process the BODY elements?
---------------------------------
Yahoo! Mail
Bring photos to life! New PhotoMail makes sharing a breeze.
---------------------------------
Yahoo! Mail
Bring photos to life! New PhotoMail makes sharing a breeze.
Re: repost - error for soap
Posted by Anne Thomas Manes <at...@gmail.com>.
People typically use a SOAP Header to perform system-level functionality,
such as authentication, session management, and routing. These functional
requirements apply to both 1-to-1 and intermediated connections.
Most web services on xmethods.com do not require these system-level
functions.
Typically header information is not passed to the application agent.
Instead, the header is processed either by an intermediary or by a handler
with the hosting SOAP engine.
Anne
On 3/5/06, susae lee <su...@yahoo.com> wrote:
>
> i just read through Axis user doc, but all sample app it mention doesn't
> show how to use the <HEADER> tag inside soap request / response.
>
> 1 -- is <HEADER> tag not much a use when doing 1 - 1 host to host request
> /response?
>
> 2 -- <HEADER> is only useful when soap massage need to pass multiple
> endpoints / hosts ?
>
> 3 -- Why most of the web services at www.xmethods.net don't use <HEADER>
> tag on request / response xml?
>
> 4 -- Is that in most cases, BODY tag in soap is enough? no HEADER needed?
>
> 5 -- Hosts in between web service client + provider process <HEADER>
> elements but not the content of BODY element? and the Ultimate SOAP receiver
> will process the BODY elements?
>
> ------------------------------
> Yahoo! Mail
> Bring photos to life! New PhotoMail
> <http://pa.yahoo.com/*http://us.rd.yahoo.com/evt=39174/*http://photomail.mail.yahoo.com>makes sharing a breeze.
>
>