Gero -
You might want to take a look in weblogic-ejb-jar.xml. These are all the
deployment settings which are specific to WLS (caching, persistence
behaviour, clustering config etc). These are all areas where WLS offer
vendor-specific enhancements. Other than this, I _think_ they are
EJB1.1. compliant.
paul.
Gero Vermaas wrote:
>
> Hi,
>
> I'm evaluating WebLogic 5.1 and I'm trying to get picture of WebLogic
> specific
> features that are not compliant with/included in the J2EE 1.2 specification.
> I'd like to know this in order to prevent a vendor lock-in when using
> WebLogic.
>
> In the perfect world it would be possible to switch from one appserver to
> another by simply taken the .EAR file en redeploying it. I don't think that
> is
> reality at this moment, unfortunately.
>
> Two things I've seen till now are (after a quick look):
> - The optimizations that can be done for persistency in de DeployerTool for
> Container managed beans.
> - It does not seem possible to deploy and EAR file. You have to deploy the
> EJB
> JAR file and Servet WAR files separately.
>
> Any other non-compliance issues?
>
> Regards,
>
> Gero Vermaas
>
> ===========================================================================
> 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".
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
===========================================================================
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".
