November 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBMETA-367) CLONE - XML schema; use of elementFormDefault='unqualified'; cannot validate some documents

by Joshua Wilson (JIRA)

[ https://issues.jboss.org/browse/JBMETA-367?page=com.atlassian.jira.plugin... ] Joshua Wilson commented on JBMETA-367: -------------------------------------- In my last comment I wrote about how changing the version makes the error go away in Eclipse. While this is true it does not actually allow you to deploy the application to JBoss (where the schema lives). After looking deeper into this I believe that you are right and that the elementFormDefault="unqualified" needs to be changed to elementFormDefault="qualified". > CLONE - XML schema; use of elementFormDefault='unqualified'; cannot validate some documents > ------------------------------------------------------------------------------------------- > > Key: JBMETA-367 > URL: https://issues.jboss.org/browse/JBMETA-367 > Project: JBoss Metadata > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Elias Ross > > When attempting to write a (seemingly) valid jboss-deployment-structure.xml using the schema in ./docs, my document fails to validate. > This is because of the settings used in the XSD. Have these XSDs been used to validate actual documents? By setting unqualified to 'qualified' then the documents will probably validate. > $ git grep elementFormDefault..unqualified > jboss-deployment-dependencies-1_0.xsd: elementFormDefault="unqualified" > jboss-deployment-structure-1_0.xsd: elementFormDefault="unqualified" > jboss-deployment-structure-1_1.xsd: elementFormDefault="unqualified" > jboss-deployment-structure-1_2.xsd: elementFormDefault="unqualified" > jboss-ejb-client_1_0.xsd: elementFormDefault="unqualified" > jboss-ejb-client_1_1.xsd: elementFormDefault="unqualified" > jboss-ejb-client_1_2.xsd: elementFormDefault="unqualified" > jboss-jpa_1_0.xsd: elementFormDefault="unqualified" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2428) MDBs should use the full identifier of the resource adapter

by Jesper Pedersen (JIRA)

Jesper Pedersen created WFLY-2428: ------------------------------------- Summary: MDBs should use the full identifier of the resource adapter Key: WFLY-2428 URL: https://issues.jboss.org/browse/WFLY-2428 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB Affects Versions: 8.0.0.CR1 Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 8.0.0.CR1 The .rar suffix shouldn't be stripped anymore, as the resource adapters are registered under their full name. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-367) CLONE - XML schema; use of elementFormDefault='unqualified'; cannot validate some documents

by Joshua Wilson (JIRA)

[ https://issues.jboss.org/browse/JBMETA-367?page=com.atlassian.jira.plugin... ] Joshua Wilson commented on JBMETA-367: -------------------------------------- I just found that if you use `<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:2.0">` it works. > CLONE - XML schema; use of elementFormDefault='unqualified'; cannot validate some documents > ------------------------------------------------------------------------------------------- > > Key: JBMETA-367 > URL: https://issues.jboss.org/browse/JBMETA-367 > Project: JBoss Metadata > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Elias Ross > > When attempting to write a (seemingly) valid jboss-deployment-structure.xml using the schema in ./docs, my document fails to validate. > This is because of the settings used in the XSD. Have these XSDs been used to validate actual documents? By setting unqualified to 'qualified' then the documents will probably validate. > $ git grep elementFormDefault..unqualified > jboss-deployment-dependencies-1_0.xsd: elementFormDefault="unqualified" > jboss-deployment-structure-1_0.xsd: elementFormDefault="unqualified" > jboss-deployment-structure-1_1.xsd: elementFormDefault="unqualified" > jboss-deployment-structure-1_2.xsd: elementFormDefault="unqualified" > jboss-ejb-client_1_0.xsd: elementFormDefault="unqualified" > jboss-ejb-client_1_1.xsd: elementFormDefault="unqualified" > jboss-ejb-client_1_2.xsd: elementFormDefault="unqualified" > jboss-jpa_1_0.xsd: elementFormDefault="unqualified" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-943) XML schema; use of elementFormDefault='unqualified'; cannot validate some documents

by Joshua Wilson (JIRA)

[ https://issues.jboss.org/browse/WFLY-943?page=com.atlassian.jira.plugin.s... ] Joshua Wilson commented on WFLY-943: ------------------------------------ I guess someone has worked it because I just found that if you use `<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:2.0">` it works. Thanks team! :) > XML schema; use of elementFormDefault='unqualified'; cannot validate some documents > ----------------------------------------------------------------------------------- > > Key: WFLY-943 > URL: https://issues.jboss.org/browse/WFLY-943 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Documentation > Affects Versions: 8.0.0.Alpha3 > Reporter: Elias Ross > Fix For: 8.0.0.CR1 > > Attachments: jboss-deployment-structure.xml > > > When attempting to write a (seemingly) valid jboss-deployment-structure.xml using the schema in ./docs, my document fails to validate. > This is because of the settings used in the XSD. Have these XSDs been used to validate actual documents? By setting unqualified to 'qualified' then the documents will probably validate. > $ git grep elementFormDefault..unqualified > jboss-deployment-dependencies-1_0.xsd: elementFormDefault="unqualified" > jboss-deployment-structure-1_0.xsd: elementFormDefault="unqualified" > jboss-deployment-structure-1_1.xsd: elementFormDefault="unqualified" > jboss-deployment-structure-1_2.xsd: elementFormDefault="unqualified" > jboss-ejb-client_1_0.xsd: elementFormDefault="unqualified" > jboss-ejb-client_1_1.xsd: elementFormDefault="unqualified" > jboss-ejb-client_1_2.xsd: elementFormDefault="unqualified" > jboss-jpa_1_0.xsd: elementFormDefault="unqualified" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-943) XML schema; use of elementFormDefault='unqualified'; cannot validate some documents

by Joshua Wilson (JIRA)

[ https://issues.jboss.org/browse/WFLY-943?page=com.atlassian.jira.plugin.s... ] Joshua Wilson commented on WFLY-943: ------------------------------------ In the version that I use it does NOT have the "p" and I still get the errors. For examples please refer to any of the Spring related [quickstarts|https://github.com/jboss-developer/jboss-wfk-quickstarts/tree...] in the JBoss Web Framework Kit quickstarts. To be clear you need to Build with Eclipse to see the errors. Does anyone know if this is being worked? > XML schema; use of elementFormDefault='unqualified'; cannot validate some documents > ----------------------------------------------------------------------------------- > > Key: WFLY-943 > URL: https://issues.jboss.org/browse/WFLY-943 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Documentation > Affects Versions: 8.0.0.Alpha3 > Reporter: Elias Ross > Fix For: 8.0.0.CR1 > > Attachments: jboss-deployment-structure.xml > > > When attempting to write a (seemingly) valid jboss-deployment-structure.xml using the schema in ./docs, my document fails to validate. > This is because of the settings used in the XSD. Have these XSDs been used to validate actual documents? By setting unqualified to 'qualified' then the documents will probably validate. > $ git grep elementFormDefault..unqualified > jboss-deployment-dependencies-1_0.xsd: elementFormDefault="unqualified" > jboss-deployment-structure-1_0.xsd: elementFormDefault="unqualified" > jboss-deployment-structure-1_1.xsd: elementFormDefault="unqualified" > jboss-deployment-structure-1_2.xsd: elementFormDefault="unqualified" > jboss-ejb-client_1_0.xsd: elementFormDefault="unqualified" > jboss-ejb-client_1_1.xsd: elementFormDefault="unqualified" > jboss-ejb-client_1_2.xsd: elementFormDefault="unqualified" > jboss-jpa_1_0.xsd: elementFormDefault="unqualified" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1716) Regression between 3.2.x and 3.3.x/3.4.x in Infinispan read simulation

by Divya Mehra (JIRA)

[ https://issues.jboss.org/browse/JGRP-1716?page=com.atlassian.jira.plugin.... ] Divya Mehra updated JGRP-1716: ------------------------------ Labels: dm (was: jdg620_dm) > Regression between 3.2.x and 3.3.x/3.4.x in Infinispan read simulation > ---------------------------------------------------------------------- > > Key: JGRP-1716 > URL: https://issues.jboss.org/browse/JGRP-1716 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.3, 3.4 > Reporter: Dan Berindei > Assignee: Bela Ban > Labels: dm > Fix For: 3.4.1, 3.5 > > Attachments: benchmark-jgroups.xml, jgroups-udp.pdf, jgroups-udp.xml > > > Comparing JGroups 3.2/3.3/3.4 performance with Radargun, the throughput of reads in scenario simulating Infinispan went down by ~10%. See the attached chart. > * getall: the get request is sent to single node (randomly picked owner) > * getfirst: the get requests are sent to 2 nodes with ResponseMode.GET_FIRST - the second response is discarded. > .h5 Suspects: > Erik Salter profiled his application and noticed that the message parsing in the UDP receiver thread seemed to slow things down. He wrote a patch that brought his throughput back to 3.2 levels: https://github.com/an1310/JGroups/compare/t_perfhack > The UDP receiver thread may not tell the whole story, however: in the Radargun tests, performance with his patch was even lower. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1722) Improve performance of ENCRYPT protocol

by Divya Mehra (JIRA)

[ https://issues.jboss.org/browse/JGRP-1722?page=com.atlassian.jira.plugin.... ] Divya Mehra updated JGRP-1722: ------------------------------ Labels: 620 (was: jdg620_dm jdg62GAblocker) > Improve performance of ENCRYPT protocol > --------------------------------------- > > Key: JGRP-1722 > URL: https://issues.jboss.org/browse/JGRP-1722 > Project: JGroups > Issue Type: Enhancement > Affects Versions: 3.4 > Reporter: Martin Gencur > Assignee: Bela Ban > Labels: 620 > Fix For: 3.5 > > > A stress tests with the following setup showed that performance (reads and writes/sec) is halved when ENCRYPT protocol is enabled: > Infinispan had distributed sync cache with 2 owners on 4 nodes, no transactions. The stress test used 10 threads on each node accessing 1024 byte entries, no conflicts on keys, 20 % writes, 80 % reads. > It would be great if we could improve the performance of ENCRYPT protocol. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1487) AUTH: X509Token Authentication is vulnerable to replay attacks

by Divya Mehra (JIRA)

[ https://issues.jboss.org/browse/JGRP-1487?page=com.atlassian.jira.plugin.... ] Divya Mehra updated JGRP-1487: ------------------------------ Labels: 620 (was: jdg620_dm jdg62GAblocker) > AUTH: X509Token Authentication is vulnerable to replay attacks > -------------------------------------------------------------- > > Key: JGRP-1487 > URL: https://issues.jboss.org/browse/JGRP-1487 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.0.9 > Reporter: sreenivas chinimilli > Assignee: Bela Ban > Labels: 620 > Fix For: 3.5 > > > In the implementation of X509Token Authentication > The auth_value is enrypted with the certificate within the keystore and > during verification encrypted auth value is decrypted with the private key > compared against the orignial auth value. > This implementation is prone to replay attacks, that is > any user with out having any knowledge of the auth value can join the group > by replaying the enrypted auth value captured in earlier sessions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1721) AUTH and ENCRYPT protocols configured with plain text passwords

by Divya Mehra (JIRA)

[ https://issues.jboss.org/browse/JGRP-1721?page=com.atlassian.jira.plugin.... ] Divya Mehra updated JGRP-1721: ------------------------------ Labels: 620 (was: jdg620_dm jdg62GAblocker) > AUTH and ENCRYPT protocols configured with plain text passwords > --------------------------------------------------------------- > > Key: JGRP-1721 > URL: https://issues.jboss.org/browse/JGRP-1721 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.4 > Reporter: Martin Gencur > Assignee: Bela Ban > Labels: 620 > Fix For: 3.5 > > > The following parameters of AUTH protocol are stored as plain text: > * keystore_password > The following parameters of ENCRYPT protocol are stored as plain text: > * store_password > * key_password > Example: > {code} > <ENCRYPT key_store_name="defaultStore.keystore" store_password="changeit" alias="myKey"/> > {code} > Requirements for storing passwords: https://docspace.corp.redhat.com/docs/DOC-131628 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 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 November 2013