[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, 7 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, 7 months
[JBoss JIRA] Created: (JBIDE-8355) Automatic detection of server ports cannot handle changing configuration from default
by Magnus Mogren (JIRA)
Automatic detection of server ports cannot handle changing configuration from default
-------------------------------------------------------------------------------------
Key: JBIDE-8355
URL: https://issues.jboss.org/browse/JBIDE-8355
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.CR1
Reporter: Magnus Mogren
Assignee: Rob Stryker
I create a new server for JBoss AS 6.0.
I select the "default" configuration in the "New server" dialog.
JNDI port is detected as 1099 as it should be.
Now i open the "Edit server runtime environment" dialog and change from "default" to "all" configuration.
I have edited the conf/bindingservice.beans\META-INF\bindings-jboss-beans.xml file to use JNDI port 11099 instead of 1099 for the "all" configuration.
Now the autodetected JNDI port is still 1099?
If i click the "Configure..." next to the auto detect checkbox and then "Edit XPath" i see that the root directory is still pointing to the default configuration.
If i click the browse button and try to change the root directory it does not take the change. It still points to the default directory the next time i open the "Edit XPath" dialog.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (JBIDE-8857) Modules deployment page: need to "Refresh table" if delete/create new project
by Andre Dietisheim (JIRA)
Modules deployment page: need to "Refresh table" if delete/create new project
-----------------------------------------------------------------------------
Key: JBIDE-8857
URL: https://issues.jboss.org/browse/JBIDE-8857
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.3.0.M1
Reporter: Andre Dietisheim
Assignee: Rob Stryker
Fix For: 3.3.0.M2
On the "Deployment" tab of the server adapter editor we currently list all dynamic web projects that are available. If you delete a project or create a new one, you'll have to hit the "Refresh" link so that the list of available projects reflects the change. The Tomcat server adapter doesn't need this manual refresh. It actually detects the change automatically and reflects the change automatically (without any user interaction).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months