Hi Chris,
You raise an interesting point that has also been raised my Microsoft and its
proponents as an argument against J2EE in general.
The idea of J2EE is to provide a base standard for distributed, enterprise
applications written in Java. But another driving idea behind J2EE is "vendor
value-add," i.e., the idea that vendors make their bread and butter in part by
extending and enriching their containers and components beyond the spec
standards.
Microsoft and others have attacked J2EE (and especially EJB) for being a
cross-purposes. Here's an excerpt from an article at Microsoft:
"Portability
Portability of enterprise beans across implementations from different vendors is
frequently cited as a primary goal of EJB. In fact, the EJB specification states
'An enterprise bean can be developed once and then deployed on multiple
platforms without recompilation or source code modification.' Yet the
specification also states that 'specialized containers can provide additional
services beyond those defined by the Enterprise JavaBeans specification. An
enterprise bean that depends on such a service must be deployed only in a
container that supports the service.' In practice, this is all but certain to
lead to significant differences among products supporting Enterprise JavaBeans,
which brings into question its validity as a standard."
http://outlook.microsoft.com/com/wpaper/mts-ejb.asp
There's a risk there, to be sure. But there's always the standard way to fall
back on. Chris, you are saying that the JRun docs emphasize the JRun-specifics
too much, right? In some areas I'd totally disagree, such as how to write and
deploy servlets and custom tags. But on EJBs, I agree that there is no where
near enough documentation on how to do things the EJB 1.1 way, hence all the
Ejipt properties files documentation.
Ejipt was a compliant EJB 1.0 server. But in EJB 1.0 there was no such thing as
ejb-jar.xml, or even any requirement that servers support Entity beans! Ejipt
is also a very compliant 1.1 server, but the documentation doesn't reflect it
very well. That's because a lot of the docs were "ported" from Ejipt's existing
doc set, which primarily covered the EJB 1.0 stuff. So for the most part, you
should be able to use off-the-shelf books on J2EE/EJB as guides for developing
with JRun 3.0. Of course this is barring any bugs in JRun. One thing to watch
out for is the processing of the ejb-jar.xml and empty elements. If an element
should be empty, don't include it. Otherwise you may get errors when trying to
run the bean in the server. I believe this has been fixed in JRun 3.0 SP1,
which should be out next week.
There will always be server-specific information that the System Administrator
role needs to access. That's a large part of what deploy.properties is for.
Most if not all bean-related information from deploy.properties can go into
env-entries in the ejb-jar.xml. But you wouldn't want to specify server ports
or database names in ejb-jar.xml because that stuff can't be guaranteed to be
portable.
Can you point to a more specific reference in section 14 of the EJB 1.1 spec
where you found a problem? I will evaluate it and make sure it's entered as a
bug if it is one.
Scott Stirling
Allaire
> -----Original Message-----
> From: Chris Wilson [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, September 21, 2000 11:41 AM
> To: JRun-Talk
> Subject: Following the J2EE specs, WAS: RE: [JRun-Talk] Non-Jrun
> specific way to get local EJBHomeObject?
>
>
> i like jrun too. but i'm a little annoyed at their docs for promoting all
> these jrun specific ways of doing things (ResourceManager, etc.). the whole
> point of j2ee is not to be locked into one vendors particular product/api.
> it would be nice if allaire documented how to jrun in the manor specified by
> the j2ee specs. for example, try managing datasources as the ejb 1.1 spec
> defines in section 14. you can't do it with jrun. the servlet/jsp support
> is very good and i can do things outlined in the servlet 2.2 spec with
> relative ease. however ejipt (the ejb container) is a another story. seems
> as if it was a quick port from some non spec ejb 1.0 server. this whole
> reliance on the deply.properties is pretty stupid. let me do stuff in the
> ejb-jar.xml file like sun says i should.
>
> moral of the story: the servlets/jsp are quite good in jrun (speed issues
> ignored), ejipt needs MUCH more work.
>
> cheerio,
> chris
>
> | chris wilson || web dev ||| www.wondergeek.com || |
------------------------------------------------------------------------------
Archives: http://www.egroups.com/group/jrun-interest/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk
or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the
body.
