[JBoss JIRA] (WFLY-11265) wildfly-feature-pack -- Dependency Error
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-11265?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFLY-11265:
-----------------------------------------
In case it helps, you don't need 1.1-b01-SNAPSHOT, you need 1.0.
The org.glassfish.soteria:parent:1.0 pom has this unfortunate business:
{code}
<properties>
...
<!--
<spec_build> and <spec_impl_version> are overridden
below for the "release" profile, and must be updated
in both places when the release or build number of
the dependency changes.
-->
<spec_build>01</spec_build>
<spec_impl_version>1.1-b01-SNAPSHOT</spec_impl_version>
<api_dependency_version>${spec_impl_version}</api_dependency_version>
...
</properties>
<profiles>
<profile>
<id>release</id>
<properties>
<spec_build>01</spec_build>
<spec_impl_version>1.0</spec_impl_version>
</properties>
</profile>
</profiles>
{code}
So when they build their stuff using the 'release' profile they depend on the non-snapshot but anyone whose tooling is following their dependency tree but not declaring a 'release' profile is going to see a SNAPSHOT version. And of course people are quite likely not going to specify a 'release' profile if they are not doing a release of their own stuff.
The org.wildfly:wildfly-parent:14.0.1.Final pom has a dependency-management section where we control this version, and we specify 1.0. I suspect you'll need to do the same.
> wildfly-feature-pack -- Dependency Error
> ----------------------------------------
>
> Key: WFLY-11265
> URL: https://issues.jboss.org/browse/WFLY-11265
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 14.0.0.Final
> Environment: Ubuntu 18.10
> JDK 11
> WildFly 14.0.1.Final
> Reporter: Dennis Gesker
> Assignee: Jason Greene
> Priority: Major
> Labels: wildfly-feature-pack
> Fix For: 14.0.0.Final
>
>
> In my gradle build I've added:
> * providedCompile "org.wildfly:wildfly-feature-pack:14.0.1.Final"*
>
> But, I'm getting:
>
> *> Could not resolve javax.security.enterprise:javax.security.enterprise-api:1.1-b01-SNAPSHOT.
> Required by:
> project : > org.wildfly:wildfly-feature-pack:14.0.1.Final > org.glassfish.soteria:javax.security.enterprise:1.0*
> > Could not resolve javax.security.enterprise:javax.security.enterprise-api:1.1-b01-SNAPSHOT.
> > Unable to load Maven meta-data from https://repository.jboss.org/nexus/content/groups/public-jboss/javax/secu....
> > Could not get resource 'https://repository.jboss.org/nexus/content/groups/public-jboss/javax/secu...'.
> > Could not GET 'https://repository.jboss.org/nexus/content/groups/public-jboss/javax/secu...'.
> > extension (10) should not be presented in server_hello
>
> Presently I have the following repositories in my build:
>
> jcenter()
> mavenCentral()
>
> maven {
> name "Gradle Repository"
> url "https://plugins.gradle.org/m2/"
> }
> maven {
> name "JBoss Public Maven Repository Group"
> url "https://repository.jboss.org/nexus/content/groups/public-jboss/"
> }
> maven {
> name "JBoss Public Maven Repository Group"
> url "http://repository.jboss.org/nexus/content/groups/public/"
> }
>
>
> But, I suspect I am missing a repository specific to WildFly. Or, maybe there is a bad entry in the POM?
>
> Thanks,
> Dennis
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11275) JSF ViewMap Regression
by Cody Lerum (Jira)
Cody Lerum created WFLY-11275:
---------------------------------
Summary: JSF ViewMap Regression
Key: WFLY-11275
URL: https://issues.jboss.org/browse/WFLY-11275
Project: WildFly
Issue Type: Bug
Components: JSF
Affects Versions: 14.0.1.Final
Environment: Java 8
Wildfly 14.0.1
Reporter: Cody Lerum
Assignee: Farah Juma
I'm been running into an occasional NPE in production with JSF after migrating from Wildfly 11 to Wildfly 14.0.1 and I believe I've tracked down a small demo project that duplicates the issue. I've set the project to JSF 2.2 so it will deploy on both WF 11 and WF 14.
The basic problem is that when two pages with the same view id are loaded in separate tabs. From there is one of the tabs is posted and the result navigates to a different view id all references to that view id are removed from the view map. If the post does not navigate to a different view id then all works normally.
My assumption is that when the post navigates away to a new view id any reference to any page with the same view id is removed from the view map. This did not occur in Wildfly 11.
Additional clue is that even though the viewmap reference is removed the view scoped beans referencing it are not destroyed.
Demo project at https://github.com/codylerum/demos/tree/ee7/jsf-npe
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3225) [DMN Designer] Decision table output data type is not stored
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3225?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-3225:
-----------------------------------
Story Points: 3
> [DMN Designer] Decision table output data type is not stored
> ------------------------------------------------------------
>
> Key: DROOLS-3225
> URL: https://issues.jboss.org/browse/DROOLS-3225
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Blocker
> Labels: drools-tools
> Fix For: 7.14.0.Final
>
> Attachments: Screenshot from 2018-11-01 10-59-08.png, Screenshot from 2018-11-01 15-31-19.png, job-interview.dmn
>
>
> Issue spotted during DROOLS-3214, however probably not related.
> If decision table output data type is changed, the change is not reflected in the xml.
> Please follow my steps:
> - Create new DMN diagram
> - Add a decision node
> - Set the decision node top level expression as a decision table
> - Double click on Output header cell
> - Select boolean lets say
> - Save the diagram
> Check the source, there will be still stored string output data type, like below:
> {code:xml}
> <dmn:decisionTable id="_DE6CDA18-99D1-4259-9F6D-825209DF7DE8" typeRef="string" hitPolicy="ANY" preferredOrientation="Rule-as-Row">
> <dmn:input id="_EB7B7C02-4131-468C-B1B1-023C39045B66">
> <dmn:inputExpression id="_C72A9C94-130C-4BA5-A529-49BAE217DDFF" typeRef="string">
> <dmn:text>input-1</dmn:text>
> </dmn:inputExpression>
> <dmn:inputValues id="_1EC58DD6-21EB-4822-A333-581363BC325B">
> <dmn:text></dmn:text>
> </dmn:inputValues>
> </dmn:input>
> <dmn:output id="_81248A6E-0239-404A-B891-C7C0BEE6B501" name="output-1" typeRef="string">
> <dmn:outputValues id="_26301186-9EB2-43E8-B6F8-458361E99B45">
> <dmn:text></dmn:text>
> </dmn:outputValues>
> <dmn:defaultOutputEntry id="_EAC89F66-3B9E-4781-B670-1282975F4F1E" typeRef="string">
> <dmn:text></dmn:text>
> </dmn:defaultOutputEntry>
> </dmn:output>
> <dmn:rule id="_EC0CEE6B-E4D5-4DE2-9EE5-86C955933B4E">
> <dmn:inputEntry id="_91AA6110-0A85-4C95-B0B3-D1B084CB0089">
> <dmn:text>"you are right"</dmn:text>
> </dmn:inputEntry>
> <dmn:outputEntry id="_6FACD1CE-8301-413E-8C77-F04AD71B3C78" typeRef="string">
> <dmn:text>true</dmn:text>
> </dmn:outputEntry>
> </dmn:rule>
> </dmn:decisionTable>
> </dmn:decision>
> {code}
> But the UI is like:
> !Screenshot from 2018-11-01 10-59-08.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3226) [DMN Designer] Function Header Cell in BKM
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3226?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-3226:
-----------------------------------
Story Points: 3
> [DMN Designer] Function Header Cell in BKM
> ------------------------------------------
>
> Key: DROOLS-3226
> URL: https://issues.jboss.org/browse/DROOLS-3226
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
> Fix For: 7.14.0.Final
>
> Attachments: Screenshot from 2018-11-01 13-25-03.png, Screenshot from 2018-11-01 13-25-21.png
>
>
> Function header cell can be selected, but user can't set its properties in PropertiesPanel if the Function is the top level Expression of the BKM node. See below comparision of Function as the top level Expression. Once in decision node, then in BKM node.
> h3. Decision node
> !Screenshot from 2018-11-01 13-25-03.png|thumbnail!
> h3. BKM node
> !Screenshot from 2018-11-01 13-25-21.png|thumbnail!
> h2. Manual Acceptance test
> - Select Expression Header cell of BKM node (/)
> - Change Properties via properties panel (/)
> - Try to clear BKM node definition, shouldn't be possible (/)
> - -Build and Deploy- decided not to check due to current issues on touched code
> - -Runtime- decided not to check due to current issues on touched code
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11259) Wildfly 11.0.0.Final org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-11259?page=com.atlassian.jira.plugin... ]
Brian Stansberry reassigned WFLY-11259:
---------------------------------------
Component/s: JPA / Hibernate
Assignee: Scott Marlow (was: Jason Greene)
If you can post the complete stack trace of the exception that may help.
> Wildfly 11.0.0.Final org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-11259
> URL: https://issues.jboss.org/browse/WFLY-11259
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 11.0.0.Final
> Reporter: Adam Bialas
> Assignee: Scott Marlow
> Priority: Major
>
> I have an ear file which I want to deploy to the Wildfly 11.0.0.Final. In this ear file in the lib folder I have dom4j-2.0.1.jar. One of the sub deployments (war) uses JPA (no dependencies to hibernate, just to javax.javaee-api as compile only). This sub deployment contains of course the persistence.xml file. I see in the logs that when the application server starts and loads this file the following exception is thrown:
> org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory
> and the application fails to deploy.
> I checked many posts and forums on the net and as far as I understand I must exclude the dom4j provided by the application server so the jar located in the lib folder of ear can be used.
> I created jboss-deployment-structure:
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss-deployment-structure>
> <deployment>
> <exclusions>
> <module name="org.dom4j"/>
> </exclusions>
> </deployment>
> </jboss-deployment-structure>
> Even though I get the same exception so I suppose both jars are loaded and cause problems.
> I checked how class loading works on Wildfly 11.0.0 in comparison to JBoss EAP 7.1. In both cases this class is first loaded from provided 1.6.1 jar. JBoss does not load the newer version. However, Wildfly does and here is the problem.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3203) [DMN Designer] Runtime issues [7.2.x]
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3203?page=com.atlassian.jira.plugi... ]
Michael Anstis resolved DROOLS-3203.
------------------------------------
Fix Version/s: 7.14.0.Final
Resolution: Done
> [DMN Designer] Runtime issues [7.2.x]
> -------------------------------------
>
> Key: DROOLS-3203
> URL: https://issues.jboss.org/browse/DROOLS-3203
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Blocker
> Fix For: 7.14.0.Final
>
>
> An umbrella for the issues we're encountering with _using_ DMN models authored with _our_ editor. A lot of issues are being reported as comments on PRs or as separate JIRA. In reality, in preparation for our MVP we need to be confident all such issues are captured, fixed and re-tested.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3203) [DMN Designer] Runtime issues [7.2.x]
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3203?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-3203:
-----------------------------------
Epic Name: [DMN Designer] Runtime issues [7.2.x] (was: [DMN Designer] Runtime issues)
> [DMN Designer] Runtime issues [7.2.x]
> -------------------------------------
>
> Key: DROOLS-3203
> URL: https://issues.jboss.org/browse/DROOLS-3203
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Blocker
>
> An umbrella for the issues we're encountering with _using_ DMN models authored with _our_ editor. A lot of issues are being reported as comments on PRs or as separate JIRA. In reality, in preparation for our MVP we need to be confident all such issues are captured, fixed and re-tested.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3203) [DMN Designer] Runtime issues [7.2.x]
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3203?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-3203:
-----------------------------------
Epic Name: [DMN Designer] Runtime issues [7.3.x] (was: [DMN Designer] Runtime issues [7.2.x])
> [DMN Designer] Runtime issues [7.2.x]
> -------------------------------------
>
> Key: DROOLS-3203
> URL: https://issues.jboss.org/browse/DROOLS-3203
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Blocker
>
> An umbrella for the issues we're encountering with _using_ DMN models authored with _our_ editor. A lot of issues are being reported as comments on PRs or as separate JIRA. In reality, in preparation for our MVP we need to be confident all such issues are captured, fixed and re-tested.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3203) [DMN Designer] Runtime issues [7.2.x]
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3203?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-3203:
-----------------------------------
Epic Name: [DMN Designer] Runtime issues [7.2.x] (was: [DMN Designer] Runtime issues [7.3.x])
> [DMN Designer] Runtime issues [7.2.x]
> -------------------------------------
>
> Key: DROOLS-3203
> URL: https://issues.jboss.org/browse/DROOLS-3203
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Blocker
>
> An umbrella for the issues we're encountering with _using_ DMN models authored with _our_ editor. A lot of issues are being reported as comments on PRs or as separate JIRA. In reality, in preparation for our MVP we need to be confident all such issues are captured, fixed and re-tested.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months