November 2009 - jbosstools-issues

[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-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-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

[JBoss JIRA] Created: (JBIDE-3574) JBoss Tools wizards have black borders around SWT controls

by Denis Golovin (JIRA)

JBoss Tools wizards have black borders around SWT controls ---------------------------------------------------------- Key: JBIDE-3574 URL: https://jira.jboss.org/jira/browse/JBIDE-3574 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.0.CR2 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 3.0.0.GA -- 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

3
21
0 / 0

[JBoss JIRA] Created: (JBIDE-4454) Write automated tests for UI part of JBT

by Yura Zhishko (JIRA)

Write automated tests for UI part of JBT ---------------------------------------- Key: JBIDE-4454 URL: https://jira.jboss.org/jira/browse/JBIDE-4454 Project: Tools (JBoss Tools) Issue Type: Sub-task Reporter: Yura Zhishko -- 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

5
11
0 / 0

[JBoss JIRA] Created: (JBIDE-4971) Deploying BIRT aaplication to JBoss AS 5.x

by Snjezana Peco (JIRA)

Deploying BIRT aaplication to JBoss AS 5.x ------------------------------------------ Key: JBIDE-4971 URL: https://jira.jboss.org/jira/browse/JBIDE-4971 Project: Tools (JBoss Tools) Issue Type: Bug Components: birt, JBossAS Affects Versions: 3.1.0.M3 Reporter: Snjezana Peco Assignee: Snjezana Peco Steps to reproduce - download testbirt.zip project from https://anonsvn.jboss.org/repos/jbosstools/workspace/snjeza/seam-examples... (56MB) - configure Seam 2.2.0 and a JBoss Runtime - deploy to JBoss AS server - call the "Test Birt" link JBoss AS 4.2.3 - works correctly JBoss AS 5.1.0 GA - doesn't work due to the problem described on http://www.jboss.org/index.html?module=bb&op=viewtopic&t=156898 JBoss EAP 5.0 You will often get warnings (eap5log1.txt) When calling the "Test Birt" action, you will get either eap5log2.txt or eap5log3.txt. The problem isn't always reproducible. Sometimes it doesn't happen, but rarely. The problem happens due to the way in which JBoss AS 5 initializes the application. BIRT uses org.eclipse.birt.report.listener.ViewerServletContextListener to initialize the BIRT engine (OSGi) when starting the application. If this listener is commented/removed, the problem won't happen. If the BIRT engine hasn't been already initialized, it will be initialized when starting a BIRT servlet so that this listener isn't obliged. Maybe this is even better because the BIRT engine is initialized only when it is called. For now, we can use this as a workaround. However, it seems that there is a problem when the JBoss AS server initializes the application. Another problem is that JBoss AS aggressively logs a warning about missing classes in BIRT internal jars (WEB-INF/platform/plugins/*.jar) when adding a new *xhtml file to the application. This can be solved by adding a line to <JBOSSAS_HOME/server/default/conf/bootstrap/profile.xml: ... <bean name="WebVisitorAttributes" class="org.jboss.system.server.profile.basic.IncludeExcludeVisitorAttributes"> <constructor> <parameter> <set> <value>.war</value> </set> </parameter> <parameter> <set> <value>WEB-INF/classes</value> <value>WEB-INF/lib</value> <value>WEB-INF/platform</value>  </set> </parameter> </constructor> </bean> ... The workaround isn't applicable to JBoss AS 5.1.0.GA. -- 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

6
19
0 / 0

[JBoss JIRA] Created: (JBIDE-4151) Disconnect between Visual Editor Source and Preview across multiple Tabs

by Drew Arrigoni (JIRA)

Disconnect between Visual Editor Source and Preview across multiple Tabs ------------------------------------------------------------------------ Key: JBIDE-4151 URL: https://jira.jboss.org/jira/browse/JBIDE-4151 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.0.0.GA Environment: Fedora 10, JBDS 2.0, JDK 1.5 x86_64 Reporter: Drew Arrigoni Priority: Minor When editing the same source file in multiple tabs, the Preview view of one tab does not remain sync'd with changes made in other tabs. Here is an example... <a href="http://s698.photobucket.com/albums/vv349/StormTAG/?action=view&current=Pr..." target="_blank"><img src="http://i698.photobucket.com/albums/vv349/StormTAG/PreviewSourceDisconnect..." border="0" alt="Source_Preview"></a> It seems limited to the Preview mode, as the Visual/Editor portion remains sync'd correctly. Here is an example... <a href="http://s698.photobucket.com/albums/vv349/StormTAG/?action=view&current=Vi..." target="_blank"><img src="http://i698.photobucket.com/albums/vv349/StormTAG/VisualSourceSource.png" border="0" alt="Source_SourceVisual"></a> I was told to report this as a bug in the associated forum. :) -- 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

7
27
0 / 0

[JBoss JIRA] Created: (JBIDE-910) Servlet Generator for Dynamic Web Project is creating errornous web.xml files

by Steve Davidson (JIRA)

Servlet Generator for Dynamic Web Project is creating errornous web.xml files ----------------------------------------------------------------------------- Key: JBIDE-910 URL: http://jira.jboss.com/jira/browse/JBIDE-910 Project: JBoss Tools Issue Type: Bug Components: JBoss Tools Core Affects Versions: 2.0.0.Beta3 Environment: Windows XP Professionial SP2 Reporter: Steve Davidson When creating a Servlet using the New File - Servlet wizard in a Dynamic Web Project in a clean workspace, the web.xml file is not properly created. Specifically, this is what gets generated; <?xml version="1.0" encoding="UTF-8"?> <web-app id="WebApp_ID" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"> <display-name> DemoFlaw</display-name> <servlet> <description> </description> <display-name> DemoServlet</display-name> <servlet-name>DemoServlet</servlet-name> <servlet-class> org.ccccd.webone.DemoServlet</servlet-class> </servlet> <servlet-mapping> <servlet-name>DemoServlet</servlet-name> <url-pattern>/DemoServlet</url-pattern> </servlet-mapping> <welcome-file-list> <welcome-file>index.html</welcome-file> <welcome-file>index.htm</welcome-file> <welcome-file>index.jsp</welcome-file> <welcome-file>default.html</welcome-file> <welcome-file>default.htm</welcome-file> <welcome-file>default.jsp</welcome-file> </welcome-file-list> </web-app> The extra whitespace at the end of the start tag <servlet-class> causes the deployment to fail. This is occuring on 100% of the computers in the Java Web Class that I am teaching. -Steve -- 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

14 years, 3 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-2726) Incorrect behavior of Server properties > Ports Monitoring

by Aliaksey Nis (JIRA)

Incorrect behavior of Server properties > Ports Monitoring ---------------------------------------------------------- Key: JBIDE-2726 URL: https://jira.jboss.org/jira/browse/JBIDE-2726 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.0.0.alpha Environment: WindowsXP SP2 JBoss Tools Version: 3.0.0.Alpha1 Build id: 200809010011-nightly Build date: 01 september 2008 JDK 1.5_08 Reporter: Aliaksey Nis Priority: Optional EXECUTE: Open Server view. EXECUTE: Right click on Server > Properties. EXECUTE: Select Monitoring. Press Add button. EXECUTE: Add port number in "Monitor port". Try to select something from drop-down menu "Content". FAILURE: Content menu is empty. But Ok button is enabled. When Ok button pressed - nothing happens (except wizard closing). -- 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, 3 months

5
5
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 November 2009