Oh and one more thing.. This plugin is designed to add any sort of
annotation to classes and methods, not just for ejb3. I thought it
might be useful for other purposes.
> -----Original Message-----
> From: Scott Allan [mailto:sallan1000_at_aol.com]
> Sent: Wednesday, August 17, 2005 8:58 AM
> To: users_at_jaxb.dev.java.net
> Subject: RE: Plugin for EJB 3.0 annotations
>
>
> I agree with both of you. I had considered making it more
> intuitive but considering my lack of programming experience,
> I wanted to come up with the simplest, most customizable
> model possible just to learn how it worked, have a plugin
> example others could refer to, and get it done fairly
> quickly. EJB3 does not seem to require that every element be
> annotated. The defaults seem to cover most scenarios.
>
>
>
> I'd like to get involved in the hyperjaxb3 but I have to
> admit I'm not sure how I could really contribute. I'm a
> self-taught programmer and I have no one to really show me
> the ropes. I never would have been able to have figured this
> out without Kohsuke's help and patience.
>
>
>
> Thanks again for all your advice. I really appreciate it.
>
>
>
>
>
>
>
> > -----Original Message-----
>
> > From: Aleksei Valikov [mailto:valikov_at_gmx.net]
>
> > Sent: Wednesday, August 17, 2005 3:49 AM
>
> > To: users_at_jaxb.dev.java.net
>
> > Subject: Re: Plugin for EJB 3.0 annotations
>
> >
>
> >
>
> > Hi.
>
> >
>
> > > It would be nice if this add-on would be hosted on java.net. The
>
> > > jaxb-commons project seems like an excellent place to host this,
>
> > > assuming that Lexi the project owner is OK with it. It
>
> > makes it easier
>
> > > for others to contribute. Lexi, how do you think?
>
> >
>
> > I think we'll need jaxbcommons2 since jaxbcommons is JAXB 1.x based.
>
> > However, ejb3 plugin seems to me much more than "commons", it is a
>
> > standalone plugin and needs a separate project, I think.
>
> >
>
> > I have already suggested joining ejb3 plugin in hyperjaxb3...
>
> > Scott, let
>
> > me know if that could be an option for you.
>
> >
>
> > > I also wonder if your plugin can automatically infer the necessary
>
> > > EJB3
>
> > > annotations from schemas as much as possible. I'm not an
>
> > EJB expert, so
>
> > > I'm not too sure, but for example I'd imagine you need to
>
> > put @Entity on
>
> > > every persistable class. If so, isn't it easier if you just
>
> > put them on
>
> > > all classes, without asking the user to put <ejb3:Entity />
>
> > on every
>
> > > complex type?
>
> >
>
> > You're absolutely right, Kohsuke. JAXB provides anough
> information to
>
> > understand the field nature (primitive, enum, dom,
> wildcard, complex,
>
> > hetero - my favorite classification), cardinality (single,
>
> > collection)
>
> > and class hierarchy. From this information, plugin can theoretically
>
> > generate all the required annotations automatically. I do not
>
> > think that
>
> > making users annotate each and every element is the right way to go.
>
> > Plugin should generate default ejb3 annotations automatically
>
> > and allow
>
> > their customizations, if required.
>
> >
>
> > Bye.
>
> > /lexi
>
> >
>
> >
> ---------------------------------------------------------------------
>
> > To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
>
> > For additional commands, e-mail: users-help_at_jaxb.dev.java.net
>
> >
>
> >
>
>
>
>
> _____
>
> << ella for Spam Control >> has removed 25444 Spam messages
> and set aside 2 Newsletters for me
> You can use it too - and it's FREE! www.ellaforspam.com
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
> For additional commands, e-mail: users-help_at_jaxb.dev.java.net
>
>
_____
<< ella for Spam Control >> has removed 25444 Spam messages and set
aside 2 Newsletters for me
You can use it too - and it's FREE! www.ellaforspam.com