On Fri, 7 Nov 2003, Keith Kwiatek wrote:
> How is everyone building their web apps.... with hand coded programs, or
> using automagic tools?
I use JBuilder Enterprise 4 which does do skeletal work, including
matching up home & remote interfaces to the businessmethods of
beans, and it produces orion-friendly jar files.
> 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?
Hmm... jbuilder allows you to treat an EJB the same way other beans can be
modified wrt set/get methods and properties.
> You can't access ejb's directly from a jsp page (like a normal bean) can
> you?
Yes, you can, if you prepare the ground first.
> Any tools that will automagically wrap an ejb in a bean for
> presentation in a JSP?
Create a class that does the gruntwork for you, and put it in a useBean
declaration at the top of the page (jbuilder does this for you, and can
create skeletal client code too).
If it sounds like I have shares in Borland... heh. no.
alternatively, if deploying to Orion, use the ejb taglib supplied with the
demos (search for ejbtags.jar)
> Am I off base here, or are ejb's a lot more work? How can people talk about
> how EJB's "speed development time"....?!?
For distributed apps, it's much easier than raw RMI or CORBA. EJB also has
a better defined instantiation lifecycle. If you need those things (plus
all the other bits that EJB containers provide) then you can cut
development time, especially if you're using tools... but I won't do any
more evangelism here :)
-[ Joshua Goodall ]-----------------------------------------------
-[ Chief Systems Architect, IP R&D ]----- Cook, Geek, Lover ------
-[ [EMAIL PROTECTED] ]--------------- [EMAIL PROTECTED] --
