[JBoss JIRA] Updated: (JBAS-1485) JMS ResourceAdapter makes unnecessary temporary delete requests
by Jesper Pedersen (JIRA)
[ https://jira.jboss.org/jira/browse/JBAS-1485?page=com.atlassian.jira.plug... ]
Jesper Pedersen updated JBAS-1485:
----------------------------------
Fix Version/s: (was: JBossAS-5.0.1.CR1)
> JMS ResourceAdapter makes unnecessary temporary delete requests
> ---------------------------------------------------------------
>
> Key: JBAS-1485
> URL: https://jira.jboss.org/jira/browse/JBAS-1485
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JMS (JBossMQ)
> Affects Versions: JBossAS-3.2.7 Final, JBossAS-4.0.1 Final, JBossAS-4.0.1 SP1
> Reporter: Adrian Brock
> Assignee: Jesper Pedersen
> Priority: Optional
>
> The JMS ResourceAdaptor keeps track of temporaries created on a connection
> (org.jboss.resource.adapter.jms.JMSSessionFactoryImpl)
> and deletes them.
> This is because we cannot expect the real JMS implementation to do this
> because the connection is pooled and not closed.
> However, if the user is deleting the temporaries themselves
> (good practice in terms of resource usage),
> the JMS ResourceAdapter does not know about this
> and tries to repeat the delete at connection.close();
> Solution:
> Add some wrapping processing for the temporary queues and topics
> so we can trap temporary.delete(). That way we will know we don't
> need to do it on close()
> IMPORTANT: Invocations like send() or JMSMessage.setJMSReplyTo will
> also need to trap these destinations to do the necessary wrapping/unwrapping.
> It is also possible to retrieve a temporary destination with Session.createQueue/Topic.
--
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, 7 months
[JBoss JIRA] Created: (JBDEPLOY-67) Add support for candidate structure based on annotations
by Adrian Brock (JIRA)
Add support for candidate structure based on annotations
--------------------------------------------------------
Key: JBDEPLOY-67
URL: https://jira.jboss.org/jira/browse/JBDEPLOY-67
Project: JBoss Deployers
Issue Type: Task
Components: structure
Reporter: Adrian Brock
Fix For: JBDEPLOY-2.0.0.CR1
To help support the ear processing that adds subdeployments
based on annotations existing we should add some generic support.
Currently the structure deployers look at candidate sub-deployments
and add them to the structure if they match.
We need a new mode where a StructureDeployer can recognise the deployment,
determine the classpath and then look for certain annotation types.
If the annotation exists then the context is added otherwise it is ignored.
Ideally all a structure deployer should have to do is provide the annotation
class names to look for, with the StructuralDeployers infrastructure
and AbstractStructureDeployer classes taking care of most of the work.
The new mode, needs a new parameter passing so this work
depends on the "StructureContext" refactoring, JBDEPLOY-66
--
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, 7 months
[JBoss JIRA] Created: (JBAS-5173) Bug with whitespace in jboss-web.xml
by Javid Jamae (JIRA)
Bug with whitespace in jboss-web.xml
------------------------------------
Key: JBAS-5173
URL: http://jira.jboss.com/jira/browse/JBAS-5173
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: EJB3
Affects Versions: JBossAS-5.0.0.Beta3
Reporter: Javid Jamae
Assigned To: Carlo de Wolf
Priority: Minor
I discovered a bug when you have whitespace in jboss-web.xml in JBoss 5.0.0.Beta3. I have a simple JSF application, and when I use the following, my application works fine:
[code]
<ejb-local-ref>
<ejb-ref-name>ejb/Calculator</ejb-ref-name>
<local-jndi-name>calculator/StatelessCalculatorBean/local</local-jndi-name>
</ejb-local-ref>
[/code]
But, when I use this (with the local-jndi-name defined on a separate line from its enclosing and closing tags and three tabs in front of the name) then it seems like the local interface does not get bound.
[code]
<ejb-local-ref>
<ejb-ref-name>ejb/Calculator</ejb-ref-name>
<local-jndi-name>
calculator/StatelessCalculatorBean/local
</local-jndi-name>
</ejb-local-ref>
[/code]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 7 months