[JBoss JIRA] (WFLY-10797) Quickstarts JBDS WSDLAnalyzer warning
by Sultan Zhantemirov (JIRA)
[ https://issues.jboss.org/browse/WFLY-10797?page=com.atlassian.jira.plugin... ]
Sultan Zhantemirov updated WFLY-10797:
--------------------------------------
Description:
The following quickstarts:
* jaxws-addressing
* jaxws-retail
* wsat-simple
have the following warning
{noformat}
WS-I: A problem occured while running the WS-I WSDL conformance check: org.eclipse.wst.wsi.internal.analyzer.WSIAnalyzerException: The WS-I Test Assertion Document (TAD)document was either not found or could not be processed.The WSDLAnalyzer was unable to validate the given WSDL File.
AddressingService.wsdl /jaxws-addressing-service/src/main/webapp/WEB-INF/wsdl line 1 WSDL Problem
RestaurantServiceAT.wsdl /wsat-simple/src/main/webapp/WEB-INF/classes/org/jboss/as/quickstarts/wsat/simple/jaxws line 1 WSDL Problem
ProfileMgmtService.wsdl /jaxws-retail-service/src/main/webapp/WEB-INF/wsdl line 1 WSDL Problem
{noformat}
This warning is not at [Known Issues|https://github.com/jboss-developer/jboss-developer-shared-resource...] section.
was:
The following quickstarts:
* jaxws-addressing
* jaxws-retail
* wsat-simple
have the following warning
{{WS-I: A problem occured while running the WS-I WSDL conformance check: org.eclipse.wst.wsi.internal.analyzer.WSIAnalyzerException: The WS-I Test Assertion Document (TAD)document was either not found or could not be processed.The WSDLAnalyzer was unable to validate the given WSDL File.}}
{{AddressingService.wsdl /jaxws-addressing-service/src/main/webapp/WEB-INF/wsdl line 1 WSDL Problem}}
{{RestaurantServiceAT.wsdl /wsat-simple/src/main/webapp/WEB-INF/classes/org/jboss/as/quickstarts/wsat/simple/jaxws line 1 WSDL Problem}}
{{ProfileMgmtService.wsdl /jaxws-retail-service/src/main/webapp/WEB-INF/wsdl line 1 WSDL Problem}}
This warning is not at [Known Issues|https://github.com/jboss-developer/jboss-developer-shared-resource...] section.
> Quickstarts JBDS WSDLAnalyzer warning
> -------------------------------------
>
> Key: WFLY-10797
> URL: https://issues.jboss.org/browse/WFLY-10797
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Environment: Fedora 27, Red Hat Developer Studio 12.0, jdk 1.8.0_162, 7.2.0.Beta.CR1 EAP/Maven/QS
> Reporter: Sultan Zhantemirov
> Assignee: Eduardo Martins
>
> The following quickstarts:
> * jaxws-addressing
> * jaxws-retail
> * wsat-simple
> have the following warning
> {noformat}
> WS-I: A problem occured while running the WS-I WSDL conformance check: org.eclipse.wst.wsi.internal.analyzer.WSIAnalyzerException: The WS-I Test Assertion Document (TAD)document was either not found or could not be processed.The WSDLAnalyzer was unable to validate the given WSDL File.
> AddressingService.wsdl /jaxws-addressing-service/src/main/webapp/WEB-INF/wsdl line 1 WSDL Problem
> RestaurantServiceAT.wsdl /wsat-simple/src/main/webapp/WEB-INF/classes/org/jboss/as/quickstarts/wsat/simple/jaxws line 1 WSDL Problem
> ProfileMgmtService.wsdl /jaxws-retail-service/src/main/webapp/WEB-INF/wsdl line 1 WSDL Problem
> {noformat}
> This warning is not at [Known Issues|https://github.com/jboss-developer/jboss-developer-shared-resource...] section.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10797) Quickstarts JBDS WSDLAnalyzer warning
by Sultan Zhantemirov (JIRA)
[ https://issues.jboss.org/browse/WFLY-10797?page=com.atlassian.jira.plugin... ]
Sultan Zhantemirov updated WFLY-10797:
--------------------------------------
Description:
The following quickstarts:
* jaxws-addressing
* jaxws-retail
* wsat-simple
have the following warning
{{WS-I: A problem occured while running the WS-I WSDL conformance check: org.eclipse.wst.wsi.internal.analyzer.WSIAnalyzerException: The WS-I Test Assertion Document (TAD)document was either not found or could not be processed.The WSDLAnalyzer was unable to validate the given WSDL File.}}
{{AddressingService.wsdl /jaxws-addressing-service/src/main/webapp/WEB-INF/wsdl line 1 WSDL Problem}}
{{RestaurantServiceAT.wsdl /wsat-simple/src/main/webapp/WEB-INF/classes/org/jboss/as/quickstarts/wsat/simple/jaxws line 1 WSDL Problem}}
{{ProfileMgmtService.wsdl /jaxws-retail-service/src/main/webapp/WEB-INF/wsdl line 1 WSDL Problem}}
This warning is not at [Known Issues|https://github.com/jboss-developer/jboss-developer-shared-resource...] section.
was:
The following quickstarts:
* jaxws-addressing
* jaxws-retail
* wsat-simple
have the following warning
{{WS-I: A problem occured while running the WS-I WSDL conformance check: org.eclipse.wst.wsi.internal.analyzer.WSIAnalyzerException: The WS-I Test Assertion Document (TAD)document was either not found or could not be processed.The WSDLAnalyzer was unable to validate the given WSDL File.
AddressingService.wsdl /jaxws-addressing-service/src/main/webapp/WEB-INF/wsdl line 1 WSDL Problem
RestaurantServiceAT.wsdl /wsat-simple/src/main/webapp/WEB-INF/classes/org/jboss/as/quickstarts/wsat/simple/jaxws line 1 WSDL Problem
ProfileMgmtService.wsdl /jaxws-retail-service/src/main/webapp/WEB-INF/wsdl line 1 WSDL Problem}}
This warning is not at [Known Issues|https://github.com/jboss-developer/jboss-developer-shared-resource...] section.
> Quickstarts JBDS WSDLAnalyzer warning
> -------------------------------------
>
> Key: WFLY-10797
> URL: https://issues.jboss.org/browse/WFLY-10797
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Environment: Fedora 27, Red Hat Developer Studio 12.0, jdk 1.8.0_162, 7.2.0.Beta.CR1 EAP/Maven/QS
> Reporter: Sultan Zhantemirov
> Assignee: Eduardo Martins
>
> The following quickstarts:
> * jaxws-addressing
> * jaxws-retail
> * wsat-simple
> have the following warning
> {{WS-I: A problem occured while running the WS-I WSDL conformance check: org.eclipse.wst.wsi.internal.analyzer.WSIAnalyzerException: The WS-I Test Assertion Document (TAD)document was either not found or could not be processed.The WSDLAnalyzer was unable to validate the given WSDL File.}}
> {{AddressingService.wsdl /jaxws-addressing-service/src/main/webapp/WEB-INF/wsdl line 1 WSDL Problem}}
> {{RestaurantServiceAT.wsdl /wsat-simple/src/main/webapp/WEB-INF/classes/org/jboss/as/quickstarts/wsat/simple/jaxws line 1 WSDL Problem}}
> {{ProfileMgmtService.wsdl /jaxws-retail-service/src/main/webapp/WEB-INF/wsdl line 1 WSDL Problem}}
> This warning is not at [Known Issues|https://github.com/jboss-developer/jboss-developer-shared-resource...] section.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10797) Quickstarts JBDS WSDLAnalyzer warning
by Sultan Zhantemirov (JIRA)
Sultan Zhantemirov created WFLY-10797:
-----------------------------------------
Summary: Quickstarts JBDS WSDLAnalyzer warning
Key: WFLY-10797
URL: https://issues.jboss.org/browse/WFLY-10797
Project: WildFly
Issue Type: Bug
Components: Quickstarts
Environment: Fedora 27, Red Hat Developer Studio 12.0, jdk 1.8.0_162, 7.2.0.Beta.CR1 EAP/Maven/QS
Reporter: Sultan Zhantemirov
Assignee: Eduardo Martins
The following quickstarts:
* jaxws-addressing
* jaxws-retail
* wsat-simple
have the following warning
{{WS-I: A problem occured while running the WS-I WSDL conformance check: org.eclipse.wst.wsi.internal.analyzer.WSIAnalyzerException: The WS-I Test Assertion Document (TAD)document was either not found or could not be processed.The WSDLAnalyzer was unable to validate the given WSDL File.
AddressingService.wsdl /jaxws-addressing-service/src/main/webapp/WEB-INF/wsdl line 1 WSDL Problem
RestaurantServiceAT.wsdl /wsat-simple/src/main/webapp/WEB-INF/classes/org/jboss/as/quickstarts/wsat/simple/jaxws line 1 WSDL Problem
ProfileMgmtService.wsdl /jaxws-retail-service/src/main/webapp/WEB-INF/wsdl line 1 WSDL Problem}}
This warning is not at [Known Issues|https://github.com/jboss-developer/jboss-developer-shared-resource...] section.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10784) WeldStartCompletionService failed when optional components not installed
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/WFLY-10784?page=com.atlassian.jira.plugin... ]
Matej Novotny commented on WFLY-10784:
--------------------------------------
We need a reproducer before we go into fixing anything.
And currently I am struggling to see the scenario in which this will happen. Do you have an example of application with optional WebComponent?
> WeldStartCompletionService failed when optional components not installed
> ------------------------------------------------------------------------
>
> Key: WFLY-10784
> URL: https://issues.jboss.org/browse/WFLY-10784
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 12.0.0.Final, 13.0.0.Final
> Reporter: Alexander Kudrevatykh
> Assignee: Matej Novotny
>
> WebComponents are optional and fail in initialising it not causes fail of deployment, but when starting EAR application with included WAR fail in deployment since Wildfly 12 because WeldStartCompletionService depends on all components regardless of their type
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFWIP-16) [Artemis 2.x upgrade] libAIO does not get loaded on RHEL 6 x86_64
by Petr Sakař (JIRA)
[ https://issues.jboss.org/browse/WFWIP-16?page=com.atlassian.jira.plugin.s... ]
Petr Sakař commented on WFWIP-16:
---------------------------------
[~martyn-taylor]
My comment is that which team does the build of maven project that team does the build of natives if they are required to be included by the given maven project (as it was for artemis 1.x)
Whether of not RHEL6 support is a requirement for Wildfly I can not answer - probably question for [~kabirkhan] or [~jason.greene] ?
> [Artemis 2.x upgrade] libAIO does not get loaded on RHEL 6 x86_64
> -----------------------------------------------------------------
>
> Key: WFWIP-16
> URL: https://issues.jboss.org/browse/WFWIP-16
> Project: WildFly WIP
> Issue Type: Bug
> Components: JMS
> Reporter: Miroslav Novak
> Assignee: Martyn Taylor
> Priority: Blocker
> Labels: activemq, feature-branch-blocker
>
> LibAIO does not get loaded on RHEL 6 x86_64:
> {code}
> [hudson@rhel6-large-2723 bin]$ sh standalone.sh -c standalone-full-ha.xml -Djboss.socket.binding.port-offset=1000
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /tmp/jboss-eap
> JAVA: java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> ...
> 10:14:31,918 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0075: AIO wasn't located on this platform, it will fall back to using pure Java NIO. Your platform is Linux, install LibAIO to enable the AIO journal and achieve optimal performance.
> 10:14:32,017 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=true,journalDirectory=/tmp/jboss-eap/standalone/data/activemq/journal,bindingsDirectory=/tmp/jboss-eap/standalone/data/activemq/bindings,largeMessagesDirectory=/tmp/jboss-eap/standalone/data/activemq/largemessages,pagingDirectory=/tmp/jboss-eap/standalone/data/activemq/paging)
> 10:14:32,110 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221013: Using NIO Journal
> ...
> {code}
> libAIO in artemis journal module from WF branch. Not from Artemis 2.5.0.Final tag.
> Wildfly: https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (06c878a313d3cad323889d017e60fd5533204d1a)
> Artemis: upstreadm master (577b62d5210cdcc0f86ab9bb1b24e944c877dfe7)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFCORE-3962) Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se
by Erich Duda (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3962?page=com.atlassian.jira.plugi... ]
Erich Duda commented on WFCORE-3962:
------------------------------------
Adding one more use case. Users may configure Wildfly using CLI wrapper and embed-server. Execution of such application will require the {{--add-modules=java.se}} option as well.
{code:java}
CLI cli = CLI.newInstance();
cli.cmd("embed-server --jboss-home=/tmp/wf14");
{code}
> Starting WFLY scripts 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: Management, Modules, Scripts
> Affects Versions: 6.0.0.Alpha3
> Reporter: Matej Novotny
> Assignee: Richard Opalka
> Priority: Blocker
> Labels: Java11, blocker-WF14
>
> 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, 11 months
[JBoss JIRA] (WFCORE-3993) Elytron module compilation failure due to "package sun.security.ec does not exist" on IBM jdk
by Petr Kremensky (JIRA)
Petr Kremensky created WFCORE-3993:
--------------------------------------
Summary: Elytron module compilation failure due to "package sun.security.ec does not exist" on IBM jdk
Key: WFCORE-3993
URL: https://issues.jboss.org/browse/WFCORE-3993
Project: WildFly Core
Issue Type: Bug
Components: Security
Environment: {noformat}
$ java -version
java version "1.8.0_171"
Java(TM) SE Runtime Environment (build 8.0.5.17 - pxa6480sr5fp17-20180627_01(SR5 FP17))
IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64-Bit Compressed References 20180626_390413 (JIT enabled, AOT enabled)
OpenJ9 - 5cdc604
OMR - a24bc01
IBM - 21870d6)
JCL - 20180619_01 based on Oracle jdk8u171-b11
$ git rev-parse --short HEAD
cb10de0cba
{noformat}
Reporter: Petr Kremensky
Assignee: Farah Juma
Compilation of Elytron module of wildfly-core on IBM jdk fails.
*reproduce*
{noformat}
mvn install -pl elytron
...
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.7.0:testCompile (default-testCompile) on project wildfly-elytron-integration: Compilation failure
[ERROR] /home/pkremens/devel/wildfly-core/elytron/src/test/java/org/wildfly/extension/elytron/KeyStoresTestCase.java:[87,23] package sun.security.ec does not exist
{noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2827) [DMN Designer] SVG produced for each save operation
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2827?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2827:
--------------------------------
Steps to Reproduce:
# Create new DMN diagram
# Check project explorer panel, just one dmn file will be present
# Do some changes to diagram and save
# Check project explorer panel, just one dmn file and one svg will be present
# Do some changes to diagram again and save
# Check project explorer panel, just one dmn file and two svg will be present
## Still just one svg should be present
was:
# Create two diagrams without explicit saving
# Check project explorer panel, just dmn files will be present
# Do some changes in both diagrams and clcik on Save button in both diagrams
# In project explorer will appear svg files, see the attachment
> [DMN Designer] SVG produced for each save operation
> ---------------------------------------------------
>
> Key: DROOLS-2827
> URL: https://issues.jboss.org/browse/DROOLS-2827
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Labels: drools-tools
> Attachments: Screenshot from 2018-08-02 10-56-15.png
>
>
> When user saves the diagram, the svg file appears in the workbench.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months