[JBoss JIRA] (WFLY-1445) Jawr servlet with name JavascriptServlet failed to initialize properly.
by Igor Shulika (JIRA)
Igor Shulika created WFLY-1445:
----------------------------------
Summary: Jawr servlet with name JavascriptServlet failed to initialize properly.
Key: WFLY-1445
URL: https://issues.jboss.org/browse/WFLY-1445
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Affects Versions: 8.0.0.Alpha2
Reporter: Igor Shulika
Assignee: Stuart Douglas
I'm deploying a OSGi WAB file on the latest WildFly 8.0.0.Alpha2-SNAPSHOT server. Can not initialize the JavascriptServlet from JAWR Bundle. Note: When I used the <extension module="org.jboss.as.web"/> insted of <extension module="org.wildfly.extension.undertow"/> it works.
Please see error trace below.
16:39:44,476 FATAL [net.jawr.web.servlet.JawrServlet] (MSC service thread 1-3) Jawr servlet with name JavascriptServlet failed to initialize properly.
16:39:44,476 FATAL [net.jawr.web.servlet.JawrServlet] (MSC service thread 1-3) Cause:
16:39:44,476 FATAL [net.jawr.web.servlet.JawrServlet] (MSC service thread 1-3) null: java.lang.reflect.UndeclaredThrowableException
at com.sun.proxy.$Proxy22.getResource(Unknown Source)
at net.jawr.web.resource.handler.reader.ServletContextResourceReaderHandler.getResource(ServletContextResourceReaderHandler.java:192) [ServletContextResourceReaderHandler.class:]
at net.jawr.web.resource.bundle.handler.ResourceBundlesHandlerImpl.joinAndPostprocessBundle(ResourceBundlesHandlerImpl.java:892) [ResourceBundlesHandlerImpl.class:]
at net.jawr.web.resource.bundle.handler.ResourceBundlesHandlerImpl.joinAndPostProcessBundle(ResourceBundlesHandlerImpl.java:835) [ResourceBundlesHandlerImpl.class:]
at net.jawr.web.resource.bundle.handler.ResourceBundlesHandlerImpl.joinAndStoreBundle(ResourceBundlesHandlerImpl.java:766) [ResourceBundlesHandlerImpl.class:]
at net.jawr.web.resource.bundle.handler.ResourceBundlesHandlerImpl.initAllBundles(ResourceBundlesHandlerImpl.java:542) [ResourceBundlesHandlerImpl.class:]
at net.jawr.web.resource.bundle.handler.CachedResourceBundlesHandler.initAllBundles(CachedResourceBundlesHandler.java:126) [CachedResourceBundlesHandler.class:]
at net.jawr.web.resource.bundle.factory.BundlesHandlerFactory.buildResourceBundlesHandler(BundlesHandlerFactory.java:233) [BundlesHandlerFactory.class:]
at net.jawr.web.resource.bundle.factory.PropertiesBasedBundlesHandlerFactory.buildResourceBundlesHandler(PropertiesBasedBundlesHandlerFactory.java:204) [PropertiesBasedBundlesHandlerFactory.class:]
at net.jawr.web.servlet.JawrRequestHandler.initializeJawrConfig(JawrRequestHandler.java:349) [JawrRequestHandler.class:]
at net.jawr.web.servlet.JawrRequestHandler.initRequestHandler(JawrRequestHandler.java:262) [JawrRequestHandler.class:]
at net.jawr.web.servlet.JawrRequestHandler.<init>(JawrRequestHandler.java:184) [JawrRequestHandler.class:]
at net.jawr.web.servlet.JawrServlet.init(JawrServlet.java:56) [JawrServlet.class:]
at javax.servlet.GenericServlet.init(GenericServlet.java:244) [jboss-servlet-api_3.1_spec-1.0.0.Alpha1.jar:1.0.0.Alpha1]
at io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy.start(ManagedServlet.java:145) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15]
at io.undertow.servlet.core.ManagedServlet.start(ManagedServlet.java:62) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15]
at io.undertow.servlet.core.DeploymentManagerImpl.start(DeploymentManagerImpl.java:599) [undertow-servlet-1.0.0.Alpha15.jar:1.0.0.Alpha15]
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:77)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_21]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_21]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_21]
at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_21]
at net.jawr.web.resource.bundle.generator.ResourceGeneratorReaderProxyFactory$ResourceGeneratorReaderWrapperInvocationHandler.invoke(ResourceGeneratorReaderProxyFactory.java:167) [ResourceGeneratorReaderProxyFactory$ResourceGeneratorReaderWrapperInvocationHandler.class:]
... 23 more
Caused by: java.lang.IllegalArgumentException: The DWR bean named 'TransactionService' was not found in any DWR configuration instance.
at net.jawr.web.resource.bundle.generator.dwr.DWRBeanGenerator.getInterfaceScript(DWRBeanGenerator.java:265) [DWRBeanGenerator.class:]
at net.jawr.web.resource.bundle.generator.dwr.DWRBeanGenerator.createResource(DWRBeanGenerator.java:134) [DWRBeanGenerator.class:]
at net.jawr.web.resource.bundle.generator.ResourceGeneratorReaderWrapper.getResource(ResourceGeneratorReaderWrapper.java:135) [ResourceGeneratorReaderWrapper.class:]
... 28 more
--
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, 1 month
[JBoss JIRA] (JGRP-1638) Memory leak
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1638?page=com.atlassian.jira.plugin.... ]
Bela Ban edited comment on JGRP-1638 at 6/3/13 12:20 PM:
---------------------------------------------------------
git bisect shows 434760c8eca1223bd3f911895cdc9c8109590946 as first bad commit. This sends STABLE messages by default to the coordinator instead of multicasting them to all members. Need to investigate what went wrong here.
WORKAROUND: set STABLE.send_stable_msgs_to_coord_only to false
was (Author: belaban):
git bisect shows 434760c8eca1223bd3f911895cdc9c8109590946 as first bad commit. This sends STABLE messages by default to the coordinator only instead of multicasting them to all members. Ned to investigate what went wrong here.
WORKAROUND: set STABLE.send_stable_msgs_to_coord_only to false
> Memory leak
> -----------
>
> Key: JGRP-1638
> URL: https://issues.jboss.org/browse/JGRP-1638
> Project: JGroups
> Issue Type: Task
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Critical
> Fix For: 3.4
>
>
> Running MPerf with conf/fast-local.xml (2 members on the same host, 20 million messages each) creates a memory leak in 3.4.x.
> This runs perfectly 3.2.8.Final, so it must be something that was introduced in 3.3.x (3.4.x at this time has almost no diffs to 3.3.0.Final).
--
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, 1 month
[JBoss JIRA] (WFLY-1186) Create JPA service callback for invoking database migration
by Anil Arora (JIRA)
[ https://issues.jboss.org/browse/WFLY-1186?page=com.atlassian.jira.plugin.... ]
Anil Arora commented on WFLY-1186:
----------------------------------
I personally think it might be easier to implement this in the persistent unit class vs a separate service. As long as I have access to the datasource object, it's all good. Even throwing an event would be useful...maybe an observer to listen to DB datasource creation events, etc. I'm sure there are clean ways of doing this.
Of course, to add a wrinkle to this, it would be useful to let Hibernate validate the schema post migration to ensure that the database was migrated properly. Useful for development time.
> Create JPA service callback for invoking database migration
> -----------------------------------------------------------
>
> Key: WFLY-1186
> URL: https://issues.jboss.org/browse/WFLY-1186
> Project: WildFly
> Issue Type: Feature Request
> Components: JPA / Hibernate
> Reporter: Anil Arora
> Assignee: Scott Marlow
>
> Looking for a simple callback/listener mechanism so that we can invoke a database migration script before JPA persistent unit starts up and runs the Hibernate schema validation mechanism.
> Ideally, there would be a property within the persistence.xml that indicates which class to call. It would also pass in/inject the datasource that is being used for the persistence unit.
> Essentially, this would solve the lack of migration support in Hibernate itself.
--
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, 1 month
[JBoss JIRA] (WFLY-1444) CNFE: javax.persistence.Converter
by Juergen Zimmermann (JIRA)
[ https://issues.jboss.org/browse/WFLY-1444?page=com.atlassian.jira.plugin.... ]
Juergen Zimmermann commented on WFLY-1444:
------------------------------------------
https://hibernate.atlassian.net/browse/HHH-8289
> CNFE: javax.persistence.Converter
> ---------------------------------
>
> Key: WFLY-1444
> URL: https://issues.jboss.org/browse/WFLY-1444
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 8.0.0.Alpha2
> Reporter: Juergen Zimmermann
> Assignee: Scott Marlow
>
> I'm using the latest WildFly snapshot containing Hibernate 4.3.0.Beta3. However, I'm getting a CNFE for javax.persistence.Converter (see stacktrace below). This class is definitely contained in modules/system/layers/base/javax/persistence/api/main/hibernate-jpa-2.1-api-1.0.0.Draft-16.jar
> Stacktrace:
> ...
> 16:45:00,362 INFO [org.hibernate.Version] HHH000412: Hibernate Core {4.3.0.Beta3}
> 16:45:00,362 INFO [org.hibernate.cfg.Environment] HHH000206: hibernate.properties not found
> 16:45:00,362 INFO [org.hibernate.cfg.Environment] HHH000021: Bytecode provider name : javassist
> 16:45:00,658 ERROR [org.hibernate.AssertionFailure] HHH000099: an assertion failure occured (this may indicate a bug in Hibernate, but is more likely due to unsafe use of the session): java.lang.ClassNotFoundException: javax.persistence.Converter from [Module "org.jboss.jandex:main" from local module loader @c84051 (finder: local module finder @f6a711 (roots: C:\Software\wildfly-8.0.0.Alpha2-20130602\modules,C:\Software\wildfly-8.0.0.Alpha2-20130602\modules\system\layers\base))]
> 16:45:00,658 ERROR [org.jboss.msc.service.fail] MSC000001: Failed to start service jboss.persistenceunit."shop2.war#de.shop.PU": org.jboss.msc.service.StartException in service jboss.persistenceunit."shop2.war#de.shop.PU": org.hibernate.AssertionFailure: The annotation javax.persistence.Converter does not define a parameter 'autoApply'
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:112) [wildfly-jpa-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final.jar:2.1.0.Final]
> Caused by: org.hibernate.AssertionFailure: The annotation javax.persistence.Converter does not define a parameter 'autoApply'
> at org.hibernate.metamodel.source.annotations.JandexHelper.getDefaultValue(JandexHelper.java:328)
> at org.hibernate.metamodel.source.annotations.JandexHelper.getValue(JandexHelper.java:111)
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.prepareMetadataSources(EntityManagerFactoryBuilderImpl.java:391)
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.<init>(EntityManagerFactoryBuilderImpl.java:224)
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.<init>(EntityManagerFactoryBuilderImpl.java:186)
> at org.hibernate.jpa.boot.spi.Bootstrap.getEntityManagerFactoryBuilder(Bootstrap.java:43)
> at org.hibernate.jpa.boot.spi.Bootstrap.getEntityManagerFactoryBuilder(Bootstrap.java:55)
> at org.hibernate.jpa.HibernatePersistenceProvider.createContainerEntityManagerFactory(HibernatePersistenceProvider.java:142)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:214) [wildfly-jpa-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.access$800(PersistenceUnitServiceImpl.java:59) [wildfly-jpa-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:108) [wildfly-jpa-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> ... 4 more
> Caused by: java.lang.ClassNotFoundException: javax.persistence.Converter from [Module "org.jboss.jandex:main" from local module loader @c84051 (finder: local module finder @f6a711 (roots: C:\Software\wildfly-8.0.0.Alpha2-20130602\modules,C:\Software\wildfly-8.0.0.Alpha2-20130602\modules\system\layers\base))]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:196) [jboss-modules.jar:1.2.1.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.1.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.1.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.1.Final]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.1.Final]
> at org.hibernate.metamodel.source.annotations.JandexHelper.getDefaultValue(JandexHelper.java:320)
> ... 14 more
--
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, 1 month
[JBoss JIRA] (JGRP-1638) Memory leak
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1638?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1638:
--------------------------------
git bisect shows 434760c8eca1223bd3f911895cdc9c8109590946 as first bad commit. This sends STABLE messages by default to the coordinator only instead of multicasting them to all members. Ned to investigate what went wrong here.
WORKAROUND: set STABLE.send_stable_msgs_to_coord_only to false
> Memory leak
> -----------
>
> Key: JGRP-1638
> URL: https://issues.jboss.org/browse/JGRP-1638
> Project: JGroups
> Issue Type: Task
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Critical
> Fix For: 3.4
>
>
> Running MPerf with conf/fast-local.xml (2 members on the same host, 20 million messages each) creates a memory leak in 3.4.x.
> This runs perfectly 3.2.8.Final, so it must be something that was introduced in 3.3.x (3.4.x at this time has almost no diffs to 3.3.0.Final).
--
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, 1 month
[JBoss JIRA] (WFLY-1444) CNFE: javax.persistence.Converter
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-1444?page=com.atlassian.jira.plugin.... ]
Scott Marlow resolved WFLY-1444.
--------------------------------
Resolution: Duplicate Issue
Please create a https://hibernate.onjira.com/browse/HHH issue instead and update this (WFLY-1444) with the HHH jira number.
>From the exception callstack, this looks like an issue in org.hibernate.metamodel.source.annotations.JandexHelper.getDefaultValue(JandexHelper.java:320) using the org.jboss.jandex.Index classloader to access the application converter class.
Thanks for reporting it!
> CNFE: javax.persistence.Converter
> ---------------------------------
>
> Key: WFLY-1444
> URL: https://issues.jboss.org/browse/WFLY-1444
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 8.0.0.Alpha2
> Reporter: Juergen Zimmermann
> Assignee: Scott Marlow
>
> I'm using the latest WildFly snapshot containing Hibernate 4.3.0.Beta3. However, I'm getting a CNFE for javax.persistence.Converter (see stacktrace below). This class is definitely contained in modules/system/layers/base/javax/persistence/api/main/hibernate-jpa-2.1-api-1.0.0.Draft-16.jar
> Stacktrace:
> ...
> 16:45:00,362 INFO [org.hibernate.Version] HHH000412: Hibernate Core {4.3.0.Beta3}
> 16:45:00,362 INFO [org.hibernate.cfg.Environment] HHH000206: hibernate.properties not found
> 16:45:00,362 INFO [org.hibernate.cfg.Environment] HHH000021: Bytecode provider name : javassist
> 16:45:00,658 ERROR [org.hibernate.AssertionFailure] HHH000099: an assertion failure occured (this may indicate a bug in Hibernate, but is more likely due to unsafe use of the session): java.lang.ClassNotFoundException: javax.persistence.Converter from [Module "org.jboss.jandex:main" from local module loader @c84051 (finder: local module finder @f6a711 (roots: C:\Software\wildfly-8.0.0.Alpha2-20130602\modules,C:\Software\wildfly-8.0.0.Alpha2-20130602\modules\system\layers\base))]
> 16:45:00,658 ERROR [org.jboss.msc.service.fail] MSC000001: Failed to start service jboss.persistenceunit."shop2.war#de.shop.PU": org.jboss.msc.service.StartException in service jboss.persistenceunit."shop2.war#de.shop.PU": org.hibernate.AssertionFailure: The annotation javax.persistence.Converter does not define a parameter 'autoApply'
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:112) [wildfly-jpa-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final.jar:2.1.0.Final]
> Caused by: org.hibernate.AssertionFailure: The annotation javax.persistence.Converter does not define a parameter 'autoApply'
> at org.hibernate.metamodel.source.annotations.JandexHelper.getDefaultValue(JandexHelper.java:328)
> at org.hibernate.metamodel.source.annotations.JandexHelper.getValue(JandexHelper.java:111)
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.prepareMetadataSources(EntityManagerFactoryBuilderImpl.java:391)
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.<init>(EntityManagerFactoryBuilderImpl.java:224)
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.<init>(EntityManagerFactoryBuilderImpl.java:186)
> at org.hibernate.jpa.boot.spi.Bootstrap.getEntityManagerFactoryBuilder(Bootstrap.java:43)
> at org.hibernate.jpa.boot.spi.Bootstrap.getEntityManagerFactoryBuilder(Bootstrap.java:55)
> at org.hibernate.jpa.HibernatePersistenceProvider.createContainerEntityManagerFactory(HibernatePersistenceProvider.java:142)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:214) [wildfly-jpa-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.access$800(PersistenceUnitServiceImpl.java:59) [wildfly-jpa-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:108) [wildfly-jpa-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> ... 4 more
> Caused by: java.lang.ClassNotFoundException: javax.persistence.Converter from [Module "org.jboss.jandex:main" from local module loader @c84051 (finder: local module finder @f6a711 (roots: C:\Software\wildfly-8.0.0.Alpha2-20130602\modules,C:\Software\wildfly-8.0.0.Alpha2-20130602\modules\system\layers\base))]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:196) [jboss-modules.jar:1.2.1.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.1.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.1.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.1.Final]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.1.Final]
> at org.hibernate.metamodel.source.annotations.JandexHelper.getDefaultValue(JandexHelper.java:320)
> ... 14 more
--
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, 1 month
[JBoss JIRA] (WFLY-1186) Create JPA service callback for invoking database migration
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-1186?page=com.atlassian.jira.plugin.... ]
Scott Marlow commented on WFLY-1186:
------------------------------------
I agree, that for the Hibernate (or any persistence provider) JPA 2.1 database migration support, the database user account used, would need permissions to execute DDL.
I think there are probably multiple ways we could handle deployment time callbacks for database migration. One strategy might be to let an application level class be invoked (at deployment time, before the persistence unit is created). This would be pretty much following your original suggestion (either via extension annotation or a persistence unit property).
The callback could probably use the JPA 2.1 database migration api or something custom like FlyWayDB (perhaps even using http://schemacrawler.sourceforge.net) that verify the schema.
> Create JPA service callback for invoking database migration
> -----------------------------------------------------------
>
> Key: WFLY-1186
> URL: https://issues.jboss.org/browse/WFLY-1186
> Project: WildFly
> Issue Type: Feature Request
> Components: JPA / Hibernate
> Reporter: Anil Arora
> Assignee: Scott Marlow
>
> Looking for a simple callback/listener mechanism so that we can invoke a database migration script before JPA persistent unit starts up and runs the Hibernate schema validation mechanism.
> Ideally, there would be a property within the persistence.xml that indicates which class to call. It would also pass in/inject the datasource that is being used for the persistence unit.
> Essentially, this would solve the lack of migration support in Hibernate itself.
--
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, 1 month
[JBoss JIRA] (WFLY-1186) Create JPA service callback for invoking database migration
by Anil Arora (JIRA)
[ https://issues.jboss.org/browse/WFLY-1186?page=com.atlassian.jira.plugin.... ]
Anil Arora commented on WFLY-1186:
----------------------------------
Yes, the DB user would have to have the "create resource" permission to do anything. I'm not sure how this would be any different than having hibernate execute SQL for creation of the database though.
When you refer to deployment time callback, are you also considering auto-deployment cases where I drop a new war into the deployments directory and restart the application/server?
> Create JPA service callback for invoking database migration
> -----------------------------------------------------------
>
> Key: WFLY-1186
> URL: https://issues.jboss.org/browse/WFLY-1186
> Project: WildFly
> Issue Type: Feature Request
> Components: JPA / Hibernate
> Reporter: Anil Arora
> Assignee: Scott Marlow
>
> Looking for a simple callback/listener mechanism so that we can invoke a database migration script before JPA persistent unit starts up and runs the Hibernate schema validation mechanism.
> Ideally, there would be a property within the persistence.xml that indicates which class to call. It would also pass in/inject the datasource that is being used for the persistence unit.
> Essentially, this would solve the lack of migration support in Hibernate itself.
--
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, 1 month