September 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBDS-856) Mac OSX Snow Leopard: Server cannot be saved for the following reasons: One or more ports have an invalid value

by Robert Morse (JIRA)

Mac OSX Snow Leopard: Server cannot be saved for the following reasons: One or more ports have an invalid value ---------------------------------------------------------------------------------------------------------------- Key: JBDS-856 URL: https://jira.jboss.org/jira/browse/JBDS-856 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 2.0.0.GA Environment: Mac OS X 10.6 (Snow Leopard) JBoss AS 5.1.0.GA JDK 1.6 Reporter: Robert Morse When trying to create a new JBoss AS server, JBDS complains with: The server cannot be saved for the following reasons: One or more ports have an invalid value. This may adversely affect the tooling's ability to interact with the server. I've never seen this error before, and I'm not sure what the port values should be. Currently, the Automatically detect check boxes are checked -- 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, 1 month

6
19
0 / 0

[JBoss JIRA] Created: (JBIDE-7125) Usage Reporting description in N&N

by Max Andersen (JIRA)

Usage Reporting description in N&N ---------------------------------- Key: JBIDE-7125 URL: https://jira.jboss.org/browse/JBIDE-7125 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: usage Reporter: Denis Golovin Assignee: Andre Dietisheim Fix For: 3.2.0.M2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
5
0 / 0

[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

14 years, 1 month

3
6
0 / 0

[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

14 years, 1 month

5
10
0 / 0

[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

14 years, 1 month

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-7141) Provide details about selected runtime in the facet configuration dialog

by Lukas Jungmann (JIRA)

Provide details about selected runtime in the facet configuration dialog ------------------------------------------------------------------------ Key: JBIDE-7141 URL: https://jira.jboss.org/browse/JBIDE-7141 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Webservices Affects Versions: 3.1.1 Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick Attachments: screenshot.png It would be nice if we could tell user some details about JBossWS runtime he is going to use. See attached screenshot for how it could look like -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

5
19
0 / 0

[JBoss JIRA] Created: (JBIDE-5045) JSF 2: Support annotated manage beans in EL

by Alexey Kazakov (JIRA)

JSF 2: Support annotated manage beans in EL ------------------------------------------- Key: JBIDE-5045 URL: https://jira.jboss.org/jira/browse/JBIDE-5045 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JSF Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: LATER We have to create JSF builder to load annotated manage beans to provide JSF model which should be used be JSF EL Resolver. -- 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, 1 month

5
9
0 / 0

[JBoss JIRA] Created: (JBIDE-6953) Disable Usage Reporting in Tests

by Andre Dietisheim (JIRA)

Disable Usage Reporting in Tests -------------------------------- Key: JBIDE-6953 URL: https://jira.jboss.org/browse/JBIDE-6953 Project: Tools (JBoss Tools) Issue Type: Release Environment: CI, Tests Reporter: Andre Dietisheim Assignee: Denis Golovin Priority: Blocker Fix For: 3.2.0.M2 the UI tests we run should not trigger hits in our usage tracking. The plugin has a preferences setting that disables reporting. It looks like we disable reporting for our UI test by having a custom config.ini for our UI tests. The preference settings is: "allowUsageReportPreference" It is in the Configuration Scope (common to all workbenches of a particular eclipse instance). For further lookup @see IUsageReportPreferenceConstants#USAGEREPORT_ENABLED_ID -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

4
16
0 / 0

[JBoss JIRA] Created: (JBIDE-6569) Make git repo available for JBoss Tools

by Max Rydahl Andersen (JIRA)

Make git repo available for JBoss Tools --------------------------------------- Key: JBIDE-6569 URL: https://jira.jboss.org/browse/JBIDE-6569 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Max Rydahl Andersen Fix For: LATER I think it would be useful to explore how to make a git-svn repo available for jboss tools trunk. Opening this issue for keeping track of what have been attempted so far. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
7
0 / 0

[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

14 years, 2 months

1
3
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 September 2010