September 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5497) Exception handling of EJB container for MDB is incorrect

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5497?page=com.atlassian.jira.plugin.s... ] Brian Stansberry resolved AS7-5497. ----------------------------------- Fix Version/s: 7.1.4.Final (EAP) Resolution: Done > Exception handling of EJB container for MDB is incorrect > -------------------------------------------------------- > > Key: AS7-5497 > URL: https://issues.jboss.org/browse/AS7-5497 > Project: Application Server 7 > Issue Type: Bug > Components: EJB > Affects Versions: 7.1.2.Final (EAP) > Environment: JBoss EAP 6.0.0 > Reporter: Adam Kovari > Assignee: JBoss SET > Priority: Minor > Labels: eap6, ejb3.1 > Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP), 7.1.3.Final (EAP) > > > After deploying a MDB with Container-Managed transaction and > TransactionAttribute NOT_SUPPORTED, a RuntimeException thrown from > within the MDB onMessage() is reported to the Adapter as such, with no > EJBException wrapping. I.e.: the "((javax.jms.MessageListener) > endPoint).onMessage(message)" call in our adapter fails with the > exception type originally thrown. > This does not look compliant with EJB 3.1 spec(JSR 318: Enterprise > JavaBeansTM, Version 3.1, Table 20 page 392, last cell bottom right): > "Throw EJBException that wraps the original exception to resource > adapter". > Another part of spec I was just made aware of says this: > p383 of the spec states - > In the case of a message-driven bean, the container logs the exception and then throws a javax.ejb.EJBException that wraps the original exception to the resource adapter. (See [15]). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-897) Findbugs 2.0.1

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-897: ------------------------------------- Summary: Findbugs 2.0.1 Key: JBJCA-897 URL: https://issues.jboss.org/browse/JBJCA-897 Project: IronJacamar Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.1.0.Beta3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-5549) Add support for @PersistenceContexts

by Scott Marlow (JIRA)

Scott Marlow created AS7-5549: --------------------------------- Summary: Add support for @PersistenceContexts Key: AS7-5549 URL: https://issues.jboss.org/browse/AS7-5549 Project: Application Server 7 Issue Type: Bug Components: JPA / Hibernate Affects Versions: 7.1.1.Final Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.2.0.Alpha1 See [example here|http://www.oracle.com/technetwork/middleware/ias/toplink-jpa-annotat...] of using @PersistenceContexts. {code} @Stateless @PersistenceContexts({ @PersistenceContext(name="OrderEM"), @PersistenceContext(name="ItemEM") }) public class OrderEntryBean implements OrderEntry { @Resource EJBContext ctx; public Customer getCustomer(int custID) { EntityManager em = (EntityManager)ctx.lookup("OrderEM"); return em.find(Customer.class, custID); } public void enterItem(int orderID, Item newItem) { EntityManager em = (EntityManager)ctx.lookup("ItemEM"); ... } } {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-8201) Patching system

by Brian Stansberry (JIRA)

Patching system --------------- Key: JBAS-8201 URL: https://jira.jboss.org/browse/JBAS-8201 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Assignee: Emanuel Muckenhuber Fix For: 7.0.0.M2 "Server" side of the patching system. Server not in the sense of the domain model Server, but rather client-server where the client is whatever tool (JON) determines there are patches available and asks the server to apply them. This does not need to implemented until M2 but thinking about it during the design of the InstalledImage is good. -- 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, 9 months

6
9
0 / 0

[JBoss JIRA] (AS7-5583) Allow defining server http port (and other basic properties) via jvm arguments

by Michal Matloka (JIRA)

Michal Matloka created AS7-5583: ----------------------------------- Summary: Allow defining server http port (and other basic properties) via jvm arguments Key: AS7-5583 URL: https://issues.jboss.org/browse/AS7-5583 Project: Application Server 7 Issue Type: Feature Request Affects Versions: 7.1.1.Final Reporter: Michal Matloka Assignee: Michal Matloka Fix For: 7.2.0.Alpha1 Currently the only way to specify server port is to edit server configuration .xml. However there are cases which could use definition via jvm arg. Forums shows the following workaround (https://community.jboss.org/thread/168140). I'd like to propose to include in default jboss-as standalone.xml configuration, properties for the most important parameters: eg. change <socket-binding name="http" port="8080"/> to <socket-binding name="http" port="${jboss.http.port:8080}"/> Then would be possible to run jboss on different port via jvm arg ./bin/standalone.sh --server-config=standalone-ha.xml -Djboss.http.port=8888 Solving this issue is important, because some other issues relies on it: eg. https://issues.jboss.org/browse/AS7-1036 With this change, solving mentioned ticket would be very easy, and will allow to run arquillian tests directly on jboss downloaded and unpacked via maven goal, and then managed directly via arquillian. I'm willing to solve this feature by myself, however I'd like to hear opinions from other people. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
3
0 / 0

[JBoss JIRA] (JBRULES-3631) ClassCastException removing a rule containing a FromNode

by Mario Fusco (JIRA)

Mario Fusco created JBRULES-3631: ------------------------------------ Summary: ClassCastException removing a rule containing a FromNode Key: JBRULES-3631 URL: https://issues.jboss.org/browse/JBRULES-3631 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco Trying to remove a rule containing a FromNode causes the following: java.lang.ClassCastException: org.drools.reteoo.FromNode cannot be cast to org.drools.reteoo.BetaNode at org.drools.reteoo.ReteooBuilder.resetMasks(ReteooBuilder.java:303) at org.drools.reteoo.ReteooBuilder.removeRule(ReteooBuilder.java:267) at org.drools.reteoo.ReteooRuleBase.removeRule(ReteooRuleBase.java:459) at org.drools.common.AbstractRuleBase.removeRule(AbstractRuleBase.java:1100) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] (AS7-5403) CLONE - Adding modcluster via the CLI fails.

by Joe Wertz (JIRA)

[ https://issues.jboss.org/browse/AS7-5403?page=com.atlassian.jira.plugin.s... ] Joe Wertz commented on AS7-5403: -------------------------------- A more elegant solution as requested. Adding a ListAttributeDefinition to the ModClusterDefinition. ModClusterConfigAttributeDefinition. The new attribute definition essentially replicates the ModClusterConfigResourceDefinition as an attribute so that it can be used during the ./subsystem=modcluster:add(__) command. This way the user can input configuration values before the modcluster subsystem attempts to start up. CLI Usage Example: {noformat} ./subsystem=modcluster:add(configuration=[{advertise-socket=ajp,connector=ajp}]) {noformat} Depending on how many of the configuration attributes the user wanted to define at the time. Only the connector would be required, like the ModClusterConfigResourceDefinition. > CLONE - Adding modcluster via the CLI fails. > -------------------------------------------- > > Key: AS7-5403 > URL: https://issues.jboss.org/browse/AS7-5403 > Project: Application Server 7 > Issue Type: Bug > Components: CLI > Affects Versions: 7.1.2.Final (EAP) > Reporter: Tom Fonteyne > Assignee: Joe Wertz > > Adding modcluster via the CLI fails. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3633) Allow encoding to be specified on a resource when using spring configuration

by Joachim Van der Auwera (JIRA)

Joachim Van der Auwera created JBRULES-3633: ----------------------------------------------- Summary: Allow encoding to be specified on a resource when using spring configuration Key: JBRULES-3633 URL: https://issues.jboss.org/browse/JBRULES-3633 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-spring Affects Versions: 5.4.0.Final Reporter: Joachim Van der Auwera Assignee: Mark Proctor Currently default encoding (which is platform specific) is used when reading resources. This can give problems when the resource (for example a rules file) is written using a different encoding. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] (JBRULES-3543) KnowledgeAgent: Doesn't remove insertLogical() Facts correctly with incremental build

by Torsten Schöne (JIRA)

13 years, 9 months

4
14
0 / 0

[JBoss JIRA] (AS7-5585) logging.properties broken on Windows after file is rewritten

by James Perkins (JIRA)

James Perkins created AS7-5585: ---------------------------------- Summary: logging.properties broken on Windows after file is rewritten Key: AS7-5585 URL: https://issues.jboss.org/browse/AS7-5585 Project: Application Server 7 Issue Type: Bug Components: Logging Environment: Windows Reporter: James Perkins Assignee: James Perkins Priority: Blocker Fix For: 7.2.0.Alpha1 The persistence of the logging.properties file writes out paths like C:\ on Windows which results in an error when trying to load the paths again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
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 2012