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 Srinath Perera <he...@gmail.com> on 2005/04/26 05:02:47 UTC
[Axis2]Article on E4X
FYI- to whoever might write the E4X provider for Axis2 ;)
http://www-128.ibm.com/developerworks/webservices/library/ws-ajax1/index.html
Re: [Axis2]Article on E4X
Posted by Srinath Perera <he...@gmail.com>.
Thanks Anthony :)
Srinath
On 4/27/05, Anthony Elder <an...@uk.ibm.com> wrote:
>
>
> I've already written an E4X provider for AXIS2 for a subsequent article in
> this dW series. I'll see if I can post the code here before the article
> comes out.
>
> ...ant
>
> Anthony Elder
> ant.elder@uk.ibm.com
> Web Services + ESB Development
> IBM UK Laboratories, Hursley Park
> (+44) 01962 818320, x248320, MP208.
>
> "Eran Chinthaka" <ch...@opensource.lk> on 27/04/2005 04:19:45
>
> Please respond to axis-dev@ws.apache.org
>
> To: <ax...@ws.apache.org>
> cc:
> Subject: RE: [Axis2]Article on E4X
>
>
> I did some work on this, before the summit.
>
> We have to write a MessageReceiver for e4x support. This MessageReceiver
> can
> use Rhino within that. And then we can deploy a javascript service (with
> of
> course with a service.xml file, pointing to E4X message receiver and giving
> the operation names).
>
> I think that's what is required to do. I wrote a HelloWorld with E4X, but
> didn't write the MessageReceiver.
>
> Venkat, if we can provide this, that will be great, and will be a good
> marketing thing as well ;).
>
> Regards,
> Eran Chinthaka
>
> > -----Original Message-----
> > From: Sanjiva Weerawarana [mailto:sanjiva@opensource.lk]
> > Sent: Tuesday, April 26, 2005 9:44 PM
> > To: axis-dev@ws.apache.org
> > Subject: Re: [Axis2]Article on E4X
> >
> > Venkat Reddy wrote:
> >
> > >I did some heavy weight implementations using javascript before, which
> > >already used asynchrounous XML communications, Javascript based MVC
> > >model using IFrames as views etc all within IE browser. But the native
> > >supprt for XML is cool. If there is any work needed for Axis in this
> > >area, leave it for me :-)
> > >
> > >Venkat
> > >
> > >
> > Excellent! There's some folks in Sri Lanka look into plugging it in as a
> > language for implementing services and to tie Axis2 into it as the
> > API for invoking services. Glad to get your help to get those done right!
> >
> > Sanjiva.
> >
> >
>
>
Re: [Axis2]Article on E4X
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Anthony Elder wrote:
>Axis 2 looks good, quick to pick up. All the doc definitely helped and
>seemed quite comprehensive for an m1 release - I think its important that
>its kept up to step as the code develops.
>
Great!
> The only issue I can think of was
>I needed somewhere to stash away the Rhino compiled script object so the
>compile only happens on the first request to a service. I ended up adding
>it with a unique key to the map of operations on the AxisService which
>isn't very nice. Maybe the AxisService should have a bag of general
>properties. (I used the M1 release)
>
>
Ah we solved this at the 2nd f2f. There's going to be a very clean
hierarchy of
contexts scoped at the different levels of the lifecycle. This will give
you a perfect
solution for this problem.
>I do agree with some of Glen's comments on the spelling in the code, but I
>can't see how that will get fixed unless native speakers like me start
>posting corrections to this list.
>
>
I agree 100% the code and comments should be in good (Queen's? :-))
English. I
too will soon be getting into the code and will fix minor stuff as I see
it. Your
contributions would be most welcome!
I didn't reply to Glen's note because I felt it was going too farand so
wanted to write
a more detailed reply .. which means I never got to it :-(. While I
would like the Sri
Lankan guys to write in perfect English, I'd rather have them having verbal
diarrorhea (sp?) on the mailing list than not writing because of
worrying about
the English. The more you write the better you get right?
The same for the docs; let's write something down and keep improving them,
rather than clamming up and not writing.
Sanjiva.
Re: [Axis2]Article on E4X
Posted by Ajith Ranabahu <aj...@gmail.com>.
Hi,
I guess for Ants specific requirement, service context is the best option
IMHO.
However he can also choose to directly store the thing in the storage
mechanism we have provided. (engine.put(), engine.get() methods that
actually calls an underlying storage)
On 4/28/05, Chathura Herath <ch...@opensource.lk> wrote:
>
> > -----Original Message-----
> > From: Sanjiva Weerawarana [mailto:sanjiva@opensource.lk]
> > Sent: Thursday, April 28, 2005 10:21 AM
> > To: axis-dev@ws.apache.org
> > Subject: Re: [Axis2]Article on E4X
> >
> > Chathura Herath wrote:
> >
> > >Hi Anthony,
> > >
> > >FYI there is a general bag of properties in both AxisService and
> > >AxisOperation inherited from the org.apache.wsdl.ComponentImpl
> > >
> > > public void setComponentProperty(Object key, Object obj);
> > > public Object getComponentProperty(Object key);
> > >
> > >Think this might serve your purpose??
> > >
> > >
> > This isn't enough .. these are not instanced per service "session";
> which
> > I
> > believe is what Ant wants.
>
> Depends on the how the hooked in property should be treated, whether to
> treat it as a "runtime service wide thing"(Context) or a "deployment time
> configuration".
> You are right about this because it's not graceful to let a provider
> change
> (add stuff into) the configuration of the service. Rather the provider can
> add stuff into the context of the service.
>
> > He really wants what we called SessionContext
> > in the F2F discussions.
>
> Shouldn't it be the ServiceContext??? (Quote Antony: I needed somewhere to
> stash away the Rhino compiled script object so the compile only happens on
> the first request to a service.)
>
> Regards,
> Chathura
>
>
--
Ajith Ranabahu
RE: [Axis2]Article on E4X
Posted by Chathura Herath <ch...@opensource.lk>.
> -----Original Message-----
> From: Sanjiva Weerawarana [mailto:sanjiva@opensource.lk]
> Sent: Thursday, April 28, 2005 10:21 AM
> To: axis-dev@ws.apache.org
> Subject: Re: [Axis2]Article on E4X
>
> Chathura Herath wrote:
>
> >Hi Anthony,
> >
> >FYI there is a general bag of properties in both AxisService and
> >AxisOperation inherited from the org.apache.wsdl.ComponentImpl
> >
> > public void setComponentProperty(Object key, Object obj);
> > public Object getComponentProperty(Object key);
> >
> >Think this might serve your purpose??
> >
> >
> This isn't enough .. these are not instanced per service "session"; which
> I
> believe is what Ant wants.
Depends on the how the hooked in property should be treated, whether to
treat it as a "runtime service wide thing"(Context) or a "deployment time
configuration".
You are right about this because it's not graceful to let a provider change
(add stuff into) the configuration of the service. Rather the provider can
add stuff into the context of the service.
> He really wants what we called SessionContext
> in the F2F discussions.
Shouldn't it be the ServiceContext??? (Quote Antony: I needed somewhere to
stash away the Rhino compiled script object so the compile only happens on
the first request to a service.)
Regards,
Chathura
Re: [Axis2]Article on E4X
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Chathura Herath wrote:
>Hi Anthony,
>
>FYI there is a general bag of properties in both AxisService and
>AxisOperation inherited from the org.apache.wsdl.ComponentImpl
>
> public void setComponentProperty(Object key, Object obj);
> public Object getComponentProperty(Object key);
>
>Think this might serve your purpose??
>
>
This isn't enough .. these are not instanced per service "session"; which I
believe is what Ant wants. He really wants what we called SessionContext
in the F2F discussions.
Sanjiva.
RE: [Axis2]Article on E4X
Posted by Chathura Herath <ch...@opensource.lk>.
Hi Anthony,
FYI there is a general bag of properties in both AxisService and
AxisOperation inherited from the org.apache.wsdl.ComponentImpl
public void setComponentProperty(Object key, Object obj);
public Object getComponentProperty(Object key);
Think this might serve your purpose??
Thanks
Chathura
> -----Original Message-----
> From: Anthony Elder [mailto:ant.elder@uk.ibm.com]
> Sent: Wednesday, April 27, 2005 6:01 PM
> To: axis-dev@ws.apache.org
> Subject: Re: [Axis2]Article on E4X
>
>
>
>
>
> Axis 2 looks good, quick to pick up. All the doc definitely helped and
> seemed quite comprehensive for an m1 release - I think its important that
> its kept up to step as the code develops. The only issue I can think of
> was
> I needed somewhere to stash away the Rhino compiled script object so the
> compile only happens on the first request to a service. I ended up adding
> it with a unique key to the map of operations on the AxisService which
> isn't very nice. Maybe the AxisService should have a bag of general
> properties. (I used the M1 release)
>
> I do agree with some of Glen's comments on the spelling in the code, but I
> can't see how that will get fixed unless native speakers like me start
> posting corrections to this list.
>
> ...ant
>
> Anthony Elder
> ant.elder@uk.ibm.com
> Web Services + ESB Development
> IBM UK Laboratories, Hursley Park
> (+44) 01962 818320, x248320, MP208.
>
>
> Sanjiva Weerawarana <sa...@opensource.lk> on 27/04/2005 10:35:47
>
> Please respond to axis-dev@ws.apache.org
>
> To: axis-dev@ws.apache.org
> cc:
> Subject: Re: [Axis2]Article on E4X
>
>
> Anthony Elder wrote:
>
> >
> >
> >I've already written an E4X provider for AXIS2 for a subsequent article
> in
> >this dW series. I'll see if I can post the code here before the article
> >comes out.
> >
> Excellent. Can you comment on your experience in writing a provider for
> Axis1
> vs. Axis2? Any other comments that you think may help improve Axis2 would
> be very welcome.
>
> Thanks,
>
> Sanjiva.
>
>
>
Re: [Axis2]Article on E4X
Posted by Anthony Elder <an...@uk.ibm.com>.
Axis 2 looks good, quick to pick up. All the doc definitely helped and
seemed quite comprehensive for an m1 release - I think its important that
its kept up to step as the code develops. The only issue I can think of was
I needed somewhere to stash away the Rhino compiled script object so the
compile only happens on the first request to a service. I ended up adding
it with a unique key to the map of operations on the AxisService which
isn't very nice. Maybe the AxisService should have a bag of general
properties. (I used the M1 release)
I do agree with some of Glen's comments on the spelling in the code, but I
can't see how that will get fixed unless native speakers like me start
posting corrections to this list.
...ant
Anthony Elder
ant.elder@uk.ibm.com
Web Services + ESB Development
IBM UK Laboratories, Hursley Park
(+44) 01962 818320, x248320, MP208.
Sanjiva Weerawarana <sa...@opensource.lk> on 27/04/2005 10:35:47
Please respond to axis-dev@ws.apache.org
To: axis-dev@ws.apache.org
cc:
Subject: Re: [Axis2]Article on E4X
Anthony Elder wrote:
>
>
>I've already written an E4X provider for AXIS2 for a subsequent article in
>this dW series. I'll see if I can post the code here before the article
>comes out.
>
Excellent. Can you comment on your experience in writing a provider for
Axis1
vs. Axis2? Any other comments that you think may help improve Axis2 would
be very welcome.
Thanks,
Sanjiva.
Re: [Axis2]Article on E4X
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Anthony Elder wrote:
>
>
>I've already written an E4X provider for AXIS2 for a subsequent article in
>this dW series. I'll see if I can post the code here before the article
>comes out.
>
Excellent. Can you comment on your experience in writing a provider for
Axis1
vs. Axis2? Any other comments that you think may help improve Axis2 would
be very welcome.
Thanks,
Sanjiva.
RE: [Axis2]Article on E4X
Posted by Anthony Elder <an...@uk.ibm.com>.
I've already written an E4X provider for AXIS2 for a subsequent article in
this dW series. I'll see if I can post the code here before the article
comes out.
...ant
Anthony Elder
ant.elder@uk.ibm.com
Web Services + ESB Development
IBM UK Laboratories, Hursley Park
(+44) 01962 818320, x248320, MP208.
"Eran Chinthaka" <ch...@opensource.lk> on 27/04/2005 04:19:45
Please respond to axis-dev@ws.apache.org
To: <ax...@ws.apache.org>
cc:
Subject: RE: [Axis2]Article on E4X
I did some work on this, before the summit.
We have to write a MessageReceiver for e4x support. This MessageReceiver
can
use Rhino within that. And then we can deploy a javascript service (with
of
course with a service.xml file, pointing to E4X message receiver and giving
the operation names).
I think that's what is required to do. I wrote a HelloWorld with E4X, but
didn't write the MessageReceiver.
Venkat, if we can provide this, that will be great, and will be a good
marketing thing as well ;).
Regards,
Eran Chinthaka
> -----Original Message-----
> From: Sanjiva Weerawarana [mailto:sanjiva@opensource.lk]
> Sent: Tuesday, April 26, 2005 9:44 PM
> To: axis-dev@ws.apache.org
> Subject: Re: [Axis2]Article on E4X
>
> Venkat Reddy wrote:
>
> >I did some heavy weight implementations using javascript before, which
> >already used asynchrounous XML communications, Javascript based MVC
> >model using IFrames as views etc all within IE browser. But the native
> >supprt for XML is cool. If there is any work needed for Axis in this
> >area, leave it for me :-)
> >
> >Venkat
> >
> >
> Excellent! There's some folks in Sri Lanka look into plugging it in as a
> language for implementing services and to tie Axis2 into it as the
> API for invoking services. Glad to get your help to get those done right!
>
> Sanjiva.
>
>
RE: [Axis2]Article on E4X
Posted by Eran Chinthaka <ch...@opensource.lk>.
I did some work on this, before the summit.
We have to write a MessageReceiver for e4x support. This MessageReceiver can
use Rhino within that. And then we can deploy a javascript service (with of
course with a service.xml file, pointing to E4X message receiver and giving
the operation names).
I think that's what is required to do. I wrote a HelloWorld with E4X, but
didn't write the MessageReceiver.
Venkat, if we can provide this, that will be great, and will be a good
marketing thing as well ;).
Regards,
Eran Chinthaka
> -----Original Message-----
> From: Sanjiva Weerawarana [mailto:sanjiva@opensource.lk]
> Sent: Tuesday, April 26, 2005 9:44 PM
> To: axis-dev@ws.apache.org
> Subject: Re: [Axis2]Article on E4X
>
> Venkat Reddy wrote:
>
> >I did some heavy weight implementations using javascript before, which
> >already used asynchrounous XML communications, Javascript based MVC
> >model using IFrames as views etc all within IE browser. But the native
> >supprt for XML is cool. If there is any work needed for Axis in this
> >area, leave it for me :-)
> >
> >Venkat
> >
> >
> Excellent! There's some folks in Sri Lanka look into plugging it in as a
> language for implementing services and to tie Axis2 into it as the
> API for invoking services. Glad to get your help to get those done right!
>
> Sanjiva.
>
>
Re: [Axis2]Article on E4X
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Venkat Reddy wrote:
>I did some heavy weight implementations using javascript before, which
>already used asynchrounous XML communications, Javascript based MVC
>model using IFrames as views etc all within IE browser. But the native
>supprt for XML is cool. If there is any work needed for Axis in this
>area, leave it for me :-)
>
>Venkat
>
>
Excellent! There's some folks in Sri Lanka look into plugging it in as a
language for implementing services and to tie Axis2 into it as the
API for invoking services. Glad to get your help to get those done right!
Sanjiva.
Re: [Axis2]Article on E4X
Posted by Venkat Reddy <vr...@gmail.com>.
I did some heavy weight implementations using javascript before, which
already used asynchrounous XML communications, Javascript based MVC
model using IFrames as views etc all within IE browser. But the native
supprt for XML is cool. If there is any work needed for Axis in this
area, leave it for me :-)
Venkat
On 4/26/05, Srinath Perera <he...@gmail.com> wrote:
> FYI- to whoever might write the E4X provider for Axis2 ;)
> http://www-128.ibm.com/developerworks/webservices/library/ws-ajax1/index.html
>