[JBoss JIRA] Created: (JBIDE-5234) jPDL 4 Graphical Designer problem when naming Nodes under Windows XP and maybe other WIndows Products
by Burjan Romulus Sorin (JIRA)
jPDL 4 Graphical Designer problem when naming Nodes under Windows XP and maybe other WIndows Products
-----------------------------------------------------------------------------------------------------
Key: JBIDE-5234
URL: https://jira.jboss.org/jira/browse/JBIDE-5234
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpm, jbpm
Affects Versions: 3.1.0.M4
Environment: Affect as far as I seen, ONLY MIcrosoft WIndows XP Machines. LINUX doesn't seem to be affected.
Reporter: Burjan Romulus Sorin
Priority: Minor
This bug affects the Graphical Designer of JBoss Tools.
Version tested on :
jBPM 4 Graphical Editor and Tools 4.0.0.v200910281724M-H247-M4 org.jboss.tools.flow.jpdl4.feature.feature.group
Issue : When creating a process definition inside a project, I open the Graphical Editor in order to design the process.
I add tasks, transitions, etc. On the bottom of the page, on the tabs list, I have a "Proprieties" tab. In there, I can chenge/add specifications to the selected node.
If I try to change the name from there, after Every character written the cursor get at the first position of the box. So then I write a task with the name : "test", it will appear "tset".
Note that editing from the XML directly works perfectly.
Note that clicking on the task name and changing it from there, works perfectly too.
Only issue is when modifying the task name from the Proprieties on the bottom area of the IDE.
This is my first bug report, so please have mercy. I tried to be as technical as I could.
--
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
12 years, 3 months
[JBoss JIRA] Created: (JBDS-1099) Verify JBDS update site capacity for Eclipse bits
by Mark Yarborough (JIRA)
Verify JBDS update site capacity for Eclipse bits
-------------------------------------------------
Key: JBDS-1099
URL: https://jira.jboss.org/jira/browse/JBDS-1099
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Components: Program
Affects Versions: LATER
Reporter: Mark Yarborough
The JBDS team would like to ensure that the JBDS update site has capacity (disk and bandwidth) to support the addition of Eclipse bits. This will ensure that the version of eclipse that users pull is the same version that the JBDS release validated in product QE, and should make updating easier for customers. However, addition of these bits will potentially take more disk space and more download bandwidth, hence this "program" related task jira...
--
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
12 years, 4 months
[JBoss JIRA] Created: (JBIDE-2791) "duplicate factory for: org.jboss.seam.web.webSession (duplicate is specified in components.xml)" error after creating a newseam project
by Riccardo Serafin (JIRA)
"duplicate factory for: org.jboss.seam.web.webSession (duplicate is specified in components.xml)" error after creating a newseam project
-----------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-2791
URL: https://jira.jboss.org/jira/browse/JBIDE-2791
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.0.0.alpha
Environment: Windows XP, Eclipse 3.4.0, JBoss AS 4.2.3-GA, Seam 2.1.0-BETA1, Java 1.6.0_10-rc
Reporter: Riccardo Serafin
After creating a new Seam project via the wizard (EAR packaging, configuration "Dynamic Web project with Seam 2.0"), starting up JBoss produces the following error:
duplicate factory for: org.jboss.seam.web.webSession (duplicate is specified in components.xml)
Even after removing jboss-seam.jar from the war MANIFEST.INF as suggested here (http://www.seamframework.org/Community/HowToUpdateProjectFrom20To21Seam) the error still occurs.
This is the only other reference that I've found to this error (http://jira.jboss.com/jira/browse/JBSEAM-2981) but it looks slightly unrelated to me.
Stack trace:
19:05:32,116 ERROR [[/hellome]] Excepción enviando evento inicializado de contexto a instancia de escuchador de clase org.jboss.seam.servlet.SeamListener
java.lang.IllegalStateException: duplicate factory for: org.jboss.seam.web.webSession (duplicate is specified in components.xml)
at org.jboss.seam.core.Init.checkDuplicateFactoryExpressions(Init.java:222)
at org.jboss.seam.core.Init.checkDuplicateFactory(Init.java:215)
at org.jboss.seam.core.Init.addFactoryValueExpression(Init.java:278)
at org.jboss.seam.init.Initialization.installComponents(Initialization.java:983)
at org.jboss.seam.init.Initialization.init(Initialization.java:631)
at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:34)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3856)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4361)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:790)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:770)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:553)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
....
I believe also these others warnings might be related to the same problem (which i suspect is duplicate jar in the classpath of the war):
19:49:24,506 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
19:49:25,506 INFO [EARDeployer] Init J2EE application: file:/D:/Java/jboss-4.2.3.GA/server/default/deploy/hellome-ear.ear/
19:49:35,459 WARN [MainDeployer] Found non-jar deployer for jboss-seam.jar: MBeanProxyExt[jboss.ejb3:service=EJB3Deployer]
19:49:42,381 WARN [DeploymentInfo] Only the root deployment can set the loader repository, ignoring config=LoaderRepositoryConfig(repositoryName: seam.jboss.org:loader=hellome, repositoryClassName: org.jboss.mx.loading.HeirarchicalLoaderRepository3, configParserClassName: org.jboss.mx.loading.HeirarchicalLoaderRepository3ConfigParser, repositoryConfig: java2ParentDelegation=false)
19:50:00,679 INFO [JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.entity.PersistenceUnitDeployment
19:50:04,976 INFO [TomcatDeployer] deploy, ctxPath=/hellome, warUrl=.../deploy/hellome-ear.ear/hellome.war/
19:50:13,554 WARN [SeamPhaseListener] There should only be one Seam phase listener per application
19:50:20,726 INFO [ServletContextListener] Welcome to Seam 2.1.0.BETA1
--
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
12 years, 4 months
[JBoss JIRA] Created: (JBIDE-2735) Error: libapr-1.dll was not found starting JBossAS in JBoss IDE
by hmr_mueller (JIRA)
Error: libapr-1.dll was not found starting JBossAS in JBoss IDE
---------------------------------------------------------------
Key: JBIDE-2735
URL: https://jira.jboss.org/jira/browse/JBIDE-2735
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 2.1.2
Environment: Eclipse: 3.3.1.1
OS: Windows
JBoss AS 4.2.2GA JBossWeb native
Reporter: hmr_mueller
When starting the JBossAS 4.2.2GA with JBoss Web native configured from within a JBoss Server configured with the Eclipse IDE (JBoss Tools), I'm getting the error '... libapr-1.dll was not found ..' as a popup. After closing the popup for 3 times the server starts, but does so with errors when starting the Tomcat https connector. When running the run.bat script from the command line everything works fine.
Tomcat is configured to used the AprLifecycleListener and a https connector for APR (OpenSSL style configuration).
The server launch configuration in eclipse contains the $JBOSS_HOME\bin\native directory in the -Djava.library.path variable
The problem seems to be that the libtcnative-1.dll is loading the libapr-1.dll dynamically but since the Path environment variable does not contain the $JBOSS_HOME\bin\native directory the library is not found (setting this is done by the run.bat script).
If I put the native directory in the Path variable, the server starts up correctly, so just defining the java.library.path in the launch configuration does not suffice.
The problem can be fixed I think, if instead of setting the java.library.path the launch configuration extends the environment (Tab Environment) to contain the native directory in the Path environment variable and changing the class
org.jboss.ide.eclipse.as.core.server.internal.launch.AbstractJBossLaunchConfigType to add this to the 'VMRunnerConfiguration' in the 'actualLaunch' method.
--
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
12 years, 4 months
[JBoss JIRA] Created: (JBIDE-3191) Cannot run tests when building JMX by itself
by Nick Boldt (JIRA)
Cannot run tests when building JMX by itself
--------------------------------------------
Key: JBIDE-3191
URL: https://jira.jboss.org/jira/browse/JBIDE-3191
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: Build/Releng
Affects Versions: 3.0.0.beta1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.0.0.cr1
Using /devstudio-trunk/releng/org.jboss.ide.eclipse.releng/hudson/build.sh with the following parameters changed, JMX will build on its own:
builders=jmx
nightlyBuildSteps=standalone.product,reports,build-results,update-site
Turning tests back on, however, the build fails:
builders=jmx
nightlyBuildSteps=standalone.product,reports,tests,build-results,update-site
[java] Java Result: 13
[echo]
[echo] The builder <b>tests</b> failed to compile with the following results:<br/><br/>
[echo]
[echo] <pre>
[echo] BUILD FAILED
[echo] /opt/public/jbt-jbds/nightly-with-tests/jbds-build/clean-eclipse/eclipse/plugins/org.eclipse.pde.build_3.4.1.R34x_v20080805/scripts/build.xml:24: The following error occurred while executing this line:
[echo] /opt/public/jbt-jbds/nightly-with-tests/jbds-build/clean-eclipse/eclipse/plugins/org.eclipse.pde.build_3.4.1.R34x_v20080805/scripts/build.xml:64: The following error occurred while executing this line:
[echo] /opt/public/jbt-jbds/nightly-with-tests/org.jboss.ide.eclipse.releng/builders/tests/customTargets.xml:13: The following error occurred while executing this line:
[echo] /opt/public/jbt-jbds/nightly-with-tests/jbds-build/clean-eclipse/eclipse/plugins/org.eclipse.pde.build_3.4.1.R34x_v20080805/scripts/genericTargets.xml:88: Bundle org.jboss.tools.common.kb.test_0.0.0 failed to resolve.:
[echo] Missing required plug-in org.jboss.tools.common_0.0.0.
[echo] Missing required plug-in org.jboss.tools.common.kb_0.0.0.
[echo] Missing required plug-in org.jboss.tools.common.test_0.0.0.
[echo] Missing required plug-in org.jboss.tools.common.projecttemplates_0.0.0.
[echo]
[echo]
[echo] Total time: 3 minutes 2 seconds
[echo] </pre>
[echo] /opt/public/jbt-jbds/nightly-with-tests/jbds-build/3.0.0.CR1/200811132054/tests
BUILD FAILED
/home/nboldt/eclipse/workspace-jboss/devstudio-trunk/releng/org.jboss.ide.eclipse.releng/builders/buildNightly.xml:12: The following error occurred while executing this line:
/home/nboldt/eclipse/workspace-jboss/devstudio-trunk/releng/org.jboss.ide.eclipse.releng/builders/build.xml:56: The following error occurred while executing this line:
/home/nboldt/eclipse/workspace-jboss/devstudio-trunk/releng/org.jboss.ide.eclipse.releng/builders/build.xml:27: The following error occurred while executing this line:
/home/nboldt/eclipse/workspace-jboss/devstudio-trunk/releng/org.jboss.ide.eclipse.releng/builders/build.xml:37: The following error occurred while executing this line:
/home/nboldt/eclipse/workspace-jboss/devstudio-trunk/releng/org.jboss.ide.eclipse.releng/builders/product/productBuild.xml:76: The following error occurred while executing this line:
/home/nboldt/eclipse/workspace-jboss/devstudio-trunk/releng/org.jboss.ide.eclipse.releng/builders/product/productBuild.xml:105: The following error occurred while executing this line:
/home/nboldt/eclipse/workspace-jboss/devstudio-trunk/releng/org.jboss.ide.eclipse.releng/builders/product/productBuild.xml:261: Specify at least one source - a file or a resource collection.
Total time: 23 minutes 21 seconds
I suspect this is a result of the tests being coupled together, such that they depend on the whole build (builders=jmx,examples,drools-ide,archives,richfaces,jbpm-convert,freemarker,hibernate-tools,struts,jbpm,as,seam,esb,ws,birt,portlet,smooks) and its output.
Would there be value in incrementally splitting each build's tests out so they can run independently? eg.,
builders=jmx,jmx-tests
nightlyBuildSteps=standalone.product,reports,tests-jmx,build-results,update-site
--
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
12 years, 5 months