[JBoss JIRA] (WFWIP-59) Enable CDI by default when MP Config usage is detected in the deployment
by Rostislav Svoboda (JIRA)
[ https://issues.jboss.org/browse/WFWIP-59?page=com.atlassian.jira.plugin.s... ]
Rostislav Svoboda updated WFWIP-59:
-----------------------------------
Priority: Major (was: Critical)
> Enable CDI by default when MP Config usage is detected in the deployment
> ------------------------------------------------------------------------
>
> Key: WFWIP-59
> URL: https://issues.jboss.org/browse/WFWIP-59
> Project: WildFly WIP
> Issue Type: Enhancement
> Components: MP Config
> Reporter: Rostislav Svoboda
> Assignee: Jeff Mesnil
>
> Enable CDI by default when MP Config usage is detected in the deployment.
> Currently users are forced to add empty {{beans.xml}} to the deployment every time they want to use MP Config - e.g. in simple servlet scenario
> {code}
> @WebServlet("/")
> public class HelloServlet extends HttpServlet {
> @Inject
> @ConfigProperty(name = "port_number")
> Integer port;
> @Override
> protected void doGet(HttpServletRequest req, HttpServletResponse resp) throws IOException {
> resp.getWriter().println("Value of port: " + port);
> }
> }
> {code}
> MP Config without CDI makes no sense to me. MP Config subsystem should be able to ensure CDI is enabled. CCing [~manovotn] [~brian.stansberry]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (DROOLS-2741) [DMN Designer] Clear the diagram toolbar button
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2741?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2741:
--------------------------------
Description:
The stunner based designers contain "Clear the diagram" button. The problem of this button for DMN Designer appears if the expression editor is opened. User has still possibility to use this button and thus can clear node that he currently edits. I think we should disable that button if expression editor is opened.
h3. Manual acceptance test
Navigate between diagram and expression editor using [1] and check button enabled in diagram, disabled in expression
[1]
- Navigation dock (/)
- Manually clicking elements (/)
was:The stunner based designers contain "Clear the diagram" button. The problem of this button for DMN Designer appears if the expression editor is opened. User has still possibility to use this button and thus can clear node that he currently edits. I think we should disable that button if expression editor is opened.
> [DMN Designer] Clear the diagram toolbar button
> -----------------------------------------------
>
> Key: DROOLS-2741
> URL: https://issues.jboss.org/browse/DROOLS-2741
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.9.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Minor
> Labels: drools-tools
>
> The stunner based designers contain "Clear the diagram" button. The problem of this button for DMN Designer appears if the expression editor is opened. User has still possibility to use this button and thus can clear node that he currently edits. I think we should disable that button if expression editor is opened.
> h3. Manual acceptance test
> Navigate between diagram and expression editor using [1] and check button enabled in diagram, disabled in expression
> [1]
> - Navigation dock (/)
> - Manually clicking elements (/)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (DROOLS-2742) [DMN Designer] Switch grid toolbar button
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2742?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2742:
--------------------------------
Description:
The stunner based designers contain "Switch grid" button. The problem of this button for DMN Designer appears if the expression editor is opened. User has still possibility to use this button. It would be more logical to disable this button while expression editor is opened as the grid is not shown at that moment.
h3. Manual acceptance test
Navigate between diagram and expression editor using [1] and check button enabled in diagram, disabled in expression
[1]
- Navigation dock (/)
- Manually clicking elements (/)
was:The stunner based designers contain "Switch grid" button. The problem of this button for DMN Designer appears if the expression editor is opened. User has still possibility to use this button. It would be more logical to disable this button while expression editor is opened as the grid is not shown at that moment.
> [DMN Designer] Switch grid toolbar button
> -----------------------------------------
>
> Key: DROOLS-2742
> URL: https://issues.jboss.org/browse/DROOLS-2742
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.9.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Minor
> Labels: drools-tools
>
> The stunner based designers contain "Switch grid" button. The problem of this button for DMN Designer appears if the expression editor is opened. User has still possibility to use this button. It would be more logical to disable this button while expression editor is opened as the grid is not shown at that moment.
> h3. Manual acceptance test
> Navigate between diagram and expression editor using [1] and check button enabled in diagram, disabled in expression
> [1]
> - Navigation dock (/)
> - Manually clicking elements (/)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (WFLY-10713) Can't build WF master with Java 11-ea+22
by Rostislav Svoboda (JIRA)
Rostislav Svoboda created WFLY-10713:
----------------------------------------
Summary: Can't build WF master with Java 11-ea+22
Key: WFLY-10713
URL: https://issues.jboss.org/browse/WFLY-10713
Project: WildFly
Issue Type: Bug
Components: Build System
Reporter: Rostislav Svoboda
Assignee: Alexey Loubyansky
Priority: Critical
Can't build WF master with 11-ea+22
{code}
[INFO] WildFly: Servlet Galleon Pack ...................... FAILURE [ 3.481 s]
[ERROR] Failed to execute goal org.wildfly.galleon-plugins:wildfly-galleon-maven-plugin:
2.0.0.Alpha4:generate-feature-specs
(feature-spec-build) on project wildfly-servlet-galleon-pack:
Feature spec generator failed: Forked embedded process has failed -> [Help 1]
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (WFWIP-65) [Artemis 2.x upgrade] Artemis RA connections disconnected after failover
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFWIP-65?page=com.atlassian.jira.plugin.s... ]
Miroslav Novak commented on WFWIP-65:
-------------------------------------
[~martyn-taylor] This is from zip from you: https://mw-messaging-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP-...
WF repo: https://github.com/mtaylor/wildfly
WF branch: EAPAMQUpgradeBranch
Artemis repo: https://github.com/apache/activemq-artemis
Artemis branch: master
> [Artemis 2.x upgrade] Artemis RA connections disconnected after failover
> -------------------------------------------------------------------------
>
> Key: WFWIP-65
> URL: https://issues.jboss.org/browse/WFWIP-65
> Project: WildFly WIP
> Issue Type: Bug
> Components: Artemis
> Reporter: Miroslav Novak
> Assignee: Martyn Taylor
> Priority: Blocker
> Attachments: DedicatedFailoverTestCaseWithMdb.testShutdownWithFailback.zip
>
>
> There is regression in scenario with failover of Artemis RA from live to backup (shared store, dedicated topology). After backup activates after failover, connections of RA does not failover to backup (or are disconnected from backup just after failover)
> Test scenario:
> * There are three servers. Live server (Node 1) and backupserver (Node 2) are in dedicated HA topology.
> * InQueue and OutQueue are deployed on live and backup. Send messages to InQueue on live server.
> * When all messages are sent, deploy message driven bean on Node 3.
> * MDB sends messages form InQueue to OutQueue.
> * Shutdown live server. Wait for backup server to alive, then start live server again and stop backup.
> * Receive messages from OutQueue from live server.
> Results:
> After live server is stopped and backup activates, no messages are processed by MDB. Looking at trace logs it seems that MDB does reconnect to backup but it's then disconnected. Then I don't see connector to backup server between tried connectors during reconnection.
> Attaching reproduce and logs.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (WFWIP-65) [Artemis 2.x upgrade] Artemis RA connections disconnected after failover
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFWIP-65?page=com.atlassian.jira.plugin.s... ]
Miroslav Novak updated WFWIP-65:
--------------------------------
Attachment: DedicatedFailoverTestCaseWithMdb.testShutdownWithFailback.zip
> [Artemis 2.x upgrade] Artemis RA connections disconnected after failover
> -------------------------------------------------------------------------
>
> Key: WFWIP-65
> URL: https://issues.jboss.org/browse/WFWIP-65
> Project: WildFly WIP
> Issue Type: Bug
> Components: Artemis
> Reporter: Miroslav Novak
> Assignee: Martyn Taylor
> Priority: Blocker
> Attachments: DedicatedFailoverTestCaseWithMdb.testShutdownWithFailback.zip
>
>
> There is regression in scenario with failover of Artemis RA from live to backup (shared store, dedicated topology). After backup activates after failover, connections of RA does not failover to backup (or are disconnected from backup just after failover)
> Test scenario:
> * There are three servers. Live server (Node 1) and backupserver (Node 2) are in dedicated HA topology.
> * InQueue and OutQueue are deployed on live and backup. Send messages to InQueue on live server.
> * When all messages are sent, deploy message driven bean on Node 3.
> * MDB sends messages form InQueue to OutQueue.
> * Shutdown live server. Wait for backup server to alive, then start live server again and stop backup.
> * Receive messages from OutQueue from live server.
> Results:
> After live server is stopped and backup activates, no messages are processed by MDB. Looking at trace logs it seems that MDB does reconnect to backup but it's then disconnected. Then I don't see connector to backup server between tried connectors during reconnection.
> Attaching reproduce and logs.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (WFCORE-3962) Starting WFLY with JDK 11 blows up with ModuleNotFoundException java.se
by Rostislav Svoboda (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3962?page=com.atlassian.jira.plugi... ]
Rostislav Svoboda updated WFCORE-3962:
--------------------------------------
Priority: Blocker (was: Major)
This is Blocker as Java 11 is LTS release and we need to support this.
> Starting WFLY with JDK 11 blows up with ModuleNotFoundException java.se
> -----------------------------------------------------------------------
>
> Key: WFCORE-3962
> URL: https://issues.jboss.org/browse/WFCORE-3962
> Project: WildFly Core
> Issue Type: Bug
> Components: Modules
> Affects Versions: 6.0.0.Alpha3
> Reporter: Matej Novotny
> Assignee: David Lloyd
> Priority: Blocker
> Labels: Java11
>
> As per request, copying MODULES-372 to WFCORE as well.
> Starting WFLY with JDK 11 using {{standalone.sh}} yields:
> {code}
> org.jboss.modules.ModuleNotFoundException: java.se
> at org.jboss.modules.Module.addPaths(Module.java:1266)
> at org.jboss.modules.Module.link(Module.java:1622)
> at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650)
> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296)
> at org.jboss.modules.Main.main(Main.java:437)
> {code}
> Output of {{java -version}}:
> {code}
> openjdk version "11-ea" 2018-09-25
> OpenJDK Runtime Environment 18.9 (build 11-ea+21)
> OpenJDK 64-Bit Server VM 18.9 (build 11-ea+21, mixed mode)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (WFWIP-65) [Artemis 2.x upgrade] Artemis RA connections disconnected after failover
by Miroslav Novak (JIRA)
Miroslav Novak created WFWIP-65:
-----------------------------------
Summary: [Artemis 2.x upgrade] Artemis RA connections disconnected after failover
Key: WFWIP-65
URL: https://issues.jboss.org/browse/WFWIP-65
Project: WildFly WIP
Issue Type: Bug
Components: Artemis
Reporter: Miroslav Novak
Assignee: Martyn Taylor
Priority: Blocker
Attachments: DedicatedFailoverTestCaseWithMdb.testShutdownWithFailback.zip
There is regression in scenario with failover of Artemis RA from live to backup (shared store, dedicated topology). After backup activates after failover, connections of RA does not failover to backup (or are disconnected from backup just after failover)
Test scenario:
* There are three servers. Live server (Node 1) and backupserver (Node 2) are in dedicated HA topology.
* InQueue and OutQueue are deployed on live and backup. Send messages to InQueue on live server.
* When all messages are sent, deploy message driven bean on Node 3.
* MDB sends messages form InQueue to OutQueue.
* Shutdown live server. Wait for backup server to alive, then start live server again and stop backup.
* Receive messages from OutQueue from live server.
Results:
After live server is stopped and backup activates, no messages are processed by MDB. Looking at trace logs it seems that MDB does reconnect to backup but it's then disconnected. Then I don't see connector to backup server between tried connectors during reconnection.
Attaching reproduce and logs.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (WFLY-10557) JPA application deploy fails with "CDI BeanManager not (yet) ready to use"
by Bartosz Baranowski (JIRA)
[ https://issues.jboss.org/browse/WFLY-10557?page=com.atlassian.jira.plugin... ]
Bartosz Baranowski commented on WFLY-10557:
-------------------------------------------
Great, thanks for follow up.
> JPA application deploy fails with "CDI BeanManager not (yet) ready to use"
> --------------------------------------------------------------------------
>
> Key: WFLY-10557
> URL: https://issues.jboss.org/browse/WFLY-10557
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, JPA / Hibernate
> Affects Versions: 13.0.0.Final
> Environment: macOS High Sierra
> Java 8
> Wildfly 13
> Reporter: Cristhian Camilo Lopez
> Assignee: Bartosz Baranowski
> Priority: Minor
> Labels: cdi, jpa2, wildfly
> Attachments: ee8-jpa-converter-1.0-SNAPSHOT.war, ee8-jpa-converter-1.0-SNAPSHOT.war, persistence-xml.png
>
>
> Deployment of app using JPA converters for enums fails with the following message
> {code:java}
> 10:01:44,044 INFO [org.hibernate.hql.internal.QueryTranslatorFactoryInitiator] (ServerService Thread Pool -- 71) HHH000397: Using ASTQueryTranslatorFactory
> 10:01:44,047 ERROR [org.hibernate.internal.SessionFactoryImpl] (ServerService Thread Pool -- 71) HHH000177: Error in named query: findEnabledProducts: org.hibernate.QueryException: Could not format constant value to SQL literal: co.cristhian.bugs.product.entity.State.ENABLED [SELECT p FROM co.cristhian.bugs.product.entity.Product p WHERE p.state = co.cristhian.bugs.product.entity.State.ENABLED]
> at org.hibernate.QueryException.generateQueryException(QueryException.java:120)
> at org.hibernate.QueryException.wrapWithQueryString(QueryException.java:103)
> at org.hibernate.hql.internal.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:219)
> at org.hibernate.hql.internal.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:143)
> at org.hibernate.engine.query.spi.HQLQueryPlan.<init>(HQLQueryPlan.java:120)
> at org.hibernate.engine.query.spi.HQLQueryPlan.<init>(HQLQueryPlan.java:81)
> at org.hibernate.engine.query.spi.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:153)
> at org.hibernate.query.spi.NamedQueryRepository.checkNamedQueries(NamedQueryRepository.java:157)
> at org.hibernate.internal.SessionFactoryImpl.checkNamedQueries(SessionFactoryImpl.java:574)
> at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:321)
> at org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:467)
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:939)
> at org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:167)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:125)
> at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:650)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:209)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> Caused by: org.hibernate.QueryException: Could not format constant value to SQL literal: co.cristhian.bugs.product.entity.State.ENABLED
> at org.hibernate.hql.internal.ast.tree.JavaConstantNode.getRenderText(JavaConstantNode.java:111)
> at org.hibernate.hql.internal.ast.SqlGenerator.out(SqlGenerator.java:116)
> at org.hibernate.hql.internal.antlr.SqlGeneratorBase.simpleExpr(SqlGeneratorBase.java:3030)
> at org.hibernate.hql.internal.antlr.SqlGeneratorBase.expr(SqlGeneratorBase.java:1633)
> at org.hibernate.hql.internal.antlr.SqlGeneratorBase.binaryComparisonExpression(SqlGeneratorBase.java:3325)
> at org.hibernate.hql.internal.antlr.SqlGeneratorBase.comparisonExpr(SqlGeneratorBase.java:1442)
> at org.hibernate.hql.internal.antlr.SqlGeneratorBase.booleanExpr(SqlGeneratorBase.java:934)
> at org.hibernate.hql.internal.antlr.SqlGeneratorBase.whereExpr(SqlGeneratorBase.java:780)
> at org.hibernate.hql.internal.antlr.SqlGeneratorBase.selectStatement(SqlGeneratorBase.java:213)
> at org.hibernate.hql.internal.antlr.SqlGeneratorBase.statement(SqlGeneratorBase.java:146)
> at org.hibernate.hql.internal.ast.QueryTranslatorImpl.generate(QueryTranslatorImpl.java:250)
> at org.hibernate.hql.internal.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:211)
> ... 20 more
> Caused by: java.lang.IllegalStateException: org.hibernate.resource.beans.container.internal.NotYetReadyException: CDI BeanManager not (yet) ready to use
> at org.hibernate.resource.beans.container.internal.JpaCompliantLifecycleStrategy$BeanImpl.initialize(JpaCompliantLifecycleStrategy.java:112)
> at org.hibernate.resource.beans.container.internal.CdiBeanContainerExtendedAccessImpl$BeanImpl.initialize(CdiBeanContainerExtendedAccessImpl.java:113)
> at org.hibernate.resource.beans.container.internal.CdiBeanContainerExtendedAccessImpl$BeanImpl.getBeanInstance(CdiBeanContainerExtendedAccessImpl.java:119)
> at org.hibernate.resource.beans.internal.ManagedBeanRegistryImpl$ContainedBeanManagedBeanAdapter.getBeanInstance(ManagedBeanRegistryImpl.java:139)
> at org.hibernate.metamodel.model.convert.internal.JpaAttributeConverterImpl.toRelationalValue(JpaAttributeConverterImpl.java:50)
> at org.hibernate.hql.internal.ast.tree.JavaConstantNode.getRenderText(JavaConstantNode.java:89)
> ... 31 more
> Caused by: org.hibernate.resource.beans.container.internal.NotYetReadyException: CDI BeanManager not (yet) ready to use
> ... 37 more
> Caused by: java.lang.NullPointerException
> at org.hibernate.resource.beans.container.internal.JpaCompliantLifecycleStrategy$BeanImpl.initialize(JpaCompliantLifecycleStrategy.java:109)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months