[JBoss JIRA] Created: (JBPM-3051) Change jbpm-gwt-console-server to use only JPA as persistence mechanism
6:57 p.m.
Change jbpm-gwt-console-server to use only JPA as persistence mechanism
-----------------------------------------------------------------------
Key: JBPM-3051
URL: https://issues.jboss.org/browse/JBPM-3051
Project: jBPM
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Console
Affects Versions: jBPM 5.0
Environment: JbossAS 5.1
Reporter: Cristiano Nicolai
Assignee: Kris Verlaenen
Currently jbpm-gwt-console-server is using Hibernate and JPA to manage persistence
information. Forcing to have two different configuration files (hibernate.cfg.xml and
persistence.xml) and API's to use.
This request is to unify the data access through JPA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:01 p.m.
New subject: [JBoss JIRA] Updated: (JBPM-3051) Change jbpm-gwt-console-server to use only JPA as persistence mechanism
[
https://issues.jboss.org/browse/JBPM-3051?page=com.atlassian.jira.plugin....
]
Cristiano Nicolai updated JBPM-3051:
------------------------------------
Attachment: 0002-Refactoring-on-jbpm-gwt-console-server-to-use-only-J.patch
patch
Change jbpm-gwt-console-server to use only JPA as persistence
mechanism
-----------------------------------------------------------------------
Key: JBPM-3051
URL: https://issues.jboss.org/browse/JBPM-3051
Project: jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Console
Affects Versions: jBPM 5.0
Environment: JbossAS 5.1
Reporter: Cristiano Nicolai
Assignee: Kris Verlaenen
Labels: jBPM5, jbpm-console
Attachments: 0002-Refactoring-on-jbpm-gwt-console-server-to-use-only-J.patch
Currently jbpm-gwt-console-server is using Hibernate and JPA to manage persistence
information. Forcing to have two different configuration files (hibernate.cfg.xml and
persistence.xml) and API's to use.
This request is to unify the data access through JPA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:08 a.m.
New subject: [JBoss JIRA] Updated: (JBPM-3051) Change jbpm-gwt-console-server to use only JPA as persistence mechanism
[
https://issues.jboss.org/browse/JBPM-3051?page=com.atlassian.jira.plugin....
]
Kris Verlaenen updated JBPM-3051:
---------------------------------
Fix Version/s: jBPM 5.1
Change jbpm-gwt-console-server to use only JPA as persistence
mechanism
-----------------------------------------------------------------------
Key: JBPM-3051
URL: https://issues.jboss.org/browse/JBPM-3051
Project: jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Console
Affects Versions: jBPM 5.0
Environment: JbossAS 5.1
Reporter: Cristiano Nicolai
Assignee: Kris Verlaenen
Labels: jBPM5, jbpm-console
Fix For: jBPM 5.1
Attachments: 0002-Refactoring-on-jbpm-gwt-console-server-to-use-only-J.patch
Currently jbpm-gwt-console-server is using Hibernate and JPA to manage persistence
information. Forcing to have two different configuration files (hibernate.cfg.xml and
persistence.xml) and API's to use.
This request is to unify the data access through JPA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5060
days inactive
5066
days old
2 comments
2 participants
participants (2)
-
Cristiano Nicolai (JIRA) -
Kris Verlaenen (JIRA)