[JBoss JIRA] (WFLY-6854) Upgrade Hibernate ORM to 5.1.x
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-6854?page=com.atlassian.jira.plugin.... ]
Scott Marlow edited comment on WFLY-6854 at 7/21/16 8:55 AM:
-------------------------------------------------------------
[~epbernard] the tracking jira is https://hibernate.atlassian.net/browse/HHH-10896. We used to be able to link jboss.org jiras with HHH jiras but that didn't seem to work from the HHH side. Next best thing is this comment that contains the HHH-10896 link and the reciprocal comment added to HHH-10896.
was (Author: smarlow):
[~epbernard] the tracking jira is https://hibernate.atlassian.net/browse/HHH-10896. We used to be able to link jboss.org jiras with HHH jiras but that didn't seem to work from the HHH side. Next best thing is this commend that contains the HHH-10896 link and the reciprocal comment HHH-10896.
> Upgrade Hibernate ORM to 5.1.x
> ------------------------------
>
> Key: WFLY-6854
> URL: https://issues.jboss.org/browse/WFLY-6854
> Project: WildFly
> Issue Type: Feature Request
> Components: JPA / Hibernate
> Reporter: Emmanuel Bernard
> Assignee: Scott Marlow
> Fix For: 11.0.0.Alpha1
>
>
> This is a follow up on WFLY-6682.
> After looking at the list of potential incompatibilities, we decided to not upgrade to 5.2 but instead to 5.1 to provide a smoother experience to users.
> We can consider adding a 5.2 optional switch via Jipijapa if bandwidth permit but let's treat it as a second issue and have [~smarlow] lead it.
> PS: I put v11Alpha1 but feel free to adjust it to any WF 11 version that fits best.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (WFLY-6854) Upgrade Hibernate ORM to 5.1.x
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-6854?page=com.atlassian.jira.plugin.... ]
Scott Marlow commented on WFLY-6854:
------------------------------------
[~epbernard] the tracking jira is https://hibernate.atlassian.net/browse/HHH-10896. We used to be able to link jboss.org jiras with HHH jiras but that didn't seem to work from the HHH side. Next best thing is this commend that contains the HHH-10896 link and the reciprocal comment HHH-10896.
> Upgrade Hibernate ORM to 5.1.x
> ------------------------------
>
> Key: WFLY-6854
> URL: https://issues.jboss.org/browse/WFLY-6854
> Project: WildFly
> Issue Type: Feature Request
> Components: JPA / Hibernate
> Reporter: Emmanuel Bernard
> Assignee: Scott Marlow
> Fix For: 11.0.0.Alpha1
>
>
> This is a follow up on WFLY-6682.
> After looking at the list of potential incompatibilities, we decided to not upgrade to 5.2 but instead to 5.1 to provide a smoother experience to users.
> We can consider adding a 5.2 optional switch via Jipijapa if bandwidth permit but let's treat it as a second issue and have [~smarlow] lead it.
> PS: I put v11Alpha1 but feel free to adjust it to any WF 11 version that fits best.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (WFLY-6865) org.jboss.modules.ModuleNotFoundException when setting annotations=true in jboss-deployment-structure.xml
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-6865?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-6865:
-----------------------------------
So issue is that dependency between modules is not introduces only by defining jboss-module-structure.xml claspath deps?
That is somewhat known/expected behavior, that is why proper dependencies ware introduces with jboss-deployment-dependencies in jboss-all.xml
> org.jboss.modules.ModuleNotFoundException when setting annotations=true in jboss-deployment-structure.xml
> ---------------------------------------------------------------------------------------------------------
>
> Key: WFLY-6865
> URL: https://issues.jboss.org/browse/WFLY-6865
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Affects Versions: 10.0.0.Final
> Reporter: Brad Maxwell
> Assignee: Jason Greene
> Attachments: reproducer.zip
>
>
> {code}
> helloWorld.ear
> - helloWorld-ejb.jar
> - HelloBean - @Stateless EJB extends AbstractBean
> - lib
> - helloWorld-api.jar
> - META-INF
> - jandex.idx
> - Hello - EJB interface
> - AbstractBean - abstract class which has @PostConstruct and implements Hello
> helloWorld2.ear
> - helloWorld2-ejb.jar
> - HelloBean2 - @Startup @Singleton extends AbstractBean
> - META-INF
> - jboss-deployment-structure.xml depends on deployment.helloWorld.ear export=true annotations=true
> {code}
> To have HelloBean2 pickup the annotations on AbstractBean, jandex.idx was generate for the helloWorld-api.jar and then the j-d-s.xml file dependency has export=true so helloWorld2-ejb.jar sees the classes and annotations=true set to pull in the annotations.
> When annotations is not set or annotations=false the helloWorld2.ear deploys (but the @PostConstruct is not run since annotations are not enabled). When annotations=true is set, helloWorld2.ear fails to deploy with the exception below.
> It looks like the annotations handling is possibly out of order as the j-d-s.xml dependency should ensure the deployment.helloWorld.ear module is there (which it does when annotations=false, but when true it seems the module is not ready)
> {code}
> 19:44:44,659 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."helloWorld2.ear".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."helloWorld2.ear".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "helloWorld2.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.modules.ModuleNotFoundException: deployment.helloWorld.ear:main
> at org.jboss.as.server.deployment.annotation.CompositeIndexProcessor.deploy(CompositeIndexProcessor.java:91)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
> ... 5 more
> Caused by: org.jboss.modules.ModuleNotFoundException: deployment.helloWorld.ear:main
> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:223)
> at org.jboss.as.server.deployment.annotation.CompositeIndexProcessor.deploy(CompositeIndexProcessor.java:81)
> ... 6 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (WFLY-6869) Make startup errors human readable when missing/unsatisfied dependencies
by Heiko Braun (JIRA)
[ https://issues.jboss.org/browse/WFLY-6869?page=com.atlassian.jira.plugin.... ]
Heiko Braun moved SWARM-550 to WFLY-6869:
-----------------------------------------
Project: WildFly (was: WildFly Swarm)
Key: WFLY-6869 (was: SWARM-550)
> Make startup errors human readable when missing/unsatisfied dependencies
> ------------------------------------------------------------------------
>
> Key: WFLY-6869
> URL: https://issues.jboss.org/browse/WFLY-6869
> Project: WildFly
> Issue Type: Enhancement
> Reporter: Claus Ibsen
>
> When you run WF-Swarm you may get some errors such as missing/unsatisfied dependencies that is hard to understand for new users to WF-Swarm.
> The output is very dense as if its a stacktrace.
> You should make it human readable and better understandable.
> {code}
> 2016-07-08 11:48:22,760 INFO [org.jboss.as.controller] (main) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service jboss.deployment.unit."forge-web.war".WeldBootstrapService (missing) dependents: [service jboss.deployment.unit."forge-web.war".component."org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation".WeldInstantiator, service jboss.deployment.unit."forge-web.war".component."org.jboss.weld.servlet.WeldInitialListener".WeldInstantiator, service jboss.deployment.unit."forge-web.war".component."org.jboss.weld.servlet.WeldTerminalListener".WeldInstantiator, service jboss.deployment.unit."forge-web.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".WeldInstantiator, WFLYCTL0208: ... and 3 more ]
> service jboss.deployment.unit."forge-web.war".WeldStartService (missing) dependents: [service jboss.deployment.unit."forge-web.war".component."org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation".WeldInstantiator, service jboss.deployment.unit."forge-web.war".component."org.jboss.weld.servlet.WeldInitialListener".WeldInstantiator, service jboss.undertow.deployment.default-server.default-host./, service jboss.deployment.unit."forge-web.war".component."org.jboss.weld.servlet.WeldTerminalListener".WeldInstantiator, WFLYCTL0208: ... and 2 more ]
> service jboss.deployment.unit."forge-web.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".CREATE (missing) dependents: [service jboss.deployment.unit."forge-web.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START]
> service jboss.deployment.unit."forge-web.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./, service jboss.deployment.unit."forge-web.war".deploymentCompleteService]
> service jboss.deployment.unit."forge-web.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."forge-web.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START]
> service jboss.deployment.unit."forge-web.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".CREATE (missing) dependents: [service jboss.deployment.unit."forge-web.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START]
> service jboss.deployment.unit."forge-web.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./, service jboss.deployment.unit."forge-web.war".deploymentCompleteService]
> service jboss.deployment.unit."forge-web.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."forge-web.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START]
> service jboss.deployment.unit."forge-web.war".component."org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./, service jboss.undertow.deployment.default-server.default-host./.UndertowDeploymentInfoService, service jboss.deployment.unit."forge-web.war".deploymentCompleteService]
> service jboss.deployment.unit."forge-web.war".component."org.jboss.weld.servlet.WeldInitialListener".CREATE (missing) dependents: [service jboss.deployment.unit."forge-web.war".component."org.jboss.weld.servlet.WeldInitialListener".START]
> service jboss.deployment.unit."forge-web.war".component."org.jboss.weld.servlet.WeldInitialListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./, service jboss.deployment.unit."forge-web.war".deploymentCompleteService]
> service jboss.deployment.unit."forge-web.war".component."org.jboss.weld.servlet.WeldInitialListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."forge-web.war".component."org.jboss.weld.servlet.WeldInitialListener".START]
> service jboss.deployment.unit."forge-web.war".component."org.jboss.weld.servlet.WeldTerminalListener".CREATE (missing) dependents: [service jboss.deployment.unit."forge-web.war".component."org.jboss.weld.servlet.WeldTerminalListener".START]
> service jboss.deployment.unit."forge-web.war".component."org.jboss.weld.servlet.WeldTerminalListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./, service jboss.deployment.unit."forge-web.war".deploymentCompleteService]
> service jboss.deployment.unit."forge-web.war".component."org.jboss.weld.servlet.WeldTerminalListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."forge-web.war".component."org.jboss.weld.servlet.WeldTerminalListener".START]
> service jboss.deployment.unit."forge-web.war".jndiDependencyService (missing) dependents: [service jboss.deployment.unit."forge-web.war".component."org.jboss.weld.servlet.WeldTerminalListener".START, service jboss.deployment.unit."forge-web.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START, service jboss.deployment.unit."forge-web.war".component."org.jboss.weld.servlet.WeldInitialListener".START, service jboss.deployment.unit."forge-web.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START]
> service jboss.undertow.deployment.default-server.default-host./ (missing) dependents: [service jboss.deployment.unit."forge-web.war".deploymentCompleteService]
> service jboss.undertow.deployment.default-server.default-host./.UndertowDeploymentInfoService (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./]
> service jboss.undertow.deployment.default-server.default-host./.session (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./.UndertowDeploymentInfoService]
> WFLYCTL0186: Services which failed to start: service jboss.deployment.unit."forge-web.war".WeldStartService
> 2016-07-08 11:48:22,762 ERROR [stderr] (main) Exception in thread "main" org.wildfly.swarm.container.DeploymentException: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"forge-web.war\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"forge-web.war\".WeldStartService: Failed to start service
> 2016-07-08 11:48:22,763 ERROR [stderr] (main) Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-000071: Managed bean with a parameterized bean class must be @Dependent: class org.apache.cxf.jaxrs.provider.XSLTJaxbProvider"}}
> 2016-07-08 11:48:22,763 ERROR [stderr] (main) at org.wildfly.swarm.container.runtime.RuntimeDeployer.deploy(RuntimeDeployer.java:159)
> 2016-07-08 11:48:22,763 ERROR [stderr] (main) at org.wildfly.swarm.container.Container.deploy(Container.java:432)
> 2016-07-08 11:48:22,763 ERROR [stderr] (main) at org.wildfly.swarm.Swarm.deploy(Swarm.java:122)
> 2016-07-08 11:48:22,763 ERROR [stderr] (main) at org.wildfly.swarm.Swarm.deploy(Swarm.java:45)
> 2016-07-08 11:48:22,763 ERROR [stderr] (main) at org.wildfly.swarm.container.Container.deploy(Container.java:416)
> 2016-07-08 11:48:22,764 ERROR [stderr] (main) at org.wildfly.swarm.Swarm.deploy(Swarm.java:117)
> 2016-07-08 11:48:22,764 ERROR [stderr] (main) at org.wildfly.swarm.Swarm.deploy(Swarm.java:45)
> 2016-07-08 11:48:22,764 ERROR [stderr] (main) at org.wildfly.swarm.Swarm.simpleMain(Swarm.java:150)
> 2016-07-08 11:48:22,764 ERROR [stderr] (main) at org.wildfly.swarm.Swarm.main(Swarm.java:141)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (WFLY-6854) Upgrade Hibernate ORM to 5.1.x
by Emmanuel Bernard (JIRA)
[ https://issues.jboss.org/browse/WFLY-6854?page=com.atlassian.jira.plugin.... ]
Emmanuel Bernard commented on WFLY-6854:
----------------------------------------
[~smarlow] about the failed PR, who is tracking and dispatching the necessary work? You? Better get that moving :)
> Upgrade Hibernate ORM to 5.1.x
> ------------------------------
>
> Key: WFLY-6854
> URL: https://issues.jboss.org/browse/WFLY-6854
> Project: WildFly
> Issue Type: Feature Request
> Components: JPA / Hibernate
> Reporter: Emmanuel Bernard
> Assignee: Scott Marlow
> Fix For: 11.0.0.Alpha1
>
>
> This is a follow up on WFLY-6682.
> After looking at the list of potential incompatibilities, we decided to not upgrade to 5.2 but instead to 5.1 to provide a smoother experience to users.
> We can consider adding a 5.2 optional switch via Jipijapa if bandwidth permit but let's treat it as a second issue and have [~smarlow] lead it.
> PS: I put v11Alpha1 but feel free to adjust it to any WF 11 version that fits best.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (WFLY-6854) Upgrade Hibernate ORM to 5.1.x
by Emmanuel Bernard (JIRA)
[ https://issues.jboss.org/browse/WFLY-6854?page=com.atlassian.jira.plugin.... ]
Emmanuel Bernard commented on WFLY-6854:
----------------------------------------
I think WF 11 is a good target, we never know what the TCK will bring as surprise. I don't see WF 10.1 as a necessary target at all, it stresses everyone for not much.
> Upgrade Hibernate ORM to 5.1.x
> ------------------------------
>
> Key: WFLY-6854
> URL: https://issues.jboss.org/browse/WFLY-6854
> Project: WildFly
> Issue Type: Feature Request
> Components: JPA / Hibernate
> Reporter: Emmanuel Bernard
> Assignee: Scott Marlow
> Fix For: 11.0.0.Alpha1
>
>
> This is a follow up on WFLY-6682.
> After looking at the list of potential incompatibilities, we decided to not upgrade to 5.2 but instead to 5.1 to provide a smoother experience to users.
> We can consider adding a 5.2 optional switch via Jipijapa if bandwidth permit but let's treat it as a second issue and have [~smarlow] lead it.
> PS: I put v11Alpha1 but feel free to adjust it to any WF 11 version that fits best.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (WFLY-6868) Remove deprecated and duplicated class AcceptEncodingGZIPInterceptor in rts subsystem
by Jim Ma (JIRA)
Jim Ma created WFLY-6868:
----------------------------
Summary: Remove deprecated and duplicated class AcceptEncodingGZIPInterceptor in rts subsystem
Key: WFLY-6868
URL: https://issues.jboss.org/browse/WFLY-6868
Project: WildFly
Issue Type: Task
Components: XTS
Affects Versions: 10.0.0.Final
Reporter: Jim Ma
Assignee: Jim Ma
Fix For: 10.1.0.CR1
AcceptEncodingGZIPInterceptor is a deprecated class and AcceptEncodingGZIPFilter is a replacement since jaxrs 2.0. We can remove this deprecated class because AcceptEncodingGZIPFilter is already added in AbstractRTSApplication.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (WFLY-6867) "JVM Options" should not be marked with asterisk
by Chao Wang (JIRA)
Chao Wang created WFLY-6867:
-------------------------------
Summary: "JVM Options" should not be marked with asterisk
Key: WFLY-6867
URL: https://issues.jboss.org/browse/WFLY-6867
Project: WildFly
Issue Type: Bug
Components: Web Console
Affects Versions: 10.0.0.Final
Reporter: Chao Wang
Assignee: Chao Wang
When editing a JVM configuration through the console in domain mode, "JVM Options" is marked with an asterisk. But "JVM Options" are not required so this asterisk should be removd.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (WFLY-6866) "JVM Options" should not be marked with asterisk
by Chao Wang (JIRA)
[ https://issues.jboss.org/browse/WFLY-6866?page=com.atlassian.jira.plugin.... ]
Chao Wang updated WFLY-6866:
----------------------------
Summary: "JVM Options" should not be marked with asterisk (was: [GSS](7.0.z) "JVM Options" should not be marked with asterisk)
> "JVM Options" should not be marked with asterisk
> ------------------------------------------------
>
> Key: WFLY-6866
> URL: https://issues.jboss.org/browse/WFLY-6866
> Project: WildFly
> Issue Type: Bug
> Components: Web Console
> Affects Versions: 10.0.0.Final
> Reporter: Chao Wang
> Assignee: Chao Wang
> Original Estimate: 3 hours
> Remaining Estimate: 3 hours
>
> When editing a JVM configuration through the console in domain mode, "JVM Options" is marked with an asterisk. But "JVM Options" are not required so this asterisk should be removd.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months