February 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4383) Wrong order of elements in appclient.xml

by Panagiotis Sotiropoulos (JIRA)

[ https://issues.jboss.org/browse/WFLY-4383?page=com.atlassian.jira.plugin.... ] Panagiotis Sotiropoulos commented on WFLY-4383: ----------------------------------------------- This issue is related to https://bugzilla.redhat.com/show_bug.cgi?id=1195138 > Wrong order of elements in appclient.xml > ------------------------------------------ > > Key: WFLY-4383 > URL: https://issues.jboss.org/browse/WFLY-4383 > Project: WildFly > Issue Type: Bug > Components: Application Client > Affects Versions: 9.0.0.Alpha1 > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > > Description of problem: > File appclient/configuration/appclient.xml has an incorrect order of elements. <core-environment> tag should be before <recovery-environment /> tag. These tags is in <subsystem xmlns="urn:jboss:domain:transactions:1.4"> and schema is in docs/schema/jboss-as-txn_1_4.xsd. This schema defines specific order of elements. > Version-Release number of selected component (if applicable): > 6.4.0.ER2 > Validate logs: > appclient/configuration/appclient.xml:150: element recovery-environment: Schemas validity error : Element '{urn:jboss:domain:transactions:1.4}recovery-environment': This element is not expected. Expected is ( {urn:jboss:domain:transactions:1.4}core-environment ). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-564) setXmlWrapperElement() doesn't work properly with multiple resource children

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFCORE-564: ---------------------------------- Summary: setXmlWrapperElement() doesn't work properly with multiple resource children Key: WFCORE-564 URL: https://issues.jboss.org/browse/WFCORE-564 Project: WildFly Core Issue Type: Bug Components: XML Frameworks Affects Versions: 1.0.0.Alpha19 Reporter: Tomaz Cerar Assignee: Tomaz Cerar {noformat}Jeff Mesnil 12:13 @ctomc hi tomaz. The setXmlWrapperElement() method in persistent xml builder API is supposed to add a XML wrapper around all the resource's XML elements, right? and not around each resource element. ie it looks like <wrapper><res /><res /></wrapper> and not <wrapper><res /></wrapper><wrapper><res /></wrapper> Tomaz Cerar 12:17 hmm, you are right also around resources it would be <wrapper> <res /> <res/> </wrapper> just remembered i had that in 1.0 xsd of undertow subsystem Jeff Mesnil 12:20 yes, I want to wrap some resources (eg queue) in a wrapper (<queues>). But the persistent XM parser is broken (it wants one wrapper around each resource) the XML persister is working as expected though Tomaz Cerar @jmesnil you are right it is broken, i can reproduce it also on undertow-1.0.xml test case i just had one resource under it so it passed{noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4383) Wrong order of elements in appclient.xml

by Panagiotis Sotiropoulos (JIRA)

Panagiotis Sotiropoulos created WFLY-4383: --------------------------------------------- Summary: Wrong order of elements in appclient.xml Key: WFLY-4383 URL: https://issues.jboss.org/browse/WFLY-4383 Project: WildFly Issue Type: Bug Components: Application Client Affects Versions: 9.0.0.Alpha1 Reporter: Panagiotis Sotiropoulos Assignee: Panagiotis Sotiropoulos Description of problem: File appclient/configuration/appclient.xml has an incorrect order of elements. <core-environment> tag should be before <recovery-environment /> tag. These tags is in <subsystem xmlns="urn:jboss:domain:transactions:1.4"> and schema is in docs/schema/jboss-as-txn_1_4.xsd. This schema defines specific order of elements. Version-Release number of selected component (if applicable): 6.4.0.ER2 Validate logs: appclient/configuration/appclient.xml:150: element recovery-environment: Schemas validity error : Element '{urn:jboss:domain:transactions:1.4}recovery-environment': This element is not expected. Expected is ( {urn:jboss:domain:transactions:1.4}core-environment ). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-706) Change the default object store of JBoss transactions to use the hornetq object store

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/WFLY-706?page=com.atlassian.jira.plugin.s... ] Michael Musgrove commented on WFLY-706: --------------------------------------- A limitation of this store is that it cannot be shared, so, for example, we could not run the recovery manager in a separate JVM. > Change the default object store of JBoss transactions to use the hornetq object store > ------------------------------------------------------------------------------------- > > Key: WFLY-706 > URL: https://issues.jboss.org/browse/WFLY-706 > Project: WildFly > Issue Type: Feature Request > Components: Transactions > Reporter: Tom Jenkinson > Fix For: Awaiting Volunteers > > > This would provide a performance boost, however it is not supportable until AS7-925 is complete as the object store cannot be manipulated on the filesystem to resolve heuristics, tooling is necessary. > PS Do not implement this feature without tooling or discussing with me, I will add this after tooling is added. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-563) Upgrade to Xerces 2.11.0.SP1

by Carlo de Wolf (JIRA)

[ https://issues.jboss.org/browse/WFCORE-563?page=com.atlassian.jira.plugin... ] Carlo de Wolf updated WFCORE-563: --------------------------------- Summary: Upgrade to Xerces 2.11.0.SP1 (was: Upgrade to Xerces 2.11.0) > Upgrade to Xerces 2.11.0.SP1 > ---------------------------- > > Key: WFCORE-563 > URL: https://issues.jboss.org/browse/WFCORE-563 > Project: WildFly Core > Issue Type: Component Upgrade > Affects Versions: 1.0.0.Alpha19 > 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)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-563) Upgrade to Xerces 2.11.0

by Carlo de Wolf (JIRA)

[ https://issues.jboss.org/browse/WFCORE-563?page=com.atlassian.jira.plugin... ] Carlo de Wolf commented on WFCORE-563: -------------------------------------- The actual bug fix is at https://github.com/jboss/xerces/commit/459d57d5804ccb6586f8a1666129dcd304... > Upgrade to Xerces 2.11.0 > ------------------------ > > Key: WFCORE-563 > URL: https://issues.jboss.org/browse/WFCORE-563 > Project: WildFly Core > Issue Type: Component Upgrade > Affects Versions: 1.0.0.Alpha19 > 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)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-724) Preemptive authentication in KIE Scanner

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-724?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-724. -------------------------------- Resolution: Won't Fix What you're asking makes sense but the current Wagon API doesn't allow me to fix this issue. The problem here is that you could have multiple servers in your settings.xml file and only one (or anyway a subset of them) could have been configured with the usePreemptive flag. Conversely the WagonProvider interface allow me to create one single Wagon to be used for all the http(s) requests. In other words there's no way to have different Wagons configured for the different servers you may have in your settings.xml file so I am obliged to use a minimal Wagon configuration. > Preemptive authentication in KIE Scanner > ---------------------------------------- > > Key: DROOLS-724 > URL: https://issues.jboss.org/browse/DROOLS-724 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 6.1.0.Final > Reporter: Rares Vernica > Assignee: Mario Fusco > > The pre-emptive authentication setting from Maven's settings.xml is not picked up by Drools: > <server> > <id>guvnor-m2-repo</id> > <username>...</username> > <password>...</password> > <configuration> > <httpConfiguration> > <usePreemptive>true</usePreemptive> > </httpConfiguration> > </configuration> > </server> > I am not sure if the bug is in Drools or Wagon. To fix it, I made the pre-emptive always true, but adding: > ... > if ( "http".equals( roleHint ) || "https".equals( roleHint ) ) { > HttpMethodConfiguration httpMethodConfiguration = new HttpMethodConfiguration(); > httpMethodConfiguration.setUsePreemptive( true ); > HttpConfiguration httpConfiguration = new HttpConfiguration(); > httpConfiguration.setAll( httpMethodConfiguration ); > > HttpWagon httpWagon = new HttpWagon(); > httpWagon.setHttpConfiguration( httpConfiguration ); > > return httpWagon; > } > ... > in Aether$ManualWagonProvider. This obviously is not a good solution. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-563) Upgrade to Xerces 2.11.0

by Carlo de Wolf (JIRA)

[ https://issues.jboss.org/browse/WFCORE-563?page=com.atlassian.jira.plugin... ] Carlo de Wolf moved WFLY-3528 to WFCORE-563: -------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-563 (was: WFLY-3528) Issue Type: Component Upgrade (was: Feature Request) Affects Version/s: 1.0.0.Alpha19 (was: 8.1.0.Final) Component/s: (was: Web Services) > Upgrade to Xerces 2.11.0 > ------------------------ > > Key: WFCORE-563 > URL: https://issues.jboss.org/browse/WFCORE-563 > Project: WildFly Core > Issue Type: Component Upgrade > Affects Versions: 1.0.0.Alpha19 > 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)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-562) Wrong order of elements in jboss-cli.xml

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-562?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated WFCORE-562: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1195132 > Wrong order of elements in jboss-cli.xml > ---------------------------------------- > > Key: WFCORE-562 > URL: https://issues.jboss.org/browse/WFCORE-562 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 1.0.0.Alpha19 > Reporter: Dominik Pospisil > Assignee: Dominik Pospisil > > File bin/jboss-cli.xml has an incorrect order of elements. <history> tag should be before <resolve-parameter-values> tag. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-562) Wrong order of elements in jboss-cli.xml

by Dominik Pospisil (JIRA)

Dominik Pospisil created WFCORE-562: --------------------------------------- Summary: Wrong order of elements in jboss-cli.xml Key: WFCORE-562 URL: https://issues.jboss.org/browse/WFCORE-562 Project: WildFly Core Issue Type: Bug Components: CLI Affects Versions: 1.0.0.Alpha19 Reporter: Dominik Pospisil Assignee: Dominik Pospisil File bin/jboss-cli.xml has an incorrect order of elements. <history> tag should be before <resolve-parameter-values> tag. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 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