September 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (JBAS-3154) Cleanup the remoting module in 3.2.x

by Dimitris Andreadis (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-3154?page=com.atlassian.jira.plug... ] Dimitris Andreadis closed JBAS-3154. ------------------------------------ Resolution: Out of Date Assignee: (was: Tom Elrod) > Cleanup the remoting module in 3.2.x > ------------------------------------ > > Key: JBAS-3154 > URL: https://jira.jboss.org/jira/browse/JBAS-3154 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Remoting > Affects Versions: JBossAS-3.2.8.SP1 > Reporter: Dimitris Andreadis > > Having removed the sources with proprietary licenses and files depending on them (all of them are tests), we need to further cleanup the remoting module in 3.2.x. As far I can tell, this is obsolete. There is only a remoting.sar installed in docs\example\remoting, who's META-INF descriptor needs renaming to jboss-service.xml to deploy properly (it does deploy with this change). > The files removed where: > src/main/test/classloading/InvokerTestCase.java > src/main/test/ComplexReturn.java > InvokerClientTest.java InvokerServerTest.java > InvokerTestCase.java OnewayInvokerServerTest.java > OnewayInvokerTestCase.java > src/main/test/classloading/server/InvokerServerNoClientTest.java > InvokerServerNoSecurityTest.java > InvokerServerNoServerTest.java > InvokerServerSecureTest.java > src/main/test/detection/DetectorUtil.java > src/main/org/jboss/remoting/transport/test/TransportTest.java > src/main/org/jboss/remoting/transport/mock/MockServerInvocationHandler.java MockTest.java > src/main/test/performance/TestServerInvocationHandler.java -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCL-37) Update to jboss-test 1.1.1.GA

by Adrian Brock (JIRA)

Update to jboss-test 1.1.1.GA ----------------------------- Key: JBCL-37 URL: https://jira.jboss.org/jira/browse/JBCL-37 Project: JBoss ClassLoader Issue Type: Component Upgrade Reporter: Adrian Brock Assignee: Adrian Brock -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCL-42) Update to jboss-classloading-spi 5.0.0.CR2

by Adrian Brock (JIRA)

Update to jboss-classloading-spi 5.0.0.CR2 ------------------------------------------ Key: JBCL-42 URL: https://jira.jboss.org/jira/browse/JBCL-42 Project: JBoss ClassLoader Issue Type: Component Upgrade Reporter: Adrian Brock Assignee: Adrian Brock -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCL-36) Update to jboss-common-core 2.2.8.GA

by Adrian Brock (JIRA)

Update to jboss-common-core 2.2.8.GA ------------------------------------ Key: JBCL-36 URL: https://jira.jboss.org/jira/browse/JBCL-36 Project: JBoss ClassLoader Issue Type: Component Upgrade Components: Release Reporter: Adrian Brock Assignee: Adrian Brock Fix For: JBossCL.2.0.0.CR2 -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5918) Hudson builds erroneously report builds as failed after ant upgrade

by Dimitris Andreadis (JIRA)

Hudson builds erroneously report builds as failed after ant upgrade ------------------------------------------------------------------- Key: JBAS-5918 URL: https://jira.jboss.org/jira/browse/JBAS-5918 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Assignee: Aleksandar Kostadinov Priority: Critical Fix For: JBossAS-5.0.0.CR2 After Scott upgraded the ant used in AS trunk from 1.6.5 to 1.7.1, all hudson testsuite builds are marked as failed, e.g. http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test... I've configured hudson to keep testsuite/output/tests.log & testsuite/output/log/test.log but they don't offer any useful information. In fact, testsuite/output/tests.log gets overwriten with useless info: BUILD FAILED /qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-jrockit15/trunk/testsuite/build.xml:968: Some servers failed to shutdown cleanly. at org.apache.tools.ant.taskdefs.Exit.execute(Exit.java:142) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:357) at org.apache.tools.ant.Target.performTasks(Target.java:385) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337) at org.apache.tools.ant.Project.executeTarget(Project.java:1306) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) at org.apache.tools.ant.Project.executeTargets(Project.java:1189) at org.apache.tools.ant.Main.runBuild(Main.java:758) at org.apache.tools.ant.Main.startAnt(Main.java:217) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104) -- 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, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (JBAS-5928) port imaps/pops change into Branch_4_2

by Jeff Zhang (JIRA)

port imaps/pops change into Branch_4_2 -------------------------------------- Key: JBAS-5928 URL: https://jira.jboss.org/jira/browse/JBAS-5928 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JCA service Reporter: Jeff Zhang Assignee: Jeff Zhang Priority: Minor Fix For: JBossAS-4.2.4.GA we have support imaps/pops on the truck, port this change to branch_4_2 -- 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, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1223) Look into the new JackRabbit release and its clustering support

by Sohil Shah (JIRA)

Look into the new JackRabbit release and its clustering support --------------------------------------------------------------- Key: JBPORTAL-1223 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1223 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6 Final Reporter: Sohil Shah Assigned To: Sohil Shah Fix For: 2.6 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, 10 months

4
8
0 / 0

[JBoss JIRA] Created: (JBAS-5249) Upgrade Bean scripting framework

by Tomaz Cerar (JIRA)

Upgrade Bean scripting framework -------------------------------- Key: JBAS-5249 URL: http://jira.jboss.com/jira/browse/JBAS-5249 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA, JBossAS-4.2.1.GA, JBossAS-4.2.0.GA Reporter: Tomaz Cerar JBoss as comes with bsf.jar version 2.3.0. It would be good to upgrade to version 2.4.0 to ease compatibility with third party scripting frameworks such as Rhino javascript engine For instance with bsf 2.3.0 latest rhino you can use is 1.5R3 which is dated in year 2002. If I just replace bsf.jar from apache site, I can use latest Rhino implementation with no problems. It also seems that there are no issues with AS. -- 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, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (JBAS-5932) Refactor redundant code in EJB2 SecurityInterceptors (invoke and invokeHome)

by Anil Saldhana (JIRA)

Refactor redundant code in EJB2 SecurityInterceptors (invoke and invokeHome) ----------------------------------------------------------------------------- Key: JBAS-5932 URL: https://jira.jboss.org/jira/browse/JBAS-5932 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: JBossAS-5.0.0.CR1 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: JBossAS-5.0.0.CR2 The SecurityInterceptors all have the same code in both invoke and invokeHome methods (except for getNext().invokexxx). Any change to the interceptors need to happen in both the methods. So refactor the common code into a separate method. -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5931) Ensure that the call into the MDB container is with no security context

by Anil Saldhana (JIRA)

Ensure that the call into the MDB container is with no security context ----------------------------------------------------------------------- Key: JBAS-5931 URL: https://jira.jboss.org/jira/browse/JBAS-5931 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: JBossAS-5.0.0.CR1 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: JBossAS-5.0.0.CR2 The call to the MDB container should be going in with a null security context. -- 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, 10 months

1
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 September 2008