[JBoss JIRA] (WFLY-10060) wsconsume script is not working on JDK9+
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-10060?page=com.atlassian.jira.plugin... ]
David Lloyd commented on WFLY-10060:
------------------------------------
JBoss Modules does have a resource iteration API. For more information, see [the JavaDoc of the method|http://jboss-modules.github.io/jboss-modules/latest/index.html?org/jboss/modules/Module.html#iterateResources-org.jboss.modules.filter.PathFilter-].
> wsconsume script is not working on JDK9+
> ----------------------------------------
>
> Key: WFLY-10060
> URL: https://issues.jboss.org/browse/WFLY-10060
> Project: WildFly
> Issue Type: Bug
> Components: Scripts, Web Services
> Affects Versions: 12.0.0.Final
> Reporter: Jan Blizňák
> Assignee: R Searls
> Priority: Blocker
> Attachments: mywsdl2java
>
>
> wsconsume script is not working on JDK9/10/11
> {code:java}
> [jbliznak@rh wildfly-13.0.0.Alpha1-SNAPSHOT]$ java -version
> java version "9.0.4"
> Java(TM) SE Runtime Environment (build 9.0.4+11)
> Java HotSpot(TM) 64-Bit Server VM (build 9.0.4+11, mixed mode)
> [jbliznak@rh wildfly-13.0.0.Alpha1-SNAPSHOT]$ bin/wsconsume.sh https://raw.githubusercontent.com/jbossws/jbossws-cxf/master/modules/test...
> Could not find log4j.properties or log4j.xml configuration, logging to console.
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by com.sun.xml.bind.v2.runtime.reflect.opt.Injector (jar:file:/tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/com/sun/xml/bind/main/jaxb-runtime-2.3.0.jar!/) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int)
> WARNING: Please consider reporting this to the maintainers of com.sun.xml.bind.v2.runtime.reflect.opt.Injector
> WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Loading FrontEnd jaxws ...
> Loading DataBinding jaxb ...
> wsdl2java -compile -exsh false -d /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430 -verbose -classdir /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output -allowElementReferences https://raw.githubusercontent.com/jbossws/jbossws-cxf/master/modules/test...
> wsdl2java - Apache CXF 3.2.2
> /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430/org/openuri/_2004/_04/helloworld/TestService.java:6: error: package javax.xml.ws is not visible
> import javax.xml.ws.WebEndpoint;
> ^
> (package javax.xml.ws is declared in module java.xml.ws, which is not in the module graph)
> /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430/org/openuri/_2004/_04/helloworld/TestService.java:7: error: package javax.xml.ws is not visible
> import javax.xml.ws.WebServiceClient;
> ^
> (package javax.xml.ws is declared in module java.xml.ws, which is not in the module graph)
> /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430/org/openuri/_2004/_04/helloworld/TestService.java:8: error: package javax.xml.ws is not visible
> import javax.xml.ws.WebServiceFeature;
> ^
> (package javax.xml.ws is declared in module java.xml.ws, which is not in the module graph)
> /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430/org/openuri/_2004/_04/helloworld/TestService.java:9: error: package javax.xml.ws is not visible
> import javax.xml.ws.Service;
> ^
> (package javax.xml.ws is declared in module java.xml.ws, which is not in the module graph)
> /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430/org/openuri/_2004/_04/helloworld/EndpointInterface.java:3: error: package javax.jws is not visible
> import javax.jws.WebMethod;
> ^
> (package javax.jws is declared in module java.xml.ws, which is not in the module graph)
> /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430/org/openuri/_2004/_04/helloworld/EndpointInterface.java:4: error: package javax.jws is not visible
> import javax.jws.WebParam;
> ^
> (package javax.jws is declared in module java.xml.ws, which is not in the module graph)
> /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430/org/openuri/_2004/_04/helloworld/EndpointInterface.java:5: error: package javax.jws is not visible
> import javax.jws.WebResult;
> ^
> (package javax.jws is declared in module java.xml.ws, which is not in the module graph)
> /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430/org/openuri/_2004/_04/helloworld/EndpointInterface.java:6: error: package javax.jws is not visible
> import javax.jws.WebService;
> ^
> (package javax.jws is declared in module java.xml.ws, which is not in the module graph)
> /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430/org/openuri/_2004/_04/helloworld/EndpointInterface.java:7: error: package javax.jws.soap is not visible
> import javax.jws.soap.SOAPBinding;
> ^
> (package javax.jws.soap is declared in module java.xml.ws, which is not in the module graph)
> /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430/org/openuri/_2004/_04/helloworld/TestService.java:72: error: cannot find symbol
> return super.getPort(EndpointInterfacePort, EndpointInterface.class);
> ^
> symbol: variable super
> location: class org.openuri._2004._04.helloworld.TestService
> /tmp/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/output/tmp854430/org/openuri/_2004/_04/helloworld/TestService.java:84: error: cannot find symbol
> return super.getPort(EndpointInterfacePort, EndpointInterface.class, features);
> ^
> symbol: variable super
> location: class org.openuri._2004._04.helloworld.TestService
> JBWS024002: Failed to invoke org.apache.cxf.tools.wsdlto.WSDLToJava
> org.apache.cxf.tools.common.ToolException: Failed to compile generated code
> at org.apache.cxf.impl//org.apache.cxf.tools.common.ClassUtils.compile(ClassUtils.java:125)
> at org.apache.cxf.impl//org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.processWsdl(WSDLToJavaContainer.java:303)
> at org.apache.cxf.impl//org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:164)
> at org.apache.cxf.impl//org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:412)
> at org.apache.cxf.impl//org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:105)
> at org.apache.cxf.impl//org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:113)
> at org.jboss.ws.jaxws-client//org.jboss.wsf.stack.cxf.tools.CXFConsumerImpl.consume(CXFConsumerImpl.java:313)
> at org.jboss.ws.tools.common//org.jboss.ws.tools.cmd.WSConsume.importServices(WSConsume.java:298)
> at org.jboss.ws.tools.common//org.jboss.ws.tools.cmd.WSConsume.mainInternal(WSConsume.java:108)
> at org.jboss.ws.tools.common//org.jboss.ws.tools.cmd.WSConsume.main(WSConsume.java:96)
> at org.jboss.modules.Module.runMainMethod(Module.java:348)
> at org.jboss.modules.Module.run(Module.java:328)
> at org.jboss.modules.Main.main(Main.java:557)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFCORE-3728) DefaultJMSConnectionFactory not found after switching to elytron and removing picketbox subsystem
by Ilia Vassilev (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3728?page=com.atlassian.jira.plugi... ]
Ilia Vassilev commented on WFCORE-3728:
---------------------------------------
[~dlofthouse] Please investigate the issue from Elytron perspective. I'm assigning the issue to you based on the latest finding from Ricardo on JBEAP-14534. Thanks!
> DefaultJMSConnectionFactory not found after switching to elytron and removing picketbox subsystem
> -------------------------------------------------------------------------------------------------
>
> Key: WFCORE-3728
> URL: https://issues.jboss.org/browse/WFCORE-3728
> Project: WildFly Core
> Issue Type: Bug
> Affects Versions: 3.0.10.Final
> Reporter: Ilia Vassilev
>
> After running the enable-elytron.cli and removing the old
> picketbox security subsystem, the deployment fails as
> it cannot find java:jboss/DefaultJMSConnectionFactory.
> java:jboss/DefaultJMSConnectionFactory is defined in the messaging
> subsystem and the ee default-bindings.
> Removing it from the ee default-bindings lets the app deploy, but it looks like there is some
> issue as it should be bound and no errors/warnings being logged.
> {code}
> 2018-04-02 12:15:36,593 ERROR
> [org.jboss.as.controller.management-operation] (Controller Boot Thread)
> WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" =>
> "ejb-security.jar")]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" =>
> ["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" =>
> ["jboss.naming.context.java.comp.ejb-security.ejb-security.SecuredEJB.DefaultJMSConnectionFactory
> is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"]
> }
> 2018-04-02 12:15:36,603 INFO [org.jboss.as.server] (ServerService
> Thread Pool -- 42) WFLYSRV0010: Deployed "ejb-security.jar"
> (runtime-name : "ejb-security.jar")
> 2018-04-02 12:15:36,607 INFO [org.jboss.as.controller] (Controller Boot
> Thread) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service
> jboss.naming.context.java.jboss.DefaultJMSConnectionFactory (missing)
> dependents: [service
> jboss.naming.context.java.comp.ejb-security.ejb-security.SecuredEJB.DefaultJMSConnectionFactory]
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFCORE-3728) DefaultJMSConnectionFactory not found after switching to elytron and removing picketbox subsystem
by Ilia Vassilev (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3728?page=com.atlassian.jira.plugi... ]
Ilia Vassilev reassigned WFCORE-3728:
-------------------------------------
Assignee: Darran Lofthouse
> DefaultJMSConnectionFactory not found after switching to elytron and removing picketbox subsystem
> -------------------------------------------------------------------------------------------------
>
> Key: WFCORE-3728
> URL: https://issues.jboss.org/browse/WFCORE-3728
> Project: WildFly Core
> Issue Type: Bug
> Affects Versions: 3.0.10.Final
> Reporter: Ilia Vassilev
> Assignee: Darran Lofthouse
>
> After running the enable-elytron.cli and removing the old
> picketbox security subsystem, the deployment fails as
> it cannot find java:jboss/DefaultJMSConnectionFactory.
> java:jboss/DefaultJMSConnectionFactory is defined in the messaging
> subsystem and the ee default-bindings.
> Removing it from the ee default-bindings lets the app deploy, but it looks like there is some
> issue as it should be bound and no errors/warnings being logged.
> {code}
> 2018-04-02 12:15:36,593 ERROR
> [org.jboss.as.controller.management-operation] (Controller Boot Thread)
> WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" =>
> "ejb-security.jar")]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" =>
> ["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" =>
> ["jboss.naming.context.java.comp.ejb-security.ejb-security.SecuredEJB.DefaultJMSConnectionFactory
> is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"]
> }
> 2018-04-02 12:15:36,603 INFO [org.jboss.as.server] (ServerService
> Thread Pool -- 42) WFLYSRV0010: Deployed "ejb-security.jar"
> (runtime-name : "ejb-security.jar")
> 2018-04-02 12:15:36,607 INFO [org.jboss.as.controller] (Controller Boot
> Thread) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service
> jboss.naming.context.java.jboss.DefaultJMSConnectionFactory (missing)
> dependents: [service
> jboss.naming.context.java.comp.ejb-security.ejb-security.SecuredEJB.DefaultJMSConnectionFactory]
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (DROOLS-2454) [DMN Designer] Decision content not visible after reopen
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2454?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-2454:
-----------------------------------
Sprint: 2018 Week 13-14
> [DMN Designer] Decision content not visible after reopen
> --------------------------------------------------------
>
> Key: DROOLS-2454
> URL: https://issues.jboss.org/browse/DROOLS-2454
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Fix For: 7.8.0.Final
>
> Attachments: Screenshot from 2018-04-05 14-35-20.png, Screenshot from 2018-04-05 14-35-52.png
>
>
> If the decision with bigger context table is reopened, its content is not visible.
> h2. Acceptance test
> In each scenario, width of columns don't have to be same as before closing, however each column should has some minimal/default width.
> # Steps to reproduce fixed
> # Define top level as Literal expression, reopen
> # Define top level as Decision table, add columns, reopen
> # Define top level as Relation, add columns, reopen
> # Define top level as Invocation, specify complex parameters, reopen
> # Define top level as Function, add a lot of parameters, reopen
> # Define top level as Context, recursively add more Contexts, reopen
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months