July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Reopened: (AS7-647) pluggable JPA providers

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/AS7-647?page=com.atlassian.jira.plugin.sy... ] Scott Marlow reopened AS7-647: ------------------------------ > pluggable JPA providers > ----------------------- > > Key: AS7-647 > URL: https://issues.jboss.org/browse/AS7-647 > Project: Application Server 7 > Issue Type: Task > Components: JPA / Hibernate > Affects Versions: 7.0.0.Beta3 > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 7.1.0.Alpha1 > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Resolved: (AS7-647) pluggable JPA providers

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/AS7-647?page=com.atlassian.jira.plugin.sy... ] Scott Marlow resolved AS7-647. ------------------------------ Resolution: Done fixed against AS7-566 > pluggable JPA providers > ----------------------- > > Key: AS7-647 > URL: https://issues.jboss.org/browse/AS7-647 > Project: Application Server 7 > Issue Type: Task > Components: JPA / Hibernate > Affects Versions: 7.0.0.Beta3 > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 7.1.0.Alpha1 > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (AS7-647) pluggable JPA providers

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/AS7-647?page=com.atlassian.jira.plugin.sy... ] Scott Marlow closed AS7-647. ---------------------------- > pluggable JPA providers > ----------------------- > > Key: AS7-647 > URL: https://issues.jboss.org/browse/AS7-647 > Project: Application Server 7 > Issue Type: Task > Components: JPA / Hibernate > Affects Versions: 7.0.0.Beta3 > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 7.1.0.Alpha1 > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (AS7-1359) Upgrade to Hibernate 4.0.0.Beta4

by Scott Marlow (JIRA)

Upgrade to Hibernate 4.0.0.Beta4 -------------------------------- Key: AS7-1359 URL: https://issues.jboss.org/browse/AS7-1359 Project: Application Server 7 Issue Type: Component Upgrade Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.0.1.Final http://in.relation.to/Bloggers/HibernateCore400Beta4Release We are currently using Hibernate 4.0.0.Beta1, lets sync up with the latest Hibernate build -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-270) Intermittent failure of undeploy

by Dennis Reed (JIRA)

Intermittent failure of undeploy -------------------------------- Key: JBDEPLOY-270 URL: https://issues.jboss.org/browse/JBDEPLOY-270 Project: JBoss Deployers Issue Type: Bug Components: deployer Affects Versions: JBDEPLOY-2.0.10.GA Reporter: Dennis Reed When components are deployed, they are assigned names with a number appended based on the order it was processed. For example "jboss.deployment:id="dennis$defaultEvictionRegionConfig#1",type=Component" The number is assigned in (line #'s are from EAP 5.0): at org.jboss.beans.metadata.plugins.AbstractBeanMetaData.setName(AbstractBeanMetaData.java:360) at org.jboss.beans.metadata.plugins.NestedBeanHandler.checkForNestedBeans(NestedBeanHandler.java:77) at org.jboss.beans.metadata.plugins.AbstractBeanMetaData.getBeans(AbstractBeanMetaData.java:202) at org.jboss.kernel.plugins.deployment.AbstractKernelDeployment.getBeans(AbstractKernelDeployment.java:233) at org.jboss.deployers.vfs.deployer.kernel.KernelDeploymentDeployer$KernelDeploymentVisitor.getBeans(KernelDeploymentDeployer.java:63) at org.jboss.deployers.vfs.deployer.kernel.KernelDeploymentDeployer$KernelDeploymentVisitor.getBeans(KernelDeploymentDeployer.java:54) at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:118) However, the beans are *not* processed in the same order every time. And they are processed separately during deployment and undeployment. This means that "myBean#1" may get deployed, but "myBean#2" is undeployed (leaving "myBean#1" still deployed). Subsequent deployments will fail with errors: 17:34:30,630 WARN [AbstractDeploymentContext] Unable to register deployment mbean dennis$defaultEvictionRegionConfig#1 javax.management.InstanceAlreadyExistsException: jboss.deployment:id="dennis$defaultEvictionRegionConfig#1",type=Component already registered. The root cause appears to be that the XML descriptor is read with jboss-xb using a Set (unordered), but then this code has a dependency on the order being consistent between deploy and undeploy. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
8
0 / 0

[JBoss JIRA] Created: (AS7-1397) JPS executable not found

by James Perkins (JIRA)

JPS executable not found ------------------------ Key: AS7-1397 URL: https://issues.jboss.org/browse/AS7-1397 Project: Application Server 7 Issue Type: Bug Reporter: James Perkins Assignee: James Perkins Fix For: 7.1.0.Alpha1 org.jboss.as.test.integration.respawn.RespawnTestCase: java.io.IOException: Cannot run program "/usr/java/jdk1.6.0_26/jre/bin/jps": java.io.IOException: error=2, No such file or directory. The JPS executable does not appear to be located in the JRE home. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
5
0 / 0

[JBoss JIRA] Created: (JBJCA-638) ActivationSpec config-property map not updated with introspected properties

by Jesper Pedersen (JIRA)

ActivationSpec config-property map not updated with introspected properties --------------------------------------------------------------------------- Key: JBJCA-638 URL: https://issues.jboss.org/browse/JBJCA-638 Project: IronJacamar Issue Type: Bug Components: Core Affects Versions: 1.0.1.Final Reporter: Jesper Pedersen Assignee: Jesper Pedersen Priority: Critical Fix For: 1.0.2.Final, 1.1.0.Alpha1 The config-property map for an Activation isn't updated with the introspected types from the ActivationSpec class. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-1426) Provide injectable BundleContext in JNDI

by Thomas Diesler (JIRA)

Provide injectable BundleContext in JNDI ---------------------------------------- Key: AS7-1426 URL: https://issues.jboss.org/browse/AS7-1426 Project: Application Server 7 Issue Type: Feature Request Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.1.0.Alpha1 The system BundleContext should be available as injectable resource -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
4
0 / 0

[JBoss JIRA] Created: (AS7-1424) Blueprint Container cannot obtain SchemaFactory

by Thomas Diesler (JIRA)

Blueprint Container cannot obtain SchemaFactory ----------------------------------------------- Key: AS7-1424 URL: https://issues.jboss.org/browse/AS7-1424 Project: Application Server 7 Issue Type: Bug Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.1.0.Alpha1 10:46:41,387 ERROR [org.apache.aries.blueprint.container.BlueprintContainerImpl] (pool-7-thread-1) Unable to start blueprint container for bundle example-blueprint: java.lang.IllegalArgumentException: No SchemaFactory that implements the schema language specified by: http://www.w3.org/2001/XMLSchema could be loaded at javax.xml.validation.SchemaFactory.newInstance(SchemaFactory.java:207) [:1.6.0_26] at org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl.getSchemaFactory(NamespaceHandlerRegistryImpl.java:266) [NamespaceHandlerRegistryImpl.class:] at org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl.getSchema(NamespaceHandlerRegistryImpl.java:236) [NamespaceHandlerRegistryImpl.class:] at org.apache.aries.blueprint.namespace.NamespaceHandlerRegistryImpl$NamespaceHandlerSetImpl.getSchema(NamespaceHandlerRegistryImpl.java:306) [NamespaceHandlerRegistryImpl$NamespaceHandlerSetImpl.class:] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1892) In failover on node leave mode, it needs to make sure when failover happens, no more messaging operations are active at the node being shutdown

by Yong Hao Gao (JIRA)

In failover on node leave mode, it needs to make sure when failover happens, no more messaging operations are active at the node being shutdown ------------------------------------------------------------------------------------------------------------------------------------------------ Key: JBMESSAGING-1892 URL: https://issues.jboss.org/browse/JBMESSAGING-1892 Project: JBoss Messaging Issue Type: Bug Components: JMS Clustering Affects Versions: 1.4.8.SP2, 1.4.0.SP3.CP14 Reporter: Yong Hao Gao Assignee: Yong Hao Gao Fix For: 1.4.0.SP3.CP15, 1.4.8.SP3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
3
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 July 2011