The J2EE RI�s DeployTool (which I usually use to package for major builds)
has a set of tests designed for checking whether your
.ear suits the specs. Also, whenever EJB 2.0 is available, you'll have a lot
of IDE's compiting to make it easier on the programmer; under the risk of
being flamed (again), check out http://www.pramati.com for an evaluation
version of Pramati Studio 2.0 beta, which is what I use for developing +
debugging + packaging (and generating descriptors in an easy yet very
complete way)
Many of the problems I'm facing now reside in the complexity of
architechting solutions + bugs/unexpected behavior from the part of my App
Server (which will keep on being Orion for any forseeable future)-- and I'm
glad that there aren't any automated tools that detect these, for when they
become available, I'll be out of the job.... ;-)
HTH,
JP
-----Original Message-----
From: Duffey, Kevin [mailto:[EMAIL PROTECTED]]
Sent: Mi�rcoles, 08 de Noviembre de 2000 17:29
To: Orion-Interest
Cc: [EMAIL PROTECTED]
Subject: RE: There has GOTTA be a BETTER way !!!!
My take on EJB is that while they seem to be more work (now that I have done
it a couple of times..but I am far from pro caliber here), they are actually
a bit less work if you are using CMP, instead of BMP. However, I have heard
that EJB 2.0 CMP is more complicated, and it along the same amount of work.
What scares the hell out of me is all the descriptor xml files. When you
make a change in code..you can build it and see problems if they exist. When
editing XML files, its not immediately apparent if there is a problem in a
CMP mapping, a reference tag, etc. Only when you try to run the app do you
see the problem. It would be nice if there was some auto-mated tool that
would look at the source (or compiled classes) and sort of "compile" an xml
file and flag if errors exist. I don't see that happening though..probably
too much work to get that to work right.
> -----Original Message-----
> From: Keith Kwiatek [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, November 07, 2000 11:48 AM
> To: Orion-Interest
> Cc: [EMAIL PROTECTED]
> Subject: Re: There has GOTTA be a BETTER way !!!!
>
>
> Does anyone know if jdeveloper (which is based on Jbuilder)
> has the same
> functionality?
>
> Keith
>
> ----- Original Message -----
> From: Cory Adams <[EMAIL PROTECTED]>
> To: Orion-Interest <[EMAIL PROTECTED]>
> Sent: Tuesday, November 07, 2000 9:34 AM
> Subject: Re: There has GOTTA be a BETTER way !!!!
>
>
> > JBuilder 4 Enterprise allows you do build Entity CMP beans
> this way. You
> > can connect to a datasource and then select tables and keys for your
> beans.
> > It's wild. I'm still getting used to it.
> >
> > Can anybody else with more experience using this tool give
> us a little
> > insight?
> >
> > Thanks,
> >
> > Cory
> >
> > At 10:34 AM 11/7/03 -0500, Keith Kwiatek wrote:
> > >Hello,
> > >
> > >EJB's are great.... if you like tripling the amount of
> code you have to
> > >write....
> > >
> > >How is everyone building their web apps.... with hand
> coded programs, or
> > >using automagic tools?
> > >
> > >It sure seems like there should be some sort of tool that
> you can just
> point
> > >at database tables, and have it build the jsp or ejb
> entity bean. AND
> > >shouldn't there be a tool that you can just drop the bean
> on an html
> > >template thus allowing visual access to the bean fields?
> > >
> > >You can't access ejb's directly from a jsp page (like a
> normal bean) can
> > >you? Any tools that will automagically wrap an ejb in a bean for
> > >presentation in a JSP?
> > >
> > >Am I off base here, or are ejb's a lot more work? How can
> people talk
> about
> > >how EJB's "speed development time"....?!?
> > >
> > >Keith
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
>
