October 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-1767) SendIcal has invalid junit.* import

by Michael Zimmermann (JIRA)

SendIcal has invalid junit.* import ----------------------------------- Key: JBRULES-1767 URL: https://jira.jboss.org/jira/browse/JBRULES-1767 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: FUTURE Environment: Linux, Drools from svn trunk Reporter: Michael Zimmermann Assignee: Mark Proctor drools-process/drools-process-task/src/main/java/org/drools/task/service/SendIcal.java has an invalid and unneded import from junit.*. This results in a broken maven build as the junit-jar is not in the classpath for the main build process (only for testing). Removing the import results in a working compile process. -- 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

15 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1772) SerializablePlaceholderResolverStrategy.accept method should call acceptor.accept

by Michal Bali (JIRA)

SerializablePlaceholderResolverStrategy.accept method should call acceptor.accept ---------------------------------------------------------------------------------- Key: JBRULES-1772 URL: https://jira.jboss.org/jira/browse/JBRULES-1772 Project: JBoss Drools Issue Type: Patch Security Level: Public (Everyone can see) Components: Reteoo Affects Versions: 5.0.0.M1 Reporter: Michal Bali Assignee: Mark Proctor Priority: Minor Hi, The SerializablePlaceholderResolverStrategy.accept method should call acceptor.accept, instead of its own method accept (which causes recursion). e.g. change line 38 to: return this.acceptor.accept( object ); the line number can be seen here: http://fisheye.jboss.org/browse/JBossRules/trunk/drools-core/src/main/jav... Thank you! Best Regards, Michal -- 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

15 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBREM-1020) Release 2.2.2.SP10

by Ron Sigal (JIRA)

Release 2.2.2.SP10 ------------------ Key: JBREM-1020 URL: https://jira.jboss.org/jira/browse/JBREM-1020 Project: JBoss Remoting Issue Type: Release Security Level: Public (Everyone can see) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.2.2.SP10 -- 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

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2185) Portlet 2 information causes NPE with remote portlets.

by Chris Laprun (JIRA)

Portlet 2 information causes NPE with remote portlets. ------------------------------------------------------ Key: JBPORTAL-2185 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2185 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.7.0 CR1 Reporter: Chris Laprun Assignee: Chris Laprun Fix For: 2.7.0 Final -- 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

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2183) Producer is not properly informed of changes in configuration if configuration was reloaded from file

by Chris Laprun (JIRA)

Producer is not properly informed of changes in configuration if configuration was reloaded from file ----------------------------------------------------------------------------------------------------- Key: JBPORTAL-2183 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2183 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.7.0 CR1 , 2.6.6 Final Reporter: Chris Laprun Assignee: Chris Laprun Fix For: 2.6.7 Final, 2.7.0 Final This has to do with listeners not being properly reset when the configuration is reloaded... -- 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

15 years, 7 months

1
2
0 / 0

[JBoss JIRA] Updated: (JBAS-2563) Cleanup the build for jboss5

by Dimitris Andreadis (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-2563?page=com.atlassian.jira.plug... ] Dimitris Andreadis updated JBAS-2563: ------------------------------------- Comment: was deleted > Cleanup the build for jboss5 > ---------------------------- > > Key: JBAS-2563 > URL: https://jira.jboss.org/jira/browse/JBAS-2563 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Scott M Stark > Assignee: Scott M Stark > Fix For: JBossAS-5.0.0.GA > > > The current jboss-head build seems rather crusty with outdated modules (media which I removed) and weird modules like jbossas. From the dev list: > This is the remoting/jbossas integration code. > i.e. the UnifiedInvoker > It shouldn't really be in jbossas which was meant to be the top level build folder replacement for "build" > e.g. in the new build > cvs .. co jbossas > cd jbossas > ant rebuild > would pull down all modules and thirdparty and build the release. > Instead jbossas has turned into another "varia" ;-) > On Tue, 2005-12-13 at 03:00, Scott M Stark wrote: > > Why is there this jbossas module in jboss-head when there is also > > remoting being pulled via the thirdparty? > > > We need a plan on cleaning up the jboss-head build using the jbossbuild before creating a jboss5 branch. -- 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

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-5919) Upgrade jboss transactions to 4.4.0.GA

by Dimitris Andreadis (JIRA)

Upgrade jboss transactions to 4.4.0.GA -------------------------------------- Key: JBAS-5919 URL: https://jira.jboss.org/jira/browse/JBAS-5919 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Transaction Manager (Arjuna) Reporter: Dimitris Andreadis Assignee: Jonathan Halliday Priority: Critical Fix For: JBossAS-5.0.0.GA -- 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

15 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBNAME-15) Remove the public fields from the NamingContext class

by Scott M Stark (JIRA)

Remove the public fields from the NamingContext class ----------------------------------------------------- Key: JBNAME-15 URL: https://jira.jboss.org/jira/browse/JBNAME-15 Project: JBoss Naming Issue Type: Sub-task Affects Versions: 5.0.0.CR2 Reporter: Scott M Stark Assignee: Scott M Stark Fix For: 5.0.0.CR3 To properly secure access we need to remove some of the public non-final class fields from the org.jnp.interfaces.NamingContext class: public static Hashtable haServers = new Hashtable(); public static Naming localServer; These would have class accessors which would have the appropriate permissions. -- 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

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-379) Split large messages into fragments

by Clebert Suconic (JIRA)

[ https://jira.jboss.org/jira/browse/JBMESSAGING-379?page=com.atlassian.jir... ] Clebert Suconic commented on JBMESSAGING-379: --------------------------------------------- It is easier to keep my work updated... for instance today you did a big commit on failover, and updating my working copy took only 10 minutes to solve merge problems. I'm planning commit this on trunk very soon as soon as everything is stable, as this work won't be as extensive as paging or other previous works... besides anyone can get the latest patch and see what's going on. > Split large messages into fragments > ----------------------------------- > > Key: JBMESSAGING-379 > URL: https://jira.jboss.org/jira/browse/JBMESSAGING-379 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assignee: Clebert Suconic > Priority: Critical > Fix For: 2.0.0 Beta > > Attachments: message-chunk-r5057-v1.patch > > > We need to split large messages into small chunks (say 1K), so the sending or receiving of a large message doesn't stall the entire connection since all traffic is multiplexed over it. -- 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

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAOP-658) Index InterceptionMarkers by classloader

by Kabir Khan (JIRA)

Index InterceptionMarkers by classloader ---------------------------------------- Key: JBAOP-658 URL: https://jira.jboss.org/jira/browse/JBAOP-658 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 2.0.0.GA skipField/ConstructorInterception are set for AnnnotatedSecuredPOJO when running AOPUnitTestCase without base-aspects.xml deployed following from JBAOP-647 (AOPUnitTestCase also deploys the classes for SecurityUnitTestCase). This only gets cleared when weaving the class in question, and is used when converting references for a class being woven. When running SecurityUnitTestCase, which deploys base-aspects.xml, AnnotatedSecuredPOJO is woven after SecurityTester, so the skipField/ConstructorInterception flags are still returning true for AnnotatedSecuredPOJO when converting SecurityTester's references. This means that the calls to AnnotatedSecuredPOJO's fields and constructors in SecurityTester are not replaced by calls to the wrapper methods. JBAOP-647 is not the cause of this behaviour, but it made this show up in the AS testsuite. -- 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

15 years, 7 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2008