February 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1037) JDBCPersistenceManager.java - reference should be inserted after message (ORA-02291: integrity constraint)

by Mariusz Olejnik (JIRA)

JDBCPersistenceManager.java - reference should be inserted after message (ORA-02291: integrity constraint) ---------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-1037 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1037 Project: JBoss Messaging Issue Type: Patch Components: Messaging Core Persistence Affects Versions: 1.4.0.CR1 Environment: Windows XP / Oracle 10g Reporter: Mariusz Olejnik Assigned To: Tim Fox Priority: Critical Fix For: 1.4.0.CR1 Reference should be inserted after message because: oracle-persistence-service.xml CREATE TABLE JBM_MSG_REF ( CHANNEL_ID INTEGER, MESSAGE_ID INTEGER REFERENCES JBM_MSG(MESSAGE_ID) [...] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

5
5
0 / 0

[JBoss JIRA] Created: (JBRULES-2279) Cached ObjectTypeNodes are not restored when deserializing session

by Kris Verlaenen (JIRA)

Cached ObjectTypeNodes are not restored when deserializing session ------------------------------------------------------------------ Key: JBRULES-2279 URL: https://jira.jboss.org/jira/browse/JBRULES-2279 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (expert) Reporter: Kris Verlaenen Assignee: Edson Tirelli When the InputMarshaller is restoring facts in the working memory, it is using the ObjectTypeNodes of the rete tree to link the facts to their object type nodes. This currently fails if no ObjectTypeNode is present for that type (because the type is not used in a rule somewhere). This ObjectTypeNode should be recreated on request if necessary. -- 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

14 years, 11 months

4
9
0 / 0

[JBoss JIRA] Created: (JBAS-7218) ENC EM injection erroneously happens only once for web modules

by henk de boer (JIRA)

ENC EM injection erroneously happens only once for web modules -------------------------------------------------------------- Key: JBAS-7218 URL: https://jira.jboss.org/jira/browse/JBAS-7218 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.1.0.GA Environment: Observed problem on Mac OS X 10.5.7 and Debian Lenny 64 bits using JDK 6 Reporter: henk de boer Using a persistence-context-ref element in the web.xml of a web module, it appears that this causes an EntityManager instance to be injected only once into the ENC of this component. However, the EJB 3.0 spec states in section 16.2.1: "In general, lookups of objects in the JNDI java: namespace are required to return a new instance of the requested object every time." So the observed behavior seems to violate the spec. In addition, this is particularly troublesome since an EntityManager is explicitly not thread-safe. Using the same EM instance for simultaneous requests therefor doesn't work. Of course there are several other methods to obtain an EM reference, for instance binding an EM factory directly to JNDI and using that to obtain the reference. -- 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

14 years, 11 months

6
11
0 / 0

[JBoss JIRA] Created: (JBXB-209) Enum parsing requires value equal to type name

by Thomas Diesler (JIRA)

Enum parsing requires value equal to type name ---------------------------------------------- Key: JBXB-209 URL: https://jira.jboss.org/jira/browse/JBXB-209 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Affects Versions: JBossXB-2.0.1.GA Reporter: Thomas Diesler Caused by: java.lang.RuntimeException: Invalid value mandatory valid are [MANDATORY, OPTIONAL] at org.jboss.xb.builder.runtime.EnumValueAdapter.cast(EnumValueAdapter.java:136) at org.jboss.xb.builder.runtime.AbstractPropertyHandler.attribute(AbstractPropertyHandler.java:115) at org.jboss.xb.binding.sunday.unmarshalling.AttributesHandler.attributes(AttributesHandler.java:51) at org.jboss.xb.binding.sunday.unmarshalling.DefaultElementHandler.attributes(DefaultElementHandler.java:65) at org.jboss.xb.builder.runtime.BeanHandler.startParticle(BeanHandler.java:124) at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:630) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) public enum TAvailability { MANDATORY("mandatory"), OPTIONAL("optional"); private final String value; TAvailability(String v) { value = v; } public String value() { return value; } public static TAvailability fromValue(String v) { for (TAvailability c : TAvailability.values()) { if (c.value.equals(v)) { return c; } } throw new IllegalArgumentException(v); } } -- 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

14 years, 12 months

1
2
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-435) Aggregate the respective API docs

by Thomas Diesler (JIRA)

Aggregate the respective API docs --------------------------------- Key: JBMICROCONT-435 URL: https://jira.jboss.org/jira/browse/JBMICROCONT-435 Project: JBoss Microcontainer Issue Type: Task Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossMC-2.2.x -- 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

14 years, 12 months

2
8
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1287) EJB3 client with service-ref

by Thomas Diesler (JIRA)

EJB3 client with service-ref ---------------------------- Key: EJBTHREE-1287 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1287 Project: EJB 3.0 Issue Type: Sub-task Reporter: Thomas Diesler -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

2
6
0 / 0

[JBoss JIRA] Created: (JBCL-133) Add resolver preferences

by Thomas Diesler (JIRA)

Add resolver preferences ------------------------ Key: JBCL-133 URL: https://jira.jboss.org/jira/browse/JBCL-133 Project: JBoss ClassLoader Issue Type: Sub-task Reporter: Thomas Diesler -- 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

14 years, 12 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-415) Comprehensive deployer framework documentation

by Thomas Diesler (JIRA)

Comprehensive deployer framework documentation ---------------------------------------------- Key: JBMICROCONT-415 URL: https://jira.jboss.org/jira/browse/JBMICROCONT-415 Project: JBoss Microcontainer Issue Type: Task Components: Deployment Reporter: Thomas Diesler Fix For: JBossMC-2.2.x Please provide comprehensive documentation for the deployer framework. It should cover the individual types of deployers, deployment states, dependency items, modules, etc. Improved javadoc is also covered by this issue. For trunk it is possible to publish the javadoc in the hudson QA environment. -- 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

14 years, 12 months

2
7
0 / 0

[JBoss JIRA] Created: (JBXB-201) Cannot parse schema/jbxb_1_0.xsd

by Thomas Diesler (JIRA)

Cannot parse schema/jbxb_1_0.xsd -------------------------------- Key: JBXB-201 URL: https://jira.jboss.org/jira/browse/JBXB-201 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Reporter: Thomas Diesler This code String jbxbSchema = "schema/jbxb_1_0.xsd"; URL jbxbXSD = context.getBundle().getResource(jbxbSchema); if (jbxbXSD == null) throw new IllegalStateException("Cannot find: " + jbxbSchema); XSModel xsModel = Util.loadSchema(jbxbXSD.toExternalForm(), (SchemaBindingResolver)null); if (xsModel == null) throw new IllegalStateException("Cannot load schema: " + jbxbSchema); fails with Caused by: org.jboss.xb.binding.JBossXBRuntimeException: -1:-1 94:47 src-element.3: Element 'class' has both a 'type' attribute and a 'anonymous type' child. Only one of these is allowed for an element. at org.jboss.xb.binding.sunday.unmarshalling.XsdBinderTerminatingErrorHandler.handleError(XsdBinderTerminatingErrorHandler.java:40) at org.apache.xerces.impl.xs.XMLSchemaLoader.reportDOMFatalError(Unknown Source) at org.apache.xerces.impl.xs.XSLoaderImpl.loadURI(Unknown Source) at org.jboss.xb.binding.Util.loadSchema(Util.java:367) -- 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

14 years, 12 months

1
3
0 / 0

[JBoss JIRA] Created: (JBXB-202) Incosistent initialization of XSImplementation

by Thomas Diesler (JIRA)

Incosistent initialization of XSImplementation ---------------------------------------------- Key: JBXB-202 URL: https://jira.jboss.org/jira/browse/JBXB-202 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Reporter: Thomas Diesler Fix For: JBossXB-2.0.1.GA In Util there is private static XSImplementation xsImpl; which gets initialized lazily in public static XSModel loadSchema(String xsdURL, SchemaBindingResolver schemaResolver) { if(xsImpl == null) { xsImpl = getXSImplementation(); } All other loadSchema method do not reuse the static property Also, private static XSImplementation getXSImplementation() relies on the thread context classloader, which is not available in an OSGi environment. Could you please provide an JBossXB initialization entry point that is public and does not make an assumption on the availability of the TCCL -- 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

14 years, 12 months

1
3
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 2010