February 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8216) WeldFacesIntegrationDeployer should be activated only for JSF 2.0 deployments

by Marius Bogoevici (JIRA)

WeldFacesIntegrationDeployer should be activated only for JSF 2.0 deployments ----------------------------------------------------------------------------- Key: JBAS-8216 URL: https://jira.jboss.org/browse/JBAS-8216 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Weld/CDI Affects Versions: 6.0.0.M3 Reporter: Marius Bogoevici Assignee: Marius Bogoevici Fix For: 6.0.0.Final Use metadata produced by the JSF deployer to assess whether the deployment unit is a JSF deployment and add the lib-int/faces directory to the CP only in that case. -- 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

15 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-8475) Add Mojarra 2.0.4 workaround information to the AS/JSK integration wiki

by Jay Balunas (JIRA)

Add Mojarra 2.0.4 workaround information to the AS/JSK integration wiki ----------------------------------------------------------------------- Key: JBAS-8475 URL: https://jira.jboss.org/browse/JBAS-8475 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Integration, JSF Affects Versions: 6.0.0.M4 Reporter: Jay Balunas Assignee: Stan Silvert See JBAS-8375 for the details. If users want to use JSF RI 2.0.4. -- 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

15 years, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-8893) Multiple war files with same context path but different virtual host cause "Web mapping already exjsts for deployment"

by Sverker Abrahamsson (JIRA)

Multiple war files with same context path but different virtual host cause "Web mapping already exjsts for deployment" ---------------------------------------------------------------------------------------------------------------------- Key: JBAS-8893 URL: https://issues.jboss.org/browse/JBAS-8893 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: 6.0.0.Final Environment: Windows 7 and CentOS Linux tested, jdk 1.6 Reporter: Sverker Abrahamsson Assignee: Remy Maucherat Example: Two war's will be deployed, The first has virtual-host=www.foo.com and context-root="/", the second has virtual-host=www.bar.com and context-root="/". This will cause an exception with message "Web mapping already exjsts for deployment" from org.jboss.web.tomcat.service.deployers.TomcatDeployer.performDeployInternal line 214. The cause of the issue is in TomcatDeployer.mapVirtualHosts, see the forum post for an analyze. A sidenote, the javadoc is incorrect on that method as well. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-8503) Depchain should exclude Seam core

by Stan Silvert (JIRA)

Depchain should exclude Seam core --------------------------------- Key: JBAS-8503 URL: https://jira.jboss.org/browse/JBAS-8503 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Build System Affects Versions: 6.0.0.M5 Reporter: Stan Silvert Assignee: Andrew Rubinger See http://community.jboss.org/message/565457 It looks like the depchain needs to exclude Seam core from the seam-int dependency. If the main Seam jar is in the classpath then you can't run non-Seam JSF apps with embedded. But I'm not sure what the ramifications of excluding it might be. -- 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

15 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8372) Weld deployer should disable EJB support (not fail) if EJB is not present in JBoss AS

by Pete Muir (JIRA)

Weld deployer should disable EJB support (not fail) if EJB is not present in JBoss AS ------------------------------------------------------------------------------------- Key: JBAS-8372 URL: https://jira.jboss.org/browse/JBAS-8372 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Weld/CDI Affects Versions: 6.0.0.M4 Reporter: Pete Muir Assignee: Marius Bogoevici If EJB is removed from JBoss AS, then Weld should continue to function, and simply disable EJB support in the application -- 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

15 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-8062) Bug with deploying entity beans in JBoss 5 .....

by Nitesh S (JIRA)

Bug with deploying entity beans in JBoss 5 ..... ------------------------------------------------ Key: JBAS-8062 URL: https://jira.jboss.org/browse/JBAS-8062 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: JBossAS-5.0.1.GA Reporter: Nitesh S Assignee: Alexey Loubyansky JBoss version ------------------------------------------------------------------ JBoss [Morpheus] 5.0.1.GA (build: SVNTag=JBoss_5_0_1_GA date=200902231221) jboss.xml ------------------------------------------------------------------ <?xml version="1.0" encoding="UTF-8"?> <jboss> <enterprise-beans> <entity> <ejb-name>MyFramework</ejb-name> <local-jndi-name>JNDI_MyFramework</local-jndi-name> <configuration-name>LEVEL 2</configuration-name> </entity> </enterprise-beans> <container-configurations> <container-configuration extends="Standard CMP 2.x EntityBean"> <container-name>LEVEL 1</container-name> <container-cache-conf> <cache-policy>org.jboss.ejb.plugins.LRUEnterpriseContextCachePolicy</cache-policy> <cache-policy-conf> <min-capacity>50</min-capacity> <max-capacity>5000</max-capacity> <overager-period>300</overager-period> <max-bean-age>7200</max-bean-age> <resizer-period>400</resizer-period> <max-cache-miss-period>60</max-cache-miss-period> <min-cache-miss-period>1</min-cache-miss-period> <cache-load-factor>0.75</cache-load-factor> </cache-policy-conf> </container-cache-conf> </container-configuration> <container-configuration extends="LEVEL 1"> <container-name>LEVEL 2</container-name> <insert-after-ejb-post-create>true</insert-after-ejb-post-create> </container-configuration> </container-configurations> </jboss> ------------------------------------------------------------------ When I started server with above configurations, it results in... and did not start... 12:41:18,126 INFO [EjbModule] Deploying MyFramework 12:41:18,303 WARN [EjbModule] EJB configured to bypass security. Please verify if this is intended. Bean=MyFramework Deployment=vfszip:/D:/digite/jboss5/server/nitesh/deploy/niteshejbs.jar/ 12:41:18,303 WARN [EjbModule] There are no interceptors configured. Check the standardjboss.xml file ------------------------------------------------------------------ When I changed entity configurations to "LEVEL 1", following way, it worked.... <entity> <ejb-name>MyFramework</ejb-name> <local-jndi-name>JNDI_MyFramework</local-jndi-name> <configuration-name>LEVEL 1</configuration-name> </entity> 12:51:21,881 INFO [EjbModule] Deploying MyFramework 12:51:22,049 WARN [EjbModule] EJB configured to bypass security. Please verify if this is intended. Bean=MyFramework Deployment=vfszip:/D:/digite/jboss5/server/nitesh/deploy/niteshejbs.jar/ When "LEVEL 2" configuration is given to entity, it is not inheriting interceptors from standardjboss.xml It is issue only in JBoss 5 ..... "LEVEL 2" configuration works fine when deployed in JBoss 4.2.3 ...... -- 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

15 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-8582) Under certain circumstances a wrong locator can be removed from UnifiedInvokerHAProxy

by Tom Ross (JIRA)

Under certain circumstances a wrong locator can be removed from UnifiedInvokerHAProxy -------------------------------------------------------------------------------------- Key: JBAS-8582 URL: https://jira.jboss.org/browse/JBAS-8582 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.1.0.GA Environment: JBoss EJB 2.1 Reporter: Tom Ross Assignee: Galder Zamarreño Fix For: TBD Thee is a small window of opportunity that under failure conditions, the locator removed could be the wrong one. Under error condition UnifiedInvokerHAProxy class calls removeDeadTarget(getLocator()) method. Problem is that the getLocator() call might return a locator not associated with current client. This should be changed to removeDeadTarget(client.getInvoker().getLocator()). This way we can be sure that correct locator is aways used. -- 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

15 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-7969) XB binding of org.jboss.logging.metadata.HandlerMetaData.propertyMetaDataList

by Alexey Loubyansky (JIRA)

XB binding of org.jboss.logging.metadata.HandlerMetaData.propertyMetaDataList ----------------------------------------------------------------------------- Key: JBAS-7969 URL: https://jira.jboss.org/jira/browse/JBAS-7969 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Logging Affects Versions: JBossAS-6.0.0.M2 Reporter: Alexey Loubyansky Assignee: David Lloyd Property order is not specified for type org.jboss.beans.metadata.spi.PropertyMetaData bound to a sequence. Property order can be specified using @XmlType.propOrder or @XmlAccessorOrder. List of properties: value preInstantiate type name at org.jboss.logging.metadata.HandlerMetaData.propertyMetaDataList at org.jboss.logging.metadata.LoggingMetaData.handlerMetaDataList at org.jboss.logging.metadata.LoggingMetaData @XmlElementWrapper(name="properties") public void setPropertyMetaDataList(final List<PropertyMetaData> propertyMetaDataList) { this.propertyMetaDataList = propertyMetaDataList; } PropertyMetaData is an interface and an implementation class must be specified. It's not actually used, is it? -- 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

15 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-7907) Create a manifest-only JAR to point to all JBAS runtime binaries

by Andrew Lee Rubinger (JIRA)

Create a manifest-only JAR to point to all JBAS runtime binaries ---------------------------------------------------------------- Key: JBAS-7907 URL: https://jira.jboss.org/jira/browse/JBAS-7907 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Build System Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger A single-JAR dependency to be used primarily by EmbeddedAS, to make everything available on the application classpath in one go. -- 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

15 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-8874) Woodstox dependency causes smoke test failures

by Thomas Diesler (JIRA)

Woodstox dependency causes smoke test failures ---------------------------------------------- Key: JBAS-8874 URL: https://issues.jboss.org/browse/JBAS-8874 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Thomas Diesler 10:40:21,112 ERROR [org.jboss.as.controller] (main) operation ("composite") failed - address: ([]): javax.xml.stream.FactoryFinder$ConfigurationError: Provider com.ctc.wstx.stax.WstxOutputFactory not found at javax.xml.stream.FactoryFinder.newInstance(FactoryFinder.java:154) [:1.6.0_21] at javax.xml.stream.FactoryFinder.findJarServiceProvider(FactoryFinder.java:308) [:1.6.0_21] at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:233) [:1.6.0_21] at javax.xml.stream.XMLOutputFactory.newInstance(XMLOutputFactory.java:99) [:1.6.0_21] at org.jboss.as.controller.persistence.AbstractConfigurationPersister.marshallAsXml(AbstractConfigurationPersister.java:80) [jboss-as-controller-7.0.0.Alpha2-SNAPSHOT.jar:7.0.0.Alpha2-SNAPSHOT] at org.jboss.as.controller.persistence.XmlConfigurationPersister.store(XmlConfigurationPersister.java:90) [jboss-as-controller-7.0.0.Alpha2-SNAPSHOT.jar:7.0.0.Alpha2-SNAPSHOT] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2011