November 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-279) Move web page from SourceForge to labs.jboss.org

by Bela Ban (JIRA)

Move web page from SourceForge to labs.jboss.org ------------------------------------------------ Key: JGRP-279 URL: http://jira.jboss.com/jira/browse/JGRP-279 Project: JGroups Issue Type: Task Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.6 -- 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, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1045) Count Message With Selector

by Hendra Sasmita (JIRA)

Count Message With Selector --------------------------- Key: JBMESSAGING-1045 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1045 Project: JBoss Messaging Issue Type: Feature Request Components: JMS Destination Manager Reporter: Hendra Sasmita Assigned To: Tim Fox Priority: Optional QueueService and TopicService have methods listAllMessages with selector. This method will return list of messages. Sometime operator / administrator wants to know only about the number of messages with certain criteria. In this case, listAllMessages will become inefficient as it returns full list of messages, therefore another method that return the number only is needed -- 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, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-4307) Tag file: Variables from outer tags are not available in inner tags

by Wolfgang Knauf (JIRA)

Tag file: Variables from outer tags are not available in inner tags ------------------------------------------------------------------- Key: JBAS-4307 URL: http://jira.jboss.com/jira/browse/JBAS-4307 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-4.2.0.CR1 Reporter: Wolfgang Knauf Assigned To: Remy Maucherat I created two tag files ("outer" and "inner"), in the jsp "inner" is a nested tag of "outer". In the outer tag file I declare a variable and write it to the jspContext. This variable is available in the jsp, but not in "inner.tag". outer.tag <%@ variable name-given="test" scope="NESTED" %> <% jspContext.setAttribute ("test", "This is a test !", PageContext.PAGE_SCOPE); %> Value before doBody: ${test} <br> <jsp:doBody/> Value after doBody: ${test} <br> inner.tag: Value in inner tag: ${test} <br> test.jsp: <?xml version="1.0" encoding="ISO-8859-1" ?> <%@ page language="java" contentType="text/html; charset=ISO-8859-1" pageEncoding="ISO-8859-1"%> <%@ taglib prefix="test" tagdir="/WEB-INF/tags" %> <html> <body> <test:outer> Value in test.jsp: ${test} <br> <test:inner/> </test:outer> </body> </html> The output is: Value before doBody: This is a test ! Value in test.jsp: This is a test ! Value in inner tag: Value after doBody: This is a test ! The inner tag does not see the attribute. I don't know whether this is a bug or whether the spec forbids this, but I think it should be possible for the inner tag to see the parent variables. A usage sample would be some iterator tag which places the current item in a jspContext variable and the inner tags must be able to access the current item (the variable name is an attribute of the inner tag). I could place the current item in the request scope, but this is much too global. -- 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, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (JBBUILD-394) jboss/jboss-deployers/2.0.0.Beta

by Pete Muir (JIRA)

jboss/jboss-deployers/2.0.0.Beta -------------------------------- Key: JBBUILD-394 URL: http://jira.jboss.com/jira/browse/JBBUILD-394 Project: JBoss Build System Issue Type: Bug Components: Maven Reporter: Pete Muir Assigned To: Paul Gier Priority: Minor jboss-deployers-2.0.0.Beta missing jar (pom is present). -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBBUILD-387) Add missing md5/sha1 checksums to repository.jboss.org

by Paul Gier (JIRA)

Add missing md5/sha1 checksums to repository.jboss.org ------------------------------------------------------ Key: JBBUILD-387 URL: http://jira.jboss.com/jira/browse/JBBUILD-387 Project: JBoss Build System Issue Type: Task Components: Maven Reporter: Paul Gier Assigned To: Paul Gier Fix For: Maven Build - Maint 2007 Several of the artifacts currently in the repository are missing the maven generated checksums. This causes warning messages to be displayed during builds. These checksums should be generated and added to the repository. -- 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, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBBUILD-424) Look into combining default pom and jdk14 poms.

by Paul Gier (JIRA)

Look into combining default pom and jdk14 poms. ----------------------------------------------- Key: JBBUILD-424 URL: http://jira.jboss.com/jira/browse/JBBUILD-424 Project: JBoss Build System Issue Type: Task Components: Maven Reporter: Paul Gier Fix For: Maven Build - Maint 2007 Having separate pom files (default and jdk14) is causing some problems with releases. Maybe the poms can be combined using profiles so that we don't have to keep two separate poms up to date. I had some issues when attempting to use profiles before: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=115157 But I think that I can get around those issues now. -- 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, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBBUILD-410) Set up retro jdk1.4 build and test of microcontainer on hudson.

by Paul Gier (JIRA)

Set up retro jdk1.4 build and test of microcontainer on hudson. --------------------------------------------------------------- Key: JBBUILD-410 URL: http://jira.jboss.com/jira/browse/JBBUILD-410 Project: JBoss Build System Issue Type: Task Components: Maven Reporter: Paul Gier Fix For: Maven Build - App Server A retro build of microcontainer should be set up on hudson so that we can see which tests are failing. -- 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, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (JBBUILD-409) Fix microcontainer jdk14 tests.

by Paul Gier (JIRA)

Fix microcontainer jdk14 tests. ------------------------------- Key: JBBUILD-409 URL: http://jira.jboss.com/jira/browse/JBBUILD-409 Project: JBoss Build System Issue Type: Task Components: JBossRetro, Maven Reporter: Paul Gier Fix For: Maven Build - App Server Many of the retro build tests for microcontainer are failing. These are mostly caused by missing features of jboss-retro. Once the relevant retro issues have been resolved, the tests should be checked again to find remaining issues. -- 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, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (JBBUILD-405) Research issue with microcontainer kernel retro builds

by Paul Gier (JIRA)

Research issue with microcontainer kernel retro builds ------------------------------------------------------ Key: JBBUILD-405 URL: http://jira.jboss.com/jira/browse/JBBUILD-405 Project: JBoss Build System Issue Type: Task Components: JBossRetro, Maven Reporter: Paul Gier Fix For: Maven Build - Maint 2007 The microcontainer kernel is not able to compile with dependency on retroed version of jboss-container. It compiles ok depending on the regular container, but with the retro container, there is a problem with the annotations. -- 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, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-4735) Upon Shutdown connectors should be stopped before applications are undeployed

by Dominik Pospisil (JIRA)

Upon Shutdown connectors should be stopped before applications are undeployed ----------------------------------------------------------------------------- Key: JBAS-4735 URL: http://jira.jboss.com/jira/browse/JBAS-4735 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Affects Versions: JBossAS-4.2.1.GA Reporter: Dominik Pospisil Assigned To: Brian Stansberry In clustered environment the process of shutting down single AS instance should be transparent to clients. This is not the case since applications are udeployed at first while connectors are still servicing requests. This causes clients not to be redirected to another cluster nodes and to receive resource not avaiable exceptions. >From the client perspective, shutdown process should should work like follows: 1) stop connectors so they refuse servicing new requests 2) complete running requests 3) undeploy applications -- 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, 7 months

4
7
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 November 2007