[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [eclipselink-users] Eclipselink persistence.xml on Tomcat 6.0 error
|
Hi michael,
Doesn't JBoss use Tomcat by default as web container? Do you know of any
issues of using JNDI in, say a Sun Glassfish setup?
-J.
> Leon,
> Hi, the eclipselink property is
>
> eclipselink.session.customizer
> http://wiki.eclipse.org/Customizing_the_EclipseLink_Application_(ELUG)
>
> persistence.xml:
> <property name="eclipselink.session.customizer"
> value="org.eclipse.persistence.example.unified.integration.JPAEclipseLinkSessionCustomizer"/>
>
> JPAEclipseLinkSessionCustomizer.java:
> // Change from Composite to String_Lookup
> connector.setLookupType(JNDIConnector.STRING_LOOKUP);
>
> I ran into the same Composite/String JNDI issue when deploying to JBoss
> 4.2.2 and required the use of a similar SessionCustomizer like the
> java.net post, however deploying to OC4J 11 did not require one. It
> looks like these issues may be due to the Tomcat and JBoss
> implementations as OC4J works fine without it. I am going to checkout
> Tomcat 6 and reproduce this issue.
>
> /michael
>
>
> -----Original Message-----
> From: Leon Derks [mailto:leon.derks@xxxxxxxxxx]
> Sent: Thursday, April 24, 2008 2:25 AM
> To: EclipseLink User Discussions
> Subject: Re: [eclipselink-users] Eclipselink persistence.xml on Tomcat
> 6.0 error
>
>
> Hello
>
> What is the eclipselink property for the old property
> name="toplink.session.customizer"?
> And is this an eclipselink or tomcat bug?
>
> Leon
>
>
> Leon Derks wrote:
>> Hello
>>
>> Today I tried to run my application on Tomcat 6.0
>>
>> I replaced the connection properties in persistence.xml into
>> <non-jta-data-source>java:comp/env/jdbc/appDS</non-jta-data-source>
>>
>> When I use <non-jta-data-source>jdbc/appDS</non-jta-data-source> I get
>> an "javax.naming.NameNotFoundException: Name jdbc is not bound in this
>> Context"
>>
>> When I use
>> <non-jta-data-source>java:comp/env/jdbc/appDS</non-jta-data-source> I
>> get an "javax.naming.NamingException: This context must be accessed
>> throught a java: URL"
>>
>> This is the same problem as described in:
>> http://forums.java.net/jive/message.jspa?messageID=158622
>>
>> There was also found a solution by adding <property
>> name="toplink.session.customizer"
>> value="com.company.application.JPAToplinkSessionCustomizationUtil"/>
>> to the persistence.xml
>>
>> But is this with eclipselink still necessary?
>>
>> Leon
>>
>>
>>
>>
>> _______________________________________________
>> eclipselink-users mailing list
>> eclipselink-users@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/eclipselink-users
>>
>>
>
> _______________________________________________
> eclipselink-users mailing list
> eclipselink-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipselink-users
> _______________________________________________
> eclipselink-users mailing list
> eclipselink-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipselink-users
>
>
