Well...

If someone implements the full specification, and a developer writes code that
only uses the features outlined in the specification, then an EJB implementation
wouldn't be proprietary.

But, with the recent growth in app server vendors, they compete (along with
other things) by adding additional features which go _beyond_ the specification.
A developer that takes advantage of such features in a specific app server
would, then, be writing a proprietary EJB implementation that couldn't be ported
as-is to another app server.

Anyway, sounds like a nomenclature issue more than a practical issue to me. :-)

/Jonas

On Fri, 25 Aug 2000, Nail A. wrote:

> > BC4Js are proprietary EJB like components that you can only deploy to >
> oracle app. servers and databases.
>
> Dear friends,
> Sun introduced the EJB's as a server-side component-model. The
> basic idea was a component-model for component-based app-servers.
>
> Well, in consequence of the idea of reusable components
> it should be possible to deploy each EJB to each other Application-Server
> which claims to be conformable to the EJB-Standard!
>
> If you talk about "proprietary EJB", i believe that this is wrong. You
> can talk about "proprietary components" (especially if you talk about that
>
> product from Oracle), but my understanding of EJB's is, that it is a
> standardised component model, which can NOT be proprietary.
>
> Please have a look at the EJB-specification_1.1/2.0.
>
> regards
> Nail
>
> --
> Sent through GMX FreeMail - http://www.gmx.net
>
> ===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff EJB-INTEREST".  For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
>
>

===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST".  For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".

Reply via email to