August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Assigned: (JBESB-55) Nightly builds of unit tests

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-55?page=all ] Mark Little reassigned JBESB-55: -------------------------------- Assignee: Kevin Conner (was: Mark Little) > Nightly builds of unit tests > ---------------------------- > > Key: JBESB-55 > URL: http://jira.jboss.com/jira/browse/JBESB-55 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Mark Little > Assigned To: Kevin Conner > Priority: Minor > Fix For: 4.0 > > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2156) Patch to add expiry queue support to JBossMQ

by Andrig Miller (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2156?page=all ] Andrig Miller updated JBAS-2156: -------------------------------- Fix Version/s: No Release (was: JBossAS-5.0.0.Beta) JBoss MQ will not be a part of JBoss AS 5, and is being replaced by JBoss Messaging. This work should be placed into JBoss Messaging, and I believe there is an existing JIRA issue in the JBoss Messaging project that deals with this. > Patch to add expiry queue support to JBossMQ > -------------------------------------------- > > Key: JBAS-2156 > URL: http://jira.jboss.com/jira/browse/JBAS-2156 > Project: JBoss Application Server > Issue Type: Patch > Security Level: Public(Everyone can see) > Components: JMS service > Affects Versions: JBossAS-4.0.3RC2 > Reporter: Elias Ross > Assigned To: Elias Ross > Fix For: No Release > > Attachments: expiry.diff, expiry.diff, expiry.txt, ExpiryDestinationTestCase.java > > > Added attributes "ExpiryDestination" to DestinationMBean and DestinationManagerMBean to indicate an ObjectName of queue to receive expired messages. This destination queue must be bound into JNDI when this queue starts. > The messages are copied over to this queue when expiry time is reached and the original expiration and destination is kept in the vendor parameters "JBOSS_ORIG_EXPIRATION" and "JBOSS_ORIG_DESTINATION". The same JMSMessageID is kept in the copied message. > The limitation of this is that the queue must be located on the same local JBoss server. > Another limitation is that the expired message is only removed after its copy has been added to the new destination. Ideally, the "move" would happen within a single transaction. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2150) Disable automatic JBossMQ destination construction

by Andrig Miller (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2150?page=all ] Andrig Miller updated JBAS-2150: -------------------------------- Fix Version/s: No Release (was: JBossAS-5.0.0.Beta) Unscheduling this from JBoss 5, because JBoss MQ will not be apart of JBoss 5, but will be replaced with JBoss Messaging. > Disable automatic JBossMQ destination construction > -------------------------------------------------- > > Key: JBAS-2150 > URL: http://jira.jboss.com/jira/browse/JBAS-2150 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JMS service > Reporter: Adrian Brock > Fix For: No Release > > > The automatic construction of JBossMQ destination construction is not portable > and confuses most users when they configure things wrong. > They don't get a reasonable error message, and sometimes no error message at all. > This was made configurable in JBoss4 and should be disabled in JBoss5 > See conf/standardjboss.xml > - <CreateJBossMQDestination>true</CreateJBossMQDestination> > + <CreateJBossMQDestination>false</CreateJBossMQDestination> > The testsuite will need fixing for any MDB deployments that were using this feature > to have explicit destination deployments. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-263) malformed '<a' tag causes Javadoc to fail

by Michael Newcomb (JIRA)

malformed '<a' tag causes Javadoc to fail ----------------------------------------- Key: JGRP-263 URL: http://jira.jboss.com/jira/browse/JGRP-263 Project: JGroups Issue Type: Bug Affects Versions: 2.3 SP1 Environment: JDK 1.5 Reporter: Michael Newcomb Assigned To: Bela Ban You can't build javadoc because of some bad '<a' tags. (http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5082928). It seems that it affects mostly where collections have been 'generified' in the javadocs: /** Map<Address, Rsp> */ in RspList.java. So, in IntelliJ, search for "<a" in src and replace all of them with < and >. It isn't too many files: GroupRequest.java RequestCorrelator.java FC.java FRAG2.java SEQUENCER.java STATS.java TP.java RspList.java Util.java Digest.java NAKACK.java Thanks, Michael -- 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, 11 months

2
3
0 / 0

[JBoss JIRA] Resolved: (JGRP-144) View bundling

by Bela Ban (JIRA)

[ http://jira.jboss.com/jira/browse/JGRP-144?page=all ] Bela Ban resolved JGRP-144. --------------------------- Resolution: Done Integrated the patch (with changes), testsuite passes, GmsTests.txt passes too. Looks pretty stable so far > View bundling > ------------- > > Key: JGRP-144 > URL: http://jira.jboss.com/jira/browse/JGRP-144 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assigned To: Bela Ban > Priority: Critical > Fix For: 2.4 > > Attachments: view_bundling.zip > > > When multiple members join/leave at the same time, we also emit 1 view per JOIN or LEAVE request. However, we could bundle multiple JOIN and LEAVE requests and only install 1 view. This would be enabled by collecting JOIN and LEAVE requests in a queue until > - N requests have queued up or > - M milliseconds have elapsed, whichever occurs first > Advantage: we can handle many JOIN/LEAVE requests at the same time, reducing time to emit views (VIEW_ACKs need to be sent fewer times) -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3462) Proper bind, unbind and rebind support for the external context and naming alias features

by Roland R?z (JIRA)

Proper bind, unbind and rebind support for the external context and naming alias features ----------------------------------------------------------------------------------------- Key: JBAS-3462 URL: http://jira.jboss.com/jira/browse/JBAS-3462 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Naming Reporter: Roland R?z Assigned To: Scott M Stark Priority: Minor Attachments: JBossJndiUnbindTest.java JBoss provides with org.jboss.naming.NamingAlias and org.jboss.naming.NamingService two nice features to create local links and integrate external jndi implementations. The jndi server implementation and the org.jboss.util.naming.Util (used in the ejb2.x & ejb 3 container) have some troubles with the bind, unbind and rebind operations. It would be a nice feature when these operations are supported by the jboss jndi implementation but fixing org.jboss.util.naming.Util is maybe simpler. The attached Junit test case shows the problems: - jboss jndi and the utility seems to have problems with the alias - jboss jndi seems to have problems with the external context (independent if it is ldap or jboss). -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Resolved: (JBPORTAL-824) Check for propagation of ServiceLayoutImpl changes

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-824?page=all ] Julien Viet resolved JBPORTAL-824. ---------------------------------- Fix Version/s: 2.4 Final (was: 2.6 Final) Resolution: Done > Check for propagation of ServiceLayoutImpl changes > -------------------------------------------------- > > Key: JBPORTAL-824 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-824 > Project: JBoss Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 2.4 Final > Reporter: Chris Laprun > Fix For: 2.4 Final > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > LayoutServiceImpl implementation has changed quite a bit lately: the underlying data model has changed but it is exposed to client classes via de-typed collections causing problem in client code (for example PortalObjectManagementbean). Make sure that the other client classes are properly adapted to the changes. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPORTAL-630) Portal name

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-630?page=comments#action_12340489 ] Julien Viet commented on JBPORTAL-630: -------------------------------------- Can't you use the org.jboss.portal.node.* API packages for this ? > Portal name > ----------- > > Key: JBPORTAL-630 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-630 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Ryszard Kozmik > Assigned To: Julien Viet > Fix For: 2.6 Final > > > I need this: req.getPortalContext().getProperty("org.jboss.portal.property.name")); > to be able to create root link in JBoss Forums. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPORTAL-848) Update Documentation for 2.4

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-848?page=all ] Julien Viet resolved JBPORTAL-848. ---------------------------------- Fix Version/s: 2.4 Final (was: 2.6 Final) Resolution: Done > Update Documentation for 2.4 > ---------------------------- > > Key: JBPORTAL-848 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-848 > Project: JBoss Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation > Affects Versions: 2.4 Final > Reporter: Roy Russo > Assigned To: Roy Russo > Fix For: 2.4 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-746) Enhance URLVisitor interface

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-746?page=all ] Julien Viet updated JBPORTAL-746: --------------------------------- Summary: Enhance URLVisitor interface (was: Enhance) > Enhance URLVisitor interface > ---------------------------- > > Key: JBPORTAL-746 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-746 > Project: JBoss Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 2.4 Final, 2.2.1 Final > Reporter: Julien Viet > Fix For: 2.6 Final > > > Improve URLVisitor and make the startDir method returns a boolean so the visitor can state if it wants to visit the children or just continue. -- 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, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2006