March 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBAS-3202) Extend the xpath test coverage

by Dimitris Andreadis (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-3202?page=com.atlassian.jira.plug... ] Dimitris Andreadis updated JBAS-3202: ------------------------------------- Comment: was deleted > Extend the xpath test coverage > ------------------------------ > > Key: JBAS-3202 > URL: https://jira.jboss.org/jira/browse/JBAS-3202 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Test Suite, XML services > Reporter: Dimitris Andreadis > Assignee: Aaron Walker > > Extend the jaxp XPath API test coverage after the inital tests introduced by JBAS-2411 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCL-93) @XmlType for CapabilitiesMetaData spells 'capabilities' wrong

by Kabir Khan (JIRA)

@XmlType for CapabilitiesMetaData spells 'capabilities' wrong ------------------------------------------------------------- Key: JBCL-93 URL: https://jira.jboss.org/jira/browse/JBCL-93 Project: JBoss ClassLoader Issue Type: Bug Affects Versions: JBossCL.2.0.3.GA Reporter: Kabir Khan Assignee: Ales Justin Fix For: JBossCL.2.2.0.Alpha It says: @XmlType(name="capabilties", propOrder= {"capabilities"}) public class CapabilitiesMetaData implements Serializable, Cloneable should probably be: @XmlType(name="capabilities", propOrder= {"capabilities"}) public class CapabilitiesMetaData implements Serializable, Cloneable -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMETA-181) Upgrade jbossxb to 2.0.1.Beta2

by Alexey Loubyansky (JIRA)

Upgrade jbossxb to 2.0.1.Beta2 ------------------------------ Key: JBMETA-181 URL: https://jira.jboss.org/jira/browse/JBMETA-181 Project: JBoss Metadata Issue Type: Thirdparty Change Security Level: Public (Everyone can see) Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 1.0.0.CR17 CR17 requires at least XB 2.0.1.Beta2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-6306) Break hibernate-annotations.jar on server/lib into three (the original ones)

by Rodolfo Rothganger (JIRA)

Break hibernate-annotations.jar on server/lib into three (the original ones) ---------------------------------------------------------------------------- Key: JBAS-6306 URL: https://jira.jboss.org/jira/browse/JBAS-6306 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ClassLoading Affects Versions: JBossAS-4.2.3.GA Environment: Windowx XP 32 Bits Reporter: Rodolfo Rothganger Assignee: Scott M Stark Currently I am developing an application that includes hibernate-3.2.6.jar and hibernate annotations WITHOUT hibernate validator on a proper classloading isolation (EAR) config. Since hibernate relies on the presence of validator classes to enable/disbale validation (regardless of the classloader it´s associate with, child or parent) I had to remove the hibernate-annotations.jar from my server/lib directory and replace it with a version WITHOUT hibernate-validator. My request is: to break the hibernate-annotations.jar file in three (the original ones): hibernate-annotations.jar, hibernate-core-annotations.jar and hibernate-validator.jar. Note: the actual problem is not the presence of hibernate-validator on the classpath but the fact that this is an outdated non-compatible with hibernate 3.2.6 version. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (JBXB-188) make sure the testsuite can be run with unordered sequences as the default

by Alexey Loubyansky (JIRA)

make sure the testsuite can be run with unordered sequences as the default -------------------------------------------------------------------------- Key: JBXB-188 URL: https://jira.jboss.org/jira/browse/JBXB-188 Project: JBoss XML Binding (JBossXB) Issue Type: Task Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: JBossXB-2.0.1.CR1 With few exceptions, the testsuite shouldn't depend on whether ordered or unordered sequences are used. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBXB-187) UnorderedSequenceBinding: incorrect parent group for repeated particle

by Alexey Loubyansky (JIRA)

UnorderedSequenceBinding: incorrect parent group for repeated particle ---------------------------------------------------------------------- Key: JBXB-187 URL: https://jira.jboss.org/jira/browse/JBXB-187 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Affects Versions: JBossXB-2.0.1.Beta2 Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: JBossXB-2.0.1.CR1 When current particle is repeated, startElement is called on the unordered sequence group itself instead of the current model group. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBXB-193) repeatable all group is unmarshalled into the same group instance

by Alexey Loubyansky (JIRA)

repeatable all group is unmarshalled into the same group instance ----------------------------------------------------------------- Key: JBXB-193 URL: https://jira.jboss.org/jira/browse/JBXB-193 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Affects Versions: JBossXB-2.0.1.Beta2 Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky There is a testcase for this issue org.jboss.test.xb.builder.object.type.jbossxmlmodelgroup.test.RepeatablePropertyAllUnmarshallingTestCase. The problem is XB doesn't create a new group when it should. For example for a gorup of a, b and c <root> <b>b</b> <c>c</c> <b>bb</b> <a>aa</a> </root> will be unmarshalled into the same group instance overriding the previous value of b. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1765) Unify InvocationHandlers into one implementation

by Andrew Lee Rubinger (JIRA)

Unify InvocationHandlers into one implementation ------------------------------------------------ Key: EJBTHREE-1765 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1765 Project: EJB 3.0 Issue Type: Task Components: proxy Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: 1.1.3 With SessionProxy.getTarget(), session IDs fall out of scope and therefore InvocationHandlers may be shared for SLSB/SFSB/@Service. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1970) Error expanding DSL when #-Character is in right-side of dsl-property

by Norbert Ziegler (JIRA)

Error expanding DSL when #-Character is in right-side of dsl-property --------------------------------------------------------------------- Key: JBRULES-1970 URL: https://jira.jboss.org/jira/browse/JBRULES-1970 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.0.0.M5 Environment: Eclipse 3.4, jre6u10, WinXp Reporter: Norbert Ziegler Assignee: Mark Proctor Having a line in a DSL like following: [condition][]Bedingung-19-MKM4 = eval ( $p.getTempVal("#UML-ATZ-1") < $p.getZvUmlStfr() ) Using "Bedingung-19-MKM4" in the LHS of a rule "Regel-151" in an dslr-File I get the following 3 errors: [12] Unable to expand: Bedingung-19-MKM4 [ERR 103] Line 201:2 no viable alternative at input 'Bedingung' in rule "Regel-151" Unknown error while parsing. This is a bug. Please contact the Development team. The problem is the #-Character. If you change the line to [condition][]Bedingung-19-MKM4 = eval ( $p.getTempVal("UML-ATZ-1") < $p.getZvUmlStfr() ) it works. But that's not what I need. Hint: maybe this is related to (JBRULES-1960) Syntaxcoloring wrong if DSLR contains a "#"-Character. But in this case it's more important because it's not an "optical" problem only. By the way: if I use the value #UML-ATZ-1 as an argument / placeholder it works (thank God, need this often). But using a placeholder is not what I need. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-6470) Open console support blockers

by Scott M Stark (JIRA)

Open console support blockers ----------------------------- Key: JBAS-6470 URL: https://jira.jboss.org/jira/browse/JBAS-6470 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Management services, ProfileService Reporter: Scott M Stark Assignee: Scott M Stark Priority: Blocker Fix For: JBossAS-5.1.0.Beta1 Updated task for the open console support issues that are blocking the embedded console -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

2
1
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 March 2009