July 2011 - jbosstools-issues - Jboss List Archives

[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

7
23
0 / 0

[JBoss JIRA] Created: (JBIDE-9096) VPE context menu for source -> "Add to Snippets" disabled item

by Vitali Yemialyanchyk (JIRA)

VPE context menu for source -> "Add to Snippets" disabled item -------------------------------------------------------------- Key: JBIDE-9096 URL: https://issues.jboss.org/browse/JBIDE-9096 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor core Affects Versions: 3.1.2 Reporter: Vitali Yemialyanchyk Assignee: Yahor Radtsevich should be enabled, should be possible to use the feature -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

5
11
0 / 0

[JBoss JIRA] Created: (JBIDE-8777) Check if VPE JUnits will run on Hudson with XULRunner 1.9.2.16

by Yahor Radtsevich (JIRA)

Check if VPE JUnits will run on Hudson with XULRunner 1.9.2.16 -------------------------------------------------------------- Key: JBIDE-8777 URL: https://issues.jboss.org/browse/JBIDE-8777 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Visual Page Editor core Affects Versions: 3.3.0.M1 Reporter: Yahor Radtsevich Assignee: Nick Boldt Priority: Critical Last time when we tried to run VPE JUnits with XULRunner 1.9.2 on Hudson (almost a year ago), they did not work. Now we need to check if this issue persists with new XULRunner 1.9.2.16 and Eclipse 3.7. XULRunner 1.9.2.16 bundles are [here|https://svn.jboss.org/repos/jbosstools/branches/xulrunner-1.9.2.16/x...]. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

6
45
0 / 0

[JBoss JIRA] Created: (JBIDE-8653) GWT facet: the project that is being created by the facet needs to be recompiled

by Andre Dietisheim (JIRA)

GWT facet: the project that is being created by the facet needs to be recompiled -------------------------------------------------------------------------------- Key: JBIDE-8653 URL: https://issues.jboss.org/browse/JBIDE-8653 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.2.0.Final, 3.3.0.M1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Priority: Minor Fix For: 3.2.1, 3.3.0.M1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
7
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-191) Missing Hibernate News and Noteworthy for 3.3.0.M1

by Jiri Peterka (JIRA)

Missing Hibernate News and Noteworthy for 3.3.0.M1 -------------------------------------------------- Key: TOOLSDOC-191 URL: https://issues.jboss.org/browse/TOOLSDOC-191 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Security Level: Public (Everyone can see) Components: Release Notes Affects Versions: 3.3.0.Final Reporter: Jiri Peterka Assignee: Isaac Rooskov Fix For: 3.3.0.Final Missing Hibernate News and Noteworthy for JBT 3.3.0.M1 http://docs.jboss.org/tools/whatsnew/ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-9338) Update GWT Plugin for Eclipse Indigo

by Andre Dietisheim (JIRA)

Update GWT Plugin for Eclipse Indigo ------------------------------------ Key: JBIDE-9338 URL: https://issues.jboss.org/browse/JBIDE-9338 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: GWT Affects Versions: 3.3.0.M3 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.M3 Google released a GWT plugin for Eclipse Indigo (3.7). We need to update our GWT facet so that it can finally work in our JBoss Tools 3.3 (which is based on Eclipse 3.7 Indigo). The google update site is listed here: http://code.google.com/intl/de-DE/eclipse/docs/getting_started.html The google update site for Indigo (3.7) is here: http://dl.google.com/eclipse/plugin/3.7 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBDS-1794) Add GWT 2.3 for Eclipse 3.7 to JBoss Tools 3.3

by Nick Boldt (JIRA)

Add GWT 2.3 for Eclipse 3.7 to JBoss Tools 3.3 ---------------------------------------------- Key: JBDS-1794 URL: https://issues.jboss.org/browse/JBDS-1794 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Components: 3rdPartyCertification, 3rdPartyDependencies, updatesite Reporter: Nick Boldt Assignee: Andre Dietisheim Fix For: 5.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
11
0 / 0

[JBoss JIRA] Created: (JBIDE-9378) test failure(s) in common: org.jboss.tools.common.verification.ui.test :: org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]

by Nick Boldt (JIRA)

test failure(s) in common: org.jboss.tools.common.verification.ui.test :: org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed] --------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-9378 URL: https://issues.jboss.org/browse/JBIDE-9378 Project: Tools (JBoss Tools) Issue Type: Bug Components: common, testing Affects Versions: 3.3.0.M3 Reporter: Nick Boldt Assignee: Alexey Kazakov Fix For: 3.3.0.M3 Attachments: console.log.txt [INFO] org.jboss.tools.common.verification.ui.test ....... FAILURE [12.416s] [ERROR] Please refer to /mnt/hudson_workspace/workspace/jbosstools-3.3_trunk.component--common/sources/tests/org.jboss.tools.common.verification.ui.test/target/surefire-reports for the individual test results. There is no report, because the test failed before it could record results. Here's the console log, captured here: https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--co... (See attached.) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
9
0 / 0

[JBoss JIRA] Created: (JBIDE-9430) JBT 3.3 aggregate build failed: results/buildResults.xsl:200: Fatal Error! A sequence of more than one item is not allowed as the first argument of tokenize()

by Nick Boldt (JIRA)

JBT 3.3 aggregate build failed: results/buildResults.xsl:200: Fatal Error! A sequence of more than one item is not allowed as the first argument of tokenize() -------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-9430 URL: https://issues.jboss.org/browse/JBIDE-9430 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng, updatesite Affects Versions: 3.3.0.M3 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.3.0.M3 [xslt] mnt/hudson_workspace/workspace/jbosstools-3.3_trunk.aggregate/sources/results/buildResults.xsl:200: Fatal Error! A sequence of more than one item is not allowed as the first argument of tokenize() ("http://anonsvn.jboss.org/repos...", "http://anonsvn.jboss.org/repos...") https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/333... Possible solution: {code} diff --git a/build/results/buildResults.xsl b/build/results/buildResults.xsl index 27346f1..da19686 100644 --- a/build/results/buildResults.xsl +++ b/build/results/buildResults.xsl @@ -197,7 +197,7 @@ </li> <xsl:for-each - select="tokenize(//property[contains(@name,'build.properties.SVN_REVISION') and contains(@name,$COMPONENT)]/@value,',')"> + select="tokenize(//property[contains(@name,'build.properties.SVN_REVISION') and contains(@name,$COMPONENT)][1]/@value,',')"> <li>SVN: <xsl:value-of select="." /></li> </xsl:for-each> </ul> {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5720) EAR Libraries in Dynamic Web Project

by Burr Sutter (JIRA)

EAR Libraries in Dynamic Web Project ------------------------------------ Key: JBIDE-5720 URL: https://jira.jboss.org/jira/browse/JBIDE-5720 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: core Environment: jbdevstudio-win32-3.0.0.v201001060655N-H50-CR1 Reporter: Burr Sutter Attachments: EAR_Libraries.jpg Creation of a New Dynamic Web Project adds "EAR Libraries" - that does not make sense because I (the user) am building a WAR and I do not want anything to do with an EAR in this case. -- 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

4
11
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2011