October 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8531) Migrate OSGi subsytem to modules 1.0.0.Beta7

by Thomas Diesler (JIRA)

Migrate OSGi subsytem to modules 1.0.0.Beta7 -------------------------------------------- Key: JBAS-8531 URL: https://jira.jboss.org/browse/JBAS-8531 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: OSGi integration Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.0.0.M1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2185) SessionProxyInvocationHandlerBase invokeEquals() doesn't take into account the business interface type of the proxies

by jaikiran pai (JIRA)

SessionProxyInvocationHandlerBase invokeEquals() doesn't take into account the business interface type of the proxies --------------------------------------------------------------------------------------------------------------------- Key: EJBTHREE-2185 URL: https://jira.jboss.org/browse/EJBTHREE-2185 Project: EJB 3.0 Issue Type: Bug Components: proxy-impl Affects Versions: depchain-1.0.0-alpha-4 Reporter: jaikiran pai Assignee: jaikiran pai EJB 3.0 Specification 3.4.5.2: "All business object references of the same interface type for the same stateless session bean have the same object identity, which is assigned by the container. ... Session bean references to either different business interface types or different session beans will not be equal." The SessionProxyInvocationHandlerBase.invokeEquals() however doesn't take into account the business interface type of the proxies and thus violates this contract. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2182) EJBRemoteHandler doesn't take into account @EJB.beanInterface while creating ENC injectors

by jaikiran pai (JIRA)

EJBRemoteHandler doesn't take into account @EJB.beanInterface while creating ENC injectors ------------------------------------------------------------------------------------------ Key: EJBTHREE-2182 URL: https://jira.jboss.org/browse/EJBTHREE-2182 Project: EJB 3.0 Issue Type: Bug Components: core Affects Versions: depchain-1.0.0-alpha-4 Reporter: jaikiran pai Assignee: jaikiran pai If a field/method has a @EJB(beanInterface="...") then the beanInterface attribute is not taken into account while creating the ENC injector in EJBRemoteHandler. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2164) Create LinkRefs in java:global namespace for EJB3.1 beans

by jaikiran pai (JIRA)

Create LinkRefs in java:global namespace for EJB3.1 beans ---------------------------------------------------------- Key: EJBTHREE-2164 URL: https://jira.jboss.org/browse/EJBTHREE-2164 Project: EJB 3.0 Issue Type: Task Reporter: jaikiran pai Assignee: jaikiran pai We currently don't bind to java:global JNDI namespace. Create a deployer which creates LinkRefs in java:global namespace to our internal jndi names. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2180) EJB3.1 spec jndi binder should only apply for EJB3.1 beans

by jaikiran pai (JIRA)

EJB3.1 spec jndi binder should only apply for EJB3.1 beans ---------------------------------------------------------- Key: EJBTHREE-2180 URL: https://jira.jboss.org/browse/EJBTHREE-2180 Project: EJB 3.0 Issue Type: Bug Reporter: jaikiran pai Assignee: jaikiran pai Currently, we even include EJB3.0 beans during EJBBinder creation. Only EJB3.1 beans should be eligible. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2724) OOME on Marshalling (JPA), caused by infinite cycle on OutputMarshaller.writeLeftTuple

by Dan Danciu (JIRA)

OOME on Marshalling (JPA), caused by infinite cycle on OutputMarshaller.writeLeftTuple -------------------------------------------------------------------------------------- Key: JBRULES-2724 URL: https://jira.jboss.org/browse/JBRULES-2724 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (expert) Affects Versions: 5.1.1.FINAL Environment: OpenSuse Linux, java version "1.6.0_21" Reporter: Dan Danciu Assignee: Mark Proctor When trying to marshal my stateful session (spring configured) using JPA, the tests failed with OutOfMemoryError. After tracing the OOEM, I found the fault in a infinite loop in org.drools.marshalling.impl.OutputMarshaller, method writeLeftTuple, for the cases: NodeTypeEnums.NotNode, NodeTypeEnums.ForallNotNode and NodeTypeEnums.ExistsNode. The problem was that childLeftTuple was not taken from childLeftTuple but from leftTuple, causing the infinite loop. Sorry, I cannot give you more info on how to reproduce the problem, for us it appears only in an certain integration test, but I did create a patch, and our code works with it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (LOGMGR-25) logrb(*) doesn't work

by David Lloyd (JIRA)

logrb(*) doesn't work --------------------- Key: LOGMGR-25 URL: https://jira.jboss.org/browse/LOGMGR-25 Project: JBoss Log Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: core Affects Versions: 1.2.0.CR7, 1.1.1.GA, 1.1.0.GA Reporter: David Lloyd Assignee: David Lloyd Fix For: 1.1.2.CR1, 1.2.0.CR8 Since LogManager started overriding logrb, those methods have never looked up the appropriate resource bundle. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBJCA-444) Register admin objects in JNDI

by Jesper Pedersen (JIRA)

Register admin objects in JNDI ------------------------------ Key: JBJCA-444 URL: https://jira.jboss.org/browse/JBJCA-444 Project: IronJacamar Issue Type: Task Components: Core, Deployer Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Beta3 Bind AdminObjects in JNDI based on the information in ironjacamar.xml or -ra.xml -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8510) Archive being scanned even though no beans.xml is present

by Stuart Douglas (JIRA)

Archive being scanned even though no beans.xml is present --------------------------------------------------------- Key: JBAS-8510 URL: https://jira.jboss.org/browse/JBAS-8510 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Weld/CDI Reporter: Stuart Douglas Assignee: Marius Bogoevici When using the latest jboss as snapshot from hudson weld-extensions tests fail. It appears this is because the weld-extensions jar is being scanned and the annotated types added even though there is no beans.xml in the archive. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

4
10
0 / 0

[JBoss JIRA] Commented: (JBBUILD-655) Wrong checksum on jboss maven repository

by Paul Gier (JIRA)

[ https://jira.jboss.org/browse/JBBUILD-655?page=com.atlassian.jira.plugin.... ] Paul Gier commented on JBBUILD-655: ----------------------------------- These artifacts were never deployed to the JBoss repository because they went directly to Maven central. Maybe we should just exclude everything under "org/jboss/*" from being pulled in from the Glassfish repo since everything under that groupId should be coming from either central or our repository. > Wrong checksum on jboss maven repository > ---------------------------------------- > > Key: JBBUILD-655 > URL: https://jira.jboss.org/browse/JBBUILD-655 > Project: JBoss Build System > Issue Type: Bug > Components: Artifact Repositories > Reporter: Fabricio Lemos > > Some POMs are with the wrong checksum on Jboss Maven Repository, which causes artifactory to reject those POMs if validation is on. > Here a few examples of artifactory output: > jboss: Downloaded 'http://repository.jboss.org/nexus/content/groups/public/org/jboss/weld/we...' with return code: 200. > (o.a.r.v.i.PomInterceptor:78) - Failed to transform pom file > java.io.IOException: Checksum policy 'GEN_IF_ABSENT' rejected the artifact 'weld-api-bom-1.0-SP1.pom'. Checksums info: [ChecksumInfo{type=SHA-1, original='11c59ba0129c15a2966adf7b993552ac0e38f5db', actual='a682982a8c581b327c79b6ef5dd239005cf4d30b'}, ChecksumInfo{type=MD5, original='645ce7c04f2650ec80b54ace02b4c1b9', actual='1f00ec3b8241348739fbb1544b53aef5'}] > (o.a.r.HttpRepo :196) - jboss: Downloaded 'http://repository.jboss.org/nexus/content/groups/public/org/jboss/weld/we...' with return code: 200. > [ERROR] (o.a.r.v.i.PomInterceptor:78) - Failed to transform pom file > java.io.IOException: Checksum policy 'GEN_IF_ABSENT' rejected the artifact 'weld-core-bom-1.0.1-Final.pom'. Checksums info: [ChecksumInfo{type=SHA-1, original='05c018953796d43baaec6b7b526883116fb4ba4c', actual='9c1d4f3ba941405a2717081d29e2b542934a69d7'}, ChecksumInfo{type=MD5, original='98167a84f872b7d2ab07c4826269cff5', actual='de063cceee5e38a7b0b9b8d82930aebb'}] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 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 October 2010