November 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Reopened: (JBMICROCONT-93) Add JBossRetro builds for Microcontainer projects

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBMICROCONT-93?page=all ] Adrian Brock reopened JBMICROCONT-93: ------------------------------------- > Add JBossRetro builds for Microcontainer projects > ------------------------------------------------- > > Key: JBMICROCONT-93 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-93 > Project: JBoss MicroContainer > Issue Type: Sub-task > Components: General > Reporter: Adrian Brock > Assigned To: Paul Gier > Fix For: JBossMC-2.0.0.Beta7 > > > Make JBossRetro builds for the microcontainer projects > such that they can use JDK5 features. -- 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

17 years, 1 month

1
0
0 / 0

[JBoss JIRA] Closed: (JBMICROCONT-93) Add JBossRetro builds for Microcontainer projects

by Adrian Brock (JIRA)

[ http://jira.jboss.com/jira/browse/JBMICROCONT-93?page=all ] Adrian Brock closed JBMICROCONT-93. ----------------------------------- Fix Version/s: JBossMC-2.0.0.Beta7 (was: JBossMC-2.0.0.CR1) Resolution: Done > Add JBossRetro builds for Microcontainer projects > ------------------------------------------------- > > Key: JBMICROCONT-93 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-93 > Project: JBoss MicroContainer > Issue Type: Sub-task > Components: General > Reporter: Adrian Brock > Assigned To: Paul Gier > Fix For: JBossMC-2.0.0.Beta7 > > > Make JBossRetro builds for the microcontainer projects > such that they can use JDK5 features. -- 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

17 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-216) Drop the DeploymentUnit.getTypes

by Scott M Stark (JIRA)

Drop the DeploymentUnit.getTypes -------------------------------- Key: JBMICROCONT-216 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-216 Project: JBoss MicroContainer Issue Type: Task Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossMC-2.0.0.CR1 The deployment unit types qualifiers should be part of the management view, not part of the DeploymentUnit api. -- 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

17 years, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-1045) test suite has to trow a runtime exception on error so meaningful report is generated

by Aleksandar Kostadinov (JIRA)

test suite has to trow a runtime exception on error so meaningful report is generated ------------------------------------------------------------------------------------- Key: JBPM-1045 URL: http://jira.jboss.com/jira/browse/JBPM-1045 Project: JBoss jBPM Issue Type: Bug Affects Versions: jBPM jPDL 3.2.2 Reporter: Aleksandar Kostadinov Assigned To: Tom Baeyens When there are test suite initialization problems, test suite ignores exception (just prints it to the output) that causes junit to crash. I identified the issue in the following files: jpdl/jar/src/test/java/org/jbpm/AllDBTests.java jpdl/jar/src/test/java/org/jbpm/AllTests.java have to have "throw t;" after "t.printStackTrace();" As well the following test cases seem suspicious to me. I mean I'm not sure if an exception by these tests will cause a test suite crash. Please inspect if trowing an axception is desirable after printStackTrace method is used in these files: ./msg/command/AsyncExecutionDbTest.java ./perf/MemLeakTest.java -- 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

17 years, 1 month

3
8
0 / 0

[JBoss JIRA] Created: (JBREM-792) Provide to the client local address of a TCP/IP connection, as seen from the server

by Ron Sigal (JIRA)

Provide to the client local address of a TCP/IP connection, as seen from the server ----------------------------------------------------------------------------------- Key: JBREM-792 URL: http://jira.jboss.com/jira/browse/JBREM-792 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.4.0.Beta1 (Pinto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.4.0.Beta1 (Pinto) When org.jboss.remoting.Client.addListener() creates a callback org.jboss.remoting.transport.Connector, by default it calls InetAddress.getLocalHost().getHostAddress() to get a local address for the callback org.jboss.remoting.InvokerLocator. If the machine happens to have multiple addresses, getLocalHost() might return the wrong one. A solution, due to Ovidiu Feodorov, is to implement an internal invocation to which the server replies by returning the remote address of the connection over which the invocation was made. This solution has been implemented for the socket transport (and bisocket, by inheritance) in conjunction with JBREM-781. It should be implemented for the other transports. -- 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

17 years, 1 month

1
4
0 / 0

[JBoss JIRA] Created: (JBREM-758) Associate remote socket address with the invocation

by Carlo de Wolf (JIRA)

Associate remote socket address with the invocation --------------------------------------------------- Key: JBREM-758 URL: http://jira.jboss.com/jira/browse/JBREM-758 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Carlo de Wolf Add remote socket address to the InvocationRequest to allow it to be used for auditing and filtering. -- 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

17 years, 1 month

2
7
0 / 0

[JBoss JIRA] Created: (JGRP-633) Connection table should remove connection that throws Exception

by Vladimir Blagojevic (JIRA)

Connection table should remove connection that throws Exception --------------------------------------------------------------- Key: JGRP-633 URL: http://jira.jboss.com/jira/browse/JGRP-633 Project: JGroups Issue Type: Bug Affects Versions: 2.6 Reporter: Vladimir Blagojevic Assigned To: Vladimir Blagojevic Priority: Minor Fix For: 2.6.1, 2.7 When reading thread that fetches data from a peer connection encounters Exception that is caused by broken socket it should remove related connection object from connection table. -- 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

17 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1813) Switching to secured login should be enabled by configuration

by Thomas Heute (JIRA)

Switching to secured login should be enabled by configuration ------------------------------------------------------------- Key: JBPORTAL-1813 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1813 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Core Reporter: Thomas Heute Assigned To: Thomas Heute Fix For: 2.6.3 Final -- 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

17 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-3423) Fix org.jboss.test.cmp2.commerce.CompleteUnitTestCase in HEAD

by Anil Saldhana (JIRA)

Fix org.jboss.test.cmp2.commerce.CompleteUnitTestCase in HEAD ------------------------------------------------------------- Key: JBAS-3423 URL: http://jira.jboss.com/jira/browse/JBAS-3423 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: CMP service Reporter: Anil Saldhana Assigned To: Alexey Loubyansky Fix For: JBossAS-5.0.0.Beta Could you please have a look at why the tests "testJBossQL, testEJBQL" are failing? ========================================================================================== Expected: SELECT t0_o1.ORDER_NUMBER FROM ORDER_DATA t0_o1, ORDER_DATA t3_o2, CUSTOMEREJB t1_o1_customer, CUSTOMEREJB t2_o2_customer WHERE (( NOT (t1_o1_customer.id=t2_o2_customer.id)) AND (t0_o1.CC_TYPE=t3_o2.CC_TYPE AND t0_o1.CC_FIRST_NAME=t3_o2.CC_FIRST_NAME AND t0_o1.CC_MI=t3_o2.CC_MI AND t0_o1.CC_LAST_NAME=t3_o2.CC_LAST_NAME AND t0_o1.CC_BILLING_ZIP=t3_o2.CC_BILLING_ZIP AND t0_o1.CC_CARD_NUMBER=t3_o2.CC_CARD_NUMBER) AND t0_o1.customer=t1_o1_customer.id AND t3_o2.customer=t2_o2_customer.id) but got: SELECT t0_o1.ORDER_NUMBER FROM ORDER_DATA t0_o1, ORDER_DATA t3_o2, CUSTOMEREJB t2_o2_customer, CUSTOMEREJB t1_o1_customer WHERE (( NOT (t1_o1_customer.id=t2_o2_customer.id)) AND (t0_o1.CC_TYPE=t3_o2.CC_TYPE AND t0_o1.CC_FIRST_NAME=t3_o2.CC_FIRST_NAME AND t0_o1.CC_MI=t3_o2.CC_MI AND t0_o1.CC_LAST_NAME=t3_o2.CC_LAST_NAME AND t0_o1.CC_BILLING_ZIP=t3_o2.CC_BILLING_ZIP AND t0_o1.CC_CARD_NUMBER=t3_o2.CC_CARD_NUMBER) AND t3_o2.customer=t2_o2_customer.id AND t0_o1.customer=t1_o1_customer.id) junit.framework.AssertionFailedError: Expected: SELECT t0_o1.ORDER_NUMBER FROM ORDER_DATA t0_o1, ORDER_DATA t3_o2, CUSTOMEREJB t1_o1_customer, CUSTOMEREJB t2_o2_customer WHERE (( NOT (t1_o1_customer.id=t2_o2_customer.id)) AND (t0_o1.CC_TYPE=t3_o2.CC_TYPE AND t0_o1.CC_FIRST_NAME=t3_o2.CC_FIRST_NAME AND t0_o1.CC_MI=t3_o2.CC_MI AND t0_o1.CC_LAST_NAME=t3_o2.CC_LAST_NAME AND t0_o1.CC_BILLING_ZIP=t3_o2.CC_BILLING_ZIP AND t0_o1.CC_CARD_NUMBER=t3_o2.CC_CARD_NUMBER) AND t0_o1.customer=t1_o1_customer.id AND t3_o2.customer=t2_o2_customer.id) but got: SELECT t0_o1.ORDER_NUMBER FROM ORDER_DATA t0_o1, ORDER_DATA t3_o2, CUSTOMEREJB t2_o2_customer, CUSTOMEREJB t1_o1_customer WHERE (( NOT (t1_o1_customer.id=t2_o2_customer.id)) AND (t0_o1.CC_TYPE=t3_o2.CC_TYPE AND t0_o1.CC_FIRST_NAME=t3_o2.CC_FIRST_NAME AND t0_o1.CC_MI=t3_o2.CC_MI AND t0_o1.CC_LAST_NAME=t3_o2.CC_LAST_NAME AND t0_o1.CC_BILLING_ZIP=t3_o2.CC_BILLING_ZIP AND t0_o1.CC_CARD_NUMBER=t3_o2.CC_CARD_NUMBER) AND t3_o2.customer=t2_o2_customer.id AND t0_o1.customer=t1_o1_customer.id) at org.jboss.test.cmp2.commerce.QueryTest.testJBossQL(QueryTest.java:173) at net.sourceforge.junitejb.EJBTestCase.runBare(EJBTestCase.java:133) at net.sourceforge.junitejb.EJBTestRunnerBean.runTestCase(EJBTestRunnerBean.java:102) at net.sourceforge.junitejb.EJBTestRunnerBean.run(EJBTestRunnerBean.java:44) at org.jboss.invocation.Invocation.performCall(Invocation.java:359) at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:228) at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:158) at org.jboss.ws.server.ServiceEndpointInterceptor.invoke(ServiceEndpointInterceptor.java:39) at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:63) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:121) at org.jboss.ejb.plugins.AbstractTxInterceptorBMT.invokeNext(AbstractTxInterceptorBMT.java:173) at org.jboss.ejb.plugins.TxInterceptorBMT.invoke(TxInterceptorBMT.java:77) at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:168) at org.jboss.ejb.plugins.SecurityAuthorizationInterceptor.invoke(SecurityAuthorizationInterceptor.java:105) at org.jboss.ejb.plugins.JaasAuthenticationInterceptor.invoke(JaasAuthenticationInterceptor.java:146) at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205) at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:136) at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:646) at org.jboss.ejb.Container.invoke(Container.java:974) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) ========================================================================================= -- 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

17 years, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (JBAOP-488) Improve AOPContainerProxy.toString()

by Kabir Khan (JIRA)

Improve AOPContainerProxy.toString() ------------------------------------ Key: JBAOP-488 URL: http://jira.jboss.com/jira/browse/JBAOP-488 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.0.0.beta2 Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.CR1 how to aviod such info [10:30:59] Ales Justin says: 19:15:46,937 TRACE [VFSStructuralDeployersImpl] client1-not.ajar recognised by org.jboss.deployers.vfs.plugins.structure.file.AOPContainerProxy$0@1c4a5ec [10:31:13] Ales Justin says: where the real deployer was aspectized [10:31:37] Ales Justin says: and the info was: "recognized by " + deployer [10:32:04] Kabir Khan says: So you would rather have the"real name of the class [10:32:09] Kabir Khan says: Not sure... [10:32:17] Ales Justin says: is there a way to config AOPContProxy to call target's toString [10:32:35] Kabir Khan says: I guess that could be added to the proxy [10:33:12] Kabir Khan says: I'd still like to have some information there that it was proxied [10:33:41] Ales Justin says: sure [10:33:52] Ales Justin says: but also the important info should be there [10:33:59] Ales Justin says: since [10:34:07] Kabir Khan says: client1-not.ajar recognised by org.jboss.deployers.vfs.plugins.structure.file.WhateverDeployer@121212d (proxied by org.jboss.deployers.vfs.plugins.structure.file.AOPContainerProxy$0@1c4a5ec) [10:34:13] Kabir Khan says: Something like that? [10:34:17] Ales Justin says: here I'm clueless to which deployer actually did the work [10:34:31] Ales Justin says: yup -- 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

17 years, 1 month

1
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2007