Re: EJB v2 and EJB v3 conflict when deploying .ear

Hello Scott,

On ke, hein=E4kuu 5, 2006 16:52, Scott Ferguson wrote:
>
> On Jul 5, 2006, at 2:37 AM, Tero Ripattila wrote:
>
>> Hello all, I'm trying to deploy an .ear, but ran into troubles. Resin
>> seems to think that I'd like to use EJB v3 (Amber) when I'm not.
>>
>> This is how I've got ejb-server block set up in my resin-web.xml:
>>
>> <ejb-server>
>>   <config-directory>WEB-INF</config-directory>
>> </ejb-server>
>>
>> Is there a way to declare which EJB version to use in ejb-server
>> tag or so?
>
> I think you're just missing a jndi-name
>
> <ejb-server jndi-name=3D"java:comp/env/cmp">
>    <config-directory>...</config-directory>
> </ejb-server>
>

Actually I do have that jndi-name now as I figured out by myself that I
need it. It's not making any difference here thought.

	<ejb-server>
		<jndi-name>java:comp/env/ejb</jndi-name>
		<config-directory>/WEB-INF</config-directory>
	</ejb-server>


> EJB 2.1 and JPA (Amber/EJB 3.0) use different discovery mechanisms,
> so Resin can tell which version to use based on how it's configured.
>

OK.

> EJB 2.1 uses the ejb-jar.xml.

Does one still need these *.ebj files or are ejb-jar.xmls enough?

> JPA uses META-INF/persistence.xml.
>

-- Tero