September 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5062) PersistenceUnitRootURL for JPA providers may not be spec compliant

by Craig Ringer (JIRA)

Craig Ringer created AS7-5062: --------------------------------- Summary: PersistenceUnitRootURL for JPA providers may not be spec compliant Key: AS7-5062 URL: https://issues.jboss.org/browse/AS7-5062 Project: Application Server 7 Issue Type: Bug Components: JPA / Hibernate Affects Versions: 7.1.1.Final Environment: $ java -version java version "1.7.0_03-icedtea" OpenJDK Runtime Environment (fedora-2.2.1.fc17.8-x86_64) OpenJDK 64-Bit Server VM (build 23.0-b21, mixed mode) $ uname -a Linux ayaki.localdomain 3.4.2-4.fc17.x86_64 #1 SMP Thu Jun 14 22:22:05 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux Reporter: Craig Ringer Assignee: Scott Marlow Discussion on the EclipseLink bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=383200 ("On JBoss AS 7, EclipseLink doesn't find entity classes unless they're explicitly listed in persistence.xml") suggests that JBoss AS 7 may not be providing a spec-compliant PersistenceUnitRootURL or contents. EclipseLink can't scan the contents of a deployment for @Entity annotated classes, so it doesn't find any entities unless they're explicitly named in persistence.xml . http://docs.oracle.com/javaee/6/api/javax/persistence/spi/PersistenceUnit... states: {quote} java.net.URL getPersistenceUnitRootUrl() Returns the URL for the jar file or directory that is the root of the persistence unit. (If the persistence unit is rooted in the WEB-INF/classes directory, this will be the URL of that directory.) The URL will either be a file: URL referring to a jar file or referring to a directory that contains an exploded jar file, or some other URL from which an InputStream in jar format can be obtained. *Returns*: a URL referring to a jar file or directory {quote} ... and that's what EclipseLink expects. However, for EclipseLink class scanning to function correctly an adapter class must be provided, such as the classes provided here: https://community.jboss.org/wiki/HowToUseEclipseLinkWithAS7 to integrate EclipseLink with JBoss's VFS. It may be worth investigating why this is necessary and whether the current behavior is standards compliant. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

3
20
0 / 0

[JBoss JIRA] (AS7-5474) Url returned by PersistenceUnitInfo#getPersistenceUnitRootUrl() point to an empty folder

by Adriano Verona (JIRA)

Adriano Verona created AS7-5474: ----------------------------------- Summary: Url returned by PersistenceUnitInfo#getPersistenceUnitRootUrl() point to an empty folder Key: AS7-5474 URL: https://issues.jboss.org/browse/AS7-5474 Project: Application Server 7 Issue Type: Bug Components: JPA / Hibernate Affects Versions: 7.2.0.Alpha1 Environment: $ java -version java version "1.6.0_31" Java(TM) SE Runtime Environment (build 1.6.0_31-b05) Java HotSpot(TM) Client VM (build 20.6-b01, mixed mode, sharing) Windows 7 x64 Reporter: Adriano Verona Assignee: Scott Marlow When setting "jboss.as.jpa.vfs" property to false in persistence.xml PersistenceUnitInfo#getPersistenceUnitRootUrl() returns an Url that points to an empty folder (named "Contents"). The parent of this folder does holds the application jar. file:/D:/Java/jboss-as-7.2.0.Alpha1/standalone/tmp/vfs/temp9c270668d311f0c4/vjpa_jboss_example.jar-7ef91a4c66eeff18/contents/ Observed this at PersistenceProvider#createContainerEntityManagerFactory() method call. -- 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

11 years, 6 months

2
7
0 / 0

[JBoss JIRA] (AS7-5281) JBoss loading wrong Hibernate version when using Persistence unit in WAR file

by Kuthair Habboush (JIRA)

Kuthair Habboush created AS7-5281: ------------------------------------- Summary: JBoss loading wrong Hibernate version when using Persistence unit in WAR file Key: AS7-5281 URL: https://issues.jboss.org/browse/AS7-5281 Project: Application Server 7 Issue Type: Feature Request Components: Class Loading, JPA / Hibernate Affects Versions: 7.1.1.Final Environment: JBoss 7.1.1.Final & Hibernate 4.1.5.SP1 on Mac OSX 10.7/10.8 SQL Server 2008 on Windows 7 virtual Reporter: Kuthair Habboush Assignee: David Lloyd Attachments: hibernate-test.zip JBoss is loading Hibernate 4.0.1.Final (ships with) instead of the version specified in my Maven POM file and embedded in WAR archive, version: 4.1.5.SP1. This ONLY occurs when I have a Persistence Unit setup in my WAR file in directory: resources/META-INF. If I rename persistence.xml to persistence.xml.old, JBoss loads the correct version: Hibernate 4.1.5.SP1. I have a sample project. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

3
24
0 / 0

[JBoss JIRA] (AS7-3298) Deployment of POJO web service faild, if virtual server by name "default-host" does not exist.

by Tomaz Zupan (JIRA)

Tomaz Zupan created AS7-3298: -------------------------------- Summary: Deployment of POJO web service faild, if virtual server by name "default-host" does not exist. Key: AS7-3298 URL: https://issues.jboss.org/browse/AS7-3298 Project: Application Server 7 Issue Type: Bug Components: Web Services Affects Versions: 7.1.0.CR1b Environment: Windows 7, Oracle Java 1.7.02 Reporter: Tomaz Zupan Assignee: Alessio Soldano If you change the name of the virtual-sarver in web subsystem, then deployment of any POJO web service failed with the folowing message: {quote} 13:21:25,506 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report}} JBAS014775: New missing/unsatisfied dependencies: service jboss.web.host.default-host (missing) dependents: [service jboss.ws.port-component-link, service jboss.web.deployment.default-host./server] {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

3
3
0 / 0

[JBoss JIRA] (AS7-5344) JPA deploymen should set the thread context classloader during PersistenceProvider.createContainerEntityManagerFactory()

by Scott Marlow (JIRA)

Scott Marlow created AS7-5344: --------------------------------- Summary: JPA deploymen should set the thread context classloader during PersistenceProvider.createContainerEntityManagerFactory() Key: AS7-5344 URL: https://issues.jboss.org/browse/AS7-5344 Project: Application Server 7 Issue Type: Bug Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.2.0.Alpha1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
7
0 / 0

[JBoss JIRA] (AS7-4065) TS: Migrate from Surefire to Failsafe maven plugin.

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-4065: --------------------------------- Summary: TS: Migrate from Surefire to Failsafe maven plugin. Key: AS7-4065 URL: https://issues.jboss.org/browse/AS7-4065 Project: Application Server 7 Issue Type: Enhancement Components: Test Suite Reporter: Ondrej Zizka Assignee: Ondrej Zizka Fix For: 7.2.0.Alpha1 Surefire aims at unit testing. Failsafe, unlike Surefire, binds to two build phases - integration-tests and verify. That not only moves test execution to the correct phase, but also brings possibility to test several issues present in the testsuite - like skipping successive Surefire executions in a single module if former fails (not affected by -fae). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

2
5
0 / 0

[JBoss JIRA] (SECURITY-668) Checkstyle into Picketbox build

by Anil Saldhana (JIRA)

Anil Saldhana created SECURITY-668: -------------------------------------- Summary: Checkstyle into Picketbox build Key: SECURITY-668 URL: https://issues.jboss.org/browse/SECURITY-668 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Task Security Level: Public (Everyone can see) Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: Picketbox_v5.0.0.Alpha Available in the JBoss AS7 workspace. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

2
2
0 / 0

[JBoss JIRA] (AS7-2792) CLI doesn't show resolved multicast address for socket-binding definition like jgroups-udp or jgroups-mping

by Rostislav Svoboda (Created) (JIRA)

CLI doesn't show resolved multicast address for socket-binding definition like jgroups-udp or jgroups-mping ----------------------------------------------------------------------------------------------------------- Key: AS7-2792 URL: https://issues.jboss.org/browse/AS7-2792 Project: Application Server 7 Issue Type: Bug Components: CLI, Domain Management Affects Versions: 7.1.0.Beta1 Reporter: Rostislav Svoboda Assignee: Alexey Loubyansky Fix For: 7.1.0.CR1 Hi Alexey. CLI doesn't show resolved multicast address for socket-binding definition like jgroups-udp or jgroups-mping. I would expect to see 'resolved-multicast-address' or something similar to 'resolved-address' for interface definition. I hope management model can provide such information. If not please reassign to Brian. {code} $ bin/standalone.sh -c standalone-ha.xml -u 224.34.3.154 $ bin/jboss-admin.sh -c [standalone@localhost:9999 /] cd /socket-binding-group=standard-sockets/socket-binding=jgroups-udp [standalone@localhost:9999 socket-binding=jgroups-udp] :read-resource(include-runtime=true) { "outcome" => "success", "result" => { "bound" => false, "bound-address" => undefined, "bound-port" => undefined, "fixed-port" => false, "interface" => undefined, "multicast-address" => expression "${jboss.default.multicast.address:230.0.0.4}", "multicast-port" => 45688, "name" => "jgroups-udp", "port" => 55200 } } {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

6
8
0 / 0

[JBoss JIRA] (AS7-3571) Console should allow setting multiple JNDI names for JMS queues/topics

by Jan Martiska (JIRA)

Jan Martiska created AS7-3571: --------------------------------- Summary: Console should allow setting multiple JNDI names for JMS queues/topics Key: AS7-3571 URL: https://issues.jboss.org/browse/AS7-3571 Project: Application Server 7 Issue Type: Feature Request Components: Console Affects Versions: 7.1.0.CR1b Reporter: Jan Martiska Assignee: Heiko Braun Priority: Optional Fix For: 7.1.1.Final The model and CLI allow setting multiple JNDI names for JMS resources. In the admin console, only one name is possible. Also, it is currently not possible to change the name after the resource is created. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

4
10
0 / 0

[JBoss JIRA] Created: (AS7-1264) Add schema references to standalone.xml, domain.xml, host.xml

by Gerry Matte (JIRA)

Add schema references to standalone.xml, domain.xml, host.xml ------------------------------------------------------------- Key: AS7-1264 URL: https://issues.jboss.org/browse/AS7-1264 Project: Application Server 7 Issue Type: Task Components: Domain Management Affects Versions: 7.0.0.CR1 Reporter: Gerry Matte Assignee: Brian Stansberry It appears that users of Jboss 7 will be often modifying these configuration files as they fine tune their server and when they discover how to implement new features. It seems quite surprising to me that these files do not have the schema references identified in the file header. Any good XML editor would use those references to validate changes and new entries and thereby avoid a great deal of frustration for users and those who provide support for forum issues. I realise that if jboss validated each xml file when starting up there would be performance penalty that may be unacceptable to many users. A command-line switch could be used to either turn on xml validation (if the default were that no validation is performed) or conversely to turn off xml validation if the default state was that xml validation was on. Personally I favor having a switch that turns off validation - to be used on production servers only. If the schema/dtd files were published online and referenced within the configuration xml files, future changes to the schema structure would be "enforced" upon the user community as they attemted to use an out-of-date version when upgrading to a new version of Jboss 7. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

7
13
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2012