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 Chathura Herath <ch...@opensource.lk> on 2004/12/02 14:31:36 UTC
[Axis2] WSDL Service Desc
Hi all ,
I have posted a proposal in the wiki for a possible Architecture for a WSDL
Service Desc for Axis 2 based on the WSDL 2.0 Component Model.
http://wiki.apache.org/ws/FrontPage_2fArchitecture_2fWSDL
I have also proposed a package structure for WSDL Object Model (WOM) which
could be
org.apache.wsdl.wom
Comments??
Regards
Chathura
Re: [Axis2] on NAMINGCLASSES or NamingClasses [ Re: [Axis2] WSDL Service Desc
Posted by ". Ias" <ia...@hotmail.com>.
Actually there are (unofficial) coding standards as alek said at
http://www.ambysoft.com/javaCodingStandards.html. In section 1.3 at
http://www.ambysoft.com/javaCodingStandards.pdf,
7. Capitalize the first letter of standard acronyms . Names will often
contain standard abbreviations, such
as SQL for Standard Query Language. Names such as sqlDatabase for an
attribute, or SqlDatabase for a
class, are easier to read than sQLDatabase and SQLDatabase.
Personally I write code in that style (yes, we have (and even created too)
many acronyms in web services :-)
Ias
>From: "Sanjiva Weerawarana" <sa...@opensource.lk>
>Reply-To: axis-dev@ws.apache.org
>To: <ax...@ws.apache.org>
>Subject: Re: [Axis2] on NAMINGCLASSES or NamingClasses [ Re: [Axis2] WSDL
Service Desc
>Date: Fri, 3 Dec 2004 00:33:16 +0600
>
>-1 :-( ... I still prefer TypedXMLPullParser instead of
>TypedXmlPullParser for example.
>
>This is clearly something we all need to come to an agreement
>on. Shall we take a poll and see? Clearly nothing breaks
>either way!
>
>Sanjiva.
>
>----- Original Message -----
>From: "Aleksander Slominski" <as...@cs.indiana.edu>
>To: <ax...@ws.apache.org>
>Sent: Thursday, December 02, 2004 10:51 PM
>Subject: [Axis2] on NAMINGCLASSES or NamingClasses [ Re: [Axis2] WSDL
>Service Desc
>
>
> > Chathura Herath wrote:
> >
> > >
> > > I have posted a proposal in the wiki for a possible Architecture for
a
> > > WSDL Service Desc for Axis 2 based on the WSDL 2.0 Component Model.
> > >
> > > http://wiki.apache.org/ws/FrontPage_2fArchitecture_2fWSDL
> > >
> > little nitpick not that is about WOM but any class in Axis2:
> >
> > could we consider that AXIS, WSDL, XML, and especially SOAP are
actually
> > used as words and not acronyms any longer?
> >
> > So we would have AxisWsdlService instead of AXISWSDLService etc.
> >
> > this is much easier (at least for me) to read ...
> >
> > thanks,
> >
> > alek
> >
> > --
> > The best way to predict the future is to invent it - Alan Kay
> >
>
Re: [Axis2] on NAMINGCLASSES or NamingClasses [ Re: [Axis2] WSDL Service Desc
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
-1 :-( ... I still prefer TypedXMLPullParser instead of
TypedXmlPullParser for example.
This is clearly something we all need to come to an agreement
on. Shall we take a poll and see? Clearly nothing breaks
either way!
Sanjiva.
----- Original Message -----
From: "Aleksander Slominski" <as...@cs.indiana.edu>
To: <ax...@ws.apache.org>
Sent: Thursday, December 02, 2004 10:51 PM
Subject: [Axis2] on NAMINGCLASSES or NamingClasses [ Re: [Axis2] WSDL
Service Desc
> Chathura Herath wrote:
>
> >
> > I have posted a proposal in the wiki for a possible Architecture for a
> > WSDL Service Desc for Axis 2 based on the WSDL 2.0 Component Model.
> >
> > http://wiki.apache.org/ws/FrontPage_2fArchitecture_2fWSDL
> >
> little nitpick not that is about WOM but any class in Axis2:
>
> could we consider that AXIS, WSDL, XML, and especially SOAP are actually
> used as words and not acronyms any longer?
>
> So we would have AxisWsdlService instead of AXISWSDLService etc.
>
> this is much easier (at least for me) to read ...
>
> thanks,
>
> alek
>
> --
> The best way to predict the future is to invent it - Alan Kay
>
[Axis2] on NAMINGCLASSES or NamingClasses [ Re: [Axis2] WSDL Service
Desc
Posted by Aleksander Slominski <as...@cs.indiana.edu>.
Chathura Herath wrote:
>
> I have posted a proposal in the wiki for a possible Architecture for a
> WSDL Service Desc for Axis 2 based on the WSDL 2.0 Component Model.
>
> http://wiki.apache.org/ws/FrontPage_2fArchitecture_2fWSDL
>
little nitpick not that is about WOM but any class in Axis2:
could we consider that AXIS, WSDL, XML, and especially SOAP are actually
used as words and not acronyms any longer?
So we would have AxisWsdlService instead of AXISWSDLService etc.
this is much easier (at least for me) to read ...
thanks,
alek
--
The best way to predict the future is to invent it - Alan Kay
Re: [Axis2] on relation between WSLD (WOM) and XmlInfoset (OM) [ Re: [Axis2] WSDL Service Desc
Posted by Srinath Perera <he...@gmail.com>.
to add few thoughts :)
>class WsdlDefinitions implements OmElement {
we do not need to make the WOM OM dependent; if we do we need support
for XML level includes and imports and we need support for almost all
XML infoset!
> The problem is that the WSDL component model is not based on
> the XML Infoset. Its a pure, clean and simple component
> model. I would prefer for org.apache.wsdl.* to be an honest,
> straight rendering of that in Java. The actual impl can be
> whatever but I'm most concerned about the interfaces.
yes the XML is just a representation of the WSDL model; We tried
represting the WSDL schema with DOM elements in 1.1. and we all know
that goes wrong. At the code generation time we need clean parsed and
resolved WOM populated. Am too -1 on the making WOM ontop of XML
infoset.
BTW we need a good Schema Model to represent schema as well
Thanks
Srinath
RE: [Axis2] on relation between WSLD (WOM) and XmlInfoset (OM) [ Re: [Axis2] WSDL Service Desc
Posted by Chathura Herath <ch...@opensource.lk>.
-----Original Message-----
From: Sanjiva Weerawarana [mailto:sanjiva@opensource.lk]
Sent: Friday, December 03, 2004 12:38 AM
To: axis-dev@ws.apache.org
Subject: Re: [Axis2] on relation between WSLD (WOM) and XmlInfoset (OM) [
Re: [Axis2] WSDL Service Desc
"Aleksander Slominski" <as...@cs.indiana.edu> writes:
>
> did you consider to have WOM classes contain reference to original XML
> Infoset with WSDL?
>
> i found in my won experience that making WOM-like model to build
> directly on top XML Infoset make it very intuitive: i can modify WSDL
> using XML constructs (including even XPath) and as well using WSDL API
> directly, example:
>
> class WsdlDefinitions implements OmElement {
> public WsdlDefinitions(OmElement defs) {
> if(!defs.getNamesapce().equals(WSDL_11_NS) &&
> !defs.getNamesapce().equals(WSDL_11_NS)) throw ...
> ...
> this.containedXml = defs;
> }
> }
The problem is that the WSDL component model is not based on
the XML Infoset. Its a pure, clean and simple component
model. I would prefer for org.apache.wsdl.* to be an honest,
straight rendering of that in Java. The actual impl can be
whatever but I'm most concerned about the interfaces.
There is a brewing proposal to re-do the WSDL 2.0 component
model as an extension of the Infoset. I'm strongly -1 on
that proposal so will be working hard to kill it :-). Of
course that doesn't mean it'll get killed but at least you
know where I'm coming from.
Sanjiva.
Hi,
I am too with the impression that the WOM should play the part of the
Component Model for WSDL. The Build mechanism is intentionally kept external
to the WOM, so that WOM is independent of the actual representation of the
component model and at this time we will consider only the XML Infoset
representation, but leaving room for other representations as well. There
Wont be any harm in doing this, rather we would increase the usability of
the WOM beyond XML Infoset represented WSDL. Pushing the OM into the WOM
itself would make it heavily dependent on XML.
Regards
Chathura
Re: [Axis2] on relation between WSLD (WOM) and XmlInfoset (OM) [ Re: [Axis2] WSDL Service Desc
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
"Aleksander Slominski" <as...@cs.indiana.edu> writes:
>
> did you consider to have WOM classes contain reference to original XML
> Infoset with WSDL?
>
> i found in my won experience that making WOM-like model to build
> directly on top XML Infoset make it very intuitive: i can modify WSDL
> using XML constructs (including even XPath) and as well using WSDL API
> directly, example:
>
> class WsdlDefinitions implements OmElement {
> public WsdlDefinitions(OmElement defs) {
> if(!defs.getNamesapce().equals(WSDL_11_NS) &&
> !defs.getNamesapce().equals(WSDL_11_NS)) throw ...
> ...
> this.containedXml = defs;
> }
> }
The problem is that the WSDL component model is not based on
the XML Infoset. Its a pure, clean and simple component
model. I would prefer for org.apache.wsdl.* to be an honest,
straight rendering of that in Java. The actual impl can be
whatever but I'm most concerned about the interfaces.
There is a brewing proposal to re-do the WSDL 2.0 component
model as an extension of the Infoset. I'm strongly -1 on
that proposal so will be working hard to kill it :-). Of
course that doesn't mean it'll get killed but at least you
know where I'm coming from.
Chathura- you should join the WSDL WG mailing list and at least
lurk on that. Please consider pointing people to this code
when you feel its ready for a first read .. primarily the
org.apache.wsdl.* stuff.
Sanjiva.
[Axis2] on relation between WSLD (WOM) and XmlInfoset (OM) [ Re:
[Axis2] WSDL Service Desc
Posted by Aleksander Slominski <as...@cs.indiana.edu>.
Chathura Herath wrote:
> Hi all ,
>
> I have posted a proposal in the wiki for a possible Architecture for a
> WSDL Service Desc for Axis 2 based on the WSDL 2.0 Component Model.
>
> http://wiki.apache.org/ws/FrontPage_2fArchitecture_2fWSDL
>
>
>
> I have also proposed a package structure for WSDL Object Model (WOM)
> which could be
>
> org.apache.wsdl.wom
>
what is relation of OM and WOM?
did you consider to have WOM classes contain reference to original XML
Infoset with WSDL?
i found in my won experience that making WOM-like model to build
directly on top XML Infoset make it very intuitive: i can modify WSDL
using XML constructs (including even XPath) and as well using WSDL API
directly, example:
class WsdlDefinitions implements OmElement {
public WsdlDefinitions(OmElement defs) {
if(!defs.getNamesapce().equals(WSDL_11_NS) &&
!defs.getNamesapce().equals(WSDL_11_NS)) throw ...
...
this.containedXml = defs;
}
}
for example of this approach see code in XSUL:
http://www.extreme.indiana.edu/viewcvs/~checkout~/xsul/java/modules/xwsdl/
in particular
http://www.extreme.indiana.edu/viewcvs/~checkout~/xsul/java/modules/xwsdl/xsul/wsdl/WsdlDefinitions.java
HTH
alek
--
The best way to predict the future is to invent it - Alan Kay