January 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8387) support injection for a servlet that is registered programmatically

by Marcel Kolsteren (JIRA)

support injection for a servlet that is registered programmatically ------------------------------------------------------------------- Key: JBAS-8387 URL: https://jira.jboss.org/browse/JBAS-8387 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Weld/CDI Affects Versions: 6.0.0.M4 Reporter: Marcel Kolsteren Assignee: Marius Bogoevici Injection of a CDI Managed Bean into a servlet works for servlets that are registered using web.xml, but fails for servlets that are registered using the addServlet() method of the servlet context. Supporting injection in both cases would be more consistent and more convenient for developers. In order to demonstrate this issue, I created an Arquillian test for a managed JBoss M4 application server. The test deploys a war-file that contains two servlets. Both servlets refer to the same servlet class. The servlet class is very simple: it has a field into which a request scoped bean is injected, and it reports to the client whether or not this field contains a null value. The first servlet is defined in the web.xml file, the second servlet is registered programmatically by calling ServletContext.addServlet. The test cases show that the first servlet works as expected. However, the second servlet detects a null value in the field that should contain an injected instance of the request scoped bean. Steps for reproduction: unpack the attached zip file export JAVA_HOME = <home of your JDK> export JBOSS_HOME = <root directory of your JBoss 6 M4 server> mvn test -- 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, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8312) Exception when trying to specify ear-specific log

by Greg Zoller (JIRA)

Exception when trying to specify ear-specific log ------------------------------------------------- Key: JBAS-8312 URL: https://jira.jboss.org/browse/JBAS-8312 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Logging Affects Versions: 6.0.0.M3 Environment: Windows, JDK 1.6 Reporter: Greg Zoller Assignee: David Lloyd I get the exception below when trying to specify my own log file for my trivial EJB EAR. My jboss-logging.jar is provided below. The exception happens while the server is coming up and the EAR is loaded, but before any attempt to access or use the log occurs. <?xml version="1.0" encoding="UTF-8"?>  <logging xmlns="urn:jboss:logging:6.0" context="com.myco.apps">  <define-context name="com.myco.apps"/>  <file-handler file-name="/logs/constellation/foo.log" name="FILE" autoflush="true" append="true"> <formatter> <pattern-formatter pattern="%d %-5p [%c] (%t) %s%E%n"/> </formatter>  </file-handler>  <root-logger> <level name="INFO"/> <handlers> <handler-ref name="FILE"/> </handlers> </root-logger> </logging> 13:05:56,284 ERROR [AbstractKernelController] Error installing to Instantiated: name=Logging:CONTEXT:com.aviall.apps state=Described: java.lang.IllegalAccessException: Class org.jboss.reflect.plugins.introspection.ReflectionUtils can not access a member of class org.jboss.logmanager.LogContext with modifiers "" at sun.reflect.Reflection.ensureMemberAccess(Unknown Source) [:1.6.0_20] at java.lang.reflect.Constructor.newInstance(Unknown Source) [:1.6.0_20] at org.jboss.reflect.plugins.introspection.ReflectionUtils.newInstance(ReflectionUtils.java:149) [jboss-reflect.jar:2.2.0.Alpha4] at org.jboss.reflect.plugins.introspection.ReflectConstructorInfoImpl.newInstance(ReflectConstructorInfoImpl.java:107) [jboss-reflect.jar:2.2.0.Alpha4] at org.jboss.joinpoint.plugins.BasicConstructorJoinPoint.dispatch(BasicConstructorJoinPoint.java:81) [jboss-reflect.jar:2.2.0.Alpha4] at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.dispatch(AOPConstructorJoinpoint.java:109) [jboss-aop-mc-int.jar:2.2.0.Alpha9] at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:257) [jboss-kernel.jar:2.2.0.Alpha9] at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47) [jboss-kernel.jar:2.2.0.Alpha9] at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:125) [jboss-kernel.jar:2.2.0.Alpha9] at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:72) [jboss-kernel.jar:2.2.0.Alpha9] at org.jboss.kernel.plugins.dependency.InstantiateAction.installActionInternal(InstantiateAction.java:67) [jboss-kernel.jar:2.2.0.Alpha9] at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54) [jboss-kernel.jar:2.2.0.Alpha9] at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42) [jboss-kernel.jar:2.2.0.Alpha9] at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) [jboss-dependency.jar:2.2.0.Alpha9] at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) [jboss-dependency.jar:2.2.0.Alpha9] at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) [jboss-dependency.jar:2.2.0.Alpha9] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:377) [jboss-dependency.jar:2.2.0.Alpha9] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2042) [jboss-dependency.jar:2.2.0.Alpha9] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1081) [jboss-dependency.jar:2.2.0.Alpha9] at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1320) [jboss-dependency.jar:2.2.0.Alpha9] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1244) [jboss-dependency.jar:2.2.0.Alpha9] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1137) [jboss-dependency.jar:2.2.0.Alpha9] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:892) [jboss-dependency.jar:2.2.0.Alpha9] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:639) [jboss-dependency.jar:2.2.0.Alpha9] at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:180) [:2.2.0.Alpha4] at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:58) [:2.2.0.Alpha4] at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62) [:2.2.0.Alpha4] at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55) [:2.2.0.Alpha4] at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) [:2.2.0.Alpha4] at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1857) [:2.2.0.Alpha4] at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1575) [:2.2.0.Alpha4] at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1596) [:2.2.0.Alpha4] at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1516) [:2.2.0.Alpha4] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:377) [jboss-dependency.jar:2.2.0.Alpha9] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2042) [jboss-dependency.jar:2.2.0.Alpha9] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1081) [jboss-dependency.jar:2.2.0.Alpha9] at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1320) [jboss-dependency.jar:2.2.0.Alpha9] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1244) [jboss-dependency.jar:2.2.0.Alpha9] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1137) [jboss-dependency.jar:2.2.0.Alpha9] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:937) [jboss-dependency.jar:2.2.0.Alpha9] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:652) [jboss-dependency.jar:2.2.0.Alpha9] at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:2008) [:2.2.0.Alpha4] at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1101) [:2.2.0.Alpha4] at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679) [:2.2.0.Alpha4] at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117) [:6.0.0.20100429-M3] at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70) [:6.0.0.20100429-M3] at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53) [:6.0.0.20100429-M3] at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:403) [:6.0.0.20100429-M3] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:377) [jboss-dependency.jar:2.2.0.Alpha9] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2042) [jboss-dependency.jar:2.2.0.Alpha9] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1081) [jboss-dependency.jar:2.2.0.Alpha9] at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1320) [jboss-dependency.jar:2.2.0.Alpha9] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1244) [jboss-dependency.jar:2.2.0.Alpha9] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1137) [jboss-dependency.jar:2.2.0.Alpha9] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:892) [jboss-dependency.jar:2.2.0.Alpha9] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:639) [jboss-dependency.jar:2.2.0.Alpha9] at org.jboss.system.server.profileservice.repository.AbstractProfileService.registerProfile(AbstractProfileService.java:308) [:6.0.0.20100429-M3] at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:256) [:6.0.0.20100429-M3] at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:97) [:6.0.0.20100429-M3] at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(AbstractServer.java:827) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5] at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:417) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5] at java.lang.Thread.run(Unknown Source) [:1.6.0_20] -- 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, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-8138) Simple script to set up a new server configuration

by Brian Stansberry (JIRA)

Simple script to set up a new server configuration -------------------------------------------------- Key: JBAS-8138 URL: https://jira.jboss.org/browse/JBAS-8138 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Brian Stansberry Fix For: Unscheduled This JIRA is based on feedback we received after the Andiamo BOF at JBoss World 2010: > A simple createServer.sh script that sets unique >> ports and unique identifiers would be handy for creating clusters in >> small environments or on a development workstation. -- 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, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-8678) Updated Filesystem deployment scanning

by Brian Stansberry (JIRA)

Updated Filesystem deployment scanning -------------------------------------- Key: JBAS-8678 URL: https://jira.jboss.org/browse/JBAS-8678 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Implement changes described at http://community.jboss.org/message/572083#572083 I'm going to create a separate subtask for the issue of a flag on the deployment repository config to remove the requirement for a .dodeploy file on an exploded deployment and instead support the legacy behavior of touching the standard deployment descriptor in META-INF. That is more of a nice-to-have and shouldn't block implementation of the rest. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1919) Add "invokerDestructionDelay" parameter to EJB3 InvokerLocator

by Ron Sigal (JIRA)

Add "invokerDestructionDelay" parameter to EJB3 InvokerLocator -------------------------------------------------------------- Key: EJBTHREE-1919 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1919 Project: EJB 3.0 Issue Type: Task Reporter: Ron Sigal Currently, each EJB3 invocation creates a new Remoting connection. However, the Remoting parameter "invokerDestructionDelay" (value in milliseconds) can be used to delay the destruction of a client invoker so that it might still exist for the next EJB3 invovation. -- 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, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBVFS-164) Add a URLStreamHandlerFactory service

by Thomas Diesler (JIRA)

Add a URLStreamHandlerFactory service ------------------------------------- Key: JBVFS-164 URL: https://jira.jboss.org/browse/JBVFS-164 Project: JBoss VFS Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: John Bailey The ModularURLStreamHandlerFactory can dynamically load stream handlers from a list of modules that contain META-INF/services/java.net.URLStreamHandlerFactory The jboss-vfs module should contain such a service definition -- 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, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2741) Unify the Marshalling Strategies for Process Variables and Session's Snapshots

by Mauricio Salatino (JIRA)

Unify the Marshalling Strategies for Process Variables and Session's Snapshots ------------------------------------------------------------------------------ Key: JBRULES-2741 URL: https://jira.jboss.org/browse/JBRULES-2741 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 5.2.0.M1 Reporter: Mauricio Salatino Assignee: Mauricio Salatino The main goal of this feature is to provide an unified mechanism to marshall objects that are used to persist the status of the knowledge session. Two different strategies were used by the sessionInfo and ProcessInstanceInfo marshallers with the Variable Persistence Strategies. -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7166) org.jboss.Shutdown to use org.jboss.naming.NamingProviderURLWriter persist file

by Juergen none (JIRA)

org.jboss.Shutdown to use org.jboss.naming.NamingProviderURLWriter persist file ------------------------------------------------------------------------------- Key: JBAS-7166 URL: https://jira.jboss.org/jira/browse/JBAS-7166 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Naming Affects Versions: JBossAS-5.1.0.GA Environment: 15:59:02,389 INFO [ServerInfo] Java version: 1.6.0_14,Sun Microsystems Inc. 15:59:02,390 INFO [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_14-b08) 15:59:02,390 INFO [ServerInfo] Java VM: Java HotSpot(TM) 64-Bit Server VM 14.0-b16,Sun Microsystems Inc. 15:59:02,390 INFO [ServerInfo] OS-System: Linux 2.6.9-22.0.1.ELsmp,amd64 Reporter: Juergen none Assignee: Scott M Stark i would like to see org.jboss.Shutdown in bin/shutdown.jar make use of persist file created by org.jboss.naming.NamingProviderURLWriter containing jnp service url i probably can do something like "java -jar shutdown.jar -s `cat jnp-service.url` -S" but it depends on OS -- 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, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2750) Drools Grid Impl2 GridServiceDescription format parsers

by Mauricio Salatino (JIRA)

Drools Grid Impl2 GridServiceDescription format parsers -------------------------------------------------------- Key: JBRULES-2750 URL: https://jira.jboss.org/browse/JBRULES-2750 Project: Drools Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Mauricio Salatino Assignee: Mauricio Salatino Define the structure of the GridServiceDescription id. Based on the id we should build the parsers to populate the GridServiceDescription fields. A possible structure could be: scheduler@localhost:8000/socket, whitepages@192.168.0.1:8001/http, executionode@salaboy.laptop:8002/rest -- 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, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2446) Drools Services API

by Mauricio Salatino (JIRA)

Drools Services API ------------------- Key: JBRULES-2446 URL: https://jira.jboss.org/jira/browse/JBRULES-2446 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: All Affects Versions: FUTURE Reporter: Mauricio Salatino Assignee: Mauricio Salatino Refactoring of the VSM APIs to the new Semantic for Local/Remote/Grid Environments. -- 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, 8 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2011