August 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Assigned: (JBAS-8303) Investigate better ways of doing injection into into EJB instances than using an interceptor

by Marius Bogoevici (JIRA)

[ https://jira.jboss.org/browse/JBAS-8303?page=com.atlassian.jira.plugin.sy... ] Marius Bogoevici reassigned JBAS-8303: -------------------------------------- Assignee: Marius Bogoevici > Investigate better ways of doing injection into into EJB instances than using an interceptor > -------------------------------------------------------------------------------------------- > > Key: JBAS-8303 > URL: https://jira.jboss.org/browse/JBAS-8303 > Project: JBoss Application Server > Issue Type: Feature Request > Components: Weld/CDI > Reporter: Pete Muir > Assignee: Marius Bogoevici > Fix For: 6.0.0.CR1 > > > Especially, a better way of getting the EJB name -- 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

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMETA-272) Update jboss-web.xml DTDs to reflect elimination of FIELD granularity session replication

by Brian Stansberry (JIRA)

Update jboss-web.xml DTDs to reflect elimination of FIELD granularity session replication ----------------------------------------------------------------------------------------- Key: JBMETA-272 URL: https://jira.jboss.org/jira/browse/JBMETA-272 Project: JBoss Metadata Issue Type: Task Security Level: Public (Everyone can see) Components: web Reporter: Brian Stansberry Fix For: jboss-metadata-web-2.0.0-alpha-15 For the legacy version DTDs, add comments that FIELD is not supported in 6.x. For 6.x version, eliminate references to FIELD. -- 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

13 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-8210) JVM configuration schema

by Brian Stansberry (JIRA)

JVM configuration schema ------------------------ Key: JBAS-8210 URL: https://jira.jboss.org/browse/JBAS-8210 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Assignee: Alexey Loubyansky Fix For: 7.0.0.M1 Domain configuration schema elements related to JVM configuration. I believe this is largely done. :) -- 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

13 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2613) Add the version for the wagon extension in the parent pom

by Mauricio Salatino (JIRA)

Add the version for the wagon extension in the parent pom --------------------------------------------------------- Key: JBRULES-2613 URL: https://jira.jboss.org/browse/JBRULES-2613 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mauricio Salatino Assignee: Mark Proctor Fix For: 5.2.0.M1 Just for correctness -- 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

13 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBJCA-396) Maven support

by Jesper Pedersen (JIRA)

Maven support ------------- Key: JBJCA-396 URL: https://jira.jboss.org/browse/JBJCA-396 Project: IronJacamar Issue Type: Task Components: Validator Reporter: Jesper Pedersen Assignee: Jeff Zhang Fix For: 1.0.0.Beta2 We need Maven support for our validator -- 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

13 years, 10 months

2
1
0 / 0

[JBoss JIRA] Closed: (JBAS-8218) Investigate potential issues with no-interface views

by Marius Bogoevici (JIRA)

[ https://jira.jboss.org/browse/JBAS-8218?page=com.atlassian.jira.plugin.sy... ] Marius Bogoevici closed JBAS-8218. ---------------------------------- Resolution: Out of Date > Investigate potential issues with no-interface views > ---------------------------------------------------- > > Key: JBAS-8218 > URL: https://jira.jboss.org/browse/JBAS-8218 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Marius Bogoevici > Assignee: Marius Bogoevici > -- 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

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-8276) Weld Extension vs. Tomcat deployer in JBoss 6

by Marius Bogoevici (JIRA)

[ https://jira.jboss.org/browse/JBAS-8276?page=com.atlassian.jira.plugin.sy... ] Marius Bogoevici commented on JBAS-8276: ---------------------------------------- Heiko, Could you upload a war for reproducing the issue? Thanks > Weld Extension vs. Tomcat deployer in JBoss 6 > --------------------------------------------- > > Key: JBAS-8276 > URL: https://jira.jboss.org/browse/JBAS-8276 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Weld/CDI > Affects Versions: 6.0.0.M4 > Reporter: Heiko Braun > Assignee: Marius Bogoevici > > When I deploy a web application that contains CDI beans to JBoss6-M4 I can see that bean deployment being executed two times. First the CDI deployer kicks in, then Tomcat deployer re-deploys the war archive, which causes a second execution of the extension: > 12:20:34,082 INFO [org.jboss.weld.Version] WELD-000900 1.0.1 (SP4) > 12:20:34,516 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] Discovered Errai Service: class com.foo.server.HelloWorldService > 12:20:34,564 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] Register CDI component as MessageCallback: @Service @ApplicationScoped com.foo.server.HelloWorldService > 12:20:34,583 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] deploy, ctxPath=/funky-app > 12:20:34,720 INFO [org.jboss.resteasy.cdi.CdiInjectorFactory] Found BeanManager at java:comp/BeanManager > 12:20:39,776 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] undeploy, ctxPath=/funky-app > 12:20:40,246 INFO [org.jboss.weld.Version] WELD-000900 1.0.1 (SP4) > 12:20:40,733 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] Discovered Errai Service: class com.foo.server.HelloWorldService > 12:20:40,844 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] Register CDI component as MessageCallback: @Service @ApplicationScoped com.foo.server.HelloWorldService > 12:20:40,856 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] deploy, ctxPath=/funky-app > 12:20:40,929 INFO [org.jboss.resteasy.cdi.CdiInjectorFactory] Found BeanManager at java:comp/BeanManager > Shouldn't it be the execution the extension tight to the tomcat deployer lifecycle? I.e. be dependent on it's meta data? -- 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

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-8281) ProcessInjectionTarget not fired for Servlet, Filter, Servlet Listener, Tag Library Listener and JSF Managed Bean

by Marius Bogoevici (JIRA)

[ https://jira.jboss.org/browse/JBAS-8281?page=com.atlassian.jira.plugin.sy... ] Marius Bogoevici closed JBAS-8281. ---------------------------------- Resolution: Done > ProcessInjectionTarget not fired for Servlet, Filter, Servlet Listener, Tag Library Listener and JSF Managed Bean > ----------------------------------------------------------------------------------------------------------------- > > Key: JBAS-8281 > URL: https://jira.jboss.org/browse/JBAS-8281 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Weld/CDI > Reporter: Jozef Hartinger > Assignee: Marius Bogoevici > Fix For: 6.0.0.CR1 > > > org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ContainerEventTest.testEventFiredForServletListener() > org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ContainerEventTest.testEventFiredForTagLibraryListener() > org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ContainerEventTest.testEventFiredForServlet() > org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ContainerEventTest.testEventFiredForFilter() > org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ContainerEventTest.testProcessInjectionTargetEventFiredForJsfManagedBean() > Note that the event is fired for Tag library handler > org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ContainerEventTest.testProcessInjectionTargetEventFiredForTagHandler() -- 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

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMETA-294) Add replication-mode, backups to replication-config in jboss-web.xml

by Paul Ferraro (JIRA)

Add replication-mode, backups to replication-config in jboss-web.xml -------------------------------------------------------------------- Key: JBMETA-294 URL: https://jira.jboss.org/browse/JBMETA-294 Project: JBoss Metadata Issue Type: Feature Request Security Level: Public (Everyone can see) Components: web Affects Versions: jboss-metadata-web-2.0.0-alpha-14 Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: jboss-metadata-web-2.0.0-alpha-15 Make the typical distributed cache configurations configurable via jboss-web.xml; don't force users to go to a separate Infinispan configuration file. Add the following elements to <replication-config/>: <replication-mode/> : either SYNCHRONOUS or ASYNCHRONOUS <backups/> : integer, negative means total replication, 0 means local-only mode, positive means distribution mode, using the specified number of backups. -- 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

13 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1235) Avoid excessive calls to InetAddress.getLocalHost() [Clone of JBREM-1234]

by Ron Sigal (JIRA)

Avoid excessive calls to InetAddress.getLocalHost() [Clone of JBREM-1234] ------------------------------------------------------------------------- Key: JBREM-1235 URL: https://jira.jboss.org/browse/JBREM-1235 Project: JBoss Remoting Issue Type: Quality Risk Security Level: Public (Everyone can see) Affects Versions: 2.5.3 (Flounder) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.5.3.SP1 >From JBPAPP-4617 "Possible performance issue in Remoting": JMS remote connections that are used locally result in a lot of calls to InetAddress.getLocalHost() which for some reason is slow. Why not: private static final InetAddress LOCAL_HOST; static { try { LOCAL_HOST = InetAddress.getLocalHost(); } catch (UnknownHostException e) { throw new ExceptionInInitializerError(e); } } private static InetAddress getLocalHost() throws UnknownHostException { return LOCAL_HOST; } Which is roughly 1000x faster. -- 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

13 years, 10 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2010