July 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBAS-3220) ejb3.deployer lost the javassit bytecode provider changes

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3220?page=comments#action_12340046 ] Dimitris Andreadis commented on JBAS-3220: ------------------------------------------ Alex, can we close this? > ejb3.deployer lost the javassit bytecode provider changes > --------------------------------------------------------- > > Key: JBAS-3220 > URL: http://jira.jboss.com/jira/browse/JBAS-3220 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB3 > Affects Versions: JBossAS-4.0.4.GA > Reporter: Scott M Stark > Assigned To: Alex Pinkin > Fix For: JBossAS-4.0.5.CR1 > > > The changes made to the ejb3.deployer to set javassist as the bytecode provider were dropped in the merge from head even though head had these changes. This was further obfuscated by the ejb3/build-test.xml having the cglib classpath when this was dropped from other build scripts. -- 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBREM-434) fix configuration data within document (socketTimeout should be timeout)

by Tom Elrod (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-434?page=all ] Tom Elrod resolved JBREM-434. ------------------------------ Resolution: Done > fix configuration data within document (socketTimeout should be timeout) > ------------------------------------------------------------------------ > > Key: JBREM-434 > URL: http://jira.jboss.com/jira/browse/JBREM-434 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: general > Affects Versions: 2.0.0.Beta1 > Reporter: Tom Elrod > Assigned To: Tom Elrod > Priority: Minor > Fix For: 2.0.0.CR1 (Boon) > > > http://labs.jboss.com/portal/jbossremoting/docs/guide/ch04.html#d0e635 says that socketTimeout should be used for socket invoker, but should now be timeout. -- 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

19 years, 10 months

1
0
0 / 0

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

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3202?page=all ] Dimitris Andreadis updated JBAS-3202: ------------------------------------- Fix Version/s: JBossAS-5.0.1.CR1 (was: JBossAS-4.0.5.CR1) I don't think it makes much sense for 4.0.x, if the test is only compiled under jdk5, so moving this to a future JB5 version. > Extend the xpath test coverage > ------------------------------ > > Key: JBAS-3202 > URL: http://jira.jboss.com/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 > Assigned To: Aaron Walker > Fix For: JBossAS-5.0.1.CR1 > > > 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: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3234) Make testsuite use installer to create server configs

by Alex Pinkin (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3234?page=comments#action_12340044 ] Alex Pinkin commented on JBAS-3234: ----------------------------------- This is currently on QA's plate: http://jira.jboss.com/jira/browse/JBQA-391 However it's not scheduled at the moment. > Make testsuite use installer to create server configs > ----------------------------------------------------- > > Key: JBAS-3234 > URL: http://jira.jboss.com/jira/browse/JBAS-3234 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Test Suite > Affects Versions: JBossAS-4.0.4.GA > Reporter: Alex Pinkin > Assigned To: Alex Pinkin > Fix For: JBossAS-4.0.5.CR1 > > > We currently use ant script to create server distributions while installer uses another mechanism. We should create distribution using installer. -- 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3265) Problem with empty classname in classloader

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3265?page=all ] Dimitris Andreadis updated JBAS-3265: ------------------------------------- Fix Version/s: JBossAS-4.0.6.CR1 (was: JBossAS-4.0.5.CR1) > Problem with empty classname in classloader > ------------------------------------------- > > Key: JBAS-3265 > URL: http://jira.jboss.com/jira/browse/JBAS-3265 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMX > Affects Versions: JBossAS-4.0.4.GA > Reporter: Adrian Brock > Assigned To: Scott M Stark > Fix For: JBossAS-4.0.6.CR1 > > > The RepositoryClassLoader doesn't handle empty classnames correctly. > It eventually breaks when it tries to do the array name handling here: > // If this is an array class, use Class.forName to resolve it > if( name.charAt(0) == '[' ) > { > result = Class.forName(name, true, this); > removeFromClassBlackList(name); > return result; > } > 17:04:42,858 ERROR [STDERR] java.lang.StringIndexOutOfBoundsException: String index out of range: 0 > 17:04:42,860 ERROR [STDERR] at java.lang.String.charAt(String.java:444) > 17:04:42,861 ERROR [STDERR] at org.jboss.mx.loading.RepositoryClassLoader.loadClassLocally(RepositoryClassLoader.java:169) > 17:04:42,862 ERROR [STDERR] at org.jboss.mx.loading.UnifiedLoaderRepository3.loadClassFromClassLoader(UnifiedLoaderRepository3.java:263) > 17:04:42,862 ERROR [STDERR] at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:270) > 17:04:42,864 ERROR [STDERR] at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:475) > 17:04:42,865 ERROR [STDERR] at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:377) > 17:04:42,865 ERROR [STDERR] at java.lang.ClassLoader.loadClass(ClassLoader.java:235) > The classloader should just reject a null or empty ("") classname in loadClass() > with a meaningful error message. > I suspect the null is handled by the cache since the cache is a Concurrent HashMap > which won't accept null as a key. -- 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBREM-383) Document new versioning for remoting

by Tom Elrod (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-383?page=all ] Tom Elrod resolved JBREM-383. ------------------------------ Resolution: Done > Document new versioning for remoting > ------------------------------------ > > Key: JBREM-383 > URL: http://jira.jboss.com/jira/browse/JBREM-383 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 2.0.0.Beta1 > Reporter: Tom Elrod > Assigned To: Tom Elrod > Fix For: 2.0.0.CR1 (Boon) > > > Need to include config for backwards compatibility. -- 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3272) update JBossRemoting to version 2.0.0

by Tom Elrod (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3272?page=comments#action_12340043 ] Tom Elrod commented on JBAS-3272: ---------------------------------- Yes. Finishing up this week. Am doing doc now, which is taking a while (coding is pretty much completed). Will then need to do integration testing (for UnifiedInvokers, ejb3, etc.). > update JBossRemoting to version 2.0.0 > ------------------------------------- > > Key: JBAS-3272 > URL: http://jira.jboss.com/jira/browse/JBAS-3272 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Remoting > Reporter: Tom Elrod > Assigned To: Tom Elrod > Fix For: JBossAS-4.0.5.CR1 > > > Need to update JBossAS to include jboss-remoting.jar for version 2.0.0.GA of JBossRemoting. -- 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3261) Serialization of EJB handles

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3261?page=all ] Dimitris Andreadis updated JBAS-3261: ------------------------------------- Fix Version/s: JBossAS-4.0.6.CR1 (was: JBossAS-4.0.5.CR1) > Serialization of EJB handles > ---------------------------- > > Key: JBAS-3261 > URL: http://jira.jboss.com/jira/browse/JBAS-3261 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB2 > Affects Versions: JBossAS-3.2.8.SP1, JBossAS-4.0.4.GA > Reporter: Lars Kral > Assigned To: Scott M Stark > Fix For: JBossAS-4.0.6.CR1 > > Attachments: test-ejb.jar > > > According to [JBAS-1620], we have to use org.jboss.naming.NamingContextFactory to allow the handle to remember the JNDI environment that was in effect when it was created. But what about handles constructed inside the JBoss server JVM and later serialized into the client JVM? Each JVM may use different properties to access the JNDI - e.g. the "java.naming.provider.url" property, which is not available in the JBoss JVM but is required in a client JVM. Sure, I can add the "java.naming.provider.url" property to the $JBOSS_SERVER_HOME/conf/jndi.properties file, but as far as I know this forces in-VM calls to use RMI. > Please have a look at the attached testcase (sources are included). The code works in our production environment (v3.2.7) but fails with the latest JBoss releases (4.0.4.GA and 3.2.8.SP1). > Regards, > lkral -- 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3234) Make testsuite use installer to create server configs

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3234?page=comments#action_12340042 ] Dimitris Andreadis commented on JBAS-3234: ------------------------------------------ Alex, do you think this will make it for 4.0.5.CR1? > Make testsuite use installer to create server configs > ----------------------------------------------------- > > Key: JBAS-3234 > URL: http://jira.jboss.com/jira/browse/JBAS-3234 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Test Suite > Affects Versions: JBossAS-4.0.4.GA > Reporter: Alex Pinkin > Assigned To: Alex Pinkin > Fix For: JBossAS-4.0.5.CR1 > > > We currently use ant script to create server distributions while installer uses another mechanism. We should create distribution using installer. -- 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

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3253) jnps not maintaining the transport settings correctly

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3253?page=all ] Dimitris Andreadis updated JBAS-3253: ------------------------------------- Fix Version/s: JBossAS-4.0.6.CR1 (was: JBossAS-4.0.5.CR1) > jnps not maintaining the transport settings correctly > ----------------------------------------------------- > > Key: JBAS-3253 > URL: http://jira.jboss.com/jira/browse/JBAS-3253 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Naming > Affects Versions: JBossAS-4.0.4.GA > Reporter: Scott M Stark > Assigned To: Scott M Stark > Fix For: JBossAS-4.0.6.CR1 > > > There is a report that using a jnps configuration does not maintain the ssl and host settings correctly when interacting with context objects returned from the InitialContext. -- 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

19 years, 10 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 July 2006