You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by Romain Manni-Bucau <rm...@gmail.com> on 2012/05/03 23:58:39 UTC
Re: [jira] [Commented] (TOMEE-171) TomEE automatically directs
embedded (@DataSourceDefinition) h2 datasource to hsqldb
i added a test for it on trunk so we shouldn't miss it again ;)
well just ran the deployment, should be available soon
- Romain
2012/5/3 Henk de Boer (JIRA) <ji...@apache.org>
>
> [
> https://issues.apache.org/jira/browse/TOMEE-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267852#comment-13267852]
>
> Henk de Boer commented on TOMEE-171:
> ------------------------------------
>
> I've waited a few days, but unfortunately it seems the maven repo doesn't
> get updated anymore. It's stuck at 27 April.
>
> Maybe worse, the TomEE I downloaded from the official download page at
> http://openejb.apache.org/downloads.html is a version seemingly from 26
> April and doesn't have the JSF injections.
>
> I'm looking forward to test again, but I can't seem to get the latest
> version I'm afraid.
>
> > TomEE automatically directs embedded (@DataSourceDefinition) h2
> datasource to hsqldb
> >
> ------------------------------------------------------------------------------------
> >
> > Key: TOMEE-171
> > URL: https://issues.apache.org/jira/browse/TOMEE-171
> > Project: TomEE
> > Issue Type: Bug
> > Affects Versions: 1.0.0-beta-2
> > Environment: Mac OS X 10.6.8, JDK6u31, h2 1.3.161
> > Reporter: Henk de Boer
> > Attachments: crudh2_eclipseproject.zip
> >
> >
> > When trying to run an example CRUD application for Java EE 6 (see
> http://henk53.wordpress.com/2012/04/15/jsf2-primefaces3-ejb3-jpa2-integration-project)
> on TomEE beta 2, I noticed that the logs and data for the embedded h2
> datasource end up as hsqldb equivalents in [TOMEE HOME]/data/hsqldb/.
> > The datasource definition in web.xml is as follows:
> > {code:xml}
> > <data-source>
> > <name>java:app/MyApp/myDS</name>
> > <class-name>org.h2.jdbcx.JdbcDataSource</class-name>
> > <url>jdbc:h2:~/mydb;DB_CLOSE_DELAY=-1</url>
> > <user>sa</user>
> > <password>sa</password>
> > <transactional>true</transactional>
> >
> <isolation-level>TRANSACTION_READ_COMMITTED</isolation-level>
> > <initial-pool-size>2</initial-pool-size>
> > <max-pool-size>10</max-pool-size>
> > <min-pool-size>5</min-pool-size>
> > <max-statements>0</max-statements>
> > </data-source>
> > {code}
> > So clearly it should be using h2, and the DB should be created in my
> home as {{mydb}}. When I remove the h2 implementation jar from WEB-INF/lib,
> TomEE does complain, so it does try to do something with h2 for sure.
> Inspecting the log reveals it really are hsqldb log lines and not h2.
> > What's happening here? Why is TomEE silently swapping one DB for the
> other?
> >
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA
> administrators:
> https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>
Re: [jira] [Commented] (TOMEE-171) TomEE automatically directs
embedded (@DataSourceDefinition) h2 datasource to hsqldb
Posted by Romain Manni-Bucau <rm...@gmail.com>.
deploy task just ended
- Romain
2012/5/3 Romain Manni-Bucau <rm...@gmail.com>
> i added a test for it on trunk so we shouldn't miss it again ;)
>
> well just ran the deployment, should be available soon
>
> - Romain
>
>
> 2012/5/3 Henk de Boer (JIRA) <ji...@apache.org>
>
>
>> [
>> https://issues.apache.org/jira/browse/TOMEE-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267852#comment-13267852]
>>
>> Henk de Boer commented on TOMEE-171:
>> ------------------------------------
>>
>> I've waited a few days, but unfortunately it seems the maven repo doesn't
>> get updated anymore. It's stuck at 27 April.
>>
>> Maybe worse, the TomEE I downloaded from the official download page at
>> http://openejb.apache.org/downloads.html is a version seemingly from 26
>> April and doesn't have the JSF injections.
>>
>> I'm looking forward to test again, but I can't seem to get the latest
>> version I'm afraid.
>>
>> > TomEE automatically directs embedded (@DataSourceDefinition) h2
>> datasource to hsqldb
>> >
>> ------------------------------------------------------------------------------------
>> >
>> > Key: TOMEE-171
>> > URL: https://issues.apache.org/jira/browse/TOMEE-171
>> > Project: TomEE
>> > Issue Type: Bug
>> > Affects Versions: 1.0.0-beta-2
>> > Environment: Mac OS X 10.6.8, JDK6u31, h2 1.3.161
>> > Reporter: Henk de Boer
>> > Attachments: crudh2_eclipseproject.zip
>> >
>> >
>> > When trying to run an example CRUD application for Java EE 6 (see
>> http://henk53.wordpress.com/2012/04/15/jsf2-primefaces3-ejb3-jpa2-integration-project)
>> on TomEE beta 2, I noticed that the logs and data for the embedded h2
>> datasource end up as hsqldb equivalents in [TOMEE HOME]/data/hsqldb/.
>> > The datasource definition in web.xml is as follows:
>> > {code:xml}
>> > <data-source>
>> > <name>java:app/MyApp/myDS</name>
>> > <class-name>org.h2.jdbcx.JdbcDataSource</class-name>
>> > <url>jdbc:h2:~/mydb;DB_CLOSE_DELAY=-1</url>
>> > <user>sa</user>
>> > <password>sa</password>
>> > <transactional>true</transactional>
>> >
>> <isolation-level>TRANSACTION_READ_COMMITTED</isolation-level>
>> > <initial-pool-size>2</initial-pool-size>
>> > <max-pool-size>10</max-pool-size>
>> > <min-pool-size>5</min-pool-size>
>> > <max-statements>0</max-statements>
>> > </data-source>
>> > {code}
>> > So clearly it should be using h2, and the DB should be created in my
>> home as {{mydb}}. When I remove the h2 implementation jar from WEB-INF/lib,
>> TomEE does complain, so it does try to do something with h2 for sure.
>> Inspecting the log reveals it really are hsqldb log lines and not h2.
>> > What's happening here? Why is TomEE silently swapping one DB for the
>> other?
>> >
>>
>> --
>> This message is automatically generated by JIRA.
>> If you think it was sent incorrectly, please contact your JIRA
>> administrators:
>> https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>>
>>
>>
>