I found some great cxf related documentation at this page when
checking request context recently:

http://open.iona.com/docs/framework/2.0/jaxws/index.html?url=http://open.iona.com/docs/framework/2.0/jaxws/JAXWSContextsService.html

this kind of stuff will help!

On 2/1/08, Daniel Kulp <[EMAIL PROTECTED]> wrote:
>
> OK.   Let's flip this around a bit...   Describe the type of example that
> would (or would have) helped you do what you wanted to do.  We can work
> to get one in place.
>
> CXF has a bunch of samples already that cover a large variety of
> different configuations and samples.  Knowing where they are deficient
> can help us get them improved.
>
> Dan
>
>
> On Thursday 31 January 2008, Phil Gibbs wrote:
> > Well, I have to agree.  The docs seem to be the last thing that a
> > developer thinks about - because it's so obvious right?  CXF, like a
> > lot of software, badly needs some end to end examples at the very
> > least.
> > Currently, it's very lacking, as was XFire!
> >
> > Mayank Thakore-2 wrote:
> > > well, i have spent a lot of time getting cxf to work.
> > > but migrating from xfire, our code reduced from about 1200 lines to
> > > 200 lines.
> > > and i find cxf to be very extensible
> > >
> > > but it's not just coincidence that someone was talking about a book
> > > on cxf just today...
> > >
> > > Regards
> > > Mayank
> > >
> > > On Jan 23, 2008 8:36 PM, jonathan doklovic <[EMAIL PROTECTED]> wrote:
> > >> The point being that since this is a users list (not a dev list) I
> > >> thought I'd share my user experience in hopes that it could help
> > >> the future of the project.
> > >>
> > >> If all anyone hears about a project is how great it is and never
> > >> hears why people choose not to use it, then it never progresses.
> > >>
> > >> I was never able to get CXF working properly simply because of the
> > >> lack of simple docs and end-to-end examples.  Maybe it's just that
> > >> I don't get it or something, but I feel there are probably a lot of
> > >> "me's" out there that struggle with getting things up and running.
> > >>
> > >> - Jonathan
> > >>
> > >> On Wed, 2008-01-23 at 14:47 +0000, Sergey Beryozkin wrote:
> > >> > > After spending about 2 weeks trying to get a very simple
> > >> > > service to return JSON in CXF, I found the Glassfish Metro
> > >> > > project and it's jaxws-json plugin.
> > >> >
> > >> > What's the point of this post ? Say to the world that you're not
> > >> > happpy with CXF ?
> > >> > Or tell everyone that you could've commited a patch after
> > >> > spending 2 days on it but just didn't get enough time :-) ?
> > >> >
> > >> > Cheers, Sergey
> > >> >
> > >> >
> > >> >
> > >> > ----- Original Message -----
> > >> > From: "jonathan doklovic" <[EMAIL PROTECTED]>
> > >> > To: "cxfuser" <cxf-user@incubator.apache.org>
> > >> > Sent: Wednesday, January 23, 2008 2:37 PM
> > >> > Subject: Leaving CXF for Glasshfish Metro
> > >> >
> > >> > > Hi,
> > >> > >
> > >> > > After spending about 2 weeks trying to get a very simple
> > >> > > service to return JSON in CXF, I found the Glassfish Metro
> > >> > > project and it's jaxws-json plugin.
> > >> > >
> > >> > > I gave it a shot and after 2 hours had my service up and
> > >> > > running. Not only that, but the plugin generates pretty api
> > >> > > docs at the
> > >> >
> > >> > endpoint
> > >> >
> > >> > > for me as well as generates a javascript client on the fly.
> > >> > >
> > >> > > It was just too easy to make me stick with CXF.
> > >> > >
> > >> > > I think CXF is probably a good framework, but the docs and
> > >> > > examples
> > >> >
> > >> > are
> > >> >
> > >> > > in pieces and without real life end-to-end tutorials, it's
> > >> > > really
> > >> >
> > >> > hard
> > >> >
> > >> > > to get things working.
> > >> > >
> > >> > > - Jonathan
> > >> >
> > >> > ----------------------------
> > >> > IONA Technologies PLC (registered in Ireland)
> > >> > Registered Number: 171387
> > >> > Registered Address: The IONA Building, Shelbourne Road, Dublin 4,
> > >>
> > >> Ireland
>
>
>
> --
> J. Daniel Kulp
> Principal Engineer, IONA
> [EMAIL PROTECTED]
> http://www.dankulp.com/blog
>

Reply via email to