You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by ia...@apache.org on 2004/01/02 17:28:51 UTC
cvs commit: ws-axis/java/src/org/apache/axis/message SOAPHeaderElement.java
ias 2004/01/02 08:28:51
Modified: java/src/org/apache/axis/message SOAPHeaderElement.java
Log:
Fix for Bug 22981 - The SAAJ 1.2 Preliminary Upgrade
Thanks to Dr. Ahn, Heejune.
Note:
-This change passed all-tests.
Revision Changes Path
1.28 +1 -1 ws-axis/java/src/org/apache/axis/message/SOAPHeaderElement.java
Index: SOAPHeaderElement.java
===================================================================
RCS file: /home/cvs/ws-axis/java/src/org/apache/axis/message/SOAPHeaderElement.java,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -r1.27 -r1.28
--- SOAPHeaderElement.java 21 Oct 2003 02:00:59 -0000 1.27
+++ SOAPHeaderElement.java 2 Jan 2004 16:28:51 -0000 1.28
@@ -79,7 +79,7 @@
implements javax.xml.soap.SOAPHeaderElement {
protected boolean processed = false;
- protected String actor = null;
+ protected String actor = "http://schemas.xmlsoap.org/soap/actor/next";
protected boolean mustUnderstand = false;
protected boolean relay = false;
RE: cvs commit: ws-axis/java/src/org/apache/axis/messageSOAPHeaderElement.java
Posted by Ias <ia...@tmax.co.kr>.
> Hi Ias!
Hi Glen, happy new year!
>
> Thanks for checking in the SAAJ 1.2 changes.
I'm rather sorry for my delay :-)
> Quick question about this one.
> The default actor value for a missing actor attribute on a
> received header is the ultimate destination (in SOAP 1.2
> there is a specific URI for the ultimate destination, but in
> SOAP 1.1 there isn't). If we make the default "next",
> headers we create from scratch will be targeted at the next
> hop and not the ultimate destination. I can see this being
> OK, but it's definitely a major change - so a) do we want to
> make this change, and b) if so, we should be careful to
> document the difference prominently.
According to Dr. Ahn's explanation, the default value is based on
javax.xml.soap.SOAPHeaderElement API described at
http://java.sun.com/j2ee/1.4/docs/api/javax/xml/soap/SOAPHeaderElement.html#
setActor(java.lang.String) .
He also assured me that a test case in SAAJ 1.2 TCK (included in J2EE 1.4
CTS) checked it out. (that's why he implemented so.)
Thanks for your question,
Ias
>
> (I'm just catching up from being away for the holidays, btw.
> Happy New
> Year!)
>
> --Glen
>
> ----- Original Message -----
> From: <ia...@apache.org>
> To: <ws...@apache.org>
> Sent: Friday, January 02, 2004 11:28 AM
> Subject: cvs commit: ws-axis/java/src/org/apache/axis/message
> SOAPHeaderElement.java
>
>
> > ias 2004/01/02 08:28:51
> >
> > Modified: java/src/org/apache/axis/message
> SOAPHeaderElement.java
> > Log:
> > Fix for Bug 22981 - The SAAJ 1.2 Preliminary Upgrade
> >
> > Thanks to Dr. Ahn, Heejune.
> >
> > Note:
> > -This change passed all-tests.
> >
> > Revision Changes Path
> > 1.28 +1 -1
> ws-axis/java/src/org/apache/axis/message/SOAPHeaderElement.java
> >
> > Index: SOAPHeaderElement.java
> >
> ===================================================================
> > RCS file:
> /home/cvs/ws-axis/java/src/org/apache/axis/message/SOAPHeaderE
> lement.java,v
> > retrieving revision 1.27
> > retrieving revision 1.28
> > diff -u -r1.27 -r1.28
> > --- SOAPHeaderElement.java 21 Oct 2003 02:00:59 -0000 1.27
> > +++ SOAPHeaderElement.java 2 Jan 2004 16:28:51 -0000 1.28
> > @@ -79,7 +79,7 @@
> > implements javax.xml.soap.SOAPHeaderElement {
> > protected boolean processed = false;
> >
> > - protected String actor = null;
> > + protected String actor =
> "http://schemas.xmlsoap.org/soap/actor/next";
> > protected boolean mustUnderstand = false;
> > protected boolean relay = false;
> >
> >
> >
> >
> >
> >
>
Re: cvs commit: ws-axis/java/src/org/apache/axis/message
SOAPHeaderElement.java
Posted by Glen Daniels <gl...@thoughtcraft.com>.
Hi Ias!
Thanks for checking in the SAAJ 1.2 changes. Quick question about this one.
The default actor value for a missing actor attribute on a received header
is the ultimate destination (in SOAP 1.2 there is a specific URI for the
ultimate destination, but in SOAP 1.1 there isn't). If we make the default
"next", headers we create from scratch will be targeted at the next hop and
not the ultimate destination. I can see this being OK, but it's definitely
a major change - so a) do we want to make this change, and b) if so, we
should be careful to document the difference prominently.
(I'm just catching up from being away for the holidays, btw. Happy New
Year!)
--Glen
----- Original Message -----
From: <ia...@apache.org>
To: <ws...@apache.org>
Sent: Friday, January 02, 2004 11:28 AM
Subject: cvs commit: ws-axis/java/src/org/apache/axis/message
SOAPHeaderElement.java
> ias 2004/01/02 08:28:51
>
> Modified: java/src/org/apache/axis/message SOAPHeaderElement.java
> Log:
> Fix for Bug 22981 - The SAAJ 1.2 Preliminary Upgrade
>
> Thanks to Dr. Ahn, Heejune.
>
> Note:
> -This change passed all-tests.
>
> Revision Changes Path
> 1.28 +1 -1
ws-axis/java/src/org/apache/axis/message/SOAPHeaderElement.java
>
> Index: SOAPHeaderElement.java
> ===================================================================
> RCS file:
/home/cvs/ws-axis/java/src/org/apache/axis/message/SOAPHeaderElement.java,v
> retrieving revision 1.27
> retrieving revision 1.28
> diff -u -r1.27 -r1.28
> --- SOAPHeaderElement.java 21 Oct 2003 02:00:59 -0000 1.27
> +++ SOAPHeaderElement.java 2 Jan 2004 16:28:51 -0000 1.28
> @@ -79,7 +79,7 @@
> implements javax.xml.soap.SOAPHeaderElement {
> protected boolean processed = false;
>
> - protected String actor = null;
> + protected String actor =
"http://schemas.xmlsoap.org/soap/actor/next";
> protected boolean mustUnderstand = false;
> protected boolean relay = false;
>
>
>
>
>
>
JAXME reengineering in axis
Posted by Srinath Perera <he...@opensource.lk>.
Hi Dims, All;
Happy new year:)
This is basically to synchornize the palns for the jaxme code in axis.
As you may have notice I have not work on it for few weeks now.
Now most of the code refactoring is done and still left is basically to get
the all test runing. But I belive the refactoring must have broke some test
cases and we have to rewirte them.
I will try it and let dev list know where we stands.
I like to know about rough time frames for bring the jaxme-axis code to
surface.
Due to my final exams(Aprail - May) and JSR109 , I prfer to have it after
the May.
If we need it earlier let us try to arrange something.
thanks
Srinath
Re: cvs commit: ws-axis/java/src/org/apache/axis/message SOAPHeaderElement.java
Posted by Davanum Srinivas <di...@yahoo.com>.
Ias,
Awesome!!! and thanks.
-- dims
--- ias@apache.org wrote:
> ias 2004/01/02 08:28:51
>
> Modified: java/src/org/apache/axis/message SOAPHeaderElement.java
> Log:
> Fix for Bug 22981 - The SAAJ 1.2 Preliminary Upgrade
>
> Thanks to Dr. Ahn, Heejune.
>
> Note:
> -This change passed all-tests.
>
> Revision Changes Path
> 1.28 +1 -1 ws-axis/java/src/org/apache/axis/message/SOAPHeaderElement.java
>
> Index: SOAPHeaderElement.java
> ===================================================================
> RCS file: /home/cvs/ws-axis/java/src/org/apache/axis/message/SOAPHeaderElement.java,v
> retrieving revision 1.27
> retrieving revision 1.28
> diff -u -r1.27 -r1.28
> --- SOAPHeaderElement.java 21 Oct 2003 02:00:59 -0000 1.27
> +++ SOAPHeaderElement.java 2 Jan 2004 16:28:51 -0000 1.28
> @@ -79,7 +79,7 @@
> implements javax.xml.soap.SOAPHeaderElement {
> protected boolean processed = false;
>
> - protected String actor = null;
> + protected String actor = "http://schemas.xmlsoap.org/soap/actor/next";
> protected boolean mustUnderstand = false;
> protected boolean relay = false;
>
>
>
>
=====
Davanum Srinivas - http://webservices.apache.org/~dims/