February 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1356) javax.sql.api should declare a dependency on javax.transaction.api

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1356?page=com.atlassian.jira.plugi... ] Tom Jenkinson updated WFCORE-1356: ---------------------------------- Labels: (was: oracle-ucp) > javax.sql.api should declare a dependency on javax.transaction.api > ------------------------------------------------------------------ > > Key: WFCORE-1356 > URL: https://issues.jboss.org/browse/WFCORE-1356 > Project: WildFly Core > Issue Type: Bug > Components: Modules > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 2.1.0.CR2 > > > javax.sql.XAConnection (https://docs.oracle.com/javase/7/docs/api/javax/sql/XAConnection.html) depends on javax.transaction.xa.XAResource > Including a partial stack trace that shows the failure: > {quote} > Caused by: java.lang.ClassNotFoundException: javax.transaction.xa.XAResource from [Module "javax.sql.api:main" from local module loader <SNIP/> > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:455) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:404) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:385) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:130) > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6136) Wildfly 10.0.0.Final duplitates contents of <jsp-config><include-prelude> or <include-coda> directives in web.xml

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6136?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-6136: ------------------------------ Component/s: Web (Undertow) > Wildfly 10.0.0.Final duplitates contents of <jsp-config><include-prelude> or <include-coda> directives in web.xml > ----------------------------------------------------------------------------------------------------------------- > > Key: WFLY-6136 > URL: https://issues.jboss.org/browse/WFLY-6136 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.Final > Environment: Ubuntu Linux 14.04 amd64 > Reporter: Juanm Manuel Enrique Muñido > Assignee: Stuart Douglas > > I have been successfully deploying an application on WildFly 8.2.1 and WildFly 9.0.2 versions with the following <jsp-config> directives in web.xml deployment descriptor: > <jsp-config> > <jsp-property-group> > <description>header and footer settings</description> > <url-pattern>/WEB-INF/view/*</url-pattern> > <url-pattern>/WEB-INF/error/*</url-pattern> > <include-prelude>/WEB-INF/jspf/header.jspf</include-prelude> > <include-coda>/WEB-INF/jspf/footer.jspf</include-coda> > </jsp-property-group> > </jsp-config> > This code fragment includes the contents of /WEB-INF/jspf/header.jspf at the beginning of each .jsp file and <include-coda>/WEB-INF/jspf/footer.jspf</include-coda> at the end of each .jsp file that matches the <url-pattern>. > But when I try to deploy this application with the same deployment descriptor in WildFly 10.0.0.Final, the contents of /WEB-INF/jspf/header.jspf and /WEB-INF/jspf/footer.jspf are included twice in each .jsp file that matches the <url-pattern>. > If I add another <url-pattern> line, then the contents of /WEB-INF/jspf/header.jspf and /WEB-INF/jspf/footer.jspf are included three times, and so on. > Any suggestion about this issue? > Is this a deployment descriptor issue or a configuration issue in the standalone.xml of WildFly 10.0.0.Final version? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6136) Wildfly 10.0.0.Final duplitates contents of <jsp-config><include-prelude> or <include-coda> directives in web.xml

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6136?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-6136: ----------------------------------- do you have simple reproducer for this? > Wildfly 10.0.0.Final duplitates contents of <jsp-config><include-prelude> or <include-coda> directives in web.xml > ----------------------------------------------------------------------------------------------------------------- > > Key: WFLY-6136 > URL: https://issues.jboss.org/browse/WFLY-6136 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.Final > Environment: Ubuntu Linux 14.04 amd64 > Reporter: Juanm Manuel Enrique Muñido > Assignee: Stuart Douglas > > I have been successfully deploying an application on WildFly 8.2.1 and WildFly 9.0.2 versions with the following <jsp-config> directives in web.xml deployment descriptor: > <jsp-config> > <jsp-property-group> > <description>header and footer settings</description> > <url-pattern>/WEB-INF/view/*</url-pattern> > <url-pattern>/WEB-INF/error/*</url-pattern> > <include-prelude>/WEB-INF/jspf/header.jspf</include-prelude> > <include-coda>/WEB-INF/jspf/footer.jspf</include-coda> > </jsp-property-group> > </jsp-config> > This code fragment includes the contents of /WEB-INF/jspf/header.jspf at the beginning of each .jsp file and <include-coda>/WEB-INF/jspf/footer.jspf</include-coda> at the end of each .jsp file that matches the <url-pattern>. > But when I try to deploy this application with the same deployment descriptor in WildFly 10.0.0.Final, the contents of /WEB-INF/jspf/header.jspf and /WEB-INF/jspf/footer.jspf are included twice in each .jsp file that matches the <url-pattern>. > If I add another <url-pattern> line, then the contents of /WEB-INF/jspf/header.jspf and /WEB-INF/jspf/footer.jspf are included three times, and so on. > Any suggestion about this issue? > Is this a deployment descriptor issue or a configuration issue in the standalone.xml of WildFly 10.0.0.Final version? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6068) Warn that attribute failback-delay is handled automatically

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-6068?page=com.atlassian.jira.plugin.... ] Jeff Mesnil reopened WFLY-6068: ------------------------------- Warning is not displayed when the failback-delay is discarded during migration > Warn that attribute failback-delay is handled automatically > ----------------------------------------------------------- > > Key: WFLY-6068 > URL: https://issues.jboss.org/browse/WFLY-6068 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.CR5 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 10.0.0.Final > > > Attribute {{failback-delay="6000"}} is not migrated. > The migrated configuration should like: > {code} > <shared-store-master failover-on-server-shutdown="true" failback-delay="6000" /> > {code} > but there is just: > {code} > <shared-store-master failover-on-server-shutdown="true" /> > {code} > See failed test in Jenkins: > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap7-migration-stand... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6048) jboss-webservices.xml descriptor doesn't override @WebContext annotation

by Dmitrii Tikhomirov (JIRA)

[ https://issues.jboss.org/browse/WFLY-6048?page=com.atlassian.jira.plugin.... ] Dmitrii Tikhomirov updated WFLY-6048: ------------------------------------- Git Pull Request: (was: https://github.com/apache/activemq-artemis/pull/376) > jboss-webservices.xml descriptor doesn't override @WebContext annotation > ------------------------------------------------------------------------ > > Key: WFLY-6048 > URL: https://issues.jboss.org/browse/WFLY-6048 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 9.0.2.Final > Environment: ubuntu 14.04, Java 7 > Reporter: Wojciech Oczkowski > Assignee: Dmitrii Tikhomirov > Priority: Minor > Attachments: ws-xml-override.zip > > > It seems that annotation WebConfig takes precedence over jboss-webservices.xml descriptor values. It doesn't seem right as you cannot override annotation values for test purposes for example. > Problematic code seems to be: > org.jboss.as.webservices.metadata.AbstractMetaDataBuilderEJB:159 > (should prefer JBossPortComponentMetaData over EJBEndpoint) > and > org.jboss.ws.common.deployment.EndpointAddressDeploymentAspect:177 > (should prefer EJBSecurityMetaData over annotation value) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1053) Change date formats for JSON representations used in the REST API

by Maciej Swiderski (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1053?page=com.atlassian.jira.plugi... ] Maciej Swiderski commented on DROOLS-1053: ------------------------------------------ this has been recently added so you can set system property to enable text based date format for JSON marshaller: https://github.com/droolsjbpm/droolsjbpm-integration/blob/master/kie-serv... though it does use certain data format pattern: https://github.com/droolsjbpm/droolsjbpm-integration/blob/master/kie-serv... would this be sufficient or shall we have another system property to control actual date format pattern? > Change date formats for JSON representations used in the REST API > ----------------------------------------------------------------- > > Key: DROOLS-1053 > URL: https://issues.jboss.org/browse/DROOLS-1053 > Project: Drools > Issue Type: Feature Request > Components: kie server > Affects Versions: 6.3.0.Final > Environment: jBPM 6.3 running on Wildfly 8.2 > Reporter: William Siqueira > Assignee: Maciej Swiderski > > The format for dates are are using milliseconds form, for example: > {code:javascript} > { > "request-instance-id" : 4, > "request-status" : "QUEUED", > "request-message" : "Ready to execute", > "request-retries" : 3, > "request-executions" : 0, > "request-command" : "org.jbpm.executor.commands.PrintOutCommand", > "request-scheduled-date" : 1455069600000 > } > {code} > The problem with this format is that it is not readable and might confuse users using other ways to communicate with the kie server than using its REST API. > The suggested solution is use a Jackson object mapper to configure the desired date format. This is better explained in this article: > http://wiki.fasterxml.com/JacksonFAQDateHandling -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1053) Change date formats for JSON representations used in the REST API

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1053?page=com.atlassian.jira.plugi... ] Edson Tirelli reassigned DROOLS-1053: ------------------------------------- Assignee: Maciej Swiderski (was: Edson Tirelli) > Change date formats for JSON representations used in the REST API > ----------------------------------------------------------------- > > Key: DROOLS-1053 > URL: https://issues.jboss.org/browse/DROOLS-1053 > Project: Drools > Issue Type: Feature Request > Components: kie server > Affects Versions: 6.3.0.Final > Environment: jBPM 6.3 running on Wildfly 8.2 > Reporter: William Siqueira > Assignee: Maciej Swiderski > > The format for dates are are using milliseconds form, for example: > {code:javascript} > { > "request-instance-id" : 4, > "request-status" : "QUEUED", > "request-message" : "Ready to execute", > "request-retries" : 3, > "request-executions" : 0, > "request-command" : "org.jbpm.executor.commands.PrintOutCommand", > "request-scheduled-date" : 1455069600000 > } > {code} > The problem with this format is that it is not readable and might confuse users using other ways to communicate with the kie server than using its REST API. > The suggested solution is use a Jackson object mapper to configure the desired date format. This is better explained in this article: > http://wiki.fasterxml.com/JacksonFAQDateHandling -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6140) Error response handling from bean validation ignores Accept header

by Marek Kopecký (JIRA)

[ https://issues.jboss.org/browse/WFLY-6140?page=com.atlassian.jira.plugin.... ] Marek Kopecký closed WFLY-6140. ------------------------------- Resolution: Duplicate Issue > Error response handling from bean validation ignores Accept header > ------------------------------------------------------------------ > > Key: WFLY-6140 > URL: https://issues.jboss.org/browse/WFLY-6140 > Project: WildFly > Issue Type: Bug > Components: REST > Affects Versions: 10.0.0.Final > Environment: Mac OS X El Captain > java version "1.8.0_66" > Java(TM) SE Runtime Environment (build 1.8.0_66-b17) > Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode) > Reporter: Marek Kopecký > Assignee: Weinan Li > > Basically I have a very simple application that has request validation in the REST endpoints. > According to the documentation of RESTEasy, I should get a JSON error response if I put "application/json" in Accept header in the request. > https://docs.jboss.org/resteasy/docs/3.0.13.Final/userguide/html/Validati... > The mentioned feature worked just fine in Wildfly 9.0.2.Final. Now, however, it doesn't. > I have tried to upgrade the dependencies in the pom.xml to use dependencies from Wildfly 10.0.0.Final, but still no luck. Though the attached application deploys just fine in Wildfly 9.0.2.Final and Wildfly 10.0.0.Final. > In WF 9.0.2.Final I used to get the below error *JSON* > {code:json} > { > "exception": null, > "fieldViolations": [], > "propertyViolations": [], > "classViolations": [], > "parameterViolations": [{ > "constraintType": "PARAMETER", > "path": "registerLogisticsNetwork.arg0.name", > "message": "may not be null", > "value": "" > }], > "returnValueViolations": [] > } > {code} > In WF 10.0.0.Final I get this: > {code} > [PARAMETER] > [registerLogisticsNetwork.arg0.name] > [may not be null] > [] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6140) Error response handling from bean validation ignores Accept header

by Marek Kopecký (JIRA)

Marek Kopecký created WFLY-6140: ----------------------------------- Summary: Error response handling from bean validation ignores Accept header Key: WFLY-6140 URL: https://issues.jboss.org/browse/WFLY-6140 Project: WildFly Issue Type: Bug Components: REST Affects Versions: 10.0.0.Final Environment: Mac OS X El Captain java version "1.8.0_66" Java(TM) SE Runtime Environment (build 1.8.0_66-b17) Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode) Reporter: Marek Kopecký Assignee: Weinan Li Basically I have a very simple application that has request validation in the REST endpoints. According to the documentation of RESTEasy, I should get a JSON error response if I put "application/json" in Accept header in the request. https://docs.jboss.org/resteasy/docs/3.0.13.Final/userguide/html/Validati... The mentioned feature worked just fine in Wildfly 9.0.2.Final. Now, however, it doesn't. I have tried to upgrade the dependencies in the pom.xml to use dependencies from Wildfly 10.0.0.Final, but still no luck. Though the attached application deploys just fine in Wildfly 9.0.2.Final and Wildfly 10.0.0.Final. In WF 9.0.2.Final I used to get the below error *JSON* {code:json} { "exception": null, "fieldViolations": [], "propertyViolations": [], "classViolations": [], "parameterViolations": [{ "constraintType": "PARAMETER", "path": "registerLogisticsNetwork.arg0.name", "message": "may not be null", "value": "" }], "returnValueViolations": [] } {code} In WF 10.0.0.Final I get this: {code} [PARAMETER] [registerLogisticsNetwork.arg0.name] [may not be null] [] {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6097) Error response handling from bean validation ignores Accept header

by Marek Kopecký (JIRA)

[ https://issues.jboss.org/browse/WFLY-6097?page=com.atlassian.jira.plugin.... ] Marek Kopecký reassigned WFLY-6097: ----------------------------------- Assignee: Weinan Li (was: Jason Greene) > Error response handling from bean validation ignores Accept header > ------------------------------------------------------------------ > > Key: WFLY-6097 > URL: https://issues.jboss.org/browse/WFLY-6097 > Project: WildFly > Issue Type: Bug > Components: REST > Affects Versions: 10.0.0.Final > Environment: Mac OS X El Captain > java version "1.8.0_66" > Java(TM) SE Runtime Environment (build 1.8.0_66-b17) > Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode) > Reporter: Renann Prado > Assignee: Weinan Li > Attachments: delivery-optimization-ear-1.0.Final.ear > > > Basically I have a very simple application that has request validation in the REST endpoints. > According to the documentation of RESTEasy, I should get a JSON error response if I put "application/json" in Accept header in the request. > https://docs.jboss.org/resteasy/docs/3.0.13.Final/userguide/html/Validati... > The mentioned feature worked just fine in Wildfly 9.0.2.Final. Now, however, it doesn't. > I have tried to upgrade the dependencies in the pom.xml to use dependencies from Wildfly 10.0.0.Final, but still no luck. Though the attached application deploys just fine in Wildfly 9.0.2.Final and Wildfly 10.0.0.Final. > In WF 9.0.2.Final I used to get the below error *JSON* > {code:json} > { > "exception": null, > "fieldViolations": [], > "propertyViolations": [], > "classViolations": [], > "parameterViolations": [{ > "constraintType": "PARAMETER", > "path": "registerLogisticsNetwork.arg0.name", > "message": "may not be null", > "value": "" > }], > "returnValueViolations": [] > } > {code} > In WF 10.0.0.Final I get this: > {code} > [PARAMETER] > [registerLogisticsNetwork.arg0.name] > [may not be null] > [] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 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 February 2016