May 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4658) merge Jipijapa source into WildFly

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4658?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4658: ------------------------------- Fix Version/s: 10.0.0.Alpha3 (was: 10.0.0.Alpha2) > merge Jipijapa source into WildFly > ---------------------------------- > > Key: WFLY-4658 > URL: https://issues.jboss.org/browse/WFLY-4658 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 10.0.0.Alpha3 > > > Merging http://github.com/jipijapa/jipijapa sources back into WildFly to increase community involvement. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4651) Change default locking isolation of infinispan caches to READ_COMMITTED

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4651?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4651: ------------------------------- Fix Version/s: 10.0.0.Alpha3 (was: 10.0.0.Alpha2) > Change default locking isolation of infinispan caches to READ_COMMITTED > ----------------------------------------------------------------------- > > Key: WFLY-4651 > URL: https://issues.jboss.org/browse/WFLY-4651 > Project: WildFly > Issue Type: Sub-task > Components: Clustering > Affects Versions: 9.0.0.CR1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 9.0.0.CR2, 10.0.0.Alpha3 > > > This will allow concurrent read access to the session using our default configuration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4705) Enable interface declaration in subsystem template

by Tomasz Adamski (JIRA)

Tomasz Adamski created WFLY-4705: ------------------------------------ Summary: Enable interface declaration in subsystem template Key: WFLY-4705 URL: https://issues.jboss.org/browse/WFLY-4705 Project: WildFly Issue Type: Feature Request Components: Build System, IIOP Affects Versions: 10.0.0.Alpha1 Reporter: Tomasz Adamski Assignee: Tomasz Adamski Priority: Optional Currently interfaces cannot be defined in subsystem templates. As a result of "unsecure" interface, which is used only by iiop subsystem, is defined in main template file and it's included in all subsystems configurations. Implement extension to feature pack plugin which enables specifying interfaces in subsystem configuration files and move "unsecure" interface configuration from main template to jacorb. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (LOGTOOL-91) Add ability to provide constant values for properties

by David Lloyd (JIRA)

David Lloyd created LOGTOOL-91: ---------------------------------- Summary: Add ability to provide constant values for properties Key: LOGTOOL-91 URL: https://issues.jboss.org/browse/LOGTOOL-91 Project: Log Tool Issue Type: Feature Request Reporter: David Lloyd Assignee: James Perkins Right now I have to do this: {code} @Message(id = 28, value = "An unexpected protocol error occurred") XAException protocolErrorXA(@Property int errorCode); // ... then later ... throw Log.log.protocolErrorXA(XAException.XAER_RMFAIL); {code} I'd rather be able to do this: {code} @Message(id = 28, value = "An unexpected protocol error occurred") @Property(name = "errorCode", intValue = XAException.XAER_RMFAIL) XAException protocolErrorXA(); // ... then later ... throw Log.log.protocolErrorXA(); {code} The same annotation ({{@Property}}) could be reused by making it multi-valued (i.e. invisible wrapper annotation) and adding in defaulted {{xxxValue}} parameters (primitive types, {{Class<XX>}}, and {{String}}) which are rejected when applied directly to a method parameter. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[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)

8 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)

8 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)

8 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)

8 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)

8 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)

8 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2015