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 Aleksander Slominski <as...@cs.indiana.edu> on 2004/11/15 18:10:18 UTC
AXIOM and data binding [Re: [Axis2] AXIOM goals
Sanjiva Weerawarana wrote:
>"Aleksander Slominski" <as...@cs.indiana.edu> writes:
>
>
>>* AXIOM API is designed to support pluggable XML transformations
>>(JavaBeans2XML, XSD with JaxMe/JAXB, Castor, XmlBeans, RelaxNG, ...)
>>discussed in http://nagoya.apache.org/jira/browse/AXIS-1498
>>
>>
>
>I can't read AXIS-1498 right now (offline ATM) but data binding is NOT
>part of AXIOM.
>
what i mean by it is "designed to support" is that doing data binding
should be make easier by making AXIOM API works well with any data
binding framework.
>In fact data binding is layered into the engine so that
>all of Axis2 can run without any data binding and with the app accessing
>the OM directly (maybe via something like JXPath layered on).
>
>
yes so AXIOM API must be designed (or changed when needed) so to support
such access.
>The point is that providers which have Java object-ified views of
>the incoming XML blob is not the only way to implement a service. For
>example, the service may be one or more XSLT scripts.
>
>
yes - i think it would be very good for doc/literal kind of services and
AXIOM should make it easy and not hard to implement such service.
alek
--
The best way to predict the future is to invent it - Alan Kay
RE: AXIOM and data binding [Re: [Axis2] AXIOM goals
Posted by Glen Daniels <gl...@thoughtcraft.com>.
+1
> -----Original Message-----
> From: Davanum Srinivas [mailto:davanum@gmail.com]
> Sent: Tuesday, November 16, 2004 7:01 AM
> To: axis-dev@ws.apache.org
> Subject: Re: AXIOM and data binding [Re: [Axis2] AXIOM goals
>
> yes, please stay here.
>
>
> On Tue, 16 Nov 2004 17:11:03 +0600, Sanjiva Weerawarana
> <sa...@opensource.lk> wrote:
> > I think we should stay on axis-dev .. even folks who are
> not actively
> > participating are "lurking" because of that. Also, once
> Axis 1.2 ships
> > the focus can change quite a bit ..
> >
> > Sanjiva.
> >
> >
> >
> > ----- Original Message -----
> > From: "Aleksander Slominski" <as...@cs.indiana.edu>
> > To: <ax...@ws.apache.org>
> > Sent: Tuesday, November 16, 2004 8:06 AM
> > Subject: Re: AXIOM and data binding [Re: [Axis2] AXIOM goals
> >
> > > Sanjiva Weerawarana wrote:
> > >
> > > >Dude, prefix your messages with [Axis2] ;-).
> > > >
> > > >
> > > for my filter it is enough if axis2 is in subject as it
> is common that
> > > when you reply you get "Re: [Axis2] ..." so otherwise i
> would miss all
> > > replies ;-)
> > >
> > > anyway i think we may need a separate mailing list ...
> > >
> > > alek
> > >
> > > >----- Original Message -----
> > > >From: "Aleksander Slominski" <as...@cs.indiana.edu>
> > > >To: <ax...@ws.apache.org>
> > > >Sent: Monday, November 15, 2004 11:10 PM
> > > >Subject: AXIOM and data binding [Re: [Axis2] AXIOM goals
> > > >
> > > >
> > > >
> > > >
> > > >>Sanjiva Weerawarana wrote:
> > > >>
> > > >>
> > > >>
> > > >>>"Aleksander Slominski" <as...@cs.indiana.edu> writes:
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >>>>* AXIOM API is designed to support pluggable XML
> transformations
> > > >>>>(JavaBeans2XML, XSD with JaxMe/JAXB, Castor,
> XmlBeans, RelaxNG, ...)
> > > >>>>discussed in http://nagoya.apache.org/jira/browse/AXIS-1498
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>I can't read AXIS-1498 right now (offline ATM) but
> data binding is NOT
> > > >>>part of AXIOM.
> > > >>>
> > > >>>
> > > >>>
> > > >>what i mean by it is "designed to support" is that
> doing data binding
> > > >>should be make easier by making AXIOM API works well
> with any data
> > > >>binding framework.
> > > >>
> > > >>
> > > >>
> > > >>>In fact data binding is layered into the engine so that
> > > >>>all of Axis2 can run without any data binding and with the app
> > accessing
> > > >>>the OM directly (maybe via something like JXPath layered on).
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >>yes so AXIOM API must be designed (or changed when
> needed) so to support
> > > >>such access.
> > > >>
> > > >>
> > > >>
> > > >>>The point is that providers which have Java
> object-ified views of
> > > >>>the incoming XML blob is not the only way to implement
> a service. For
> > > >>>example, the service may be one or more XSLT scripts.
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >>yes - i think it would be very good for doc/literal
> kind of services and
> > > >>AXIOM should make it easy and not hard to implement
> such service.
> > > >>
> > > >>alek
> > > >>
> > > >>--
> > > >>The best way to predict the future is to invent it - Alan Kay
> > > >>
> > > >>
> > > >>
> > > >>
> > >
> > >
> > > --
> > > The best way to predict the future is to invent it - Alan Kay
> > >
> > >
> >
> >
>
>
> --
> Davanum Srinivas - http://webservices.apache.org/~dims/
>
>
Re: AXIOM and data binding [Re: [Axis2] AXIOM goals
Posted by Srinath Perera <he...@gmail.com>.
yap +1 I feel we should be in axis dev list , we need the lessons from
axis 1.x and want the people to remind if we missing them :)
Thanks
Srinath
On Tue, 16 Nov 2004 07:01:22 -0500, Davanum Srinivas <da...@gmail.com> wrote:
> yes, please stay here.
>
> On Tue, 16 Nov 2004 17:11:03 +0600, Sanjiva Weerawarana
>
>
> <sa...@opensource.lk> wrote:
> > I think we should stay on axis-dev .. even folks who are not actively
> > participating are "lurking" because of that. Also, once Axis 1.2 ships
> > the focus can change quite a bit ..
> >
> > Sanjiva.
> >
> >
> >
> > ----- Original Message -----
> > From: "Aleksander Slominski" <as...@cs.indiana.edu>
> > To: <ax...@ws.apache.org>
> > Sent: Tuesday, November 16, 2004 8:06 AM
> > Subject: Re: AXIOM and data binding [Re: [Axis2] AXIOM goals
> >
> > > Sanjiva Weerawarana wrote:
> > >
> > > >Dude, prefix your messages with [Axis2] ;-).
> > > >
> > > >
> > > for my filter it is enough if axis2 is in subject as it is common that
> > > when you reply you get "Re: [Axis2] ..." so otherwise i would miss all
> > > replies ;-)
> > >
> > > anyway i think we may need a separate mailing list ...
> > >
> > > alek
> > >
> > > >----- Original Message -----
> > > >From: "Aleksander Slominski" <as...@cs.indiana.edu>
> > > >To: <ax...@ws.apache.org>
> > > >Sent: Monday, November 15, 2004 11:10 PM
> > > >Subject: AXIOM and data binding [Re: [Axis2] AXIOM goals
> > > >
> > > >
> > > >
> > > >
> > > >>Sanjiva Weerawarana wrote:
> > > >>
> > > >>
> > > >>
> > > >>>"Aleksander Slominski" <as...@cs.indiana.edu> writes:
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >>>>* AXIOM API is designed to support pluggable XML transformations
> > > >>>>(JavaBeans2XML, XSD with JaxMe/JAXB, Castor, XmlBeans, RelaxNG, ...)
> > > >>>>discussed in http://nagoya.apache.org/jira/browse/AXIS-1498
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>I can't read AXIS-1498 right now (offline ATM) but data binding is NOT
> > > >>>part of AXIOM.
> > > >>>
> > > >>>
> > > >>>
> > > >>what i mean by it is "designed to support" is that doing data binding
> > > >>should be make easier by making AXIOM API works well with any data
> > > >>binding framework.
> > > >>
> > > >>
> > > >>
> > > >>>In fact data binding is layered into the engine so that
> > > >>>all of Axis2 can run without any data binding and with the app
> > accessing
> > > >>>the OM directly (maybe via something like JXPath layered on).
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >>yes so AXIOM API must be designed (or changed when needed) so to support
> > > >>such access.
> > > >>
> > > >>
> > > >>
> > > >>>The point is that providers which have Java object-ified views of
> > > >>>the incoming XML blob is not the only way to implement a service. For
> > > >>>example, the service may be one or more XSLT scripts.
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >>yes - i think it would be very good for doc/literal kind of services and
> > > >>AXIOM should make it easy and not hard to implement such service.
> > > >>
> > > >>alek
> > > >>
> > > >>--
> > > >>The best way to predict the future is to invent it - Alan Kay
> > > >>
> > > >>
> > > >>
> > > >>
> > >
> > >
> > > --
> > > The best way to predict the future is to invent it - Alan Kay
> > >
> > >
> >
> >
>
>
> --
> Davanum Srinivas - http://webservices.apache.org/~dims/
>
Re: AXIOM and data binding [Re: [Axis2] AXIOM goals
Posted by Davanum Srinivas <da...@gmail.com>.
yes, please stay here.
On Tue, 16 Nov 2004 17:11:03 +0600, Sanjiva Weerawarana
<sa...@opensource.lk> wrote:
> I think we should stay on axis-dev .. even folks who are not actively
> participating are "lurking" because of that. Also, once Axis 1.2 ships
> the focus can change quite a bit ..
>
> Sanjiva.
>
>
>
> ----- Original Message -----
> From: "Aleksander Slominski" <as...@cs.indiana.edu>
> To: <ax...@ws.apache.org>
> Sent: Tuesday, November 16, 2004 8:06 AM
> Subject: Re: AXIOM and data binding [Re: [Axis2] AXIOM goals
>
> > Sanjiva Weerawarana wrote:
> >
> > >Dude, prefix your messages with [Axis2] ;-).
> > >
> > >
> > for my filter it is enough if axis2 is in subject as it is common that
> > when you reply you get "Re: [Axis2] ..." so otherwise i would miss all
> > replies ;-)
> >
> > anyway i think we may need a separate mailing list ...
> >
> > alek
> >
> > >----- Original Message -----
> > >From: "Aleksander Slominski" <as...@cs.indiana.edu>
> > >To: <ax...@ws.apache.org>
> > >Sent: Monday, November 15, 2004 11:10 PM
> > >Subject: AXIOM and data binding [Re: [Axis2] AXIOM goals
> > >
> > >
> > >
> > >
> > >>Sanjiva Weerawarana wrote:
> > >>
> > >>
> > >>
> > >>>"Aleksander Slominski" <as...@cs.indiana.edu> writes:
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>>* AXIOM API is designed to support pluggable XML transformations
> > >>>>(JavaBeans2XML, XSD with JaxMe/JAXB, Castor, XmlBeans, RelaxNG, ...)
> > >>>>discussed in http://nagoya.apache.org/jira/browse/AXIS-1498
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>I can't read AXIS-1498 right now (offline ATM) but data binding is NOT
> > >>>part of AXIOM.
> > >>>
> > >>>
> > >>>
> > >>what i mean by it is "designed to support" is that doing data binding
> > >>should be make easier by making AXIOM API works well with any data
> > >>binding framework.
> > >>
> > >>
> > >>
> > >>>In fact data binding is layered into the engine so that
> > >>>all of Axis2 can run without any data binding and with the app
> accessing
> > >>>the OM directly (maybe via something like JXPath layered on).
> > >>>
> > >>>
> > >>>
> > >>>
> > >>yes so AXIOM API must be designed (or changed when needed) so to support
> > >>such access.
> > >>
> > >>
> > >>
> > >>>The point is that providers which have Java object-ified views of
> > >>>the incoming XML blob is not the only way to implement a service. For
> > >>>example, the service may be one or more XSLT scripts.
> > >>>
> > >>>
> > >>>
> > >>>
> > >>yes - i think it would be very good for doc/literal kind of services and
> > >>AXIOM should make it easy and not hard to implement such service.
> > >>
> > >>alek
> > >>
> > >>--
> > >>The best way to predict the future is to invent it - Alan Kay
> > >>
> > >>
> > >>
> > >>
> >
> >
> > --
> > The best way to predict the future is to invent it - Alan Kay
> >
> >
>
>
--
Davanum Srinivas - http://webservices.apache.org/~dims/
Re: AXIOM and data binding [Re: [Axis2] AXIOM goals
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
I think we should stay on axis-dev .. even folks who are not actively
participating are "lurking" because of that. Also, once Axis 1.2 ships
the focus can change quite a bit ..
Sanjiva.
----- Original Message -----
From: "Aleksander Slominski" <as...@cs.indiana.edu>
To: <ax...@ws.apache.org>
Sent: Tuesday, November 16, 2004 8:06 AM
Subject: Re: AXIOM and data binding [Re: [Axis2] AXIOM goals
> Sanjiva Weerawarana wrote:
>
> >Dude, prefix your messages with [Axis2] ;-).
> >
> >
> for my filter it is enough if axis2 is in subject as it is common that
> when you reply you get "Re: [Axis2] ..." so otherwise i would miss all
> replies ;-)
>
> anyway i think we may need a separate mailing list ...
>
> alek
>
> >----- Original Message -----
> >From: "Aleksander Slominski" <as...@cs.indiana.edu>
> >To: <ax...@ws.apache.org>
> >Sent: Monday, November 15, 2004 11:10 PM
> >Subject: AXIOM and data binding [Re: [Axis2] AXIOM goals
> >
> >
> >
> >
> >>Sanjiva Weerawarana wrote:
> >>
> >>
> >>
> >>>"Aleksander Slominski" <as...@cs.indiana.edu> writes:
> >>>
> >>>
> >>>
> >>>
> >>>>* AXIOM API is designed to support pluggable XML transformations
> >>>>(JavaBeans2XML, XSD with JaxMe/JAXB, Castor, XmlBeans, RelaxNG, ...)
> >>>>discussed in http://nagoya.apache.org/jira/browse/AXIS-1498
> >>>>
> >>>>
> >>>>
> >>>>
> >>>I can't read AXIS-1498 right now (offline ATM) but data binding is NOT
> >>>part of AXIOM.
> >>>
> >>>
> >>>
> >>what i mean by it is "designed to support" is that doing data binding
> >>should be make easier by making AXIOM API works well with any data
> >>binding framework.
> >>
> >>
> >>
> >>>In fact data binding is layered into the engine so that
> >>>all of Axis2 can run without any data binding and with the app
accessing
> >>>the OM directly (maybe via something like JXPath layered on).
> >>>
> >>>
> >>>
> >>>
> >>yes so AXIOM API must be designed (or changed when needed) so to support
> >>such access.
> >>
> >>
> >>
> >>>The point is that providers which have Java object-ified views of
> >>>the incoming XML blob is not the only way to implement a service. For
> >>>example, the service may be one or more XSLT scripts.
> >>>
> >>>
> >>>
> >>>
> >>yes - i think it would be very good for doc/literal kind of services and
> >>AXIOM should make it easy and not hard to implement such service.
> >>
> >>alek
> >>
> >>--
> >>The best way to predict the future is to invent it - Alan Kay
> >>
> >>
> >>
> >>
>
>
> --
> The best way to predict the future is to invent it - Alan Kay
>
>
Re: AXIOM and data binding [Re: [Axis2] AXIOM goals
Posted by Aleksander Slominski <as...@cs.indiana.edu>.
Sanjiva Weerawarana wrote:
>Dude, prefix your messages with [Axis2] ;-).
>
>
for my filter it is enough if axis2 is in subject as it is common that
when you reply you get "Re: [Axis2] ..." so otherwise i would miss all
replies ;-)
anyway i think we may need a separate mailing list ...
alek
>----- Original Message -----
>From: "Aleksander Slominski" <as...@cs.indiana.edu>
>To: <ax...@ws.apache.org>
>Sent: Monday, November 15, 2004 11:10 PM
>Subject: AXIOM and data binding [Re: [Axis2] AXIOM goals
>
>
>
>
>>Sanjiva Weerawarana wrote:
>>
>>
>>
>>>"Aleksander Slominski" <as...@cs.indiana.edu> writes:
>>>
>>>
>>>
>>>
>>>>* AXIOM API is designed to support pluggable XML transformations
>>>>(JavaBeans2XML, XSD with JaxMe/JAXB, Castor, XmlBeans, RelaxNG, ...)
>>>>discussed in http://nagoya.apache.org/jira/browse/AXIS-1498
>>>>
>>>>
>>>>
>>>>
>>>I can't read AXIS-1498 right now (offline ATM) but data binding is NOT
>>>part of AXIOM.
>>>
>>>
>>>
>>what i mean by it is "designed to support" is that doing data binding
>>should be make easier by making AXIOM API works well with any data
>>binding framework.
>>
>>
>>
>>>In fact data binding is layered into the engine so that
>>>all of Axis2 can run without any data binding and with the app accessing
>>>the OM directly (maybe via something like JXPath layered on).
>>>
>>>
>>>
>>>
>>yes so AXIOM API must be designed (or changed when needed) so to support
>>such access.
>>
>>
>>
>>>The point is that providers which have Java object-ified views of
>>>the incoming XML blob is not the only way to implement a service. For
>>>example, the service may be one or more XSLT scripts.
>>>
>>>
>>>
>>>
>>yes - i think it would be very good for doc/literal kind of services and
>>AXIOM should make it easy and not hard to implement such service.
>>
>>alek
>>
>>--
>>The best way to predict the future is to invent it - Alan Kay
>>
>>
>>
>>
--
The best way to predict the future is to invent it - Alan Kay
Re: AXIOM and data binding [Re: [Axis2] AXIOM goals
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Dude, prefix your messages with [Axis2] ;-).
Sanjiva.
----- Original Message -----
From: "Aleksander Slominski" <as...@cs.indiana.edu>
To: <ax...@ws.apache.org>
Sent: Monday, November 15, 2004 11:10 PM
Subject: AXIOM and data binding [Re: [Axis2] AXIOM goals
> Sanjiva Weerawarana wrote:
>
> >"Aleksander Slominski" <as...@cs.indiana.edu> writes:
> >
> >
> >>* AXIOM API is designed to support pluggable XML transformations
> >>(JavaBeans2XML, XSD with JaxMe/JAXB, Castor, XmlBeans, RelaxNG, ...)
> >>discussed in http://nagoya.apache.org/jira/browse/AXIS-1498
> >>
> >>
> >
> >I can't read AXIS-1498 right now (offline ATM) but data binding is NOT
> >part of AXIOM.
> >
> what i mean by it is "designed to support" is that doing data binding
> should be make easier by making AXIOM API works well with any data
> binding framework.
>
> >In fact data binding is layered into the engine so that
> >all of Axis2 can run without any data binding and with the app accessing
> >the OM directly (maybe via something like JXPath layered on).
> >
> >
> yes so AXIOM API must be designed (or changed when needed) so to support
> such access.
>
> >The point is that providers which have Java object-ified views of
> >the incoming XML blob is not the only way to implement a service. For
> >example, the service may be one or more XSLT scripts.
> >
> >
> yes - i think it would be very good for doc/literal kind of services and
> AXIOM should make it easy and not hard to implement such service.
>
> alek
>
> --
> The best way to predict the future is to invent it - Alan Kay
>
>