[JBoss JIRA] Created: (JBPM-1029) calling getGroupTaskList results in 4N queries being made to the database
by David Sheth (JIRA)
calling getGroupTaskList results in 4N queries being made to the database
-------------------------------------------------------------------------
Key: JBPM-1029
URL: http://jira.jboss.com/jira/browse/JBPM-1029
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.1
Reporter: David Sheth
Assigned To: Tom Baeyens
In the seam 2.0.0.Beta 1 dvdstore example, which uses jbpm-jpdl 3.2.1, one of the admin pages lists all the tasks assigned to the group of the admin, allowing the admin to assign one of the tasks to him or herself. In this page, a task represents an order placed in the store.
Each time a new order is placed in the store, the number of tasks on that admin page goes up by one, as would be expected. However, the number of queries used render the page of tasks goes up by 4 each time a new order is placed.
This seems bad. I asked about this in the seam forum, and got this back from Gavin:
--begin quote
AFAIK, this is a jBPM question, not a Seam question, unless you have evidence otherwise.
--end quote
The specific bit of code in the seam bpm libs that is being called is :
return ManagedJbpmContext.instance()
.getGroupTaskList( new ArrayList( Actor.instance().getGroupActorIds() ) );
which is basically just calling getGroupTaskList on an org.jbpm.JbpmContext instance.
Reference to the post in the seam forum:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=114668
--
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
18 years, 8 months
[JBoss JIRA] Created: (JBAS-4655) HandleImplIIOP not retrieving EJBObject correctly
by Adrian Brock (JIRA)
HandleImplIIOP not retrieving EJBObject correctly
-------------------------------------------------
Key: JBAS-4655
URL: http://jira.jboss.com/jira/browse/JBAS-4655
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: IIOP service
Affects Versions: JBossAS-4.2.1.GA
Reporter: Adrian Brock
Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
The IIOP tests in JBoss Head are failing because the
HandleImplIIOP.getEJBObject()
is returning a stub only for EJBObject and not for the business interface.
The test should also be failing in jboss-4.2 but the test isn't failing because
it is using commit option A and thus not reloading from the database.
I'm going to change the bankiiop stress test in jboss-4.2 to use "instance per transaction" to show the problem.
--
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
18 years, 8 months
[JBoss JIRA] Created: (JBRULES-1148) Out of memory exception asserting more than 100 facts
by eymeric vieuille (JIRA)
Out of memory exception asserting more than 100 facts
-----------------------------------------------------
Key: JBRULES-1148
URL: http://jira.jboss.com/jira/browse/JBRULES-1148
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: All
Affects Versions: 4.0.0.GA
Environment: JDK 1.5; OS = Windows 2000 pro.
For the version of Drools, I am not sure but that is the 4.0 version that you can currently download here : http://labs.jboss.com/drools/downloads/;jsessionid=4BFE39586019C6B98C9B4E...
Reporter: eymeric vieuille
Assigned To: Mark Proctor
Fix For: 4.0.0.GA
Attachments: Out_Of_Memory_Test.zip
I got a java.lang.OutOfMemoryException when I assert more than 100 objects.
I gave you a sample project tracing trucks progression between your firm and the purveyor thanks to message received from trucks. (for more details see on the JBoss forum reference given)
You can see there logs obtained launching the sample project main class :
Launching RULES ENGINE
100 Facts
Facts : [OUT:TLSE:PRS::2007-04-20T23:00:00Z, OFF:TLSE:PRS::2007-04-20T23:00:01Z, ON:TLSE:PRS::2007-04-20T23:00:02Z, IN:TLSE:PRS::2007-04-20T23:00:03Z, OUT:TLSE:PRS::2007-04-20T23:01:00Z, OFF:TLSE:PRS::2007-04-20T23:01:01Z, ON:TLSE:PRS::2007-04-20T23:01:02Z, IN:TLSE:PRS::2007-04-20T23:01:03Z, OUT:TLSE:PRS::2007-04-20T23:02:00Z, OFF:TLSE:PRS::2007-04-20T23:02:01Z, ON:TLSE:PRS::2007-04-20T23:02:02Z, IN:TLSE:PRS::2007-04-20T23:02:03Z, OUT:TLSE:PRS::2007-04-20T23:03:00Z, OFF:TLSE:PRS::2007-04-20T23:03:01Z, ON:TLSE:PRS::2007-04-20T23:03:02Z, IN:TLSE:PRS::2007-04-20T23:03:03Z, OUT:TLSE:PRS::2007-04-20T23:04:00Z, OFF:TLSE:PRS::2007-04-20T23:04:01Z, ON:TLSE:PRS::2007-04-20T23:04:02Z, IN:TLSE:PRS::2007-04-20T23:04:03Z, OUT:TLSE:PRS::2007-04-20T23:05:00Z, OFF:TLSE:PRS::2007-04-20T23:05:01Z, ON:TLSE:PRS::2007-04-20T23:05:02Z, IN:TLSE:PRS::2007-04-20T23:05:03Z, OUT:TLSE:PRS::2007-04-20T23:06:00Z, OFF:TLSE:PRS::2007-04-20T23:06:01Z, ON:TLSE:PRS::2007-04-20T23:06:02Z, IN:TLSE:PRS::2007-04-20T23:06:03Z, OUT:TLSE:PRS::2007-04-20T23:07:00Z, OFF:TLSE:PRS::2007-04-20T23:07:01Z, ON:TLSE:PRS::2007-04-20T23:07:02Z, IN:TLSE:PRS::2007-04-20T23:07:03Z, OUT:TLSE:PRS::2007-04-20T23:08:00Z, OFF:TLSE:PRS::2007-04-20T23:08:01Z, ON:TLSE:PRS::2007-04-20T23:08:02Z, IN:TLSE:PRS::2007-04-20T23:08:03Z, OUT:TLSE:PRS::2007-04-20T23:09:00Z, OFF:TLSE:PRS::2007-04-20T23:09:01Z, ON:TLSE:PRS::2007-04-20T23:09:02Z, IN:TLSE:PRS::2007-04-20T23:09:03Z, OUT:TLSE:PRS::2007-04-20T23:10:00Z, OFF:TLSE:PRS::2007-04-20T23:10:01Z, ON:TLSE:PRS::2007-04-20T23:10:02Z, IN:TLSE:PRS::2007-04-20T23:10:03Z, OUT:TLSE:PRS::2007-04-20T23:11:00Z, OFF:TLSE:PRS::2007-04-20T23:11:01Z, ON:TLSE:PRS::2007-04-20T23:11:02Z, IN:TLSE:PRS::2007-04-20T23:11:03Z, OUT:TLSE:PRS::2007-04-20T23:12:00Z, OFF:TLSE:PRS::2007-04-20T23:12:01Z, ON:TLSE:PRS::2007-04-20T23:12:02Z, IN:TLSE:PRS::2007-04-20T23:12:03Z, OUT:TLSE:PRS::2007-04-20T23:13:00Z, OFF:TLSE:PRS::2007-04-20T23:13:01Z, ON:TLSE:PRS::2007-04-20T23:13:02Z, IN:TLSE:PRS::2007-04-20T23:13:03Z, OUT:TLSE:PRS::2007-04-20T23:14:00Z, OFF:TLSE:PRS::2007-04-20T23:14:01Z, ON:TLSE:PRS::2007-04-20T23:14:02Z, IN:TLSE:PRS::2007-04-20T23:14:03Z, OUT:TLSE:PRS::2007-04-20T23:15:00Z, OFF:TLSE:PRS::2007-04-20T23:15:01Z, ON:TLSE:PRS::2007-04-20T23:15:02Z, IN:TLSE:PRS::2007-04-20T23:15:03Z, OUT:TLSE:PRS::2007-04-20T23:16:00Z, OFF:TLSE:PRS::2007-04-20T23:16:01Z, ON:TLSE:PRS::2007-04-20T23:16:02Z, IN:TLSE:PRS::2007-04-20T23:16:03Z, OUT:TLSE:PRS::2007-04-20T23:17:00Z, OFF:TLSE:PRS::2007-04-20T23:17:01Z, ON:TLSE:PRS::2007-04-20T23:17:02Z, IN:TLSE:PRS::2007-04-20T23:17:03Z, OUT:TLSE:PRS::2007-04-20T23:18:00Z, OFF:TLSE:PRS::2007-04-20T23:18:01Z, ON:TLSE:PRS::2007-04-20T23:18:02Z, IN:TLSE:PRS::2007-04-20T23:18:03Z, OUT:TLSE:PRS::2007-04-20T23:19:00Z, OFF:TLSE:PRS::2007-04-20T23:19:01Z, ON:TLSE:PRS::2007-04-20T23:19:02Z, IN:TLSE:PRS::2007-04-20T23:19:03Z, OUT:TLSE:PRS::2007-04-20T23:20:00Z, OFF:TLSE:PRS::2007-04-20T23:20:01Z, ON:TLSE:PRS::2007-04-20T23:20:02Z, IN:TLSE:PRS::2007-04-20T23:20:03Z, OUT:TLSE:PRS::2007-04-20T23:21:00Z, OFF:TLSE:PRS::2007-04-20T23:21:01Z, ON:TLSE:PRS::2007-04-20T23:21:02Z, IN:TLSE:PRS::2007-04-20T23:21:03Z, OUT:TLSE:PRS::2007-04-20T23:22:00Z, OFF:TLSE:PRS::2007-04-20T23:22:01Z, ON:TLSE:PRS::2007-04-20T23:22:02Z, IN:TLSE:PRS::2007-04-20T23:22:03Z, OUT:TLSE:PRS::2007-04-20T23:23:00Z, OFF:TLSE:PRS::2007-04-20T23:23:01Z, ON:TLSE:PRS::2007-04-20T23:23:02Z, IN:TLSE:PRS::2007-04-20T23:23:03Z, OUT:TLSE:PRS::2007-04-20T23:24:00Z, OFF:TLSE:PRS::2007-04-20T23:24:01Z, ON:TLSE:PRS::2007-04-20T23:24:02Z, IN:TLSE:PRS::2007-04-20T23:24:03Z]
Add object : OUT:TLSE:PRS::2007-04-20T23:00:00Z
Add object : OFF:TLSE:PRS::2007-04-20T23:00:01Z
Add object : ON:TLSE:PRS::2007-04-20T23:00:02Z
Add object : IN:TLSE:PRS::2007-04-20T23:00:03Z
Add object : OUT:TLSE:PRS::2007-04-20T23:01:00Z
Add object : OFF:TLSE:PRS::2007-04-20T23:01:01Z
Add object : ON:TLSE:PRS::2007-04-20T23:01:02Z
Add object : IN:TLSE:PRS::2007-04-20T23:01:03Z
Add object : OUT:TLSE:PRS::2007-04-20T23:02:00Z
Add object : OFF:TLSE:PRS::2007-04-20T23:02:01Z
Add object : ON:TLSE:PRS::2007-04-20T23:02:02Z
Add object : IN:TLSE:PRS::2007-04-20T23:02:03Z
Add object : OUT:TLSE:PRS::2007-04-20T23:03:00Z
Add object : OFF:TLSE:PRS::2007-04-20T23:03:01Z
Add object : ON:TLSE:PRS::2007-04-20T23:03:02Z
Add object : IN:TLSE:PRS::2007-04-20T23:03:03Z
Add object : OUT:TLSE:PRS::2007-04-20T23:04:00Z
Add object : OFF:TLSE:PRS::2007-04-20T23:04:01Z
Add object : ON:TLSE:PRS::2007-04-20T23:04:02Z
Add object : IN:TLSE:PRS::2007-04-20T23:04:03Z
Add object : OUT:TLSE:PRS::2007-04-20T23:05:00Z
Add object : OFF:TLSE:PRS::2007-04-20T23:05:01Z
Add object : ON:TLSE:PRS::2007-04-20T23:05:02Z
Add object : IN:TLSE:PRS::2007-04-20T23:05:03Z
Add object : OUT:TLSE:PRS::2007-04-20T23:06:00Z
Add object : OFF:TLSE:PRS::2007-04-20T23:06:01Z
Add object : ON:TLSE:PRS::2007-04-20T23:06:02Z
Add object : IN:TLSE:PRS::2007-04-20T23:06:03Z
Add object : OUT:TLSE:PRS::2007-04-20T23:07:00Z
Add object : OFF:TLSE:PRS::2007-04-20T23:07:01Z
Add object : ON:TLSE:PRS::2007-04-20T23:07:02Z
Add object : IN:TLSE:PRS::2007-04-20T23:07:03Z
Add object : OUT:TLSE:PRS::2007-04-20T23:08:00Z
Add object : OFF:TLSE:PRS::2007-04-20T23:08:01Z
Add object : ON:TLSE:PRS::2007-04-20T23:08:02Z
Add object : IN:TLSE:PRS::2007-04-20T23:08:03Z
Add object : OUT:TLSE:PRS::2007-04-20T23:09:00Z
Add object : OFF:TLSE:PRS::2007-04-20T23:09:01Z
Add object : ON:TLSE:PRS::2007-04-20T23:09:02Z
Add object : IN:TLSE:PRS::2007-04-20T23:09:03Z
Add object : OUT:TLSE:PRS::2007-04-20T23:10:00Z
Add object : OFF:TLSE:PRS::2007-04-20T23:10:01Z
Add object : ON:TLSE:PRS::2007-04-20T23:10:02Z
Add object : IN:TLSE:PRS::2007-04-20T23:10:03Z
Add object : OUT:TLSE:PRS::2007-04-20T23:11:00Z
Add object : OFF:TLSE:PRS::2007-04-20T23:11:01Z
Add object : ON:TLSE:PRS::2007-04-20T23:11:02Z
Add object : IN:TLSE:PRS::2007-04-20T23:11:03Z
Add object : OUT:TLSE:PRS::2007-04-20T23:12:00Z
Add object : OFF:TLSE:PRS::2007-04-20T23:12:01Z
Add object : ON:TLSE:PRS::2007-04-20T23:12:02Z
Add object : IN:TLSE:PRS::2007-04-20T23:12:03Z
Add object : OUT:TLSE:PRS::2007-04-20T23:13:00Z
Add object : OFF:TLSE:PRS::2007-04-20T23:13:01Z
Add object : ON:TLSE:PRS::2007-04-20T23:13:02Z
Add object : IN:TLSE:PRS::2007-04-20T23:13:03Z
Add object : OUT:TLSE:PRS::2007-04-20T23:14:00Z
Add object : OFF:TLSE:PRS::2007-04-20T23:14:01Z
Add object : ON:TLSE:PRS::2007-04-20T23:14:02Z
Add object : IN:TLSE:PRS::2007-04-20T23:14:03Z
Add object : OUT:TLSE:PRS::2007-04-20T23:15:00Z
Add object : OFF:TLSE:PRS::2007-04-20T23:15:01Z
Add object : ON:TLSE:PRS::2007-04-20T23:15:02Z
Add object : IN:TLSE:PRS::2007-04-20T23:15:03Z
Add object : OUT:TLSE:PRS::2007-04-20T23:16:00Z
Add object : OFF:TLSE:PRS::2007-04-20T23:16:01Z
Add object : ON:TLSE:PRS::2007-04-20T23:16:02Z
Add object : IN:TLSE:PRS::2007-04-20T23:16:03Z
Add object : OUT:TLSE:PRS::2007-04-20T23:17:00Z
Add object : OFF:TLSE:PRS::2007-04-20T23:17:01Z
Add object : ON:TLSE:PRS::2007-04-20T23:17:02Z
Add object : IN:TLSE:PRS::2007-04-20T23:17:03Z
Add object : OUT:TLSE:PRS::2007-04-20T23:18:00Z
Add object : OFF:TLSE:PRS::2007-04-20T23:18:01Z
Add object : ON:TLSE:PRS::2007-04-20T23:18:02Z
Add object : IN:TLSE:PRS::2007-04-20T23:18:03Z
Add object : OUT:TLSE:PRS::2007-04-20T23:19:00Z
Add object : OFF:TLSE:PRS::2007-04-20T23:19:01Z
Add object : ON:TLSE:PRS::2007-04-20T23:19:02Z
Add object : IN:TLSE:PRS::2007-04-20T23:19:03Z
Add object : OUT:TLSE:PRS::2007-04-20T23:20:00Z
Add object : OFF:TLSE:PRS::2007-04-20T23:20:01Z
Add object : ON:TLSE:PRS::2007-04-20T23:20:02Z
Add object : IN:TLSE:PRS::2007-04-20T23:20:03Z
Add object : OUT:TLSE:PRS::2007-04-20T23:21:00Z
Add object : OFF:TLSE:PRS::2007-04-20T23:21:01Z
Add object : ON:TLSE:PRS::2007-04-20T23:21:02Z
Add object : IN:TLSE:PRS::2007-04-20T23:21:03Z
Add object : OUT:TLSE:PRS::2007-04-20T23:22:00Z
Add object : OFF:TLSE:PRS::2007-04-20T23:22:01Z
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
--
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
18 years, 8 months
[JBoss JIRA] Created: (JBPM-1016) ProcessState 'leave' method always returns default transition
by Randy Gullett (JIRA)
ProcessState 'leave' method always returns default transition
--------------------------------------------------------------
Key: JBPM-1016
URL: http://jira.jboss.com/jira/browse/JBPM-1016
Project: JBoss jBPM
Issue Type: Patch
Components: Core Engine
Affects Versions: jBPM jPDL 3.2
Reporter: Randy Gullett
Assigned To: Tom Baeyens
The leave method for ProcessStates currently automatically takes the default transition despite taking a transition as a parameter. Can it be modified so that it leaves by the transition passed in (if it isn't null) like you'd expect it to? I want to be able to short-circuit my subprocesses in certain scenarios. See the method as it's currently coded below.
public void leave(ExecutionContext executionContext, Transition transition) {
ProcessInstance subProcessInstance = executionContext.getSubProcessInstance();
Token superProcessToken = subProcessInstance.getSuperProcessToken();
// feed the readable variableInstances
if ((variableAccesses != null) && (!variableAccesses.isEmpty())) {
ContextInstance superContextInstance = executionContext.getContextInstance();
ContextInstance subContextInstance = subProcessInstance.getContextInstance();
// loop over all the variable accesses
Iterator iter = variableAccesses.iterator();
while (iter.hasNext()) {
VariableAccess variableAccess = (VariableAccess) iter.next();
// if this variable access is writable
if (variableAccess.isWritable()) {
// the variable is copied from the sub process mapped name
// to the super process variable name
String mappedName = variableAccess.getMappedName();
Object value = subContextInstance.getVariable(mappedName);
String variableName = variableAccess.getVariableName();
log.debug("copying sub process var '"+mappedName+"' to super process var '"+variableName+"': "+value);
if (value!=null) {
superContextInstance.setVariable(variableName, value, superProcessToken);
}
}
}
}
// fire the subprocess ended event
fireEvent(Event.EVENTTYPE_SUBPROCESS_END, executionContext);
// remove the subprocess reference
superProcessToken.setSubProcessInstance(null);
// We replaced the normal log generation of super.leave() by creating the log here
// and overriding the addNodeLog method with an empty version
superProcessToken.addLog(new ProcessStateLog(this, superProcessToken.getNodeEnter(), new Date(), subProcessInstance));
// call the subProcessEndAction
[b]super.leave(executionContext, getDefaultLeavingTransition());[/b] }
The bold line could be replaced by something like:
if(transition != null) {
super.leave(executionContext, transition);
} else {
super.leave(executionContext, getDefaultLeavingTransition());
--
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
18 years, 8 months
[JBoss JIRA] Updated: (JBPM-457) Parent process deployment does not link process-state with subprocess definition
by Tom Baeyens (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-457?page=all ]
Tom Baeyens updated JBPM-457:
-----------------------------
Fix Version/s: jBPM jPDL 3.2.2
Priority: Critical (was: Major)
> Parent process deployment does not link process-state with subprocess definition
> --------------------------------------------------------------------------------
>
> Key: JBPM-457
> URL: http://jira.jboss.com/jira/browse/JBPM-457
> Project: JBoss jBPM
> Issue Type: Bug
> Components: Core Engine
> Reporter: Eduardo Jimenez
> Assigned To: Tom Baeyens
> Priority: Critical
> Fix For: jBPM jPDL 3.2.2
>
>
> From the ProcessState code:
> Code:
> if (jbpmSession != null) {
>
> // now, we must be able to find the sub-process
> if (subProcessName != null) {
>
> // if the name and the version are specified
> if (subProcessVersion != null) {
>
> try {
> int version = Integer.parseInt(subProcessVersion);
> // select that exact process definition as the subprocess definition
> subProcessDefinition = jbpmSession.getGraphSession().findProcessDefinition(subProcessNam
> e, version);
> } catch (NumberFormatException e) {
> jpdlReader.addWarning("version in process-state was not a number: " + processStateElement.asXML());
> }
>
> } else { // if only the name is specified
> // select the latest version of that process as the subprocess
> // definition
> subProcessDefinition = jbpmSession.getGraphSession().findLatestProcessDefinition(subProces
> sName);
> }
> } else {
> jpdlReader.addWarning("no sub-process name specified in process-state " + processStateElement.asXML());
> }
> }
>
> if there is no session open, it simply won't look for the parent process.
> Now, from the ProcessArchiveDeployer:
> Code:
> public static void deployZipInputStream(ZipInputStream zipInputStream, JbpmSessionFactory jbpmSessio
> nFactory) {
> ProcessDefinition processDefinition = ProcessDefinition.parseParZipInputStream(zipInputStream);
> deployProcessDefinition(processDefinition, jbpmSessionFactory);
> }
>
> It reads the process definition first, then calls deploy, which opens the first jbpmSession!!!. The session must be open first before attempting to deploy!.
> Now, you might say, use the ant task, but the bug is still there:
> Code:
> private void deploy(File file, JbpmSessionFactory jbpmSessionFactory) throws IOException, FileNotFou
> ndException {
> ZipInputStream zipInputStream = new ZipInputStream(new FileInputStream(file));
> ProcessArchiveDeployer.deployZipInputStream(zipInputStream,jbpmSessionFactory);
> }
>
> See, the ant task doens't open a jbpmSession either, so its up to ProcessArchiveDeployer.deployZipInputStream() to do it, which is the same method I'm having an issue with.
> Examining ProcessArchiveDeployer, every way of deploying a process would have the same problem.
--
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
18 years, 8 months
[JBoss JIRA] Created: (HIBERNATE-71) ".." in relative path to orm.xml not properly recognized
by Ronald Fischer (JIRA)
".." in relative path to orm.xml not properly recognized
--------------------------------------------------------
Key: HIBERNATE-71
URL: http://jira.jboss.com/jira/browse/HIBERNATE-71
Project: Hibernate
Issue Type: Bug
Environment: Windows XP
Reporter: Ronald Fischer
Assigned To: Steve Ebersole
I have the following files:
\thome\tmp\MyApplication.class
\thome\tmp\META-INF\persistence.xml
\thome\etc\orm.xml
The file persistence.xml contains the line
<mapping-file>../etc/orm.xml</mapping-file>
The directory \thome\tmp is in my classpath.
MyApplication.class throws exception
[java] log4j:WARN Please initialize the log4j system properly.
[java] Exception in thread "main" javax.persistence.PersistenceException: [
PersistenceUnit: TFW_InsertMasterData_SCM] Unable to find XML mapping file in cl
asspath: /../etc/orm.xml
[java] at org.hibernate.ejb.Ejb3Configuration.addClassesToSessionFactor
y(Ejb3Configuration.java:914)
[java] at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configurati
on.java:772)
[java] at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configurati
on.java:183)
[java] at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configurati
on.java:240)
[java] at org.hibernate.ejb.HibernatePersistence.createEntityManagerFac
tory(HibernatePersistence.java:120)
[java] at javax.persistence.Persistence.createEntityManagerFactory(Pers
istence.java:51)
[java] at javax.persistence.Persistence.createEntityManagerFactory(Pers
istence.java:33)
[java] at InsertMasterData.main(InsertMasterData.java:27)
When I copy orm.xml into my META-INF directory and change my persistence.xml
to
<mapping-file>/META-INF/orm.xml</mapping-file>
everything works fine.
>From this I conclude that Hibernate can not follow a path starting with .. to find the
mapping file.
--
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
18 years, 8 months