May 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3439) Websockets not working

by Kadhem Kacem (JIRA)

[ https://issues.jboss.org/browse/WFLY-3439?page=com.atlassian.jira.plugin.... ] Kadhem Kacem commented on WFLY-3439: ------------------------------------ have you find a solution? > Websockets not working > ---------------------- > > Key: WFLY-3439 > URL: https://issues.jboss.org/browse/WFLY-3439 > Project: WildFly > Issue Type: Bug > Components: Web Sockets > Affects Versions: 8.1.0.Final > Reporter: Veli Cris > Assignee: Stuart Douglas > Fix For: 9.0.0.Alpha1 > > > Hi, > I deployed a .war file containing a single endpoint definition (Websocket). I can see following lines in console but nothing happens when trying to open connection from a websocket client. Same .war deployed in WildFly 8.0.0 is working. Please investigate! > The configuration is standalone. > [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017519: Undertow HTTP listener default listening on /0.0.0.0:8080 > [io.undertow.websockets.jsr] (MSC service thread 1-4) UT026003: Adding annotated server endpoint ... > [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017534: Registered web context: ... > [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS018559: Deployed "web.war" (runtime-name : "web.war") -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4694) FEATURE REQUEST: Include JSF libraries in the Web distribution

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-4694?page=com.atlassian.jira.plugin.... ] James Perkins closed WFLY-4694. ------------------------------- Resolution: Rejected This will add too much bloat to the servlet dist which is intended to be small. JSF requires other parts of Java EE to work. It's better to just use the full distribution to take advantage of Java EE if you're using JSF IMO. > FEATURE REQUEST: Include JSF libraries in the Web distribution > -------------------------------------------------------------- > > Key: WFLY-4694 > URL: https://issues.jboss.org/browse/WFLY-4694 > Project: WildFly > Issue Type: Feature Request > Components: Build System, JSF, Web (Undertow) > Affects Versions: 9.0.0.CR1 > Environment: Any > Reporter: Francesco Marchioni > Assignee: David Lloyd > Priority: Minor > Fix For: 9.0.0.CR2 > > > The current version (9.0.0.CR1 Web) does not include the faces libraries which are anyway needed in many web applications. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-722) Add real REST patterns to the HTTP management API

by Jason Greene (JIRA)

Jason Greene created WFCORE-722: ----------------------------------- Summary: Add real REST patterns to the HTTP management API Key: WFCORE-722 URL: https://issues.jboss.org/browse/WFCORE-722 Project: WildFly Core Issue Type: Feature Request Reporter: Jason Greene The HTTP API should be expanded to support a REST style layout and additionally JSON Patching (RFC 6902) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-721) Create a ModelNode to CLI call transformation facility

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFCORE-721?page=com.atlassian.jira.plugin... ] Jason Greene updated WFCORE-721: -------------------------------- Summary: Create a ModelNode to CLI call transformation facility (was: Create a toCLI() transformer method for an operation based ModelNodes ) > Create a ModelNode to CLI call transformation facility > ------------------------------------------------------ > > Key: WFCORE-721 > URL: https://issues.jboss.org/browse/WFCORE-721 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Jason Greene > Assignee: luck3y > > Add a transformation function that can convert a ModelNode representation of an operation into a CLI command. In the case of a composite operation, this should result in a CLI batch with multiple CLI commands. > This capability involves introducing a transformation API (ModelNodeTransformer?), and perhaps an SPI to support pluggable transformation algorithms. > Future transformations might be: > - Java code - Transformation of a ModelNode based management operation into Java code using the jboss-dmr API to build a ModelNode and use the ModelController client API > - Python code - Transformation of a ModelNode based management operation into Python code that builds a JSON representation of the model node and some demo code calling an HTTP API in python to make the invocation > - Curl code - Transformation of a ModelNode based management operation into a curl statement(s) that can be cut and paste into a console > - XHR JS code - Transformation of a ModelNode based management operation into JS XHR calls > This functionality belongs in a new library, and once completed should be directly ported to HAL(console) as a prototype (this would enable HAL to record and display operations, CLI calls, or even code of the work performance based on user selection) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-721) Create a toCLI() transformer method for an operation based ModelNodes

by Jason Greene (JIRA)

Jason Greene created WFCORE-721: ----------------------------------- Summary: Create a toCLI() transformer method for an operation based ModelNodes Key: WFCORE-721 URL: https://issues.jboss.org/browse/WFCORE-721 Project: WildFly Core Issue Type: Feature Request Components: Domain Management Reporter: Jason Greene Assignee: luck3y Add a transformation function that can convert a ModelNode representation of an operation into a CLI command. In the case of a composite operation, this should result in a CLI batch with multiple CLI commands. This capability involves introducing a transformation API (ModelNodeTransformer?), and perhaps an SPI to support pluggable transformation algorithms. Future transformations might be: - Java code - Transformation of a ModelNode based management operation into Java code using the jboss-dmr API to build a ModelNode and use the ModelController client API - Python code - Transformation of a ModelNode based management operation into Python code that builds a JSON representation of the model node and some demo code calling an HTTP API in python to make the invocation - Curl code - Transformation of a ModelNode based management operation into a curl statement(s) that can be cut and paste into a console - XHR JS code - Transformation of a ModelNode based management operation into JS XHR calls This functionality belongs in a new library, and once completed should be directly ported to HAL(console) as a prototype (this would enable HAL to record and display operations, CLI calls, or even code of the work performance based on user selection) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-715) Xalan Linkage error : TransformerConfigurationException for domain setup

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-715?page=com.atlassian.jira.plugin... ] Darran Lofthouse resolved WFCORE-715. ------------------------------------- Assignee: Darran Lofthouse Fix Version/s: 1.0.0.CR6 Resolution: Duplicate Issue This is in relation to an issue already fixed upstream. > Xalan Linkage error : TransformerConfigurationException for domain setup > ------------------------------------------------------------------------ > > Key: WFCORE-715 > URL: https://issues.jboss.org/browse/WFCORE-715 > Project: WildFly Core > Issue Type: Bug > Environment: Wildfly 8.2-Final Domain configuration > JDK 1.8.0_45 > Windows only > Reporter: Renan Galang > Assignee: Darran Lofthouse > Fix For: 1.0.0.CR6 > > > Running into the same error as WFCORE-519, but on domain setup. Issue persists on 8.2-FINAL > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:76) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:166) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:197) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:759) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: com.lawson.util.eli.xslt.LawXsltException: javax.xml.transform.TransformerConfigurationException: Translet class loaded, but unable to create translet instance. > at com.lawson.util.eli.xslt.LawTransform.doTransform(LawTransform.java:148) > at com.lawson.util.eli.xslt.LawTransform.transform(LawTransform.java:57) > at com.lawson.servlet.Transform.doGet(Transform.java:218) > ... 42 more > Caused by: javax.xml.transform.TransformerConfigurationException: Translet class loaded, but unable to create translet instance. > at com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.defineTransletClasses(TemplatesImpl.java:390) > at com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.getTransletInstance(TemplatesImpl.java:404) > at com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.newTransformer(TemplatesImpl.java:439) > at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTransformer(TransformerFactoryImpl.java:792) > at __redirected.__TransformerFactory.newTransformer(__TransformerFactory.java:132) > at com.lawson.util.eli.xslt.LawTransform.doTransform(LawTransform.java:142) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-201) Add client side HTTP authentication mechanism support.

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-201: ------------------------------------ Summary: Add client side HTTP authentication mechanism support. Key: ELY-201 URL: https://issues.jboss.org/browse/ELY-201 Project: WildFly Elytron Issue Type: Feature Request Components: HTTP Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 2.0.0.Alpha1 Generally this will need to follow similar patterns as used for the server side mechanisms. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-201) Add client side HTTP authentication mechanism support.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-201?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse reassigned ELY-201: ------------------------------------ Assignee: (was: Darran Lofthouse) > Add client side HTTP authentication mechanism support. > ------------------------------------------------------ > > Key: ELY-201 > URL: https://issues.jboss.org/browse/ELY-201 > Project: WildFly Elytron > Issue Type: Feature Request > Components: HTTP > Reporter: Darran Lofthouse > Fix For: 2.0.0.Alpha1 > > > Generally this will need to follow similar patterns as used for the server side mechanisms. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-800) KieBase compilation fails when @PropertyReactive declared in different DRL

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-800?page=com.atlassian.jira.plugin... ] Mario Fusco commented on DROOLS-800: ------------------------------------ The problem was caused by the fact that resources with 1-char long file name placed directly under the /resources folder were never added to the KieBase. Fixed by https://github.com/droolsjbpm/drools/commit/0ff466aac > KieBase compilation fails when @PropertyReactive declared in different DRL > -------------------------------------------------------------------------- > > Key: DROOLS-800 > URL: https://issues.jboss.org/browse/DROOLS-800 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.2.0.Final > Environment: Mac OS X 10.10.3, Oracle Hotspot 1.7.0_79, Drools 6.3.0-SNAPSHOT, JBoss BRMS 6.1.0 > Reporter: Duncan Doyle > Assignee: Mario Fusco > Fix For: 6.3.0.Beta1 > > > I declare my events in a DRL that is different from the DRL that contains my rules. I declare my event with @propertyReactive. In my rule I use an @watch annotation. In JBoss BRMS 6.1 / Drools 6.2+, this causes an error when building my KieBase: > {code} > java.lang.RuntimeException: Error while creating KieBase[Message [id=1, level=ERROR, path=rules.drl, line=7, column=0 > text=Wrong usage of @Watch annotation on class org.jboss.ddoyle.drools.propreactive.model.Event1 that is not annotated as @PropertyReactive]] > at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:418) > at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:396) > {code} > The interesting thing is that the error only occurs if I give my DRL with my 'declare' a certain name. I.e. if I name it 'a.drl', building the KieBase fails, if I name it 'ab.drl', it succeeds. > A reproducer can be found here: https://github.com/DuncanDoyle/drools-propreactive-kiebase-build-issue > Just run a 'mvn clean test' on the project. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-800) KieBase compilation fails when @PropertyReactive declared in different DRL

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-800?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-800. -------------------------------- Fix Version/s: 6.3.0.Beta1 Resolution: Done > KieBase compilation fails when @PropertyReactive declared in different DRL > -------------------------------------------------------------------------- > > Key: DROOLS-800 > URL: https://issues.jboss.org/browse/DROOLS-800 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.2.0.Final > Environment: Mac OS X 10.10.3, Oracle Hotspot 1.7.0_79, Drools 6.3.0-SNAPSHOT, JBoss BRMS 6.1.0 > Reporter: Duncan Doyle > Assignee: Mario Fusco > Fix For: 6.3.0.Beta1 > > > I declare my events in a DRL that is different from the DRL that contains my rules. I declare my event with @propertyReactive. In my rule I use an @watch annotation. In JBoss BRMS 6.1 / Drools 6.2+, this causes an error when building my KieBase: > {code} > java.lang.RuntimeException: Error while creating KieBase[Message [id=1, level=ERROR, path=rules.drl, line=7, column=0 > text=Wrong usage of @Watch annotation on class org.jboss.ddoyle.drools.propreactive.model.Event1 that is not annotated as @PropertyReactive]] > at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:418) > at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:396) > {code} > The interesting thing is that the error only occurs if I give my DRL with my 'declare' a certain name. I.e. if I name it 'a.drl', building the KieBase fails, if I name it 'ab.drl', it succeeds. > A reproducer can be found here: https://github.com/DuncanDoyle/drools-propreactive-kiebase-build-issue > Just run a 'mvn clean test' on the project. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2015