July 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5201) 128.3.8 Stopping the Web Application Bundle

by David Bosschaert (JIRA)

David Bosschaert created AS7-5201: ------------------------------------- Summary: 128.3.8 Stopping the Web Application Bundle Key: AS7-5201 URL: https://issues.jboss.org/browse/AS7-5201 Project: Application Server 7 Issue Type: Sub-task Components: OSGi Reporter: David Bosschaert Assignee: David Bosschaert -- 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-5202) 128.5 Events

by David Bosschaert (JIRA)

David Bosschaert created AS7-5202: ------------------------------------- Summary: 128.5 Events Key: AS7-5202 URL: https://issues.jboss.org/browse/AS7-5202 Project: Application Server 7 Issue Type: Sub-task Components: OSGi Reporter: David Bosschaert Assignee: David Bosschaert -- 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-5200) 128.3.5 Static Content

by David Bosschaert (JIRA)

David Bosschaert created AS7-5200: ------------------------------------- Summary: 128.3.5 Static Content Key: AS7-5200 URL: https://issues.jboss.org/browse/AS7-5200 Project: Application Server 7 Issue Type: Sub-task Components: OSGi Reporter: David Bosschaert Assignee: David Bosschaert -- 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-5197) 128.3.1 WAB Definition

by David Bosschaert (JIRA)

David Bosschaert created AS7-5197: ------------------------------------- Summary: 128.3.1 WAB Definition Key: AS7-5197 URL: https://issues.jboss.org/browse/AS7-5197 Project: Application Server 7 Issue Type: Sub-task Components: OSGi Reporter: David Bosschaert Assignee: David Bosschaert -- 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-5198) 128.3.2 Starting the Web Application Bundle

by David Bosschaert (JIRA)

David Bosschaert created AS7-5198: ------------------------------------- Summary: 128.3.2 Starting the Web Application Bundle Key: AS7-5198 URL: https://issues.jboss.org/browse/AS7-5198 Project: Application Server 7 Issue Type: Sub-task Components: OSGi Reporter: David Bosschaert Assignee: David Bosschaert -- 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-5196) Uninstalling bootstrap/persistent bundles brings OSGi subsystem down

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5196: ----------------------------------- Summary: Uninstalling bootstrap/persistent bundles brings OSGi subsystem down Key: AS7-5196 URL: https://issues.jboss.org/browse/AS7-5196 Project: Application Server 7 Issue Type: Bug Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.2.0.Alpha1 {code} 10:14:11,284 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011005: Bundle uninstalled: org.apache.felix.eventadmin:1.2.14 10:14:11,287 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jbosgi.integration.PersistentBundles.RESOLVE: org.jboss.msc.service.StartException in service jbosgi.integration.PersistentBundles.RESOLVE: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_33] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_33] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_33] Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jbosgi.bundle.10."org.apache.felix.eventadmin"."1.2.14".INSTALLED not found at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:447) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.osgi.framework.BootstrapBundlesResolve.start(BootstrapBundlesResolve.java:63) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] ... 3 more 10:14:11,461 INFO [org.jboss.as.server] (HttpManagementService-threads - 9) JBAS018558: Undeployed "org.apache.felix:org.apache.felix.eventadmin:1.2.14" 10:14:11,462 INFO [org.jboss.as.controller] (HttpManagementService-threads - 9) JBAS014774: Service status report JBAS014775: New missing/unsatisfied dependencies: service jbosgi.integration.PersistentBundles.ACTIVATE (missing) dependents: [service jbosgi.framework.INIT] service jbosgi.integration.PersistentBundles.COMPLETE (missing) dependents: [service jbosgi.framework.INIT] JBAS014777: Services which failed to start: service jbosgi.integration.PersistentBundles.RESOLVE: org.jboss.msc.service.StartException in service jbosgi.integration.PersistentBundles.RESOLVE: Failed to start service {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

13 years, 11 months

1
2
0 / 0

[JBoss JIRA] (AS7-5161) @Resource injection in producer bean

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5161: ----------------------------------- Summary: @Resource injection in producer bean Key: AS7-5161 URL: https://issues.jboss.org/browse/AS7-5161 Project: Application Server 7 Issue Type: Bug Components: CDI / Weld Reporter: Thomas Diesler Assignee: Stuart Douglas Using a simple producer bean like this {code} @ManagedBean public class SimpleProducerBean { @Resource(name = "java:jboss/datasources/ExampleDS") DataSource dataSource; @Produces public String getDriverName() { try { Connection con = dataSource.getConnection(); try { return con.getMetaData().getDriverName(); } finally { con.close(); } } catch (SQLException ex) { return ex.toString(); } } } {code} I get {code} 10:09:18,782 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/simple]] (http-/127.0.0.1:8080-1) Marking servlet SimpleBeanServlet as unavailable 10:09:18,783 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/simple].[SimpleBeanServlet]] (http-/127.0.0.1:8080-1) Allocate exception for servlet SimpleBeanServlet: javax.naming.NameNotFoundException: env/java:jboss/datasources/ExampleDS -- service jboss.naming.context.java.module.simple.simple.env.java:jboss.datasources.ExampleDS at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179) at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:129) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:215) at javax.naming.InitialContext.lookup(InitialContext.java:392) [rt.jar:1.6.0_33] at org.jboss.weld.injection.spi.helpers.AbstractResourceServices.resolveResource(AbstractResourceServices.java:47) [weld-spi-1.1.Final.jar:20110112-1536] {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

13 years, 11 months

2
7
0 / 0

[JBoss JIRA] (JBRULES-3318) Enable the Use of Different Table Names in drools-persistence-jpa

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3318?page=com.atlassian.jira.plug... ] Geoffrey De Smet edited comment on JBRULES-3318 at 7/18/12 3:18 AM: -------------------------------------------------------------------- >From my experience, the META-INF/orm.xml is indeed the way to do it: it can override any annotation in the code. Problem is they have to put it in the drools/jbpm-persistence-jpa.jar file AFAIK, so that's a PITA when upgrading to a new drools/jbpm version. You might not want to use "xml-mapping-metadata-complete", as you don't want to disable all annotations in code. For example, disabling @Temporal(TemporalType.TIMESTAMP) and requiring them to rewrite it, is unnecessary duplication (and prone to bugs, especially when it changes in a new version). If all they want to do is change the table names (not the column names), it could be just a list of @Table(tableName) overrides in the orm.xml file. was (Author: ge0ffrey): From my experience, the META-INF/orm.xml is indeed the way to do it: it can override any annotation in the code. Problem is they have to put it in the drools/jbpm-persistence-jpa.jar file AFAIK, so that's a PITA when upgrading to a new drools/jbpm version. You might not want to use "xml-mapping-metadata-complete", as you don't want to disable all annotations in code. For example, disabling @Temporal(TemporalType.TIMESTAMP) and requiring them to rewrite it, is unnecessary duplication. If all they want to do is change the table names (not the column names), it could be just a list of @Table(tableName) overrides in the orm.xml file. > Enable the Use of Different Table Names in drools-persistence-jpa > ----------------------------------------------------------------- > > Key: JBRULES-3318 > URL: https://issues.jboss.org/browse/JBRULES-3318 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Jim Tyrrell > Assignee: Marco Rietveld > Fix For: FUTURE > > > Customer is noticing a few table names that they would like to change out, ie use different ones. They also would like the table structure to match the naming conventions their organization employes. -- 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3318) Enable the Use of Different Table Names in drools-persistence-jpa

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3318?page=com.atlassian.jira.plug... ] Geoffrey De Smet commented on JBRULES-3318: ------------------------------------------- >From my experience, the META-INF/orm.xml is indeed the way to do it: it can override any annotation in the code. Problem is they have to put it in the drools/jbpm-persistence-jpa.jar file AFAIK, so that's a PITA when upgrading to a new drools/jbpm version. You might not want to use "xml-mapping-metadata-complete", as you don't want to disable all annotations in code. For example, disabling @Temporal(TemporalType.TIMESTAMP) and requiring them to rewrite it, is unnecessary duplication. If all they want to do is change the table names (not the column names), it could be just a list of @Table(tableName) overrides in the orm.xml file. > Enable the Use of Different Table Names in drools-persistence-jpa > ----------------------------------------------------------------- > > Key: JBRULES-3318 > URL: https://issues.jboss.org/browse/JBRULES-3318 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Jim Tyrrell > Assignee: Marco Rietveld > Fix For: FUTURE > > > Customer is noticing a few table names that they would like to change out, ie use different ones. They also would like the table structure to match the naming conventions their organization employes. -- 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-835) CCI information

by Jesper Pedersen (JIRA)

13 years, 11 months

2
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 2012