[JBoss JIRA] (JBIDE-13855) Invalid JPA Error message for Hibernate Joined inheritance
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13855?page=com.atlassian.jira.plugi... ]
Koen Aers commented on JBIDE-13855:
-----------------------------------
Hi Cody,
Can you please explain me in detail what I need to do to reproduce the problem? I have created the above class with JBoss Tools 4.1.0.Final and I don't see any error messages.
Regards,
Koen
> Invalid JPA Error message for Hibernate Joined inheritance
> ----------------------------------------------------------
>
> Key: JBIDE-13855
> URL: https://issues.jboss.org/browse/JBIDE-13855
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.0.0.Final
> Reporter: Cody Lerum
> Assignee: Koen Aers
> Fix For: 4.0.x
>
>
> Discriminator column "DTYPE" cannot be resolved on table "Order_"
> In this case
> {code}
> @Entity
> @Inheritance(strategy = InheritanceType.JOINED)
> @Table(name = "Order_")
> public abstract class Order implements Serializable
> {code}
> Hibernate does not require the use of a Discriminator column
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15614) Rename EAP 6.1 server type to 6.1+, ensure runtime detection is accurate
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15614?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-15614:
---------------------------------------
[~rob.stryker], I just found out that I cannot connect to the server (EAP 6.2.0.ER4/ER5) in MBean explorer - it shows the server as [disconnected] and cannot be connected. This was with JBDS 7.1.0.Alpha2 B431. Is it related to what you described above?
> Rename EAP 6.1 server type to 6.1+, ensure runtime detection is accurate
> ------------------------------------------------------------------------
>
> Key: JBIDE-15614
> URL: https://issues.jboss.org/browse/JBIDE-15614
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: runtime-detection, server
> Affects Versions: 4.1.0.Final
> Environment: JBDS 7.0.0.GA
> Reporter: Martin Malina
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.1.Beta1
>
>
> 1. When you try to add EAP 6.2 using runtime detection, it detects it as EAP 6.0.
> 2. When trying to add EAP 6.2 manually, there is no type EAP 6.2
> Let me know if you want subtasks for these two.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBTIS-186) ModeShape sometimes doesn't publish all models of Teiid VDB
by Lucie Fabrikova (JIRA)
[ https://issues.jboss.org/browse/JBTIS-186?page=com.atlassian.jira.plugin.... ]
Lucie Fabrikova commented on JBTIS-186:
---------------------------------------
In the console of server, there was:
13:48:42,536 INFO [org.hibernate.search.store.impl.DirectoryProviderHelper] (http-localhost/127.0.0.1:8080-2) HSEARCH000041: Index directory not found, creating: '/home/jbossqa/workspace/jbtis.modeshape.bot.tests.single/tests/org.jboss.tools.modeshape.ui.bot.test/target/requirements/jboss-eap-6.1/standalone/data/modeshape/dv/indexes/nodeinfo'
13:49:59,805 ERROR [org.modeshape.jcr.SequencingRunner] (modeshape-sequencer-8-thread-3) The 'teiid-model-sequencer' sequencer of repository 'dv' had an error while processing '/files/ModeShapeGoodies/RelModels/Books_Oracle.xmi/jcr:content/jcr:data' in workspace 'default' and generating output '/derived/teiid/models/ModeShapeGoodies/RelModels/Books_Oracle.xmi': javax.jcr.RepositoryException: The session with an ID of '75fd022ad' has been closed and can no longer be used.
at org.modeshape.jcr.JcrSession.checkLive(JcrSession.java:285) [modeshape-jcr-3.3.5.GA-redhat-1.jar:3.3.5.GA-redhat-1]
at org.modeshape.jcr.JcrSession.getValueFactory(JcrSession.java:1203) [modeshape-jcr-3.3.5.GA-redhat-1.jar:3.3.5.GA-redhat-1]
at org.modeshape.jcr.JcrSession.getValueFactory(JcrSession.java:123) [modeshape-jcr-3.3.5.GA-redhat-1.jar:3.3.5.GA-redhat-1]
at org.modeshape.sequencer.teiid.model.ModelNodeWriter.writeUnresolvedReferences(ModelNodeWriter.java:207)
at org.modeshape.sequencer.teiid.model.ModelNodeWriter.write(ModelNodeWriter.java:161)
at org.modeshape.sequencer.teiid.model.ModelSequencer.sequenceModel(ModelSequencer.java:187)
at org.modeshape.sequencer.teiid.model.ModelSequencer.execute(ModelSequencer.java:98)
at org.modeshape.jcr.SequencingRunner.run(SequencingRunner.java:227) [modeshape-jcr-3.3.5.GA-redhat-1.jar:3.3.5.GA-redhat-1]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_39]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_39]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_39]
13:50:20,652 INFO [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue1) ModeShapeExecutionFactory Commit=true;DatabaseProductName=ModeShape;DatabaseProductVersion=3.3.5.GA-redhat-1;DriverMajorVersion=3;DriverMajorVersion=3;DriverName=ModeShape JDBC Driver for JCR;DriverVersion=3.3.5.GA-redhat-1;IsolationLevel=0
Resulting contents of the ModeShape VDB: Books_Oracle.xmi: false, BooksInfo.xmi: true
> ModeShape sometimes doesn't publish all models of Teiid VDB
> -----------------------------------------------------------
>
> Key: JBTIS-186
> URL: https://issues.jboss.org/browse/JBTIS-186
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: modeshape
> Affects Versions: 4.1.3
> Environment: Ubuntu 12.04, JBTIS 4.1.3.Beta4, DV 6.0.0.ER2, sun jdk 1.6
> Reporter: Lucie Fabrikova
> Attachments: BooksMode.vdb
>
>
> If I publish a teiid VDB with relational models .xmi in given environment, sometimes some (or all) of the models are not published.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months