February 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-543) Revisit how the model validation happens

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-543?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-543: ------------------------------------ Fix Version/s: 1.0.0.Alpha19 (was: 1.0.0.Alpha18) > Revisit how the model validation happens > ---------------------------------------- > > Key: WFCORE-543 > URL: https://issues.jboss.org/browse/WFCORE-543 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Kabir Khan > Assignee: Brian Stansberry > Fix For: 1.0.0.Alpha19 > > > Currently the ValidateModelStepHandler is triggered by AbstractAddStepHandler. Not all add handlers extend AbstractAddStepHandler. Also, it does not seem to be triggered for writes. > Also if used in a composite along the lines of > {code} > [standalone@localhost:9990 /] batch > [standalone@localhost:9990 / #] /system-property=xxx:add(value=test) > [standalone@localhost:9990 / #] /system-property=xxx:remove > [standalone@localhost:9990 / #] run-batch > {code} > the handler will get triggered at the end for the add. It will fail for the add since there is no such resource. While that is easy to work around by checking for a NoSuchResourceException around the OC.readResource() it seems that what triggers the use of the ValidateModelStepHandler should be more an intrinsic part of the controller which knows what has and has not been added/removed/written to. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-496) add-user.sh - if password contains § it is not possible to log into the webinterface

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-496?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-496: ------------------------------------ Fix Version/s: 1.0.0.Alpha19 (was: 1.0.0.Alpha18) > add-user.sh - if password contains § it is not possible to log into the webinterface > ------------------------------------------------------------------------------------ > > Key: WFCORE-496 > URL: https://issues.jboss.org/browse/WFCORE-496 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Environment: wheezy, Firefox 34.0.5, Chrome 36.0.1985.125 > Reporter: do ev > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha19 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-489) The "access-mechanism" field in the active-operation resources is always undefined

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-489?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-489: ------------------------------------ Fix Version/s: 1.0.0.Alpha19 (was: 1.0.0.Alpha18) > The "access-mechanism" field in the active-operation resources is always undefined > ---------------------------------------------------------------------------------- > > Key: WFCORE-489 > URL: https://issues.jboss.org/browse/WFCORE-489 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha15 > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > Fix For: 1.0.0.Alpha19 > > > The "access-mechanism" field in core-service=management/service=active-operations/active-operation=* is always undefined. The code that sets it is using the wrong var: > {code} > ModelNode accessMechanismNode = model.get(ACCESS_MECHANISM); > if (accessMechanism != null) { > accessMechanismNode.set(accessMechanismNode.toString()); > } > {code} > It should be accessMechanism.toString() -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-815) Some org.apache.xml.resolver classes in both jaxb-xjc-2.2.jar , xml-resolver-1.2.jar

by Frank Langelage (JIRA)

[ https://issues.jboss.org/browse/WFLY-815?page=com.atlassian.jira.plugin.s... ] Frank Langelage commented on WFLY-815: -------------------------------------- Close, Outdated. jar -tf modules/system/layers/base/com/sun/xml/bind/main/jaxb-xjc-2.2.7.jar | grep ".class$" | while read i; do jar -tf modules/system/layers/base/org/apache/xml-resolver/main/xml-resolver-1.2.jar $i done does not find anything. > Some org.apache.xml.resolver classes in both jaxb-xjc-2.2.jar , xml-resolver-1.2.jar > ------------------------------------------------------------------------------------ > > Key: WFLY-815 > URL: https://issues.jboss.org/browse/WFLY-815 > Project: WildFly > Issue Type: Bug > Components: Build System > Reporter: Ondrej Zizka > Assignee: Paul Gier > > These classes are in both modules: > org.apache.xml.resolver.Catalog > org.apache.xml.resolver.CatalogEntry > org.apache.xml.resolver.CatalogException > org.apache.xml.resolver.CatalogManager > org.apache.xml.resolver.Resolver > org.apache.xml.resolver.Version > org.apache.xml.resolver.apps.XParseError > org.apache.xml.resolver.apps.resolver > org.apache.xml.resolver.apps.xparse > org.apache.xml.resolver.apps.xread > org.apache.xml.resolver.helpers.Debug > org.apache.xml.resolver.helpers.Namespaces > org.apache.xml.resolver.helpers.PublicId > org.apache.xml.resolver.readers.CatalogReader > org.apache.xml.resolver.readers.DOMCatalogParser > org.apache.xml.resolver.readers.DOMCatalogReader > org.apache.xml.resolver.readers.ExtendedXMLCatalogReader > org.apache.xml.resolver.readers.OASISXMLCatalogReader > org.apache.xml.resolver.readers.SAXCatalogParser > org.apache.xml.resolver.readers.SAXCatalogReader > org.apache.xml.resolver.readers.SAXParserHandler > org.apache.xml.resolver.readers.TR9401CatalogReader > org.apache.xml.resolver.readers.TextCatalogReader > org.apache.xml.resolver.readers.XCatalogReader > org.apache.xml.resolver.tools.CatalogResolver > org.apache.xml.resolver.tools.ResolvingParser > org.apache.xml.resolver.tools.ResolvingXMLFilter > org.apache.xml.resolver.tools.ResolvingXMLReader > These are only in xml-resolver: > org.apache.xml.resolver.helpers.BootstrapResolver > org.apache.xml.resolver.helpers.FileURL > See https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-Miscellaneous/job/... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4313) Clean-up tests which use Kerberos in the WildFly testsuite

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4313?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4313: ----------------------------------------------- Josef Cacek <jcacek(a)redhat.com> changed the Status of [bug 1189141|https://bugzilla.redhat.com/show_bug.cgi?id=1189141] from ASSIGNED to POST > Clean-up tests which use Kerberos in the WildFly testsuite > ---------------------------------------------------------- > > Key: WFLY-4313 > URL: https://issues.jboss.org/browse/WFLY-4313 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Reporter: Josef Cacek > Assignee: Josef Cacek > > Clean up Kerberos tests and add an unified logic for skipping Kerberos test configurations which proved to be unstable/buggy. By a configuration here is meant combination of Java vendor, version and IP stack. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4280) Component upgrade of Hibernate Validator to version 5.1.next.Final when HV-861 is fixed

by Hardy Ferentschik (JIRA)

[ https://issues.jboss.org/browse/WFLY-4280?page=com.atlassian.jira.plugin.... ] Hardy Ferentschik commented on WFLY-4280: ----------------------------------------- [~juan.hernandez], what exactly do you want me to do to reproduce the problem. Your setup contains a bunch of domain classes and create a jar file with an empty {{beans.xml}}. I deploy this jar via the jboss command line client and get: {noformat} 21:27:15,018 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "hv-861-1.0-SNAPSHOT.jar" (runtime-name: "hv-861-1.0-SNAPSHOT.jar") 21:27:15,859 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016002: Processing weld deployment hv-861-1.0-SNAPSHOT.jar 21:27:16,355 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-7) HV000001: Hibernate Validator 5.1.3.Final 21:27:16,859 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) JBAS016005: Starting Services for CDI deployment: hv-861-1.0-SNAPSHOT.jar 21:27:17,148 INFO [org.jboss.weld.Version] (MSC service thread 1-5) WELD-000900: 2.2.6 (Final) 21:27:17,321 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) JBAS016008: Starting weld service for deployment hv-861-1.0-SNAPSHOT.jar 21:27:20,193 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "hv-861-1.0-SNAPSHOT.jar" (runtime-name : "hv-861-1.0-SNAPSHOT.jar") {noformat} According to your description I would have expected this to throw an exception. I am also a bit surprised that your code does not contain any actual Bean Validation constraints. There is a {{@Valid}} on a string property, but that is not a constraint and in the context of Bean Validation does not even make sense, since {{@Valid}} is used to trigger cascaded validation for object graphs which does not really apply to a "simple" string. Are you sure this is what I need to reproduce the problem? It would be great if you could double check your attached tarball and provide some detailed instructions on how to reproduce the error. Last but not least, I am using Wildfly 8.2.0.Final "Tweek" > Component upgrade of Hibernate Validator to version 5.1.next.Final when HV-861 is fixed > --------------------------------------------------------------------------------------- > > Key: WFLY-4280 > URL: https://issues.jboss.org/browse/WFLY-4280 > Project: WildFly > Issue Type: Bug > Affects Versions: 8.1.0.Final, 8.2.0.Final > Environment: Fedora 21, OpenJDK 1.8.0_25-b18. > Reporter: Juan Hernández > Assignee: Scott Marlow > Attachments: hv-861.tar.gz > > > The version of Hibernate Validator included in WildFly 8.1 and 8.2 throws an {{ArrayIndexOutOfBounds}} exception when deploying some applications. This is already reported in the Hibernate Validator JIRA: > https://hibernate.atlassian.net/browse/HV-861 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3528) Upgrade to Xerces 2.11.0

by Frank Langelage (JIRA)

[ https://issues.jboss.org/browse/WFLY-3528?page=com.atlassian.jira.plugin.... ] Frank Langelage commented on WFLY-3528: --------------------------------------- PR for 8.x: https://github.com/wildfly/wildfly/pull/7165 > Upgrade to Xerces 2.11.0 > ------------------------ > > Key: WFLY-3528 > URL: https://issues.jboss.org/browse/WFLY-3528 > Project: WildFly > Issue Type: Feature Request > Components: Web Services > Affects Versions: 8.1.0.Final > Environment: WildFly 8.1.0.Final, JDK 7, Ubuntu, Windows, Mac OS > Reporter: Carlos Barragan > Assignee: Carlo de Wolf > Priority: Critical > Attachments: stacktrace.txt > > > Xerces 2.9.1 has a bug when parsing Times with "24" hrs. > {code} > DatatypeFactory.newInstance().newXMLGregorianCalendar("24:00:00Z"); > {code} > We have this problem in one of our web services because we get request with the above time format. > Xerces 2.11.0 does not contain that bug. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4040) add support for persistence-fragment.xml

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-4040?page=com.atlassian.jira.plugin.... ] David Lloyd updated WFLY-4040: ------------------------------ Component/s: JPA / Hibernate (was: EE) > add support for persistence-fragment.xml > ---------------------------------------- > > Key: WFLY-4040 > URL: https://issues.jboss.org/browse/WFLY-4040 > Project: WildFly > Issue Type: Feature Request > Components: JPA / Hibernate > Reporter: Mathieu Lachance > Assignee: David Lloyd > > It would be nice if JBoss / Hibernate could support the TomEE / OpenJPA persistence-fragment.xml vendor specific feature. > This feature would allow easier application modularization by not relying on any custom build process to compose a valid persistence.xml from many fragments. > See TomEE exemple here: > http://tomee.apache.org/examples-trunk/persistence-fragment/README.html -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1244) LocalXAResourceImpl returns RBROLLBACK in certain scenarios which violate the XA specification

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1244?page=com.atlassian.jira.plugin... ] Jesper Pedersen resolved JBJCA-1244. ------------------------------------ Fix Version/s: 1.0.31.Final 1.2.3.Final Resolution: Done > LocalXAResourceImpl returns RBROLLBACK in certain scenarios which violate the XA specification > ---------------------------------------------------------------------------------------------- > > Key: JBJCA-1244 > URL: https://issues.jboss.org/browse/JBJCA-1244 > Project: IronJacamar > Issue Type: Bug > Affects Versions: 1.0.30.Final > Reporter: Tom Jenkinson > Assignee: Jesper Pedersen > Fix For: 1.0.31.Final, 1.2.3.Final > > > The XA specification states the following about the RBROLLBACK error code for xa_commit(): > {quote} > [XA_RB∗] > The resource manager did not commit the work done on behalf of the transaction branch. Upon return, the resource manager has rolled back the branch’s work and has released all held resources. These values may be returned only if TMONEPHASE is set in flags: > [XA_RBROLLBACK] > The resource manager rolled back the transaction branch for an unspecified reason > {quote} > It is clear that the RBROLLBACK code may only be returned if the branch is known to have rolled back (and indeed if the onePhase flag is set to true). > To cater for scenarios where the XAResource is not able to determine the outcome of the resource managers commit. In those scenarios the XA specification is clear that the only legal error code to return is: > {quote} > [XAER_RMFAIL] > An error occurred that makes the resource manager unavailable. > {quote} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4040) add support for persistence-fragment.xml

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-4040?page=com.atlassian.jira.plugin.... ] David Lloyd reassigned WFLY-4040: --------------------------------- Assignee: Scott Marlow (was: David Lloyd) > add support for persistence-fragment.xml > ---------------------------------------- > > Key: WFLY-4040 > URL: https://issues.jboss.org/browse/WFLY-4040 > Project: WildFly > Issue Type: Feature Request > Components: JPA / Hibernate > Reporter: Mathieu Lachance > Assignee: Scott Marlow > > It would be nice if JBoss / Hibernate could support the TomEE / OpenJPA persistence-fragment.xml vendor specific feature. > This feature would allow easier application modularization by not relying on any custom build process to compose a valid persistence.xml from many fragments. > See TomEE exemple here: > http://tomee.apache.org/examples-trunk/persistence-fragment/README.html -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 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 February 2015