IMHO: EJB is the best option. If JOnAS doesn't do it for you, you can
'upgrade' to a commercial server with little effort. Watch out for adding
vendor specific stuff to your client or EJBs. Also be wary of the
limitations of applets.
> I know my title may seem a bit irrelevant, since JOnAS and Enhydra are
> coming together in Enhydra Enterprise, but I'm trying to work out my
> development strategy for a project I'm working on and am trying to
> choose between EJB or Enhydra's tools, such as DODS.
>
> I'm porting an existing database for use on a departmental intranet. In
> the near future (next few months) there will be more databases coming,
> and some of them will be accessed on a company-wide basis.
>
> I'm leaning toward JOnAS, but wanted to do a sanity check with this
> group before committing to anything. I'd like to use a Java/JFC applet
> for the client and it seems that EJB is a better fit for this than
> servlets. However, I just don't want to get too far down the road with
> JOnAS, only to find that it's not quite ready for a production project.
> Looking at the JOnAS FAQ, it seems that it's currently used mostly for
> prototyping and research projects. (See "Is there a list of customers
> that currently use JOnAS?" under the General category.)
>
> It looks like some exciting things are coming with Enhydra Enterprise,
> and it seems that the EJB work I do for JOnAS will be able to run on
> that platform, but am I rushing too quickly into an emerging
> technology? I also wonder if EJB is overkill considering the scope of
> my project?
>
> TIA for any insights.
>
> Jim Caley
> Graco Children's Products
> Elverson, PA
>
> P.S. In the interest of full disclosure, I'm cross-posting a similar
> message on the Enhydra mailing list to get a perspective from that
> group. :)
> ----
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
