[JBoss JIRA] Created: (HIBERNATE-56) NamedQueries not honoured on mapped supperclasses
by Heiko W. Rupp (JIRA)
NamedQueries not honoured on mapped supperclasses
-------------------------------------------------
Key: HIBERNATE-56
URL: http://jira.jboss.com/jira/browse/HIBERNATE-56
Project: Hibernate
Issue Type: Bug
Environment: jboss embedded alpha 9
Reporter: Heiko W. Rupp
Assigned To: Steve Ebersole
INFO 16-01 15:50:34,265 (Version.java:<clinit>:15) -Hibernate EntityManager 3.2.0.CR1
INFO 16-01 15:50:34,281 (Version.java:<clinit>:15) -Hibernate Annotations 3.2.0.CR1
INFO 16-01 15:50:34,287 (Environment.java:<clinit>:499) -Hibernate 3.2 cr2
INFO 16-01 15:50:34,291 (Environment.java:<clinit>:532) -hibernate.properties not found
If a @NamedQuery or @NamedNativeQuery is applied on a class that is marked as a @MappedSuperclass, then the named queries are ignored
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Created: (JBPM-779) remember the previous form generation data fields
by Tom Baeyens (JIRA)
remember the previous form generation data fields
-------------------------------------------------
Key: JBPM-779
URL: http://jira.jboss.com/jira/browse/JBPM-779
Project: JBoss jBPM
Issue Type: Feature Request
Components: Graphical Process Designer
Reporter: Tom Baeyens
Assigned To: Koen Aers
Fix For: jBPM 3.2
In the form generation, we currently start from the data entered in the task controller (if any)
Whenever a form is generated, I would like the form generation data to be stored in the gpd.xml. Then, whenever the user does a second generation, the taskform generation form is prefilled with the previous data instead of starting from the controller data again.
The motivation for this is that mostly people will not have controllers. Then if they have 5 data items to display and collect, it takes a lot of clicking. Users don't want to redo this effort for every little change they want to make to the form (additions and removals of fields).
I think users should be able to live with the fact that controller data items are not kept automatically in sync with the task form data items.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Created: (JBPM-727) add support for adding Action to Nodes without adding Event
by mehmet bozok (JIRA)
add support for adding Action to Nodes without adding Event
-----------------------------------------------------------
Key: JBPM-727
URL: http://jira.jboss.com/jira/browse/JBPM-727
Project: JBoss jBPM
Issue Type: Feature Request
Components: Graphical Process Designer
Reporter: mehmet bozok
Assigned To: Tom Baeyens
We are extending some parts of GDP in our project, and we need to add Action to Node without adding an Event then show this Aciton on outline tree view. Althought there is a mechanism to add a single Action to Nodes(not in GDP menu but implemented in
org.jbpm.ui.model.Node), it is not shown at outline tree view. In order to make Action appear on tree view as a Node child we needed to
add a menu option, and handle ActionTreeEditPart and NodeTreeEditpart relation in a different way. (not by changing GPD code, but instantiating editparts then reflecting org.eclipse.gef.AbstractEditPart and calling its protected methods which is not a very safe way.)
Therefore it seems neccesary to change iplementation so that single Action (also providing which Action to add) can be added to Node and shown in outline tree view.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Closed: (JBPM-688) Class chooser limited to jbpm3.1.1 jar classes in Eclipse 3.2 (designer 3.0.9+)
by Koen Aers (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-688?page=all ]
Koen Aers closed JBPM-688.
--------------------------
Resolution: Done
This issue is replaced by GPD-32
> Class chooser limited to jbpm3.1.1 jar classes in Eclipse 3.2 (designer 3.0.9+)
> -------------------------------------------------------------------------------
>
> Key: JBPM-688
> URL: http://jira.jboss.com/jira/browse/JBPM-688
> Project: JBoss jBPM
> Issue Type: Bug
> Components: Graphical Process Designer
> Environment: Eclipse 3.2, designer 3.0.9.x (as in JBossIDE-200607022024-nightly-ALL.zip), Windows XP, java version "1.5.0_06", jBPM-3.1.1
> Reporter: hoogenbj
> Assigned To: Koen Aers
>
> When trying to lookup the class implementing an action handler, the class chooser dialog fails to see classes other than those in jBPM-3.1.1.
> This applies to task assignments as well.
> To re-create, create an action handler in a different eclipse project, place that project on the classpath of the process project, and invoke the class chooser for an action in a process definition. Typing the short name of the class does not cause the list of candidates to appear. Nor does typing the fully qualified name. Typing in "ActionHandler" causes candidates from the jBPM-3.1.1 jar file to appear.
> Classpath is proven to be complete, because pasting the fully qualified class name into the handler class field causes the designer to display the configuration fields that are available. This is also the workaround.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months