[JBoss JIRA] Created: (JBIDE-3795) Hibernate Config view cannot create JPA based configuration with @GeneratedValue using a @GenericGenerator
by Bob Thule (JIRA)
Hibernate Config view cannot create JPA based configuration with @GeneratedValue using a @GenericGenerator
----------------------------------------------------------------------------------------------------------
Key: JBIDE-3795
URL: https://jira.jboss.org/jira/browse/JBIDE-3795
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 3.0.0.CR2
Environment: Hibernate Tools 3.2.4.GA-N200902101801, Java Persistence API Tools 2.1.0.v200812180210
Reporter: Bob Thule
This may be related to issue JBIDE-3636. https://jira.jboss.org/jira/browse/JBIDE-3636
With a @GenericGenerator declared as:
@GenericGenerator(name = "SeqBase",... ) //either in package-info.java or on the class
and used with:
@GeneratedValue(generator = "SeqBase") private Long id;
when in the "Hibernate Config" view and the hibernate configuration is trying to be displayed or rebuilt, Eclipse gives the following exception:
org.hibernate.console.HibernateConsoleRuntimeException: Could not create JPA based Configuration
Could not create JPA based Configuration
<No message>
java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException: <no message>
java.lang.reflect.InvocationTargetException
javax.persistence.PersistenceException: org.hibernate.AnnotationException: Unknown Id.generator: SeqBase
org.hibernate.AnnotationException: Unknown Id.generator: SeqBase
org.hibernate.AnnotationException: Unknown Id.generator: SeqBase
Unknown Id.generator: SeqBase
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] Created: (JBIDE-5284) Warning related to incorrect Seam project name don't appear
by Aliaksey Nis (JIRA)
Warning related to incorrect Seam project name don't appear
-----------------------------------------------------------
Key: JBIDE-5284
URL: https://jira.jboss.org/jira/browse/JBIDE-5284
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.1.0.CR1
Environment: WindowsXP SP2
JBoss Tools
Version: 3.1.0.CR1
eclipse-SDK-3.5RC3-win32.zip
Build id: JBossTools-Update-3.1.0.v200911251807N-H130-RC1
JRE 1.6
Reporter: Aliaksey Nis
Priority: Optional
Attachments: NoWarningSeam.JPG
Related to JBIDE-5223
EXECUTE: New Seam project.
EXECUTE: Input name "blahblah+".
EXECUTE: Press next few times.
ASSERT: At step "Web module" button Next is in disable state, due to incorrect project name.
FAILURE: No warning appears. It appears only if you press Back, then Next again.
Screenshot attached.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] Created: (JBDS-904) JBDS 2.1 GA, JBPM and Seam
by Gary Lamperillo (JIRA)
JBDS 2.1 GA, JBPM and Seam
--------------------------
Key: JBDS-904
URL: https://jira.jboss.org/jira/browse/JBDS-904
Project: JBoss Developer Studio
Issue Type: Bug
Components: integration
Affects Versions: 2.1.0
Environment: JBDS 2.1 GA, EAP 5 Beta 2, Seam 2.2 , jBPM
Reporter: Gary Lamperillo
The jBPM New Process Definition wizard will not create a process in the EAR level. According to the Seam Reference manual, it should go at the EAR level. The Process Definition created by the wizard creates 3 files in a directory. the components.xml can not use the directory for the process definition, you get the following on deploy:
Caused by: org.jbpm.jpdl.JpdlException: [[ERROR] resource not found: /seam_drools10_15-ejb/jbpm_to_rules]
at org.jbpm.graph.def.ProcessDefinition.parseXmlResource(ProcessDefinition.java:162)
at org.jboss.seam.bpm.Jbpm.deployProcess(Jbpm.java:311)
at org.jboss.seam.bpm.Jbpm.installProcessDefinitions(Jbpm.java:294)
... 85 more
when using a location for the processdefinition.xml in this directory, you will get:
Caused by: java.lang.RuntimeException: could not deploy a process definition
at org.jboss.seam.bpm.Jbpm.installProcessDefinitions(Jbpm.java:300)
at org.jboss.seam.bpm.Jbpm.startup(Jbpm.java:80)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.jboss.seam.util.Reflections.invoke(Reflections.java:22)
at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:144)
at org.jboss.seam.Component.callComponentMethod(Component.java:2249)
at org.jboss.seam.Component.callCreateMethod(Component.java:2172)
at org.jboss.seam.Component.newInstance(Component.java:2132)
... 75 more
Caused by: org.jbpm.jpdl.JpdlException: [[ERROR] resource not found: /seam_drools10_15-ejb/jbpm_to_rules/processdefinition.xml]
at org.jbpm.graph.def.ProcessDefinition.parseXmlResource(ProcessDefinition.java:162)
at org.jboss.seam.bpm.Jbpm.deployProcess(Jbpm.java:311)
at org.jboss.seam.bpm.Jbpm.installProcessDefinitions(Jbpm.java:294)
... 85 more
Is the plan for this process definition editor to work with Seam? Is there something missing in this setup?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] Created: (JBIDE-4127) "Add JSF-Capabilities" adds jsf-facelets.jar which is older than the one in .classpath
by Leiv Hellebo (JIRA)
"Add JSF-Capabilities" adds jsf-facelets.jar which is older than the one in .classpath
--------------------------------------------------------------------------------------
Key: JBIDE-4127
URL: https://jira.jboss.org/jira/browse/JBIDE-4127
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.0.0.GA
Environment: JBDS 2.0.GA
Seam 2.1.X
Reporter: Leiv Hellebo
The Add JSF-Capabilities dialog makes it possible to shoot oneself in the foot:
It will happily add jsf-facelets.jar with Implementation-Version: 1.1.11, even if the one mentioned in .classpath has Implementation-Version: 1.1.15.B1
AFAICS, when performing a redirect within a long-running conversation, this makes
"DEBUG [org.jboss.seam.contexts.ServletLifecycle] >>> Begin re-initialization"
disappear from server.log, and needed context vars are not initialized.
I'd file this as an "Improvement", not a "Bug" if it was possible. You may want to say "PEBKAC" to this...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months