[JBoss JIRA] (DROOLS-3731) DMN UX - More info overlaid on models.
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3731?page=com.atlassian.jira.plugi... ]
Michael Anstis edited comment on DROOLS-3731 at 3/15/19 3:54 PM:
-----------------------------------------------------------------
[~uxdlc] IMO some (yes, yes, I changed my mind) of this JIRA is not covered by DROOLS-3674 :-)
DROOLS-3674 covers popovers to show the results of running tests. This JIRA could also include what to show as an overlay when the DMN is, for example, invalid (e.g. a duff expression). See DROOLS-3657.
That said; it's probably sufficient to consider this JIRA complete and covered by DROOLS-3674.
was (Author: manstis):
[~uxdlc] IMO *all* of this JIRA is not covered by DROOLS-3674 :-)
DROOLS-3674 covers popovers to show the results of running tests.
This JIRA could also include what to show as an overlay when the DMN is, for example, invalid (e.g. a duff expression). See DROOLS-3657.
That said; it's probably sufficient to consider this JIRA complete and covered by DROOLS-3674.
> DMN UX - More info overlaid on models.
> --------------------------------------
>
> Key: DROOLS-3731
> URL: https://issues.jboss.org/browse/DROOLS-3731
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: download (1).png, download.png
>
>
> As a practitioner, there are situations where I need to show additional information about a model... for instance: test coverage report: I need to draw a model and color code the nodes to show which nodes were executed by tests, or which rows on a DT were a match. Or when I execute a single test, what was the actual value of a given node or expression.
> Note: Maybe in read-only mode with an "overlay" on top of the model the additional metadata information. See process instance diagram design examples.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (DROOLS-3731) DMN UX - More info overlaid on models.
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3731?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-3731:
----------------------------------------
[~uxdlc] IMO *all* of this JIRA is not covered by DROOLS-3674 :-)
DROOLS-3674 covers popovers to show the results of running tests.
This JIRA could also include what to show as an overlay when the DMN is, for example, invalid (e.g. a duff expression). See DROOLS-3657.
That said; it's probably sufficient to consider this JIRA complete and covered by DROOLS-3674.
> DMN UX - More info overlaid on models.
> --------------------------------------
>
> Key: DROOLS-3731
> URL: https://issues.jboss.org/browse/DROOLS-3731
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: download (1).png, download.png
>
>
> As a practitioner, there are situations where I need to show additional information about a model... for instance: test coverage report: I need to draw a model and color code the nodes to show which nodes were executed by tests, or which rows on a DT were a match. Or when I execute a single test, what was the actual value of a given node or expression.
> Note: Maybe in read-only mode with an "overlay" on top of the model the additional metadata information. See process instance diagram design examples.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (WFLY-11856) WildFlyInitialContext is not working and throw a NoInitialContextException for a lookup
by Tomasz Adamski (Jira)
Tomasz Adamski created WFLY-11856:
-------------------------------------
Summary: WildFlyInitialContext is not working and throw a NoInitialContextException for a lookup
Key: WFLY-11856
URL: https://issues.jboss.org/browse/WFLY-11856
Project: WildFly
Issue Type: Bug
Components: EJB
Reporter: Tomasz Adamski
Assignee: Tomasz Adamski
Fix For: 17.0.0.Beta1
As per documentation (https://github.com/wildfly/wildfly-naming-client#usage)
the standard discovery can be bypassed with
InitialContext ctx = new WildFlyInitialContext();
Blah blah = (Blah) ctx.lookup("foo:blah");
But this aproach will fail with the following Exception:
Exception in thread "main" javax.naming.NoInitialContextException
at org.wildfly.naming.client.WildFlyInitialContext.getDefaultInitCtx(WildFlyInitialContext.java:65)
at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:350)
at javax.naming.InitialContext.lookup(InitialContext.java:417)
at org.jboss.wfink.eap71.playground.client.SimpleWildFlyInitialContextClient.main(SimpleWildFlyInitialContextClient.java:41)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (WFLY-10279) [JDK9] Xalan - Provider class org.apache.bsf.BSFManager not in module
by Scott Marlow (Jira)
[ https://issues.jboss.org/browse/WFLY-10279?page=com.atlassian.jira.plugin... ]
Scott Marlow commented on WFLY-10279:
-------------------------------------
[~rsvoboda] what are the possible ways to solve this issue? Perhaps a documentation change that mentions that Xalan is not a JDK module?
CC [~bstansberry2]
> [JDK9] Xalan - Provider class org.apache.bsf.BSFManager not in module
> ---------------------------------------------------------------------
>
> Key: WFLY-10279
> URL: https://issues.jboss.org/browse/WFLY-10279
> Project: WildFly
> Issue Type: Bug
> Components: XML Frameworks
> Affects Versions: 12.0.0.Final
> Reporter: Rostislav Svoboda
> Assignee: Scott Marlow
> Priority: Major
>
> jar -d --file dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT//modules/system/layers/base/org/apache/xalan/main/xalan-2.7.1.jbossorg-4.jar
> Unable to derive module descriptor for: dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/apache/xalan/main/xalan-2.7.1.jbossorg-4.jar
> Provider class org.apache.bsf.BSFManager not in module
> CCing [~ropalka] [~dlloyd]
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (WFLY-11793) JPA EntityManager merge infinite loop - java.lang.StackOverflowError
by Scott Marlow (Jira)
[ https://issues.jboss.org/browse/WFLY-11793?page=com.atlassian.jira.plugin... ]
Scott Marlow commented on WFLY-11793:
-------------------------------------
[~brunomaioli] Please add a comment here with the link to the HHH jira issue or community HHH user forum link, in case others have the same issue and are curious as to the solution.
Thanks,
Scott
> JPA EntityManager merge infinite loop - java.lang.StackOverflowError
> --------------------------------------------------------------------
>
> Key: WFLY-11793
> URL: https://issues.jboss.org/browse/WFLY-11793
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 15.0.1.Final
> Environment: MAC OS Mojave
> Java 11
> Wildfly 15.0.1-Final
> Data Base Postgresql
> Reporter: Bruno Maioli Martins
> Assignee: Scott Marlow
> Priority: Critical
> Attachments: jstack.txt, server+querys.log, server-1.log, teste.zip
>
>
> Dear,
> When executing the update of a record invoking getEntityManager().merge(obj) the application goes into infinite loop. This behavior only occurs when there is a OneToMany bidirectional mapping of the entity Papel -> PermissaoAtribuida.
> If the same code runs outside of the Wildfly server context its execution occurs normally.
> Apparently the call getEntityManager.().merge(obj) attempts infinite selects to sync the object with transaction context before doing the merge.
> Attach the source code of my test classes.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (WFLY-11832) Transaction for Hibernate Interceptor is null
by Scott Marlow (Jira)
[ https://issues.jboss.org/browse/WFLY-11832?page=com.atlassian.jira.plugin... ]
Scott Marlow commented on WFLY-11832:
-------------------------------------
I'm not sure if afterCompletion should have a transaction passed in or not, with Hibernate ORM 5.3 but it does seem like a bug in Hibernate ORM 5.3.* to me as well.
[~mchur]Could you please report this via a Hibernate HHH jira as well, be sure to link back to this issue, from the HHH issue. Please follow [https://hibernate.atlassian.net/browse/HHH] to report this to the Hibernate ORM team. After you create the HHH issue, please also update this issue, to include the HHH jira link. Thanks for reporting this!
[~gbadner] FYI, the following is the NPE that I get with WildFly, after deploying the attached hibernate-interceptor-reproducer-0.0.1-SNAPSHOT.jar (using JDK11).
{code}
13:38:55,144 ERROR [org.hibernate.internal.SessionImpl] (EJB default - 1) HHH000087: Exception in interceptor afterTransactionCompletion(): java.lang.NullPointerException
at deployment.hibernate-interceptor-reproducer-0.0.1-SNAPSHOT.jar//de.mc.ReproducerInterceptor.afterTransactionCompletion(ReproducerInterceptor.java:15)
at org.hibernate@5.3.9.Final//org.hibernate.internal.SessionImpl.afterTransactionCompletion(SessionImpl.java:2509)
at org.hibernate@5.3.9.Final//org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.afterTransactionCompletion(JdbcCoordinatorImpl.java:479)
at org.hibernate@5.3.9.Final//org.hibernate.resource.transaction.backend.jta.internal.JtaTransactionCoordinatorImpl.afterCompletion(JtaTransactionCoordinatorImpl.java:381)
at org.hibernate@5.3.9.Final//org.hibernate.resource.transaction.backend.jta.internal.synchronization.SynchronizationCallbackCoordinatorNonTrackingImpl.doAfterCompletion(SynchronizationCallbackCoordinatorNonTrackingImpl.java:60)
at org.hibernate@5.3.9.Final//org.hibernate.resource.transaction.backend.jta.internal.synchronization.SynchronizationCallbackCoordinatorTrackingImpl.afterCompletion(SynchronizationCallbackCoordinatorTrackingImpl.java:72)
at org.hibernate@5.3.9.Final//org.hibernate.resource.transaction.backend.jta.internal.synchronization.RegisteredSynchronization.afterCompletion(RegisteredSynchronization.java:44)
at org.jboss.as.transactions@17.0.0.Beta1-SNAPSHOT//org.jboss.as.txn.service.internal.tsr.JCAOrderedLastSynchronizationList.afterCompletion(JCAOrderedLastSynchronizationList.java:144)
at org.wildfly.transaction.client@1.1.3.Final//org.wildfly.transaction.client.AbstractTransaction.performConsumer(AbstractTransaction.java:223)
at org.wildfly.transaction.client@1.1.3.Final//org.wildfly.transaction.client.AbstractTransaction$AssociatingSynchronization.afterCompletion(AbstractTransaction.java:306)
at org.jboss.jts//com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.afterCompletion(SynchronizationImple.java:96)
at org.jboss.jts//com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:545)
at org.jboss.jts//com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:101)
at org.jboss.jts//com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162)
at org.jboss.jts//com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1288)
at org.jboss.jts//com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126)
at org.jboss.jts.integration//com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:89)
at org.wildfly.transaction.client@1.1.3.Final//org.wildfly.transaction.client.LocalTransaction.commitAndDissociate(LocalTransaction.java:75)
at org.wildfly.transaction.client@1.1.3.Final//org.wildfly.transaction.client.ContextTransactionManager.commit(ContextTransactionManager.java:71)
at org.jboss.as.ejb3@17.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:88)
at org.jboss.as.ejb3@17.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:261)
at org.jboss.as.ejb3@17.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:362)
at org.jboss.as.ejb3@17.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:144)
at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509)
at org.jboss.weld.core@3.1.0.Final//org.jboss.weld.module.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:81)
at org.jboss.as.weld.common@17.0.0.Beta1-SNAPSHOT//org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89)
at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.as.ejb3@17.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.as.ejb3@17.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100)
at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509)
at org.jboss.as.ejb3@17.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.component.singleton.ContainerManagedConcurrencyInterceptor.processInvocation(ContainerManagedConcurrencyInterceptor.java:106)
at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.as.ejb3@17.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.as.ee@17.0.0.Beta1-SNAPSHOT//org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60)
at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:438)
at org.wildfly.security.elytron-private@1.8.0.Final//org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:618)
at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:57)
at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53)
at org.jboss.as.ejb3@17.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:99)
at org.jboss.as.ejb3@17.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.timerservice.CalendarTimerTask.invokeBeanMethod(CalendarTimerTask.java:64)
at org.jboss.as.ejb3@17.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.timerservice.CalendarTimerTask.callTimeout(CalendarTimerTask.java:53)
at org.jboss.as.ejb3@17.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.timerservice.TimerTask.run(TimerTask.java:181)
at org.jboss.as.ejb3@17.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.timerservice.TimerServiceImpl$Task$1.run(TimerServiceImpl.java:1302)
at org.wildfly.extension.request-controller@8.0.0.Final//org.wildfly.extension.requestcontroller.RequestController$QueuedTask$1.run(RequestController.java:494)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
at org.jboss.threads@2.3.3.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485)
{code}
> Transaction for Hibernate Interceptor is null
> ---------------------------------------------
>
> Key: WFLY-11832
> URL: https://issues.jboss.org/browse/WFLY-11832
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate, Transactions
> Affects Versions: 14.0.0.Final, 15.0.1.Final, 16.0.0.Final
> Reporter: Markus Chur
> Assignee: Scott Marlow
> Priority: Major
> Attachments: hibernate-interceptor-reproducer-0.0.1-SNAPSHOT.jar, src -WFLY-11832.zip
>
>
> With Wildfly 13 - javaee7 transactions in hibernate interceptors were never null.
> Since Wildfly 14 - javaee8 transactions in hibernate interceptors are always null.
> Attached sources and a jar of a minimal reproducer for Wildfly 16. This is reproducible by using a fresh unchanged Wildfly 16 and unchanged standalone.xml. Extract Wildfly 16, drop in the jar in the deployments folder and start the server.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months