Re: [Axis2] AXIOM or JBIX

2007-03-29 Thread Xinjun Chen

Hi Jose,

Could you kindly share how XMLBean handles xsd:anyType?
Thanks.

On 3/26/07, José Antonio Sánchez [EMAIL PROTECTED] wrote:


Not exactly. Xmlbeans can generate classes for every possible schema
automatically. JiBX only generates both classes and mapping
description for a limited set of schemas (for example, no xsd:anyType
is allowed). For that schemas you have to define the mapping manually.

On 3/26/07, Josh [EMAIL PROTECTED] wrote:
 Just for my own knowledge, is this a true statement?: This is because
 XMLBeans implementation can understand all the XSD (i.e. schema)
 constructs.  Does JiBX have mapping limitations?

 Regards,

 Joshua



 On 3/26/07, Nilesh Ghorpade [EMAIL PROTECTED] wrote:
 
 
 
  Hi,
 
  As per my understanding AXIS 2 uses AXIOM API's internally for any XML
 related activities. Hence as you have mentioned that you are confused to
 choose between POJO, AXIOM, JIBX, ADB or XMLBeans, the AXIOM is an
invalid
 option here.
 
  Secondly in AXIS 2 you can create web services using either the Spring
 Framework or POJO.
 
  JiBX, XMLBeans and ADB are more related to the data binding frameworks
 which AXIS 2 supports. Hence it depends on your schema on which data
binding
 framework you would want to select. As per my knowledge XMLBeans is the
best
 when it comes to complex schemas. This is because XMLBeans
implementation
 can understand all the XSD ( i.e. schema) constructs.
 
  To answer your second question, the answer is YES. If you want to use
the
 wsdl2java command from AXIS2 for generating your stubs and skeletons you
 will need the WSDL. Generating a WSDL is also not a diccficult task. YOu
can
 have your SEI defined i.e. the Service Endpoint Interface with all the
 method signatures which you want to expose as web service operations. On
 executing the java2wsdl command from AXIS2 you would be able to get the
 WSDL. And using this WSDL you can generate the remaining artifacts of
your
 web service. WSDL is nothing but an interface and hence even if you have
 defined an interface in Java, you can generate a WSDL from it.
 
 
  Hope that answers your queries.
 
 
  Regards
 
  Niles
 
  - Original Message 
  From: Martin Gainty  [EMAIL PROTECTED]
  To: axis-user@ws.apache.org
 
  Sent: Monday, March 26, 2007 3:15:01 AM
  Subject: Re: [Axis2] AXIOM or JBIX
 
 
  Anil-
 
  I found this whitepaper quite informative
  SAX2 processes fastest..with DOM bein
 

http://www.mail-archive.com/jibx-users@lists.sourceforge.net/msg01044.html
 
  FWIW,
  M--
 

---
  This e-mail message (including attachments, if any) is intended for
the
 use of the individual or entity to which it is addressed and may contain
 information that is privileged, proprietary , confidential and exempt
from
 disclosure. If you are not the intended recipient, you are notified that
any
 dissemination, distribution or copying of this communication is strictly
 prohibited.
 

---
  Le présent message électronique (y compris les pièces qui y sont
annexées,
 le cas échéant) s'adresse au destinataire indiqué et peut contenir des
 renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le
 destinataire de ce document, nous vous signalons qu'il est strictement
 interdit de le diffuser, de le distribuer ou de le reproduire.
  - Original Message -
  From: Anil [EMAIL PROTECTED]
  To:  axis-user@ws.apache.org
  Sent: Sunday, March 25, 2007 4:37 PM
  Subject: [Axis2] AXIOM or JBIX
 
 
   Hi,
  
   I'm new to Axis2, what is the criteria to choose
   between POJO, AXIOM, JIBX, ADB or XMLBeans. How do we
   decide architecture wise.
  
   My second question is, is wsdl file mandatory to
   create stub and skeleton interfaces or can we use just
   skeleton file to create wsdl file.
  
   Thanks.
  
  
  
  


   Bored stiff? Loosen up...
   Download and play hundreds of games for free on Yahoo! Games.
   http://games.yahoo.com/games/front
  
  
 -
   To unsubscribe, e-mail:
 [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  
  
 
 
  
  TV dinner still cooling?
  Check out Tonight's Picks on Yahoo! TV.




--
Saludos.
José Antonio Sánchez

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Re: [Axis2] AXIOM or JBIX

2007-03-29 Thread Xinjun Chen
 XMLBeans
 implementation
 can understand all the XSD ( i.e. schema) constructs.
 
  To answer your second question, the answer is YES. If you want to
 use the
 wsdl2java command from AXIS2 for generating your stubs and skeletons
you
 will need the WSDL. Generating a WSDL is also not a diccficult task.
 YOu can
 have your SEI defined i.e. the Service Endpoint Interface with all the
 method signatures which you want to expose as web service operations.
On
 executing the java2wsdl command from AXIS2 you would be able to get the
 WSDL. And using this WSDL you can generate the remaining artifacts of
 your
 web service. WSDL is nothing but an interface and hence even if you
have
 defined an interface in Java, you can generate a WSDL from it.
 
 
  Hope that answers your queries.
 
 
  Regards
 
  Niles
 
  - Original Message 
  From: Martin Gainty  [EMAIL PROTECTED]
  To: axis-user@ws.apache.org
 
  Sent: Monday, March 26, 2007 3:15:01 AM
  Subject: Re: [Axis2] AXIOM or JBIX
 
 
  Anil-
 
  I found this whitepaper quite informative
  SAX2 processes fastest..with DOM bein
 

http://www.mail-archive.com/jibx-users@lists.sourceforge.net/msg01044.html

 
  FWIW,
  M--
 

---

  This e-mail message (including attachments, if any) is intended for
 the
 use of the individual or entity to which it is addressed and may
contain
 information that is privileged, proprietary , confidential and exempt
 from
 disclosure. If you are not the intended recipient, you are notified
 that any
 dissemination, distribution or copying of this communication is
strictly
 prohibited.
 

---

  Le présent message électronique (y compris les pièces qui y sont
 annexées,
 le cas échéant) s'adresse au destinataire indiqué et peut contenir des
 renseignements de caractère privé ou confidentiel. Si vous n'êtes pas
le
 destinataire de ce document, nous vous signalons qu'il est strictement
 interdit de le diffuser, de le distribuer ou de le reproduire.
  - Original Message -
  From: Anil [EMAIL PROTECTED]
  To:  axis-user@ws.apache.org
  Sent: Sunday, March 25, 2007 4:37 PM
  Subject: [Axis2] AXIOM or JBIX
 
 
   Hi,
  
   I'm new to Axis2, what is the criteria to choose
   between POJO, AXIOM, JIBX, ADB or XMLBeans. How do we
   decide architecture wise.
  
   My second question is, is wsdl file mandatory to
   create stub and skeleton interfaces or can we use just
   skeleton file to create wsdl file.
  
   Thanks.
  
  
  
  



   Bored stiff? Loosen up...
   Download and play hundreds of games for free on Yahoo! Games.
   http://games.yahoo.com/games/front
  
  
 -
   To unsubscribe, e-mail:
 [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  
  
 
 
  
  TV dinner still cooling?
  Check out Tonight's Picks on Yahoo! TV.





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Re: [Axis2] AXIOM or JBIX

2007-03-29 Thread José Antonio Sánchez

In xmlbeans xsd:anyType maps to XmlObject, which is the most basic
class in xmlbeans.
This is the class hierarchy that xmlbeans maps:

http://xmlbeans.apache.org/docs/2.0.0/guide/conXMLBeansSupportBuiltInSchemaTypes.html

On 3/29/07, Xinjun Chen [EMAIL PROTECTED] wrote:

Hi Jose,

Could you kindly share how XMLBean handles xsd:anyType?
Thanks.


On 3/26/07, José Antonio Sánchez [EMAIL PROTECTED] wrote:
 Not exactly. Xmlbeans can generate classes for every possible schema
 automatically. JiBX only generates both classes and mapping
 description for a limited set of schemas (for example, no xsd:anyType
 is allowed). For that schemas you have to define the mapping manually.

 On 3/26/07, Josh [EMAIL PROTECTED]  wrote:
  Just for my own knowledge, is this a true statement?: This is because
  XMLBeans implementation can understand all the XSD (i.e. schema)
  constructs.  Does JiBX have mapping limitations?
 
  Regards,
 
  Joshua
 
 
 
  On 3/26/07, Nilesh Ghorpade [EMAIL PROTECTED] wrote:
  
  
  
   Hi,
  
   As per my understanding AXIS 2 uses AXIOM API's internally for any XML
  related activities. Hence as you have mentioned that you are confused to
  choose between POJO, AXIOM, JIBX, ADB or XMLBeans, the AXIOM is an
invalid
  option here.
  
   Secondly in AXIS 2 you can create web services using either the Spring
  Framework or POJO.
  
   JiBX, XMLBeans and ADB are more related to the data binding frameworks
  which AXIS 2 supports. Hence it depends on your schema on which data
binding
  framework you would want to select. As per my knowledge XMLBeans is the
best
  when it comes to complex schemas. This is because XMLBeans
implementation
  can understand all the XSD ( i.e. schema) constructs.
  
   To answer your second question, the answer is YES. If you want to use
the
  wsdl2java command from AXIS2 for generating your stubs and skeletons you
  will need the WSDL. Generating a WSDL is also not a diccficult task. YOu
can
  have your SEI defined i.e. the Service Endpoint Interface with all the
  method signatures which you want to expose as web service operations. On
  executing the java2wsdl command from AXIS2 you would be able to get the
  WSDL. And using this WSDL you can generate the remaining artifacts of
your
  web service. WSDL is nothing but an interface and hence even if you have
  defined an interface in Java, you can generate a WSDL from it.
  
  
   Hope that answers your queries.
  
  
   Regards
  
   Niles
  
   - Original Message 
   From: Martin Gainty  [EMAIL PROTECTED]
   To: axis-user@ws.apache.org
  
   Sent: Monday, March 26, 2007 3:15:01 AM
   Subject: Re: [Axis2] AXIOM or JBIX
  
  
   Anil-
  
   I found this whitepaper quite informative
   SAX2 processes fastest..with DOM bein
  
 
http://www.mail-archive.com/jibx-users@lists.sourceforge.net/msg01044.html
  
   FWIW,
   M--
  
 
---
   This e-mail message (including attachments, if any) is intended for
the
  use of the individual or entity to which it is addressed and may contain
  information that is privileged, proprietary , confidential and exempt
from
  disclosure. If you are not the intended recipient, you are notified that
any
  dissemination, distribution or copying of this communication is strictly
  prohibited.
  
 
---
   Le présent message électronique (y compris les pièces qui y sont
annexées,
  le cas échéant) s'adresse au destinataire indiqué et peut contenir des
  renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le
  destinataire de ce document, nous vous signalons qu'il est strictement
  interdit de le diffuser, de le distribuer ou de le reproduire.
   - Original Message -
   From: Anil [EMAIL PROTECTED]
   To:  axis-user@ws.apache.org
   Sent: Sunday, March 25, 2007 4:37 PM
   Subject: [Axis2] AXIOM or JBIX
  
  
Hi,
   
I'm new to Axis2, what is the criteria to choose
between POJO, AXIOM, JIBX, ADB or XMLBeans. How do we
decide architecture wise.
   
My second question is, is wsdl file mandatory to
create stub and skeleton interfaces or can we use just
skeleton file to create wsdl file.
   
Thanks.
   
   
   
   
 

Bored stiff? Loosen up...
Download and play hundreds of games for free on Yahoo! Games.
http://games.yahoo.com/games/front
   
   
 
-
To unsubscribe, e-mail:
  [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
   
   
  
  
   
   TV dinner still cooling?
   Check out Tonight's Picks on Yahoo! TV.
 
 


 --
 Saludos.
 José Antonio Sánchez


-
 To unsubscribe, e-mail:
[EMAIL PROTECTED]
 For additional

Re: [Axis2] AXIOM or JBIX

2007-03-29 Thread robert lazarski
. schema)
  constructs.  Does JiBX have mapping limitations?
 
  Regards,
 
  Joshua
 
 
 
  On 3/26/07, Nilesh Ghorpade [EMAIL PROTECTED] wrote:
  
  
  
   Hi,
  
   As per my understanding AXIS 2 uses AXIOM API's internally for any
XML
  related activities. Hence as you have mentioned that you are confused
to
  choose between POJO, AXIOM, JIBX, ADB or XMLBeans, the AXIOM is an
  invalid
  option here.
  
   Secondly in AXIS 2 you can create web services using either the
Spring
  Framework or POJO.
  
   JiBX, XMLBeans and ADB are more related to the data binding
frameworks
  which AXIS 2 supports. Hence it depends on your schema on which data
  binding
  framework you would want to select. As per my knowledge XMLBeans is
  the best
  when it comes to complex schemas. This is because XMLBeans
  implementation
  can understand all the XSD ( i.e. schema) constructs.
  
   To answer your second question, the answer is YES. If you want to
  use the
  wsdl2java command from AXIS2 for generating your stubs and skeletons
you
  will need the WSDL. Generating a WSDL is also not a diccficult task.
  YOu can
  have your SEI defined i.e. the Service Endpoint Interface with all the
  method signatures which you want to expose as web service operations.
On
  executing the java2wsdl command from AXIS2 you would be able to get the
  WSDL. And using this WSDL you can generate the remaining artifacts of
  your
  web service. WSDL is nothing but an interface and hence even if you
have
  defined an interface in Java, you can generate a WSDL from it.
  
  
   Hope that answers your queries.
  
  
   Regards
  
   Niles
  
   - Original Message 
   From: Martin Gainty  [EMAIL PROTECTED]
   To: axis-user@ws.apache.org
  
   Sent: Monday, March 26, 2007 3:15:01 AM
   Subject: Re: [Axis2] AXIOM or JBIX
  
  
   Anil-
  
   I found this whitepaper quite informative
   SAX2 processes fastest..with DOM bein
  
 
http://www.mail-archive.com/jibx-users@lists.sourceforge.net/msg01044.html
 
  
   FWIW,
   M--
  
 
---
 
   This e-mail message (including attachments, if any) is intended for
  the
  use of the individual or entity to which it is addressed and may
contain
  information that is privileged, proprietary , confidential and exempt
  from
  disclosure. If you are not the intended recipient, you are notified
  that any
  dissemination, distribution or copying of this communication is
strictly
  prohibited.
  
 
---
 
   Le présent message électronique (y compris les pièces qui y sont
  annexées,
  le cas échéant) s'adresse au destinataire indiqué et peut contenir des
  renseignements de caractère privé ou confidentiel. Si vous n'êtes pas
le
  destinataire de ce document, nous vous signalons qu'il est strictement
  interdit de le diffuser, de le distribuer ou de le reproduire.
   - Original Message -
   From: Anil [EMAIL PROTECTED] 
   To:  axis-user@ws.apache.org
   Sent: Sunday, March 25, 2007 4:37 PM
   Subject: [Axis2] AXIOM or JBIX
  
  
Hi,
   
I'm new to Axis2, what is the criteria to choose
between POJO, AXIOM, JIBX, ADB or XMLBeans. How do we
decide architecture wise.
   
My second question is, is wsdl file mandatory to
create stub and skeleton interfaces or can we use just
skeleton file to create wsdl file.
   
Thanks.
   
   
   
   
 

 
Bored stiff? Loosen up...
Download and play hundreds of games for free on Yahoo! Games.
http://games.yahoo.com/games/front
   
   
 
-
To unsubscribe, e-mail:
  [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
   
   
  
  
   
   TV dinner still cooling?
   Check out Tonight's Picks on Yahoo! TV.
 
 
 
 


-
 To unsubscribe, e-mail:
[EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [Axis2] AXIOM or JBIX

2007-03-29 Thread robert lazarski
 only generates both classes and mapping
   description for a limited set of schemas (for example, no xsd:anyType
   is allowed). For that schemas you have to define the mapping manually.
  
   On 3/26/07, Josh [EMAIL PROTECTED] wrote:
   Just for my own knowledge, is this a true statement?: This is because
   XMLBeans implementation can understand all the XSD (i.e. schema)
   constructs.  Does JiBX have mapping limitations?
  
   Regards,
  
   Joshua
  
  
  
   On 3/26/07, Nilesh Ghorpade [EMAIL PROTECTED] wrote:
   
   
   
Hi,
   
As per my understanding AXIS 2 uses AXIOM API's internally for any
 XML
   related activities. Hence as you have mentioned that you are confused
 to
   choose between POJO, AXIOM, JIBX, ADB or XMLBeans, the AXIOM is an
   invalid
   option here.
   
Secondly in AXIS 2 you can create web services using either the
 Spring
   Framework or POJO.
   
JiBX, XMLBeans and ADB are more related to the data binding
 frameworks
   which AXIS 2 supports. Hence it depends on your schema on which data
   binding
   framework you would want to select. As per my knowledge XMLBeans is
   the best
   when it comes to complex schemas. This is because XMLBeans
   implementation
   can understand all the XSD ( i.e. schema) constructs.
   
To answer your second question, the answer is YES. If you want to
   use the
   wsdl2java command from AXIS2 for generating your stubs and skeletons
 you
   will need the WSDL. Generating a WSDL is also not a diccficult task.
   YOu can
   have your SEI defined i.e. the Service Endpoint Interface with all the
   method signatures which you want to expose as web service operations.
 On
   executing the java2wsdl command from AXIS2 you would be able to get the
   WSDL. And using this WSDL you can generate the remaining artifacts of
   your
   web service. WSDL is nothing but an interface and hence even if you
 have
   defined an interface in Java, you can generate a WSDL from it.
   
   
Hope that answers your queries.
   
   
Regards
   
Niles
   
- Original Message 
From: Martin Gainty  [EMAIL PROTECTED]
To: axis-user@ws.apache.org
   
Sent: Monday, March 26, 2007 3:15:01 AM
Subject: Re: [Axis2] AXIOM or JBIX
   
   
Anil-
   
I found this whitepaper quite informative
SAX2 processes fastest..with DOM bein
   
  
 http://www.mail-archive.com/jibx-users@lists.sourceforge.net/msg01044.html
  
   
FWIW,
M--
   
  
 ---
  
This e-mail message (including attachments, if any) is intended for
   the
   use of the individual or entity to which it is addressed and may
 contain
   information that is privileged, proprietary , confidential and exempt
   from
   disclosure. If you are not the intended recipient, you are notified
   that any
   dissemination, distribution or copying of this communication is
 strictly
   prohibited.
   
  
 ---
  
Le présent message électronique (y compris les pièces qui y sont
   annexées,
   le cas échéant) s'adresse au destinataire indiqué et peut contenir des
   renseignements de caractère privé ou confidentiel. Si vous n'êtes pas
 le
   destinataire de ce document, nous vous signalons qu'il est strictement
   interdit de le diffuser, de le distribuer ou de le reproduire.
- Original Message -
From: Anil [EMAIL PROTECTED] 
To:  axis-user@ws.apache.org
Sent: Sunday, March 25, 2007 4:37 PM
Subject: [Axis2] AXIOM or JBIX
   
   
 Hi,

 I'm new to Axis2, what is the criteria to choose
 between POJO, AXIOM, JIBX, ADB or XMLBeans. How do we
 decide architecture wise.

 My second question is, is wsdl file mandatory to
 create stub and skeleton interfaces or can we use just
 skeleton file to create wsdl file.

 Thanks.




  
 

  
 Bored stiff? Loosen up...
 Download and play hundreds of games for free on Yahoo! Games.
 http://games.yahoo.com/games/front


  
 -
 To unsubscribe, e-mail:
   [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


   
   

TV dinner still cooling?
Check out Tonight's Picks on Yahoo! TV.
  
  
  
  
 
 
 -
  To unsubscribe, e-mail:
 [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [Axis2] AXIOM or JBIX

2007-03-29 Thread Martin Gainty
so your suggestion is to go AXIS2 with ADB for speed?

dims -- There seems to be a few pics missing on the link 
http://wso2.org/library/91
http://www.wso2.net/article/perf_1/images/set1-echo-primitives.png
http://www.wso2.net/article/perf_1/images/set1-echo-complextypes.png
http://www.wso2.net/article/perf_1/images/set2-send-receive-echo-doubles.png

overall a complete and comprehensive analysis--
Thanks,
M--
--- 
This e-mail message (including attachments, if any) is intended for the use of 
the individual or entity to which it is addressed and may contain information 
that is privileged, proprietary , confidential and exempt from disclosure. If 
you are not the intended recipient, you are notified that any dissemination, 
distribution or copying of this communication is strictly prohibited.
--- 
Le présent message électronique (y compris les pièces qui y sont annexées, le 
cas échéant) s'adresse au destinataire indiqué et peut contenir des 
renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le 
destinataire de ce document, nous vous signalons qu'il est strictement interdit 
de le diffuser, de le distribuer ou de le reproduire.
- Original Message - 
From: robert lazarski [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Thursday, March 29, 2007 9:21 AM
Subject: Re: [Axis2] AXIOM or JBIX


I meant to add that it may be worth exploring jaxws, since it seems to
have some code in svn which works with ejb - not sure about how mature
it is at this point. I believe jaxws will be labeled experimental in
the 1.2 release.

Robert

On 3/29/07, robert lazarski [EMAIL PROTECTED] wrote:
 I'll step in here to briefly comment about the ejb part of the
 question. I think its pretty clear that if full schema support is
 required, use xmlbeans or jaxb. adb and jibx come close enough in many
 cases, and give better performance which you can see here:

 http://wso2.org/library/91

 (seem to remember there was an adb / jibx performance comparison ar
 some point but I can't find it easily).

 Regarding ejb, axis2 1.2rc1 has support in
 org.apache.axis2.rpc.receivers.ejb . There was a tutorial in the works
 but it doesn't seem to be in svn.

 Another option which I often do is simply create the service, and
 inside that do local ejb calls.

 HTH,
 Robert

 On 3/29/07, Xinjun Chen [EMAIL PROTECTED] wrote:
  Hi Dennis,
 
  I am trying to expose existing EJBs as web services. What I want to do is as
  follows:
  1. Receive an EJB Remote interface and the related domain object classes,
  and generate data binder classes for the Remote interface methods.
  2. Generate wsdl for the EJB Remote interface.
  3. When receives SOAP Request from a client, I convert the XML message into
  domain object using the binder classes and invoke an appropriate EJB with
  the domain object. Since the remote EJB and domain objects are fixed, the
  generated binder must do binding for the existing domain object class
  (without modifying the domain object class since they will be used in rmi).
  What's the data binding tool I should use?
 
  Regards,
  Xinjun
 
 
 
  On 3/27/07, Dennis Sosnoski [EMAIL PROTECTED] wrote:
   Good summary, José, but I'll add that even with manual binding
   definitions JiBX can't handle all aspects of schema correctly. Of
   course, that's also true of most data binding frameworks. XMLBeans was
   designed from the start to handle all of schema, and aside from some
   quirks and peculiarities it does so pretty well. But schema is a mess,
   and not all parts of it can be handled cleanly. The biggest downsides to
   XMLBeans for Java developers are that (1) many people find the generated
   data model API awkward to work with, (2) XMLBeans performance can be
   relatively poor (both in terms of time and memory usage), and (3) schema
   is being misused (especially in the web services world) in ways which
   AFAIK XMLBeans cannot handle.
  
   For (3), I'll point in particular at the use of flexible
   unmarshalling. What this means is taking the schema as a base, but then
   ignoring any elements which do not match the schema. This was the way
   most of the first- and second-generation web services frameworks
   operated, and some users now demand it. JAXB 2.0 operates this way by
   default (over my objections), and I added support for it in JiBX due to
   client requests. I personally think it's a bad way to go - why have a
   schema at all, if you're not going to enforce it? - but can see the
   appeal. It allows groups to use a common schema with ad hoc extensions
   for individual needs.
  
   JiBX was originally designed with the focus on providing fast and
   flexible conversions between XML and Java. Schema was an afterthought
   for JiBX, though it's become more of a driving force as developers using
   JiBX have wanted to support different

Re: [Axis2] AXIOM or JBIX

2007-03-29 Thread Xinjun Chen
   is allowed). For that schemas you have to define the mapping
manually.
  
   On 3/26/07, Josh [EMAIL PROTECTED] wrote:
   Just for my own knowledge, is this a true statement?: This is
because
   XMLBeans implementation can understand all the XSD (i.e. schema)
   constructs.  Does JiBX have mapping limitations?
  
   Regards,
  
   Joshua
  
  
  
   On 3/26/07, Nilesh Ghorpade [EMAIL PROTECTED] wrote:
   
   
   
Hi,
   
As per my understanding AXIS 2 uses AXIOM API's internally for
any
 XML
   related activities. Hence as you have mentioned that you are
confused
 to
   choose between POJO, AXIOM, JIBX, ADB or XMLBeans, the AXIOM is an
   invalid
   option here.
   
Secondly in AXIS 2 you can create web services using either the
 Spring
   Framework or POJO.
   
JiBX, XMLBeans and ADB are more related to the data binding
 frameworks
   which AXIS 2 supports. Hence it depends on your schema on which
data
   binding
   framework you would want to select. As per my knowledge XMLBeans is
   the best
   when it comes to complex schemas. This is because XMLBeans
   implementation
   can understand all the XSD ( i.e. schema) constructs.
   
To answer your second question, the answer is YES. If you want to
   use the
   wsdl2java command from AXIS2 for generating your stubs and
skeletons
 you
   will need the WSDL. Generating a WSDL is also not a diccficult
task.
   YOu can
   have your SEI defined i.e. the Service Endpoint Interface with all
the
   method signatures which you want to expose as web service
operations.
 On
   executing the java2wsdl command from AXIS2 you would be able to get
the
   WSDL. And using this WSDL you can generate the remaining artifacts
of
   your
   web service. WSDL is nothing but an interface and hence even if you
 have
   defined an interface in Java, you can generate a WSDL from it.
   
   
Hope that answers your queries.
   
   
Regards
   
Niles
   
- Original Message 
From: Martin Gainty  [EMAIL PROTECTED]
To: axis-user@ws.apache.org
   
Sent: Monday, March 26, 2007 3:15:01 AM
Subject: Re: [Axis2] AXIOM or JBIX
   
   
Anil-
   
I found this whitepaper quite informative
SAX2 processes fastest..with DOM bein
   
  

http://www.mail-archive.com/jibx-users@lists.sourceforge.net/msg01044.html
  
   
FWIW,
M--
   
  

---
  
This e-mail message (including attachments, if any) is intended
for
   the
   use of the individual or entity to which it is addressed and may
 contain
   information that is privileged, proprietary , confidential and
exempt
   from
   disclosure. If you are not the intended recipient, you are notified
   that any
   dissemination, distribution or copying of this communication is
 strictly
   prohibited.
   
  

---
  
Le présent message électronique (y compris les pièces qui y sont
   annexées,
   le cas échéant) s'adresse au destinataire indiqué et peut contenir
des
   renseignements de caractère privé ou confidentiel. Si vous n'êtes
pas
 le
   destinataire de ce document, nous vous signalons qu'il est
strictement
   interdit de le diffuser, de le distribuer ou de le reproduire.
- Original Message -
From: Anil [EMAIL PROTECTED] 
To:  axis-user@ws.apache.org
Sent: Sunday, March 25, 2007 4:37 PM
Subject: [Axis2] AXIOM or JBIX
   
   
 Hi,

 I'm new to Axis2, what is the criteria to choose
 between POJO, AXIOM, JIBX, ADB or XMLBeans. How do we
 decide architecture wise.

 My second question is, is wsdl file mandatory to
 create stub and skeleton interfaces or can we use just
 skeleton file to create wsdl file.

 Thanks.




  


  
 Bored stiff? Loosen up...
 Download and play hundreds of games for free on Yahoo! Games.
 http://games.yahoo.com/games/front


  
 -
 To unsubscribe, e-mail:
   [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


   
   

TV dinner still cooling?
Check out Tonight's Picks on Yahoo! TV.
  
  
  
  
 
 
 -
  To unsubscribe, e-mail:
 [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Re: [Axis2] AXIOM or JBIX

2007-03-27 Thread Anil VVNN

Hi Nilesh,

Thanks for detailed response. 

So, the AddressBookService example (at
http://people.apache.org/~thilina/axis2/docs/jibx/jibx-unwrapped-example.html)
which uses POJO as a data transfer object, can be implemented using any Data
binding framework (JIBX or ADB) to create Java classes. 

What is JiBX binding definition, is this property only applicable to JiBX
framework
-EbindingFile /resources/jibxbindingFile.xml 

And also, can we send the client request using SOAP (instead of writing Java
Client) and get the response back in SOAP? In which case,  this type of
scenario comes in.

Thanks,
Anil



Nilesh Ghorpade wrote:
 
 Hi Anil,
 
 The Data binding frameworks come into picture when you are generating the
 Java code artifacts from WSDL. If you observe the wsdl2java command
 there is a command line argument namely -d with which you can specify
 the Data binding framework which you want to use. In case u want to use
 JiBX you would be specifying something like 
 
 $ wsdl2java -o /outputDir -d jibx -EbindingFile
 /resources/jibxbindingFile.xml -uri MyWebService.wsdl
 
 The above command is just for making things more simpler. Also if there
 are no schema references in the WSDL or if the WSDL is not having any
 schema types then the Data binding framework would not be coming into
 picture. (Others Please correct me if I am wrong.)
 
 You would just be deciding which Data binding framework you should be
 using. AXIS 2 would internally be using the same and generating the Java
 classes for you. Do not get confused by the approach which you are
 choosing to build the web service and the data binding framework. The data
 binding framework is just to map the schema which is defined in the WSDL
 to Java classes. Thats the only purpose of the data binding framework. 
 
 Using POJO's for web services means you would be writing a POJO class
 which would be capturing all the information you need for invoking the
 particular web service operation. For example if you see the
 AddressBookService in the AXIS 2 samples you can see that the addEntry
 method takes in a POJO as its input parameter namely Entry.
 
 
 Regarding your second question I am not able to understand it correctly.  
 
 Also the flow which you have mentioned from the Client to the Service is
 correct and it would remain the same for any Web service for that matter
 i.e. not only AXIS 2 but any web service which is developed using any
 other framework.
 
 Hope that answers your queries.
 
 
 Regards
 
 Nilesh
 
 - Original Message 
 From: Anil VVNN [EMAIL PROTECTED]
 To: axis-user@ws.apache.org
 Sent: Monday, March 26, 2007 7:56:35 PM
 Subject: Re: [Axis2] AXIOM or JBIX
 
 
 Hi Niles,
 
 Thanks for answering my questions. As I said I'm a beginner, I have few
 more
 questions related to previous one.
 
 (1) When exactly do we use Binding frameworks (JIBX, ADB or XMLBeans) ? 
 For instance, the examples given in Axis2 website (i.e. StockQuoteService)
 referring to simple method call, client calling WS for getPrice/update
 operations but there's no XSD involved, I think this kind of operations
 can
 be easily accomplished using POJO option. But I'm confused when to use
 POJO
 or anyother Binding framework(JIBX).
 
 (2) What is the difference between XML Processing Model and SOAP
 Processing Model, when do we use these models independently.
 
 To my understanding, this is the typical flow of Axis2 services,
 
 Client calls--- Stub (generated by wsdl2java) calls[SOAP
 request]--- Skeleton Interface (generated by wsdl2java) --Business Logic
 
 And this SOAP request can be handled using any transport (eg. TCP, JMS
 etc.)
 
 Please correct me if I'm wrong. Thanks.
 
 - Anil
 
 
 Nilesh Ghorpade wrote:
 
 Hi,
 
 As per my understanding AXIS 2 uses AXIOM API's internally for any XML
 related activities. Hence as you have mentioned that you are confused to
 choose between POJO, AXIOM, JIBX, ADB or XMLBeans, the AXIOM is an
 invalid
 option here.
 
 Secondly in AXIS 2 you can create web services using either the Spring
 Framework or POJO. 
 
 JiBX, XMLBeans and ADB are more related to the data binding frameworks
 which AXIS 2 supports. Hence it depends on your schema on which data
 binding framework you would want to select. As per my knowledge XMLBeans
 is the best when it comes to complex schemas. This is because XMLBeans
 implementation can understand all the XSD (i.e. schema) constructs.
 
 To answer your second question, the answer is YES. If you want to use the
 wsdl2java command from AXIS2 for generating your stubs and skeletons you
 will need the WSDL. Generating a WSDL is also not a diccficult task. YOu
 can have your SEI defined i.e. the Service Endpoint Interface with all
 the
 method signatures which you want to expose as web service operations. On
 executing the java2wsdl command from AXIS2 you would be able to get the
 WSDL. And using this WSDL you can generate the remaining artifacts of
 your
 web service. WSDL is nothing

Re: [Axis2] AXIOM or JBIX

2007-03-27 Thread Nilesh Ghorpade
Hi Anil,
  
  The JiBX XML file which I had mentioned contains the mapping between  XML and 
the Java classes. You can generate this file using the jibx  commands. Please 
refer the JiBX documentation for more details.
  
  Secondly your question related to sending a SOAP request. We always  send a 
SOAP request to a Web Service. I mean even if we have a Java  client written 
what we do is create a SOAP request and then send the  same over HTTP or any 
other transport protocol to the Web Service  endpoint. So the Client request 
would always be in SOAP whether you  have a java/.NET/C/C++ client accessing 
the web service.
  
  
  Regards
  
  Nilesh
  
  
  
  

Anil VVNN [EMAIL PROTECTED] wrote:  
Hi Nilesh,

Thanks for detailed response. 

So, the AddressBookService example (at
http://people.apache.org/~thilina/axis2/docs/jibx/jibx-unwrapped-example.html)
which uses POJO as a data transfer object, can be implemented using any Data
binding framework (JIBX or ADB) to create Java classes. 

What is JiBX binding definition, is this property only applicable to JiBX
framework
-EbindingFile /resources/jibxbindingFile.xml 

And also, can we send the client request using SOAP (instead of writing Java
Client) and get the response back in SOAP? In which case,  this type of
scenario comes in.

Thanks,
Anil



Nilesh Ghorpade wrote:
 
 Hi Anil,
 
 The Data binding frameworks come into picture when you are generating the
 Java code artifacts from WSDL. If you observe the wsdl2java command
 there is a command line argument namely -d with which you can specify
 the Data binding framework which you want to use. In case u want to use
 JiBX you would be specifying something like 
 
 $ wsdl2java -o /outputDir -d jibx -EbindingFile
 /resources/jibxbindingFile.xml -uri MyWebService.wsdl
 
 The above command is just for making things more simpler. Also if there
 are no schema references in the WSDL or if the WSDL is not having any
 schema types then the Data binding framework would not be coming into
 picture. (Others Please correct me if I am wrong.)
 
 You would just be deciding which Data binding framework you should be
 using. AXIS 2 would internally be using the same and generating the Java
 classes for you. Do not get confused by the approach which you are
 choosing to build the web service and the data binding framework. The data
 binding framework is just to map the schema which is defined in the WSDL
 to Java classes. Thats the only purpose of the data binding framework. 
 
 Using POJO's for web services means you would be writing a POJO class
 which would be capturing all the information you need for invoking the
 particular web service operation. For example if you see the
 AddressBookService in the AXIS 2 samples you can see that the addEntry
 method takes in a POJO as its input parameter namely Entry.
 
 
 Regarding your second question I am not able to understand it correctly.  
 
 Also the flow which you have mentioned from the Client to the Service is
 correct and it would remain the same for any Web service for that matter
 i.e. not only AXIS 2 but any web service which is developed using any
 other framework.
 
 Hope that answers your queries.
 
 
 Regards
 
 Nilesh
 
 - Original Message 
 From: Anil VVNN 
 To: axis-user@ws.apache.org
 Sent: Monday, March 26, 2007 7:56:35 PM
 Subject: Re: [Axis2] AXIOM or JBIX
 
 
 Hi Niles,
 
 Thanks for answering my questions. As I said I'm a beginner, I have few
 more
 questions related to previous one.
 
 (1) When exactly do we use Binding frameworks (JIBX, ADB or XMLBeans) ? 
 For instance, the examples given in Axis2 website (i.e. StockQuoteService)
 referring to simple method call, client calling WS for getPrice/update
 operations but there's no XSD involved, I think this kind of operations
 can
 be easily accomplished using POJO option. But I'm confused when to use
 POJO
 or anyother Binding framework(JIBX).
 
 (2) What is the difference between XML Processing Model and SOAP
 Processing Model, when do we use these models independently.
 
 To my understanding, this is the typical flow of Axis2 services,
 
 Client calls--- Stub (generated by wsdl2java) calls[SOAP
 request]--- Skeleton Interface (generated by wsdl2java) --Business Logic
 
 And this SOAP request can be handled using any transport (eg. TCP, JMS
 etc.)
 
 Please correct me if I'm wrong. Thanks.
 
 - Anil
 
 
 Nilesh Ghorpade wrote:
 
 Hi,
 
 As per my understanding AXIS 2 uses AXIOM API's internally for any XML
 related activities. Hence as you have mentioned that you are confused to
 choose between POJO, AXIOM, JIBX, ADB or XMLBeans, the AXIOM is an
 invalid
 option here.
 
 Secondly in AXIS 2 you can create web services using either the Spring
 Framework or POJO. 
 
 JiBX, XMLBeans and ADB are more related to the data binding frameworks
 which AXIS 2 supports. Hence it depends on your schema on which data
 binding framework you would want to select. As per my knowledge XMLBeans

Re: [Axis2] AXIOM or JBIX

2007-03-27 Thread Nilesh Ghorpade
Hi Anil,
  
 The JiBX XML file which I had mentioned contains the  mapping between XML and 
the Java classes. You can generate this file  using the jibx commands. Please 
refer the JiBX documentation for more  details.
  
 Secondly your question related to sending a SOAP  request. We always send a 
SOAP request to a Web Service. I mean even if  we have a Java client written 
what we do is create a SOAP request and  then send the same over HTTP or any 
other transport protocol to the Web  Service endpoint. So the Client request 
would always be in SOAP whether  you have a java/.NET/C/C++ client accessing 
the web service.
  
  
  Regards
  
  Nilesh
  
  
  
  

Anil VVNN [EMAIL PROTECTED] wrote:  
Hi Nilesh,

Thanks for detailed response. 

So, the AddressBookService example (at
http://people.apache.org/~thilina/axis2/docs/jibx/jibx-unwrapped-example.html)
which uses POJO as a data transfer object, can be implemented using any Data
binding framework (JIBX or ADB) to create Java classes. 

What is JiBX binding definition, is this property only applicable to JiBX
framework
-EbindingFile /resources/jibxbindingFile.xml 

And also, can we send the client request using SOAP (instead of writing Java
Client) and get the response back in SOAP? In which case,  this type of
scenario comes in.

Thanks,
Anil



Nilesh Ghorpade wrote:
 
 Hi Anil,
 
 The Data binding frameworks come into picture when you are generating the
 Java code artifacts from WSDL. If you observe the wsdl2java command
 there is a command line argument namely -d with which you can specify
 the Data binding framework which you want to use. In case u want to use
 JiBX you would be specifying something like 
 
 $ wsdl2java -o /outputDir -d jibx -EbindingFile
 /resources/jibxbindingFile.xml -uri MyWebService.wsdl
 
 The above command is just for making things more simpler. Also if there
 are no schema references in the WSDL or if the WSDL is not having any
 schema types then the Data binding framework would not be coming into
 picture. (Others Please correct me if I am wrong.)
 
 You would just be deciding which Data binding framework you should be
 using. AXIS 2 would internally be using the same and generating the Java
 classes for you. Do not get confused by the approach which you are
 choosing to build the web service and the data binding framework. The data
 binding framework is just to map the schema which is defined in the WSDL
 to Java classes. Thats the only purpose of the data binding framework. 
 
 Using POJO's for web services means you would be writing a POJO class
 which would be capturing all the information you need for invoking the
 particular web service operation. For example if you see the
 AddressBookService in the AXIS 2 samples you can see that the addEntry
 method takes in a POJO as its input parameter namely Entry.
 
 
 Regarding your second question I am not able to understand it correctly.  
 
 Also the flow which you have mentioned from the Client to the Service is
 correct and it would remain the same for any Web service for that matter
 i.e. not only AXIS 2 but any web service which is developed using any
 other framework.
 
 Hope that answers your queries.
 
 
 Regards
 
 Nilesh
 
 - Original Message 
 From: Anil VVNN 
 To: axis-user@ws.apache.org
 Sent: Monday, March 26, 2007 7:56:35 PM
 Subject: Re: [Axis2] AXIOM or JBIX
 
 
 Hi Niles,
 
 Thanks for answering my questions. As I said I'm a beginner, I have few
 more
 questions related to previous one.
 
 (1) When exactly do we use Binding frameworks (JIBX, ADB or XMLBeans) ? 
 For instance, the examples given in Axis2 website (i.e. StockQuoteService)
 referring to simple method call, client calling WS for getPrice/update
 operations but there's no XSD involved, I think this kind of operations
 can
 be easily accomplished using POJO option. But I'm confused when to use
 POJO
 or anyother Binding framework(JIBX).
 
 (2) What is the difference between XML Processing Model and SOAP
 Processing Model, when do we use these models independently.
 
 To my understanding, this is the typical flow of Axis2 services,
 
 Client calls--- Stub (generated by wsdl2java) calls[SOAP
 request]--- Skeleton Interface (generated by wsdl2java) --Business Logic
 
 And this SOAP request can be handled using any transport (eg. TCP, JMS
 etc.)
 
 Please correct me if I'm wrong. Thanks.
 
 - Anil
 
 
 Nilesh Ghorpade wrote:
 
 Hi,
 
 As per my understanding AXIS 2 uses AXIOM API's internally for any XML
 related activities. Hence as you have mentioned that you are confused to
 choose between POJO, AXIOM, JIBX, ADB or XMLBeans, the AXIOM is an
 invalid
 option here.
 
 Secondly in AXIS 2 you can create web services using either the Spring
 Framework or POJO. 
 
 JiBX, XMLBeans and ADB are more related to the data binding frameworks
 which AXIS 2 supports. Hence it depends on your schema on which data
 binding framework you would want to select. As per my knowledge XMLBeans

Re: [Axis2] AXIOM or JBIX

2007-03-27 Thread Nilesh Ghorpade
Hi Anil,

The JiBX XML file which I had mentioned contains the mapping between XML and 
the Java classes. You can generate this file using the jibx commands. Please 
refer the JiBX documentation for more details.

Secondly your question related to sending a SOAP request. We always send a SOAP 
request to a Web Service. I mean even if we have a Java client written what we 
do is create a SOAP request and then send the same over HTTP or any other 
transport protocol to the Web Service endpoint. So the Client request would 
always be in SOAP whether you have a java/.NET/C/C++ client accessing the web 
service.


Regards

Nilesh 


- Original Message 
From: Anil VVNN [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Wednesday, March 28, 2007 2:53:58 AM
Subject: Re: [Axis2] AXIOM or JBIX


Hi Nilesh,

Thanks for detailed response. 

So, the AddressBookService example (at
http://people.apache.org/~thilina/axis2/docs/jibx/jibx-unwrapped-example.html)
which uses POJO as a data transfer object, can be implemented using any Data
binding framework (JIBX or ADB) to create Java classes. 

What is JiBX binding definition, is this property only applicable to JiBX
framework
-EbindingFile /resources/jibxbindingFile.xml 

And also, can we send the client request using SOAP (instead of writing Java
Client) and get the response back in SOAP? In which case,  this type of
scenario comes in.

Thanks,
Anil



Nilesh Ghorpade wrote:
 
 Hi Anil,
 
 The Data binding frameworks come into picture when you are generating the
 Java code artifacts from WSDL. If you observe the wsdl2java command
 there is a command line argument namely -d with which you can specify
 the Data binding framework which you want to use. In case u want to use
 JiBX you would be specifying something like 
 
 $ wsdl2java -o /outputDir -d jibx -EbindingFile
 /resources/jibxbindingFile.xml -uri MyWebService.wsdl
 
 The above command is just for making things more simpler. Also if there
 are no schema references in the WSDL or if the WSDL is not having any
 schema types then the Data binding framework would not be coming into
 picture. (Others Please correct me if I am wrong.)
 
 You would just be deciding which Data binding framework you should be
 using. AXIS 2 would internally be using the same and generating the Java
 classes for you. Do not get confused by the approach which you are
 choosing to build the web service and the data binding framework. The data
 binding framework is just to map the schema which is defined in the WSDL
 to Java classes. Thats the only purpose of the data binding framework. 
 
 Using POJO's for web services means you would be writing a POJO class
 which would be capturing all the information you need for invoking the
 particular web service operation. For example if you see the
 AddressBookService in the AXIS 2 samples you can see that the addEntry
 method takes in a POJO as its input parameter namely Entry.
 
 
 Regarding your second question I am not able to understand it correctly.  
 
 Also the flow which you have mentioned from the Client to the Service is
 correct and it would remain the same for any Web service for that matter
 i.e. not only AXIS 2 but any web service which is developed using any
 other framework.
 
 Hope that answers your queries.
 
 
 Regards
 
 Nilesh
 
 - Original Message 
 From: Anil VVNN [EMAIL PROTECTED]
 To: axis-user@ws.apache.org
 Sent: Monday, March 26, 2007 7:56:35 PM
 Subject: Re: [Axis2] AXIOM or JBIX
 
 
 Hi Niles,
 
 Thanks for answering my questions. As I said I'm a beginner, I have few
 more
 questions related to previous one.
 
 (1) When exactly do we use Binding frameworks (JIBX, ADB or XMLBeans) ? 
 For instance, the examples given in Axis2 website (i.e. StockQuoteService)
 referring to simple method call, client calling WS for getPrice/update
 operations but there's no XSD involved, I think this kind of operations
 can
 be easily accomplished using POJO option. But I'm confused when to use
 POJO
 or anyother Binding framework(JIBX).
 
 (2) What is the difference between XML Processing Model and SOAP
 Processing Model, when do we use these models independently.
 
 To my understanding, this is the typical flow of Axis2 services,
 
 Client calls--- Stub (generated by wsdl2java) calls[SOAP
 request]--- Skeleton Interface (generated by wsdl2java) --Business Logic
 
 And this SOAP request can be handled using any transport (eg. TCP, JMS
 etc.)
 
 Please correct me if I'm wrong. Thanks.
 
 - Anil
 
 
 Nilesh Ghorpade wrote:
 
 Hi,
 
 As per my understanding AXIS 2 uses AXIOM API's internally for any XML
 related activities. Hence as you have mentioned that you are confused to
 choose between POJO, AXIOM, JIBX, ADB or XMLBeans, the AXIOM is an
 invalid
 option here.
 
 Secondly in AXIS 2 you can create web services using either the Spring
 Framework or POJO. 
 
 JiBX, XMLBeans and ADB are more related to the data binding frameworks
 which AXIS 2 supports. Hence

Re: [Axis2] AXIOM or JBIX

2007-03-26 Thread Nilesh Ghorpade
Hi,

As per my understanding AXIS 2 uses AXIOM API's internally for any XML related 
activities. Hence as you have mentioned that you are confused to choose between 
POJO, AXIOM, JIBX, ADB or XMLBeans, the AXIOM is an invalid option here.

Secondly in AXIS 2 you can create web services using either the Spring 
Framework or POJO. 

JiBX, XMLBeans and ADB are more related to the data binding frameworks which 
AXIS 2 supports. Hence it depends on your schema on which data binding 
framework you would want to select. As per my knowledge XMLBeans is the best 
when it comes to complex schemas. This is because XMLBeans implementation can 
understand all the XSD (i.e. schema) constructs.

To answer your second question, the answer is YES. If you want to use the 
wsdl2java command from AXIS2 for generating your stubs and skeletons you will 
need the WSDL. Generating a WSDL is also not a diccficult task. YOu can have 
your SEI defined i.e. the Service Endpoint Interface with all the method 
signatures which you want to expose as web service operations. On executing the 
java2wsdl command from AXIS2 you would be able to get the WSDL. And using this 
WSDL you can generate the remaining artifacts of your web service. WSDL is 
nothing but an interface and hence even if you have defined an interface in 
Java, you can generate a WSDL from it.


Hope that answers your queries.


Regards

Niles

- Original Message 
From: Martin Gainty [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Monday, March 26, 2007 3:15:01 AM
Subject: Re: [Axis2] AXIOM or JBIX


Anil-

I found this whitepaper quite informative
SAX2 processes fastest..with DOM bein
http://www.mail-archive.com/jibx-users@lists.sourceforge.net/msg01044.html

FWIW,
M--
--- 
This e-mail message (including attachments, if any) is intended for the use of 
the individual or entity to which it is addressed and may contain information 
that is privileged, proprietary , confidential and exempt from disclosure. If 
you are not the intended recipient, you are notified that any dissemination, 
distribution or copying of this communication is strictly prohibited.
--- 
Le présent message électronique (y compris les pièces qui y sont annexées, le 
cas échéant) s'adresse au destinataire indiqué et peut contenir des 
renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le 
destinataire de ce document, nous vous signalons qu'il est strictement interdit 
de le diffuser, de le distribuer ou de le reproduire.
- Original Message - 
From: Anil [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Sunday, March 25, 2007 4:37 PM
Subject: [Axis2] AXIOM or JBIX


 Hi,
 
 I'm new to Axis2, what is the criteria to choose
 between POJO, AXIOM, JIBX, ADB or XMLBeans. How do we
 decide architecture wise. 
 
 My second question is, is wsdl file mandatory to
 create stub and skeleton interfaces or can we use just
 skeleton file to create wsdl file. 
 
 Thanks.
 
 
 
 
 Bored stiff? Loosen up... 
 Download and play hundreds of games for free on Yahoo! Games.
 http://games.yahoo.com/games/front
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 



 

The fish are biting. 
Get more visitors on your site using Yahoo! Search Marketing.
http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php

Re: [Axis2] AXIOM or JBIX

2007-03-26 Thread Josh

Just for my own knowledge, is this a true statement?: This is because
XMLBeans implementation can understand all the XSD (i.e. schema)
constructs.  Does JiBX have mapping limitations?

Regards,

Joshua


On 3/26/07, Nilesh Ghorpade [EMAIL PROTECTED] wrote:


 Hi,

As per my understanding AXIS 2 uses AXIOM API's internally for any XML
related activities. Hence as you have mentioned that you are confused to
choose between POJO, AXIOM, JIBX, ADB or XMLBeans, the AXIOM is an invalid
option here.

Secondly in AXIS 2 you can create web services using either the Spring
Framework or POJO.

JiBX, XMLBeans and ADB are more related to the data binding frameworks
which AXIS 2 supports. Hence it depends on your schema on which data binding
framework you would want to select. As per my knowledge XMLBeans is the best
when it comes to complex schemas. This is because XMLBeans implementation
can understand all the XSD (i.e. schema) constructs.

To answer your second question, the answer is YES. If you want to use the
wsdl2java command from AXIS2 for generating your stubs and skeletons you
will need the WSDL. Generating a WSDL is also not a diccficult task. YOu can
have your SEI defined i.e. the Service Endpoint Interface with all the
method signatures which you want to expose as web service operations. On
executing the java2wsdl command from AXIS2 you would be able to get the
WSDL. And using this WSDL you can generate the remaining artifacts of your
web service. WSDL is nothing but an interface and hence even if you have
defined an interface in Java, you can generate a WSDL from it.


Hope that answers your queries.


Regards

Niles

- Original Message 
From: Martin Gainty [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Monday, March 26, 2007 3:15:01 AM
Subject: Re: [Axis2] AXIOM or JBIX

Anil-

I found this whitepaper quite informative
SAX2 processes fastest..with DOM bein
http://www.mail-archive.com/jibx-users@lists.sourceforge.net/msg01044.html

FWIW,
M--
---

This e-mail message (including attachments, if any) is intended for the
use of the individual or entity to which it is addressed and may contain
information that is privileged, proprietary , confidential and exempt from
disclosure. If you are not the intended recipient, you are notified that any
dissemination, distribution or copying of this communication is strictly
prohibited.
---

Le présent message électronique (y compris les pièces qui y sont annexées,
le cas échéant) s'adresse au destinataire indiqué et peut contenir des
renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le
destinataire de ce document, nous vous signalons qu'il est strictement
interdit de le diffuser, de le distribuer ou de le reproduire.
- Original Message -
From: Anil [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Sunday, March 25, 2007 4:37 PM
Subject: [Axis2] AXIOM or JBIX


 Hi,

 I'm new to Axis2, what is the criteria to choose
 between POJO, AXIOM, JIBX, ADB or XMLBeans. How do we
 decide architecture wise.

 My second question is, is wsdl file mandatory to
 create stub and skeleton interfaces or can we use just
 skeleton file to create wsdl file.

 Thanks.





 Bored stiff? Loosen up...
 Download and play hundreds of games for free on Yahoo! Games.
 http://games.yahoo.com/games/front

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]





--
TV dinner still cooling?
Check out Tonight's 
Pickshttp://us.rd.yahoo.com/evt=49979/*http://tv.yahoo.com/on Yahoo! TV.



Re: [Axis2] AXIOM or JBIX

2007-03-26 Thread Anil VVNN

Hi Niles,

Thanks for answering my questions. As I said I'm a beginner, I have few more
questions related to previous one.

(1) When exactly do we use Binding frameworks (JIBX, ADB or XMLBeans) ? 
For instance, the examples given in Axis2 website (i.e. StockQuoteService)
referring to simple method call, client calling WS for getPrice/update
operations but there's no XSD involved, I think this kind of operations can
be easily accomplished using POJO option. But I'm confused when to use POJO
or anyother Binding framework(JIBX).

(2) What is the difference between XML Processing Model and SOAP
Processing Model, when do we use these models independently.

To my understanding, this is the typical flow of Axis2 services,

Client calls--- Stub (generated by wsdl2java) calls[SOAP
request]--- Skeleton Interface (generated by wsdl2java) --Business Logic

And this SOAP request can be handled using any transport (eg. TCP, JMS etc.)

Please correct me if I'm wrong. Thanks.

- Anil


Nilesh Ghorpade wrote:
 
 Hi,
 
 As per my understanding AXIS 2 uses AXIOM API's internally for any XML
 related activities. Hence as you have mentioned that you are confused to
 choose between POJO, AXIOM, JIBX, ADB or XMLBeans, the AXIOM is an invalid
 option here.
 
 Secondly in AXIS 2 you can create web services using either the Spring
 Framework or POJO. 
 
 JiBX, XMLBeans and ADB are more related to the data binding frameworks
 which AXIS 2 supports. Hence it depends on your schema on which data
 binding framework you would want to select. As per my knowledge XMLBeans
 is the best when it comes to complex schemas. This is because XMLBeans
 implementation can understand all the XSD (i.e. schema) constructs.
 
 To answer your second question, the answer is YES. If you want to use the
 wsdl2java command from AXIS2 for generating your stubs and skeletons you
 will need the WSDL. Generating a WSDL is also not a diccficult task. YOu
 can have your SEI defined i.e. the Service Endpoint Interface with all the
 method signatures which you want to expose as web service operations. On
 executing the java2wsdl command from AXIS2 you would be able to get the
 WSDL. And using this WSDL you can generate the remaining artifacts of your
 web service. WSDL is nothing but an interface and hence even if you have
 defined an interface in Java, you can generate a WSDL from it.
 
 
 Hope that answers your queries.
 
 
 Regards
 
 Niles
 
 - Original Message 
 From: Martin Gainty [EMAIL PROTECTED]
 To: axis-user@ws.apache.org
 Sent: Monday, March 26, 2007 3:15:01 AM
 Subject: Re: [Axis2] AXIOM or JBIX
 
 
 Anil-
 
 I found this whitepaper quite informative
 SAX2 processes fastest..with DOM bein
 http://www.mail-archive.com/jibx-users@lists.sourceforge.net/msg01044.html
 
 FWIW,
 M--
 --- 
 This e-mail message (including attachments, if any) is intended for the
 use of the individual or entity to which it is addressed and may contain
 information that is privileged, proprietary , confidential and exempt from
 disclosure. If you are not the intended recipient, you are notified that
 any dissemination, distribution or copying of this communication is
 strictly prohibited.
 --- 
 Le présent message électronique (y compris les pièces qui y sont annexées,
 le cas échéant) s'adresse au destinataire indiqué et peut contenir des
 renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le
 destinataire de ce document, nous vous signalons qu'il est strictement
 interdit de le diffuser, de le distribuer ou de le reproduire.
 - Original Message - 
 From: Anil [EMAIL PROTECTED]
 To: axis-user@ws.apache.org
 Sent: Sunday, March 25, 2007 4:37 PM
 Subject: [Axis2] AXIOM or JBIX
 
 
 Hi,
 
 I'm new to Axis2, what is the criteria to choose
 between POJO, AXIOM, JIBX, ADB or XMLBeans. How do we
 decide architecture wise. 
 
 My second question is, is wsdl file mandatory to
 create stub and skeleton interfaces or can we use just
 skeleton file to create wsdl file. 
 
 Thanks.
 
 
 
 
 Bored stiff? Loosen up... 
 Download and play hundreds of games for free on Yahoo! Games.
 http://games.yahoo.com/games/front
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 

 
 
  
 
 The fish are biting. 
 Get more visitors on your site using Yahoo! Search Marketing.
 http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php
 

-- 
View this message in context: 
http://www.nabble.com/-Axis2--AXIOM-or-JBIX-tf3463792.html#a9674209
Sent from the Axis - User mailing list archive at Nabble.com

Re: [Axis2] AXIOM or JBIX

2007-03-26 Thread José Antonio Sánchez

Not exactly. Xmlbeans can generate classes for every possible schema
automatically. JiBX only generates both classes and mapping
description for a limited set of schemas (for example, no xsd:anyType
is allowed). For that schemas you have to define the mapping manually.

On 3/26/07, Josh [EMAIL PROTECTED] wrote:

Just for my own knowledge, is this a true statement?: This is because
XMLBeans implementation can understand all the XSD (i.e. schema)
constructs.  Does JiBX have mapping limitations?

Regards,

Joshua



On 3/26/07, Nilesh Ghorpade [EMAIL PROTECTED] wrote:



 Hi,

 As per my understanding AXIS 2 uses AXIOM API's internally for any XML
related activities. Hence as you have mentioned that you are confused to
choose between POJO, AXIOM, JIBX, ADB or XMLBeans, the AXIOM is an invalid
option here.

 Secondly in AXIS 2 you can create web services using either the Spring
Framework or POJO.

 JiBX, XMLBeans and ADB are more related to the data binding frameworks
which AXIS 2 supports. Hence it depends on your schema on which data binding
framework you would want to select. As per my knowledge XMLBeans is the best
when it comes to complex schemas. This is because XMLBeans implementation
can understand all the XSD ( i.e. schema) constructs.

 To answer your second question, the answer is YES. If you want to use the
wsdl2java command from AXIS2 for generating your stubs and skeletons you
will need the WSDL. Generating a WSDL is also not a diccficult task. YOu can
have your SEI defined i.e. the Service Endpoint Interface with all the
method signatures which you want to expose as web service operations. On
executing the java2wsdl command from AXIS2 you would be able to get the
WSDL. And using this WSDL you can generate the remaining artifacts of your
web service. WSDL is nothing but an interface and hence even if you have
defined an interface in Java, you can generate a WSDL from it.


 Hope that answers your queries.


 Regards

 Niles

 - Original Message 
 From: Martin Gainty  [EMAIL PROTECTED]
 To: axis-user@ws.apache.org

 Sent: Monday, March 26, 2007 3:15:01 AM
 Subject: Re: [Axis2] AXIOM or JBIX


 Anil-

 I found this whitepaper quite informative
 SAX2 processes fastest..with DOM bein

http://www.mail-archive.com/jibx-users@lists.sourceforge.net/msg01044.html

 FWIW,
 M--

---
 This e-mail message (including attachments, if any) is intended for the
use of the individual or entity to which it is addressed and may contain
information that is privileged, proprietary , confidential and exempt from
disclosure. If you are not the intended recipient, you are notified that any
dissemination, distribution or copying of this communication is strictly
prohibited.

---
 Le présent message électronique (y compris les pièces qui y sont annexées,
le cas échéant) s'adresse au destinataire indiqué et peut contenir des
renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le
destinataire de ce document, nous vous signalons qu'il est strictement
interdit de le diffuser, de le distribuer ou de le reproduire.
 - Original Message -
 From: Anil [EMAIL PROTECTED]
 To:  axis-user@ws.apache.org
 Sent: Sunday, March 25, 2007 4:37 PM
 Subject: [Axis2] AXIOM or JBIX


  Hi,
 
  I'm new to Axis2, what is the criteria to choose
  between POJO, AXIOM, JIBX, ADB or XMLBeans. How do we
  decide architecture wise.
 
  My second question is, is wsdl file mandatory to
  create stub and skeleton interfaces or can we use just
  skeleton file to create wsdl file.
 
  Thanks.
 
 
 
 

  Bored stiff? Loosen up...
  Download and play hundreds of games for free on Yahoo! Games.
  http://games.yahoo.com/games/front
 
 
-
  To unsubscribe, e-mail:
[EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 


 
 TV dinner still cooling?
 Check out Tonight's Picks on Yahoo! TV.





--
Saludos.
José Antonio Sánchez

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [Axis2] AXIOM or JBIX

2007-03-26 Thread Dennis Sosnoski
 that answers your queries.


 Regards

 Niles

 - Original Message 
 From: Martin Gainty  [EMAIL PROTECTED]
 To: axis-user@ws.apache.org

 Sent: Monday, March 26, 2007 3:15:01 AM
 Subject: Re: [Axis2] AXIOM or JBIX


 Anil-

 I found this whitepaper quite informative
 SAX2 processes fastest..with DOM bein

http://www.mail-archive.com/jibx-users@lists.sourceforge.net/msg01044.html 



 FWIW,
 M--

--- 

 This e-mail message (including attachments, if any) is intended for 
the

use of the individual or entity to which it is addressed and may contain
information that is privileged, proprietary , confidential and exempt 
from
disclosure. If you are not the intended recipient, you are notified 
that any

dissemination, distribution or copying of this communication is strictly
prohibited.

--- 

 Le présent message électronique (y compris les pièces qui y sont 
annexées,

le cas échéant) s'adresse au destinataire indiqué et peut contenir des
renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le
destinataire de ce document, nous vous signalons qu'il est strictement
interdit de le diffuser, de le distribuer ou de le reproduire.
 - Original Message -
 From: Anil [EMAIL PROTECTED]
 To:  axis-user@ws.apache.org
 Sent: Sunday, March 25, 2007 4:37 PM
 Subject: [Axis2] AXIOM or JBIX


  Hi,
 
  I'm new to Axis2, what is the criteria to choose
  between POJO, AXIOM, JIBX, ADB or XMLBeans. How do we
  decide architecture wise.
 
  My second question is, is wsdl file mandatory to
  create stub and skeleton interfaces or can we use just
  skeleton file to create wsdl file.
 
  Thanks.
 
 
 
 
 


  Bored stiff? Loosen up...
  Download and play hundreds of games for free on Yahoo! Games.
  http://games.yahoo.com/games/front
 
 
-
  To unsubscribe, e-mail:
[EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 


 
 TV dinner still cooling?
 Check out Tonight's Picks on Yahoo! TV.







-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [Axis2] AXIOM or JBIX

2007-03-26 Thread Nilesh Ghorpade
Hi Anil,

The Data binding frameworks come into picture when you are generating the Java 
code artifacts from WSDL. If you observe the wsdl2java command there is a 
command line argument namely -d with which you can specify the Data binding 
framework which you want to use. In case u want to use JiBX you would be 
specifying something like 

$ wsdl2java -o /outputDir -d jibx -EbindingFile /resources/jibxbindingFile.xml 
-uri MyWebService.wsdl

The above command is just for making things more simpler. Also if there are no 
schema references in the WSDL or if the WSDL is not having any schema types 
then the Data binding framework would not be coming into picture. (Others 
Please correct me if I am wrong.)

You would just be deciding which Data binding framework you should be using. 
AXIS 2 would internally be using the same and generating the Java classes for 
you. Do not get confused by the approach which you are choosing to build the 
web service and the data binding framework. The data binding framework is just 
to map the schema which is defined in the WSDL to Java classes. Thats the only 
purpose of the data binding framework. 

Using POJO's for web services means you would be writing a POJO class which 
would be capturing all the information you need for invoking the particular web 
service operation. For example if you see the AddressBookService in the AXIS 2 
samples you can see that the addEntry method takes in a POJO as its input 
parameter namely Entry.


Regarding your second question I am not able to understand it correctly.  

Also the flow which you have mentioned from the Client to the Service is 
correct and it would remain the same for any Web service for that matter i.e. 
not only AXIS 2 but any web service which is developed using any other 
framework.

Hope that answers your queries.


Regards

Nilesh

- Original Message 
From: Anil VVNN [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Monday, March 26, 2007 7:56:35 PM
Subject: Re: [Axis2] AXIOM or JBIX


Hi Niles,

Thanks for answering my questions. As I said I'm a beginner, I have few more
questions related to previous one.

(1) When exactly do we use Binding frameworks (JIBX, ADB or XMLBeans) ? 
For instance, the examples given in Axis2 website (i.e. StockQuoteService)
referring to simple method call, client calling WS for getPrice/update
operations but there's no XSD involved, I think this kind of operations can
be easily accomplished using POJO option. But I'm confused when to use POJO
or anyother Binding framework(JIBX).

(2) What is the difference between XML Processing Model and SOAP
Processing Model, when do we use these models independently.

To my understanding, this is the typical flow of Axis2 services,

Client calls--- Stub (generated by wsdl2java) calls[SOAP
request]--- Skeleton Interface (generated by wsdl2java) --Business Logic

And this SOAP request can be handled using any transport (eg. TCP, JMS etc.)

Please correct me if I'm wrong. Thanks.

- Anil


Nilesh Ghorpade wrote:
 
 Hi,
 
 As per my understanding AXIS 2 uses AXIOM API's internally for any XML
 related activities. Hence as you have mentioned that you are confused to
 choose between POJO, AXIOM, JIBX, ADB or XMLBeans, the AXIOM is an invalid
 option here.
 
 Secondly in AXIS 2 you can create web services using either the Spring
 Framework or POJO. 
 
 JiBX, XMLBeans and ADB are more related to the data binding frameworks
 which AXIS 2 supports. Hence it depends on your schema on which data
 binding framework you would want to select. As per my knowledge XMLBeans
 is the best when it comes to complex schemas. This is because XMLBeans
 implementation can understand all the XSD (i.e. schema) constructs.
 
 To answer your second question, the answer is YES. If you want to use the
 wsdl2java command from AXIS2 for generating your stubs and skeletons you
 will need the WSDL. Generating a WSDL is also not a diccficult task. YOu
 can have your SEI defined i.e. the Service Endpoint Interface with all the
 method signatures which you want to expose as web service operations. On
 executing the java2wsdl command from AXIS2 you would be able to get the
 WSDL. And using this WSDL you can generate the remaining artifacts of your
 web service. WSDL is nothing but an interface and hence even if you have
 defined an interface in Java, you can generate a WSDL from it.
 
 
 Hope that answers your queries.
 
 
 Regards
 
 Niles
 
 - Original Message 
 From: Martin Gainty [EMAIL PROTECTED]
 To: axis-user@ws.apache.org
 Sent: Monday, March 26, 2007 3:15:01 AM
 Subject: Re: [Axis2] AXIOM or JBIX
 
 
 Anil-
 
 I found this whitepaper quite informative
 SAX2 processes fastest..with DOM bein
 http://www.mail-archive.com/jibx-users@lists.sourceforge.net/msg01044.html
 
 FWIW,
 M--
 --- 
 This e-mail message (including attachments, if any) is intended for the
 use of the individual

[Axis2] AXIOM or JBIX

2007-03-25 Thread Anil
Hi,

I'm new to Axis2, what is the criteria to choose
between POJO, AXIOM, JIBX, ADB or XMLBeans. How do we
decide architecture wise. 

My second question is, is wsdl file mandatory to
create stub and skeleton interfaces or can we use just
skeleton file to create wsdl file. 

Thanks.


 

Bored stiff? Loosen up... 
Download and play hundreds of games for free on Yahoo! Games.
http://games.yahoo.com/games/front

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [Axis2] AXIOM or JBIX

2007-03-25 Thread Martin Gainty
Anil-

I found this whitepaper quite informative
SAX2 processes fastest..with DOM bein
http://www.mail-archive.com/jibx-users@lists.sourceforge.net/msg01044.html

FWIW,
M--
--- 
This e-mail message (including attachments, if any) is intended for the use of 
the individual or entity to which it is addressed and may contain information 
that is privileged, proprietary , confidential and exempt from disclosure. If 
you are not the intended recipient, you are notified that any dissemination, 
distribution or copying of this communication is strictly prohibited.
--- 
Le présent message électronique (y compris les pièces qui y sont annexées, le 
cas échéant) s'adresse au destinataire indiqué et peut contenir des 
renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le 
destinataire de ce document, nous vous signalons qu'il est strictement interdit 
de le diffuser, de le distribuer ou de le reproduire.
- Original Message - 
From: Anil [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Sunday, March 25, 2007 4:37 PM
Subject: [Axis2] AXIOM or JBIX


 Hi,
 
 I'm new to Axis2, what is the criteria to choose
 between POJO, AXIOM, JIBX, ADB or XMLBeans. How do we
 decide architecture wise. 
 
 My second question is, is wsdl file mandatory to
 create stub and skeleton interfaces or can we use just
 skeleton file to create wsdl file. 
 
 Thanks.
 
 
 
 
 Bored stiff? Loosen up... 
 Download and play hundreds of games for free on Yahoo! Games.
 http://games.yahoo.com/games/front
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]