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 "Wang, Hailong (NIH/CIT) [C]" <wa...@mail.nih.gov> on 2007/06/08 20:03:03 UTC
setOperationContext does not get a chance to run
Hi,
My setOperationContext function does not get a chance to run. Is there
anyone ever has same problem? Thanks.
Hailong Wang
National Database for Autism Research(NDAR)
NIH/CIT/DECA (MOM CONTRACTOR)
9000 Rockville Pike, Bld 12A/Room 2027
Bethesda, MD 20892
Phone: 301-402-3045
Fax: 301-480-0028
Email: wangh3@mail.nih.gov
URL: http://ndar.nih.gov
Re: [Axis2][Rampart]setOperationContext does not get a chance to run
Posted by Ruchith Fernando <ru...@gmail.com>.
IMHO it involves a bit of changes to WSS4J core. I'll try to get this
fixed in the next release :-)
Thanks,
Ruchith
On 6/12/07, Deepal Jayasinghe <de...@opensource.lk> wrote:
>
>
> Ruchith Fernando wrote:
> > The rampart inflow handlers are invoked way before the message
> > receiver. And the MessageContext.getCurrentContext() will only work
> > after the message receiver is invoked. Therefore calling
> > MessageContext.getCurrentContext() will not yield anything.
> >
> > Also at the moment we cannot access the message context from the
> > password callback handler.
> Is that possible for you to make MC available to password callback handler ?
>
> Thanks
> Deepal
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
www.ruchith.org
www.wso2.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2][Rampart]setOperationContext does not get a chance to
run
Posted by Deepal Jayasinghe <de...@opensource.lk>.
Ruchith Fernando wrote:
> The rampart inflow handlers are invoked way before the message
> receiver. And the MessageContext.getCurrentContext() will only work
> after the message receiver is invoked. Therefore calling
> MessageContext.getCurrentContext() will not yield anything.
>
> Also at the moment we cannot access the message context from the
> password callback handler.
Is that possible for you to make MC available to password callback handler ?
Thanks
Deepal
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2][Rampart]setOperationContext does not get a chance to run
Posted by Ruchith Fernando <ru...@gmail.com>.
The rampart inflow handlers are invoked way before the message
receiver. And the MessageContext.getCurrentContext() will only work
after the message receiver is invoked. Therefore calling
MessageContext.getCurrentContext() will not yield anything.
Also at the moment we cannot access the message context from the
password callback handler.
Thanks,
Ruchith
On 6/12/07, Chad DeBauch <cd...@gmail.com> wrote:
> Deepal...that is what I don't understand. The MessageContext is not passed
> to the PasswordCallback. Here is an example PasswordCallback:
>
> import java.io.IOException;
> import javax.security.auth.callback.Callback;
> import javax.security.auth.callback.CallbackHandler;
> import
> javax.security.auth.callback.UnsupportedCallbackException;
> import org.apache.ws.security.WSPasswordCallback;
>
> public class PWCallback implements CallbackHandler {
> public void handle(Callback[] callbacks) throws IOException,
> UnsupportedCallbackException {
> for (int i = 0; i < callbacks.length; i++) {
> if (callbacks[i] instanceof WSPasswordCallback) {
> WSPasswordCallback pc =
> (WSPasswordCallback)callbacks[i];
> // set the password given a username
> if ("wss4j".equals(pc.getIdentifer())) {
> pc.setPassword("security");
> }
> } else {
> throw new UnsupportedCallbackException(callbacks[i],
> "Unrecognized Callback");
> }
> }
> }
> }
>
> In Axis1 I could call MessageContext.getCurrentContext();
> and get the MessageContext within the PasswordCallback class. But in Axis2
> if I call MessageContext.getCurrentMessageContext(); it
> returns null. Any ideas?
>
> Thanks
> Chad
>
>
> On 6/11/07, Deepal Jayasinghe <de...@opensource.lk> wrote:
> > Hi Chad ,
> > What I told was , Message context is available to security handler , and
> > security handler is the one who call PasswordCallback , so that handler
> > should pass the MC to the PasswordCallback.
> >
> > Thanks
> > Deepal
> > > Thanks Deepal for your response. If I understand you correctly it is
> > > possible to get the MessageContext from within the PasswordCallback.
> > > Can you give an example?
> > >
> > > Thanks
> > > Chad
> > >
> > > On 6/11/07, *Deepal Jayasinghe* <deepal@opensource.lk
> > > <ma...@opensource.lk>> wrote:
> > >
> > > Hi Chad ,
> > > > With Axis1 this was possible by calling
> > > > MessageContext.getCurrentContext(); This doesn't
> appear to be
> > > > possible in Axis2, is that right?
> > > It does , but only for the service impl class, not for others.
> > > Since all
> > > the handlers have access to message context directly.
> > >
> > > Thanks
> > > Deepal
> > >
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> axis-user-unsubscribe@ws.apache.org
> > > <mailto: axis-user-unsubscribe@ws.apache.org>
> > > For additional commands, e-mail: axis-user-help@ws.apache.org
> > > <ma...@ws.apache.org>
> > >
> > >
> >
> > --
> > Thanks,
> > Deepal
> >
> ................................................................
> > "The highest tower is built one brick at a time"
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >
>
>
--
www.ruchith.org
www.wso2.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis2][Rampart]setOperationContext does not get a chance to run
Posted by Chad DeBauch <cd...@gmail.com>.
Deepal...that is what I don't understand. The MessageContext is not passed
to the PasswordCallback. Here is an example PasswordCallback:
import java.io.IOException;
import javax.security.auth.callback.Callback;
import javax.security.auth.callback.CallbackHandler;
import javax.security.auth.callback.UnsupportedCallbackException;
import org.apache.ws.security.WSPasswordCallback;
public class PWCallback implements CallbackHandler {
public void handle(Callback[] callbacks) throws IOException,
UnsupportedCallbackException {
for (int i = 0; i < callbacks.length; i++) {
if (callbacks[i] instanceof WSPasswordCallback) {
WSPasswordCallback pc = (WSPasswordCallback)callbacks[i];
// set the password given a username
if ("wss4j".equals(pc.getIdentifer())) {
pc.setPassword("security");
}
} else {
throw new UnsupportedCallbackException(callbacks[i],
"Unrecognized Callback");
}
}
}
}
In Axis1 I could call MessageContext.getCurrentContext(); and get the
MessageContext within the PasswordCallback class. But in Axis2 if I call
MessageContext.getCurrentMessageContext(); it returns null. Any ideas?
Thanks
Chad
On 6/11/07, Deepal Jayasinghe <de...@opensource.lk> wrote:
>
> Hi Chad ,
> What I told was , Message context is available to security handler , and
> security handler is the one who call PasswordCallback , so that handler
> should pass the MC to the PasswordCallback.
>
> Thanks
> Deepal
> > Thanks Deepal for your response. If I understand you correctly it is
> > possible to get the MessageContext from within the PasswordCallback.
> > Can you give an example?
> >
> > Thanks
> > Chad
> >
> > On 6/11/07, *Deepal Jayasinghe* <deepal@opensource.lk
> > <ma...@opensource.lk>> wrote:
> >
> > Hi Chad ,
> > > With Axis1 this was possible by calling
> > > MessageContext.getCurrentContext(); This doesn't appear to be
> > > possible in Axis2, is that right?
> > It does , but only for the service impl class, not for others.
> > Since all
> > the handlers have access to message context directly.
> >
> > Thanks
> > Deepal
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > <ma...@ws.apache.org>
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> > <ma...@ws.apache.org>
> >
> >
>
> --
> Thanks,
> Deepal
> ................................................................
> "The highest tower is built one brick at a time"
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
[Axis2][Rampart]setOperationContext does not get a chance to run
Posted by Deepal Jayasinghe <de...@opensource.lk>.
Hi Chad ,
What I told was , Message context is available to security handler , and
security handler is the one who call PasswordCallback , so that handler
should pass the MC to the PasswordCallback.
Thanks
Deepal
> Thanks Deepal for your response. If I understand you correctly it is
> possible to get the MessageContext from within the PasswordCallback.
> Can you give an example?
>
> Thanks
> Chad
>
> On 6/11/07, *Deepal Jayasinghe* <deepal@opensource.lk
> <ma...@opensource.lk>> wrote:
>
> Hi Chad ,
> > With Axis1 this was possible by calling
> > MessageContext.getCurrentContext(); This doesn't appear to be
> > possible in Axis2, is that right?
> It does , but only for the service impl class, not for others.
> Since all
> the handlers have access to message context directly.
>
> Thanks
> Deepal
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: axis-user-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
--
Thanks,
Deepal
................................................................
"The highest tower is built one brick at a time"
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: setOperationContext does not get a chance to run
Posted by Chad DeBauch <cd...@gmail.com>.
Thanks Deepal for your response. If I understand you correctly it is
possible to get the MessageContext from within the PasswordCallback. Can
you give an example?
Thanks
Chad
On 6/11/07, Deepal Jayasinghe <de...@opensource.lk> wrote:
>
> Hi Chad ,
> > With Axis1 this was possible by calling
> > MessageContext.getCurrentContext(); This doesn't appear to be
> > possible in Axis2, is that right?
> It does , but only for the service impl class, not for others. Since all
> the handlers have access to message context directly.
>
> Thanks
> Deepal
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
Re: setOperationContext does not get a chance to run
Posted by Deepal Jayasinghe <de...@opensource.lk>.
Hi Chad ,
> With Axis1 this was possible by calling
> MessageContext.getCurrentContext(); This doesn't appear to be
> possible in Axis2, is that right?
It does , but only for the service impl class, not for others. Since all
the handlers have access to message context directly.
Thanks
Deepal
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: setOperationContext does not get a chance to run
Posted by Chad DeBauch <cd...@gmail.com>.
With Axis1 this was possible by calling MessageContext.getCurrentContext();
This doesn't appear to be possible in Axis2, is that right?
Chad
On 6/11/07, Chad DeBauch <cd...@gmail.com> wrote:
>
> I also have the need to get access to the MessageContext within the
> PasswordCallback class. Any ideas on how to do this would be appreciated.
>
> Thanks,
> Chad
>
> On 6/11/07, Deepal Jayasinghe <de...@opensource.lk> wrote:
> >
> > Hi Ruchith
> >
> > I think you need to help in this situation since it has something to do
> > with security.
> >
> > Thanks
> > Deepal
> >
> > Wang, Hailong (NIH/CIT) [C] wrote:
> > > I actually want to access MessageContext in PasswordCallback function.
> >
> > > Can I do that? If yes, could you tell me how. Thanks.
> > >
> > >
> > > Hailong
> > >
> > > -----Original Message-----
> > > From: Deepal Jayasinghe [mailto:deepal@opensource.lk ]
> > > Sent: Sunday, June 10, 2007 12:37 AM
> > > To: axis-user@ws.apache.org
> > > Subject: Re: setOperationContext does not get a chance to run
> > >
> > > Hi Wang,
> > > setOperationContext method had threading issue so we removed that and
> > > introduced new way of accessing the context inside the service impl
> > > class. You can get the current message context and from that you can
> > get
> > > any context you want.
> > >
> > > public int add(int a , int b){
> > > MessageContext msgCtx = MessageContext.getCurrentMessageContext();
> > > .....
> > > }
> > >
> > >> Hi,
> > >>
> > >>
> > >>
> > >> My setOperationContext function does not get a chance to run. Is
> > there
> > >> anyone ever has same problem? Thanks.
> > >>
> > >>
> > >>
> > >> **Hailong Wang**
> > >>
> > >> National Database for Autism Research(NDAR)
> > >>
> > >> NIH/CIT/DECA (MOM CONTRACTOR)
> > >>
> > >> 9000 Rockville Pike, Bld 12A/Room 2027
> > >>
> > >> Bethesda, MD 20892
> > >>
> > >> Phone: 301-402-3045
> > >>
> > >> Fax: 301-480-0028
> > >>
> > >> Email: wangh3@mail.nih.gov <mailto: wangh3@mail.nih.gov>
> > >>
> > >> URL: http://ndar.nih.gov
> > >>
> > >>
> > >>
> > >>
> > >
> > >
> >
> > --
> > Thanks,
> > Deepal
> > ................................................................
> > "The highest tower is built one brick at a time"
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >
>
Re: setOperationContext does not get a chance to run
Posted by Deepal Jayasinghe <de...@opensource.lk>.
Hi Chad ,
As I know PasswordCallback class is called inside the DoAllreciver
handler in the security module and that handler has access to the
message context , so it should do is provide a way to access the
MessageContext inside the PasswordCallback.
Thanks
Deepal
> I also have the need to get access to the MessageContext within the
> PasswordCallback class. Any ideas on how to do this would be appreciated.
>
> Thanks,
> Chad
>
> On 6/11/07, * Deepal Jayasinghe* <deepal@opensource.lk
> <ma...@opensource.lk>> wrote:
>
> Hi Ruchith
>
> I think you need to help in this situation since it has something
> to do
> with security.
>
> Thanks
> Deepal
>
> Wang, Hailong (NIH/CIT) [C] wrote:
> > I actually want to access MessageContext in PasswordCallback
> function.
> > Can I do that? If yes, could you tell me how. Thanks.
> >
> >
> > Hailong
> >
> > -----Original Message-----
> > From: Deepal Jayasinghe [mailto:deepal@opensource.lk
> <ma...@opensource.lk>]
> > Sent: Sunday, June 10, 2007 12:37 AM
> > To: axis-user@ws.apache.org <ma...@ws.apache.org>
> > Subject: Re: setOperationContext does not get a chance to run
> >
> > Hi Wang,
> > setOperationContext method had threading issue so we removed
> that and
> > introduced new way of accessing the context inside the service impl
> > class. You can get the current message context and from that you
> can get
> > any context you want.
> >
> > public int add(int a , int b){
> > MessageContext msgCtx =
> MessageContext.getCurrentMessageContext();
> > .....
> > }
> >
> >> Hi,
> >>
> >>
> >>
> >> My setOperationContext function does not get a chance to run.
> Is there
> >> anyone ever has same problem? Thanks.
> >>
> >>
> >>
> >> **Hailong Wang**
> >>
> >> National Database for Autism Research(NDAR)
> >>
> >> NIH/CIT/DECA (MOM CONTRACTOR)
> >>
> >> 9000 Rockville Pike, Bld 12A/Room 2027
> >>
> >> Bethesda, MD 20892
> >>
> >> Phone: 301-402-3045
> >>
> >> Fax: 301-480-0028
> >>
> >> Email: wangh3@mail.nih.gov <ma...@mail.nih.gov>
> <mailto: wangh3@mail.nih.gov <ma...@mail.nih.gov>>
> >>
> >> URL: http://ndar.nih.gov
> >>
> >>
> >>
> >>
> >
> >
>
> --
> Thanks,
> Deepal
> ................................................................
> "The highest tower is built one brick at a time"
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: axis-user-help@ws.apache.org
> <ma...@ws.apache.org>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: setOperationContext does not get a chance to run
Posted by Chad DeBauch <cd...@gmail.com>.
I also have the need to get access to the MessageContext within the
PasswordCallback class. Any ideas on how to do this would be appreciated.
Thanks,
Chad
On 6/11/07, Deepal Jayasinghe <de...@opensource.lk> wrote:
>
> Hi Ruchith
>
> I think you need to help in this situation since it has something to do
> with security.
>
> Thanks
> Deepal
>
> Wang, Hailong (NIH/CIT) [C] wrote:
> > I actually want to access MessageContext in PasswordCallback function.
> > Can I do that? If yes, could you tell me how. Thanks.
> >
> >
> > Hailong
> >
> > -----Original Message-----
> > From: Deepal Jayasinghe [mailto:deepal@opensource.lk]
> > Sent: Sunday, June 10, 2007 12:37 AM
> > To: axis-user@ws.apache.org
> > Subject: Re: setOperationContext does not get a chance to run
> >
> > Hi Wang,
> > setOperationContext method had threading issue so we removed that and
> > introduced new way of accessing the context inside the service impl
> > class. You can get the current message context and from that you can get
> > any context you want.
> >
> > public int add(int a , int b){
> > MessageContext msgCtx = MessageContext.getCurrentMessageContext();
> > .....
> > }
> >
> >> Hi,
> >>
> >>
> >>
> >> My setOperationContext function does not get a chance to run. Is there
> >> anyone ever has same problem? Thanks.
> >>
> >>
> >>
> >> **Hailong Wang**
> >>
> >> National Database for Autism Research(NDAR)
> >>
> >> NIH/CIT/DECA (MOM CONTRACTOR)
> >>
> >> 9000 Rockville Pike, Bld 12A/Room 2027
> >>
> >> Bethesda, MD 20892
> >>
> >> Phone: 301-402-3045
> >>
> >> Fax: 301-480-0028
> >>
> >> Email: wangh3@mail.nih.gov <ma...@mail.nih.gov>
> >>
> >> URL: http://ndar.nih.gov
> >>
> >>
> >>
> >>
> >
> >
>
> --
> Thanks,
> Deepal
> ................................................................
> "The highest tower is built one brick at a time"
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
Re: setOperationContext does not get a chance to run
Posted by Deepal Jayasinghe <de...@opensource.lk>.
Hi Ruchith
I think you need to help in this situation since it has something to do
with security.
Thanks
Deepal
Wang, Hailong (NIH/CIT) [C] wrote:
> I actually want to access MessageContext in PasswordCallback function.
> Can I do that? If yes, could you tell me how. Thanks.
>
>
> Hailong
>
> -----Original Message-----
> From: Deepal Jayasinghe [mailto:deepal@opensource.lk]
> Sent: Sunday, June 10, 2007 12:37 AM
> To: axis-user@ws.apache.org
> Subject: Re: setOperationContext does not get a chance to run
>
> Hi Wang,
> setOperationContext method had threading issue so we removed that and
> introduced new way of accessing the context inside the service impl
> class. You can get the current message context and from that you can get
> any context you want.
>
> public int add(int a , int b){
> MessageContext msgCtx = MessageContext.getCurrentMessageContext();
> .....
> }
>
>> Hi,
>>
>>
>>
>> My setOperationContext function does not get a chance to run. Is there
>> anyone ever has same problem? Thanks.
>>
>>
>>
>> **Hailong Wang**
>>
>> National Database for Autism Research(NDAR)
>>
>> NIH/CIT/DECA (MOM CONTRACTOR)
>>
>> 9000 Rockville Pike, Bld 12A/Room 2027
>>
>> Bethesda, MD 20892
>>
>> Phone: 301-402-3045
>>
>> Fax: 301-480-0028
>>
>> Email: wangh3@mail.nih.gov <ma...@mail.nih.gov>
>>
>> URL: http://ndar.nih.gov
>>
>>
>>
>>
>
>
--
Thanks,
Deepal
................................................................
"The highest tower is built one brick at a time"
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: setOperationContext does not get a chance to run
Posted by "Wang, Hailong (NIH/CIT) [C]" <wa...@mail.nih.gov>.
I actually want to access MessageContext in PasswordCallback function.
Can I do that? If yes, could you tell me how. Thanks.
Hailong
-----Original Message-----
From: Deepal Jayasinghe [mailto:deepal@opensource.lk]
Sent: Sunday, June 10, 2007 12:37 AM
To: axis-user@ws.apache.org
Subject: Re: setOperationContext does not get a chance to run
Hi Wang,
setOperationContext method had threading issue so we removed that and
introduced new way of accessing the context inside the service impl
class. You can get the current message context and from that you can get
any context you want.
public int add(int a , int b){
MessageContext msgCtx = MessageContext.getCurrentMessageContext();
.....
}
>
> Hi,
>
>
>
> My setOperationContext function does not get a chance to run. Is there
> anyone ever has same problem? Thanks.
>
>
>
> **Hailong Wang**
>
> National Database for Autism Research(NDAR)
>
> NIH/CIT/DECA (MOM CONTRACTOR)
>
> 9000 Rockville Pike, Bld 12A/Room 2027
>
> Bethesda, MD 20892
>
> Phone: 301-402-3045
>
> Fax: 301-480-0028
>
> Email: wangh3@mail.nih.gov <ma...@mail.nih.gov>
>
> URL: http://ndar.nih.gov
>
>
>
--
Thanks,
Deepal
................................................................
"The highest tower is built one brick at a time"
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: setOperationContext does not get a chance to run
Posted by Deepal Jayasinghe <de...@opensource.lk>.
Hi Wang,
setOperationContext method had threading issue so we removed that and
introduced new way of accessing the context inside the service impl
class. You can get the current message context and from that you can get
any context you want.
public int add(int a , int b){
MessageContext msgCtx = MessageContext.getCurrentMessageContext();
.....
}
>
> Hi,
>
>
>
> My setOperationContext function does not get a chance to run. Is there
> anyone ever has same problem? Thanks.
>
>
>
> **Hailong Wang**
>
> National Database for Autism Research(NDAR)
>
> NIH/CIT/DECA (MOM CONTRACTOR)
>
> 9000 Rockville Pike, Bld 12A/Room 2027
>
> Bethesda, MD 20892
>
> Phone: 301-402-3045
>
> Fax: 301-480-0028
>
> Email: wangh3@mail.nih.gov <ma...@mail.nih.gov>
>
> URL: http://ndar.nih.gov
>
>
>
--
Thanks,
Deepal
................................................................
"The highest tower is built one brick at a time"
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org