[JBoss JIRA] Created: (JBAS-8948) Switchboard: Add configuration option to ResourceEnvRefProvider to not throw RuntimeException upon missing @Resource annotation
by Daniel Bevenius (JIRA)
Switchboard: Add configuration option to ResourceEnvRefProvider to not throw RuntimeException upon missing @Resource annotation
-------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-8948
URL: https://issues.jboss.org/browse/JBAS-8948
Project: JBoss Application Server
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Reporter: Daniel Bevenius
Assignee: jaikiran pai
Using a javax.annotation.Resource that is not intended for JBoss MC, perhaps Spring is being used, causes a RuntimeException to be throw upon startup of JBoss AS 6.0.0.Final.
For example, if you have a class that looks like this:
{code}
import javax.annotation.Resource;
public class AnnotatedClass
{
@Resource
public void setterMethodWithAnnotation(SampleClass sample)
{
}
}
{code}
And this class in packaged into a war and deployed the exception below will be thrown:
{noformat}
Caused by: java.lang.RuntimeException: Neither any mapped-name/lookup/jndi-name specified nor any ResourceProvider could process resource-env-ref named env/se.rl.pop.AnnotatedClass/terMethodWithAnnotation of type se.rl.pop.SampleClass
at org.jboss.switchboard.mc.resource.provider.ResourceEnvRefProvider.provide(ResourceEnvRefProvider.java:136) [:1.0.0-alpha-16-SNAPSHOT]
at org.jboss.switchboard.mc.resource.provider.ResourceEnvRefProvider.provide(ResourceEnvRefProvider.java:1) [:1.0.0-alpha-16-SNAPSHOT]
at org.jboss.switchboard.mc.JndiEnvironmentProcessor.process(JndiEnvironmentProcessor.java:68) [:1.0.0-alpha-16-SNAPSHOT]
at org.jboss.switchboard.mc.deployer.AbstractSwitchBoardDeployer.process(AbstractSwitchBoardDeployer.java:119) [:1.0.0-alpha-16-SNAPSHOT]
at org.jboss.switchboard.mc.deployer.WebEnvironmentSwitchBoardDeployer.internalDeploy(WebEnvironmentSwitchBoardDeployer.java:66) [:1.0.0-alpha-16-SNAPSHOT]
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55) [:2.2.0.GA]
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) [:2.2.0.GA]
... 43 more
{noformat}
Resource scanning can be turned off by adding a jboss-scanning.xml to WEB-INF/META-INF but this jira suggests that a property be added to ResourceEnvRefProvider that configures if this class should throw a RuntimeException of just log a message. This would save users to have to add a jboss-scanning.xml to their deployments.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] Created: (JBAS-9386) Upgrade to Remoting 2.5.4.SP2
by Ron Sigal (JIRA)
Upgrade to Remoting 2.5.4.SP2
-----------------------------
Key: JBAS-9386
URL: https://issues.jboss.org/browse/JBAS-9386
Project: Legacy JBoss Application Server 6
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Ron Sigal
Assignee: Shelly McGowan
Fix For: 6.1.0
Remoting release 2.5.4.SP2 incorporates the issues from "ephemeral" releases 2.5.4 and 2.5.4.SP1 (see JBAS-9043 "Upgrade to Remoting 2.5.4.SP1") plus
Release Notes - JBoss Remoting - Version 2.5.4.SP2
Bug
* [JBREM-1276] - SecondaryServerSocketThread should catch java.lang.Error
* [JBREM-1282] - ServerInvoker does not close StreamHandler in the case of "addstreamcallback"
* [JBREM-1285] - Callback Connector for in-jvm connection should create a LocalServerInvoker
* [JBREM-1288] - StreamServer for in-jvm connection should create a LocalServerInvoker
Enhancement
* [JBREM-1277] - Allow configuration of socket and bisocket accept thread priority
* [JBREM-1283] - CLONE [JBREM-1281] - Support setting executor in CoyoteInvoker
Release
* [JBREM-1291] - Release 2.5.4.SP2
Task
* [JBREM-1290] - Assure version compatibility with earlier versions of Remoting
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] Moved: (AS7-766) EAR and other top level deployments should be Atomic
by Brad Maxwell (JIRA)
[ https://issues.jboss.org/browse/AS7-766?page=com.atlassian.jira.plugin.sy... ]
Brad Maxwell moved JBPAPP-6518 to AS7-766:
------------------------------------------
Project: Application Server 7 (was: JBoss Enterprise Application Platform)
Key: AS7-766 (was: JBPAPP-6518)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: (was: EAP_EWP 5.1.0)
Component/s: Server
(was: System)
Security: (was: Public)
Fix Version/s: (was: EAP_EWP 5.1.2)
Docs QE Status: (was: NEW)
> EAR and other top level deployments should be Atomic
> ----------------------------------------------------
>
> Key: AS7-766
> URL: https://issues.jboss.org/browse/AS7-766
> Project: Application Server 7
> Issue Type: Bug
> Components: Server
> Reporter: Brad Maxwell
> Assignee: Jason Greene
>
> Issue: If an ear or other deployment that contains sub-deployments is deployed and one of the sub-deployments fails to deploy, the ear should fail and unwind all sub-deployments.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] Created: (JBMESSAGING-1863) Adding more unit tests
by Yong Hao Gao (JIRA)
Adding more unit tests
----------------------
Key: JBMESSAGING-1863
URL: https://issues.jboss.org/browse/JBMESSAGING-1863
Project: JBoss Messaging
Issue Type: Quality Risk
Reporter: Yong Hao Gao
Assignee: Yong Hao Gao
In messaging-service.xml, the following attributes were found not tested, it's possible to add them to unit test:
1 EnableMessageCounters
Set this to true to enable message counters when the server starts
This is used to turn on some of ServerPeer's mbean opeartions:
getMessageCounters
getMessageStatistics
getDefaultMessageCounterHistoryDayLimit
2 Destinations
Returns a list of the destinations (queues and topics) currently deployed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months