February 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6564) JSR-322 Java EE Connector Architecture 1.7

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/AS7-6564?page=com.atlassian.jira.plugin.s... ] Jesper Pedersen updated AS7-6564: --------------------------------- Component/s: JCA > JSR-322 Java EE Connector Architecture 1.7 > ------------------------------------------ > > Key: AS7-6564 > URL: https://issues.jboss.org/browse/AS7-6564 > Project: Application Server 7 > Issue Type: Sub-task > Components: JCA > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 8.0.0.Alpha1 > > -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6564) JSR-322 Java EE Connector Architecture 1.7

by Jesper Pedersen (JIRA)

Jesper Pedersen created AS7-6564: ------------------------------------ Summary: JSR-322 Java EE Connector Architecture 1.7 Key: AS7-6564 URL: https://issues.jboss.org/browse/AS7-6564 Project: Application Server 7 Issue Type: Sub-task Reporter: Jesper Pedersen Assignee: Jesper Pedersen -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6531) Reverse controller transformer test checks

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6531?page=com.atlassian.jira.plugin.s... ] Brian Stansberry resolved AS7-6531. ----------------------------------- Resolution: Done > Reverse controller transformer test checks > ------------------------------------------ > > Key: AS7-6531 > URL: https://issues.jboss.org/browse/AS7-6531 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Kabir Khan > Assignee: Brian Stansberry > Fix For: 7.3.0.Alpha1 > > > When starting up the legacy controller in the transformers tests it now boots up a main controller using the boot operations used to boot up the legacy controller. This is to go some way towards ensuring that scripts written for the legacy controller can still work with the current controller. > The calls to LegacyKernelServicesInitializer.skipReverseControllerCheck()in the sub-issues should be removed, and if necessary the reverse check can be further configured via LegacyKernelServicesInitializer.configureReverseControllerCheck(). -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-3110) Enhance validation message when multiple persistence units are found

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/AS7-3110?page=com.atlassian.jira.plugin.s... ] Scott Marlow updated AS7-3110: ------------------------------ Fix Version/s: (was: 7.2.0.Alpha1) > Enhance validation message when multiple persistence units are found > -------------------------------------------------------------------- > > Key: AS7-3110 > URL: https://issues.jboss.org/browse/AS7-3110 > Project: Application Server 7 > Issue Type: Enhancement > Components: JPA / Hibernate > Reporter: Markus Dahm > Assignee: Scott Marlow > Priority: Minor > > The current message is > Caused by: java.lang.IllegalArgumentException: JBAS011470: Persistence unitName was not specified and there are 9 persistence unit definitions in application deployment "test.ear". Either change the application to have only one persistence unit definition or specify the unitName for each reference to a persistence unit. > Yet what is always helpful in search of such validation errors is the context. > In that case the offending class name would suffice, you should have this information at hands since you're scanning the classes, right? > > Given that information I'd have found the problem immediately. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6563) JSR-343 JMS 2.0 Support

by David Lloyd (JIRA)

David Lloyd created AS7-6563: -------------------------------- Summary: JSR-343 JMS 2.0 Support Key: AS7-6563 URL: https://issues.jboss.org/browse/AS7-6563 Project: Application Server 7 Issue Type: Sub-task Components: JMS Reporter: David Lloyd Assignee: Jeff Mesnil Fix For: 8.0.0.Alpha1 Add support for JMS 2.0 as per Java EE 7 specification. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-4873) Strict location check of persistence.xml deployments

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/AS7-4873?page=com.atlassian.jira.plugin.s... ] Scott Marlow updated AS7-4873: ------------------------------ Fix Version/s: 8.0.0.Alpha1 (was: 7.2.0.Alpha1) > Strict location check of persistence.xml deployments > ---------------------------------------------------- > > Key: AS7-4873 > URL: https://issues.jboss.org/browse/AS7-4873 > Project: Application Server 7 > Issue Type: Enhancement > Components: JPA / Hibernate > Affects Versions: 7.1.2.Final (EAP) > Reporter: Bartosz Baranowski > Assignee: Scott Marlow > Priority: Minor > Fix For: 8.0.0.Alpha1 > > > As of: https://github.com/jbossas/jboss-as/commit/38815193011fba624170a7d938118e... it is possible to deploy persistence.xml from invalid location: > As per JPA spec(https://docs.jboss.org/author/display/AS71/JPA+Reference+Guide), valid locations are: > - an EJB-JAR file > - the WEB-INF/classes directory of a WAR file > - a jar file in the WEB-INF/lib directory of a WAR file > - a jar file in the EAR library directory > - an application client jar file -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-5063) AS7 should pass the property "eclipselink.target-server = JBoss" to persistence providers, or at least EclipseLink

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/AS7-5063?page=com.atlassian.jira.plugin.s... ] Scott Marlow updated AS7-5063: ------------------------------ Fix Version/s: 8.0.0.Alpha1 (was: 7.2.0.Alpha1) > AS7 should pass the property "eclipselink.target-server = JBoss" to persistence providers, or at least EclipseLink > ------------------------------------------------------------------------------------------------------------------ > > Key: AS7-5063 > URL: https://issues.jboss.org/browse/AS7-5063 > Project: Application Server 7 > Issue Type: Enhancement > Components: JPA / Hibernate > Affects Versions: 7.1.1.Final > Reporter: Craig Ringer > Assignee: Scott Marlow > Priority: Minor > Labels: eclipselink, jpa > Fix For: 8.0.0.Alpha1 > > > For EclipseLink to properly identify the container and set up correct transaction integration, etc, it needs the property "eclipselink.target-server" to be set to "JBoss". > There's an open issue asking EclipseLink to auto detect the container (https://bugs.eclipse.org/bugs/show_bug.cgi?id=383257) but right now, a simple solution to making EclipseLink work well on AS7 is for AS7 to pass that property to EclipseLink. > That'll help prevent issues and confusion like this: https://bugs.eclipse.org/bugs/show_bug.cgi?id=365704 > Users can set it as a system property right now as shown on bug 383257, but really it'd be best if JBoss passed it to the persistence unit during creation. > Time permitting I'll give this a go. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6562) JSR-352 Batch Applications API support

by David Lloyd (JIRA)

David Lloyd created AS7-6562: -------------------------------- Summary: JSR-352 Batch Applications API support Key: AS7-6562 URL: https://issues.jboss.org/browse/AS7-6562 Project: Application Server 7 Issue Type: Sub-task Components: EE Reporter: David Lloyd Support the Batch Applications for the Java Platform 1.0 spec as per Java EE 7 specification. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6561) JSR-345 EJB 3.2 API Support

by David Lloyd (JIRA)

David Lloyd created AS7-6561: -------------------------------- Summary: JSR-345 EJB 3.2 API Support Key: AS7-6561 URL: https://issues.jboss.org/browse/AS7-6561 Project: Application Server 7 Issue Type: Sub-task Components: EJB Reporter: David Lloyd Assignee: jaikiran pai Fix For: 8.0.0.Alpha1 Implement EJB 3.2 specification as per Java EE 7 specification. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-4857) correct JPA dependency injection (stop injecting javassist and let Hibernate include envers)

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/AS7-4857?page=com.atlassian.jira.plugin.s... ] Scott Marlow updated AS7-4857: ------------------------------ Fix Version/s: 8.0.0.Alpha1 (was: 7.2.0.Alpha1) > correct JPA dependency injection (stop injecting javassist and let Hibernate include envers) > -------------------------------------------------------------------------------------------- > > Key: AS7-4857 > URL: https://issues.jboss.org/browse/AS7-4857 > Project: Application Server 7 > Issue Type: Task > Components: JPA / Hibernate > Affects Versions: 7.1.2.Final (EAP) > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 8.0.0.Alpha1 > > > Rather than export the javassist dependency, see if we can change javassist to generate proxies for the application classes which aren't on the hibernate module class path. -- 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, 5 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 February 2013