axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "robert lazarski" <robertlazar...@gmail.com>
Subject Re: Recommendations for a new project?
Date Mon, 28 May 2007 16:35:50 GMT
JIBX has its own site and docs - I'd follow those to get on the right track.


Robert

On 5/28/07, Michael.Davis@servicecanada.gc.ca <
Michael.Davis@servicecanada.gc.ca> wrote:
>
>  Thanks very much. I am using Hibernate and fortunately I have complete
> control over the schema, so I'll check out jibx.
>
> So assuming I'm creating my own wsdl and will use jibx, would you generate
> code using wsdl2java or would you start from scratch? I suspect that
> starting from scratch will allow for cleaner and simpler code in the long
> run, because as the number of operations grows then there will be more
> opportunities for refactoring code rather than having lots of redundant
> generated code, am I right?
>
> cheers
> md
>
> -----Original Message-----
> *From:* robert lazarski [mailto:robertlazarski@gmail.com]
> *Sent:* Monday, May 28, 2007 12:18 PM
> *To:* axis-user@ws.apache.org
> *Subject:* Re: Recommendations for a new project?
>
> From what you say I'd go with ADB databinding, creating and validating
> your WSDL via eclipse's WST. If you are using hibernate / jdo and such, I'd
> consider jibx. If you have complex schemas out of your control - which is
> often the case for me - use xmlbeans. Either way, starting with the WSDL for
> a 'contract first' approach is often a good choice.
>
> If you've never done single sign on before I recommend CAS:
>
> http://www.ja-sig.org/products/cas/
>
> See rampart for ws-security - available for axis2 1.1.1 . Search the
> archives for questions related to soap headers as the subject comes up
> frequently.
>
> HTH,
> Robert
>
> On 5/28/07, Michael.Davis@servicecanada.gc.ca <
> Michael.Davis@servicecanada.gc.ca> wrote:
> >
> > I forgot to mention, in case it's important. I'm using axis2 1.1.1,
> > because due to circumstances beyond my control, I'm forced to use jdk
> > 1.4.2 and WebSphere 6.1, and I couldn't get axis2 1.2 to work with that
> > combination.
> >
> > md
> >
> > > -----Original Message-----
> > > From: Michael.Davis@servicecanada.gc.ca
> > > [mailto:Michael.Davis@servicecanada.gc.ca ]
> > > Sent: Monday, May 28, 2007 11:44 AM
> > > To: axis-user@ws.apache.org
> > > Subject: Recommendations for a new project?
> > >
> > >
> > > Hi,
> > >
> > > I apologize in advance for a slightly rambling and unfocussed
> > > request for advice. The short questions are: if you are a
> > > really experienced Axis user, and are starting a brand new
> > > project, would you write everything from scratch using Axiom?
> > > Would you use one of the data binding libraries such as JiBX?
> > > Would you maintain your wsdl/xsd files by hand?
> > >
> > > Now for the long version:
> > >
> > > I'm new to Axis and web services, but have been programming
> > > Java for several years.
> > >
> > > I'm working on a simple web service that provides a
> > > single-sign-on for our organization's applications. The first
> > > operation I'm working on is very simple - it just takes three
> > > strings (user name, password and application name) and
> > > returns a string containing a list of permissions.
> > >
> > > It works fine, but I've implemented it using the easiest way
> > > possible. I just wrote a POJO class with a method
> > >
> > > String authenticate( String, String, String )
> > >
> > > and ran Java2Wsdl using the basic defaults. I don't
> > > explicitly use any of the Axis apis.
> > >
> > > However, looking to the future, I can see where I'll
> > > eventually need to take more control, for example I might
> > > want to manipulate the SOAP headers and/or use WS-Security,
> > > and I'll probably eventually want to pass around more
> > > complicated structures than strings.
> > >
> > > So I'm trying to determine the best strategy. I'm slightly
> > > bewildered with all of the choices:
> > >
> > > 1. Should I write the clients and services from scratch using
> > > the axiom libraries, or generate the stubs and skeletons?
> > >
> > > 2. If I write them from scratch, and already have my own
> > > model classes (representing such things as users), should I
> > > use one of the data binding libraries such as XMLBeans or
> > > JiBX? If so, which one?
> > >
> > > 3. Should I be maintaining my wsdl file (and included schema
> > > files) by hand (or using an appropriate editing tool) in
> > > order to maitain control over the various types, as opposed
> > > to generating it using Java2Wsdl every time the interface changes?
> > >
> > > I can see that the Axis developers have tried hard to provide
> > > a spectrum of methods and interfaces from the easy/simple to
> > > the complex/powerful. But I'd be very interested to know what
> > > methods a really experienced Axis user would use.
> > >
> > > Many thanks,
> > > Michael Davis
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: axis-user-help@ws.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >
>

Mime
View raw message