September 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8264) @FacesValidator annotated class not registered as Validator

by Vladimir Blagojevic (JIRA)

@FacesValidator annotated class not registered as Validator ------------------------------------------------------------ Key: JBAS-8264 URL: https://jira.jboss.org/browse/JBAS-8264 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JSF Affects Versions: 6.0.0.M4 Reporter: Vladimir Blagojevic Assignee: Stan Silvert The presence of @FacesValidator [1] annotation on a class should automatically registers the class with the runtime as a Validator. However, AS 6.0.0.M4 fails to do so. Use of @FacesValidator worked in M3. [1] http://download-llnw.oracle.com/javaee/6/api/javax/faces/validator/FacesV... -- 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, 10 months

3
7
0 / 0

[JBoss JIRA] Reopened: (JBAS-6795) NullPointerException thrown from getEntityManagerFactory() when persistence unit is packaged with WAR

by Shelly McGowan (JIRA)

[ https://jira.jboss.org/browse/JBAS-6795?page=com.atlassian.jira.plugin.sy... ] Shelly McGowan reopened JBAS-6795: ---------------------------------- > NullPointerException thrown from getEntityManagerFactory() when persistence unit is packaged with WAR > ----------------------------------------------------------------------------------------------------- > > Key: JBAS-6795 > URL: https://jira.jboss.org/browse/JBAS-6795 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Deployers > Reporter: Shelly McGowan > Assignee: Carlo de Wolf > Priority: Critical > Fix For: 6.0.0.M5 > > > 2009-04-15 00:26:45,056 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (ResourceContainer.invoker.nonDaemon-12) deploy, ctxPath=/web_pkg_standalone_component_web > 2009-04-15 00:26:45,082 ERROR [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (ResourceContainer.invoker.nonDaemon-12) ENC setup failed > java.lang.NullPointerException > at org.jboss.injection.PersistenceUnitHandler.getEntityManagerFactory(PersistenceUnitHandler.java:172) > at org.jboss.injection.PersistenceUnitHandler.getFactory(PersistenceUnitHandler.java:163) > at org.jboss.injection.PuEncInjector.inject(PuEncInjector.java:54) > at org.jboss.web.tomcat.service.TomcatInjectionContainer.populateEnc(TomcatInjectionContainer.java:482) > at org.jboss.web.tomcat.service.deployers.TomcatDeployment$EncListener.lifecycleEvent(TomcatDeployment.java:471) > at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) > at org.apache.catalina.core.StandardContext.start(StandardContext.java:4388) > at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:310) > at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:142) > at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:461) > at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) > at org.jboss.web.deployers.WebModule.start(WebModule.java:97) > This is reproducable with the following packaging scenarios: > persistence unit in the WEB-INF/classes directory of a standalone .war > persistence unit in the WEB-INF/lib directory of a standalone .war > persistence unit in the lib directory of an enterprise archive containing a .war and and ejb.jar -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBAS-6795) NullPointerException thrown from getEntityManagerFactory() when persistence unit is packaged with WAR

by Shelly McGowan (JIRA)

[ https://jira.jboss.org/browse/JBAS-6795?page=com.atlassian.jira.plugin.sy... ] Shelly McGowan resolved JBAS-6795. ---------------------------------- Fix Version/s: 6.0.0.M5 (was: 6.0.0.CR1) Resolution: Done > NullPointerException thrown from getEntityManagerFactory() when persistence unit is packaged with WAR > ----------------------------------------------------------------------------------------------------- > > Key: JBAS-6795 > URL: https://jira.jboss.org/browse/JBAS-6795 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Deployers > Reporter: Shelly McGowan > Assignee: Carlo de Wolf > Priority: Critical > Fix For: 6.0.0.M5 > > > 2009-04-15 00:26:45,056 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (ResourceContainer.invoker.nonDaemon-12) deploy, ctxPath=/web_pkg_standalone_component_web > 2009-04-15 00:26:45,082 ERROR [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (ResourceContainer.invoker.nonDaemon-12) ENC setup failed > java.lang.NullPointerException > at org.jboss.injection.PersistenceUnitHandler.getEntityManagerFactory(PersistenceUnitHandler.java:172) > at org.jboss.injection.PersistenceUnitHandler.getFactory(PersistenceUnitHandler.java:163) > at org.jboss.injection.PuEncInjector.inject(PuEncInjector.java:54) > at org.jboss.web.tomcat.service.TomcatInjectionContainer.populateEnc(TomcatInjectionContainer.java:482) > at org.jboss.web.tomcat.service.deployers.TomcatDeployment$EncListener.lifecycleEvent(TomcatDeployment.java:471) > at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) > at org.apache.catalina.core.StandardContext.start(StandardContext.java:4388) > at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:310) > at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:142) > at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:461) > at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) > at org.jboss.web.deployers.WebModule.start(WebModule.java:97) > This is reproducable with the following packaging scenarios: > persistence unit in the WEB-INF/classes directory of a standalone .war > persistence unit in the WEB-INF/lib directory of a standalone .war > persistence unit in the lib directory of an enterprise archive containing a .war and and ejb.jar -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-7285) Lazy initialization fix for wrong use case.

by Vicky Kak (JIRA)

Lazy initialization fix for wrong use case. ------------------------------------------- Key: JBAS-7285 URL: https://jira.jboss.org/jira/browse/JBAS-7285 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Reporter: Vicky Kak Assignee: Vicky Kak Fix For: JBossAS-5.2.0.GA, JBossAS-Branch_4_2 The JCA lazy initialization does not work in the following sceanrio ********************************************************************* DataSource ds = ... Connection c = ds.getConnection(); UserTransaction ut = ... ut.begin(); // Do work c = ds.getConnection(); // This should be avoided and looks antipattern. ut.commit(); ut.begin(); ********************************************************************* Getting the connection again in the TX context causes the issue, the subsequent ds.getConnection() leads to multiple enlistment of the local XAResources and thus causing this warning http://www.jboss.org/community/wiki/Multiple1pc The application developers should not follow the above coding pattern, however we should fix the issue cropping due to this coding practice as it could lead some misbehaviour in container, there are no evidences about the misbehaviour but it had been reported by our customers. -- 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, 10 months

5
9
0 / 0

[JBoss JIRA] Reopened: (JBAS-8217) Simple war based ejb deployment does not work on JBoss 6.0M3

by Shelly McGowan (JIRA)

[ https://jira.jboss.org/browse/JBAS-8217?page=com.atlassian.jira.plugin.sy... ] Shelly McGowan reopened JBAS-8217: ---------------------------------- > Simple war based ejb deployment does not work on JBoss 6.0M3 > ------------------------------------------------------------- > > Key: JBAS-8217 > URL: https://jira.jboss.org/browse/JBAS-8217 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Weld/CDI > Environment: Snow Leopard 10.6.3, Java 6. > Reporter: Vladimir Blagojevic > Assignee: Marius Bogoevici > Fix For: 6.0.0.M5 > > Attachments: weldint-64.zip > > > Have a simple war app with pojo ejb, trying to inject ejb field into a managed bean which is in turn accessed from a facelet. @EJB and @Inject dot not work on JBoss 6.0 M3. Attaching minimal example app. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBAS-8217) Simple war based ejb deployment does not work on JBoss 6.0M3

by Shelly McGowan (JIRA)

[ https://jira.jboss.org/browse/JBAS-8217?page=com.atlassian.jira.plugin.sy... ] Shelly McGowan resolved JBAS-8217. ---------------------------------- Fix Version/s: 6.0.0.M5 (was: 6.0.0.CR1) Resolution: Done > Simple war based ejb deployment does not work on JBoss 6.0M3 > ------------------------------------------------------------- > > Key: JBAS-8217 > URL: https://jira.jboss.org/browse/JBAS-8217 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Weld/CDI > Environment: Snow Leopard 10.6.3, Java 6. > Reporter: Vladimir Blagojevic > Assignee: Marius Bogoevici > Fix For: 6.0.0.M5 > > Attachments: weldint-64.zip > > > Have a simple war app with pojo ejb, trying to inject ejb field into a managed bean which is in turn accessed from a facelet. @EJB and @Inject dot not work on JBoss 6.0 M3. Attaching minimal example app. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-7924) smoke-tests build SUCCESS despite FAILURE

by Thomas Diesler (JIRA)

smoke-tests build SUCCESS despite FAILURE ----------------------------------------- Key: JBAS-7924 URL: https://jira.jboss.org/jira/browse/JBAS-7924 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Reporter: Thomas Diesler Assignee: Shelly McGowan Fix For: JBossAS-6.0.0.M3 [tdiesler@tdvaio testsuite]$ ./build.sh clean jars smoke-tests smoke-tests: [server:start] Starting server "all", with command (start timeout is 120 seconds ): [server:start] /usr/java/jdk1.6.0_17/bin/java -cp /home/tdiesler/git/jbossas/build/target/jboss-6.0.0-SNAPSHOT/bin/run.jar:/usr/java/jdk1.6/lib/tools.jar -Xms128m -Xmx512m -XX:MaxPermSize=512m -XX:+HeapDumpOnOutOfMemoryError -XX:-UseGCOverheadLimit -Djava.net.preferIPv4Stack=true -Djava.endorsed.dirs=/home/tdiesler/git/jbossas/build/target/jboss-6.0.0-SNAPSHOT/lib/endorsed -Djgroups.udp.ip_ttl=0 -Djboss.server.log.threshold=DEBUG -Djava.endorsed.dirs=/home/tdiesler/git/jbossas/build/target/jboss-6.0.0-SNAPSHOT/lib/endorsed/ -Dxb.builder.useUnorderedSequence=true org.jboss.Main -c all -b localhost -g DefaultPartition [server:start] Server started. ... smoke-tests-raw: [echo] [echo] junit.timeout: 300000 [echo] jbosstest.iterationcount: 10 [echo] jbosstest.threadcount: 5 [echo] jbosstest.beancount: 5 [echo] [mkdir] Created dir: /home/tdiesler/git/jbossas/testsuite/output/log ... [junit] Running org.jboss.test.jmsra.test.RaJMSSessionUnitTestCase [junit] javax.ejb.EJBException: javax.jms.JMSException: Could not create a session: Unable to get managed connection for JmsXA) [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 2.423 sec [junit] Test org.jboss.test.jmsra.test.RaJMSSessionUnitTestCase FAILED ... [server:stop] Shutting down server: all [server:stop] log4j:WARN No appenders could be found for logger (org.jnp.interfaces.TimedSocketFactory). [server:stop] log4j:WARN Please initialize the log4j system properly. [server:stop] shutdownTimeout will be=45 [server:stop] Server stopped. BUILD SUCCESSFUL Total time: 6 minutes 3 seconds -- 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, 10 months

4
10
0 / 0

[JBoss JIRA] Created: (JBAS-8230) Migrate to Google Guava from google-collections

by Nick Belaevski (JIRA)

Migrate to Google Guava from google-collections ----------------------------------------------- Key: JBAS-8230 URL: https://jira.jboss.org/browse/JBAS-8230 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Weld/CDI Affects Versions: 6.0.0.M4 Reporter: Nick Belaevski Assignee: Pete Muir weld-deployer comes with google-collections library and that seems to be causing problems for projects using guava (that is the later version of collections library + foundation classes). Please see related forum thread also. -- 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, 10 months

4
5
0 / 0

[JBoss JIRA] Created: (JBAS-8226) All EJB 3.1 Session Beans are treated as no-interface views

by Marius Bogoevici (JIRA)

All EJB 3.1 Session Beans are treated as no-interface views ----------------------------------------------------------- Key: JBAS-8226 URL: https://jira.jboss.org/browse/JBAS-8226 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.M4 JBossSessionBean31DescriptorAdaptor.noInterfaceView is always set to true -- 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, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-8018) Complete Site and Documentation for AS6 JSF

by Stan Silvert (JIRA)

Complete Site and Documentation for AS6 JSF ------------------------------------------- Key: JBAS-8018 URL: https://jira.jboss.org/jira/browse/JBAS-8018 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Stan Silvert Assignee: Stan Silvert -- 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, 10 months

2
4
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 September 2010