December 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBESB-288) Merge configuration documents into the administration guide.

by Mark Little (JIRA)

Merge configuration documents into the administration guide. ------------------------------------------------------------ Key: JBESB-288 URL: http://jira.jboss.com/jira/browse/JBESB-288 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.0 RC1 Reporter: Mark Little Assigned To: Mark Little 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

19 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-280) Gateway listeners cannot be registered under the same name as their message aware counterparts

by Tom Fennelly (JIRA)

Gateway listeners cannot be registered under the same name as their message aware counterparts ---------------------------------------------------------------------------------------------- Key: JBESB-280 URL: http://jira.jboss.com/jira/browse/JBESB-280 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 RC1 Reporter: Tom Fennelly Assigned To: Mark Little Fix For: 5.0 The Gateways need to be registered under a completely different name than the message aware "Service " listener they are fronting. -- 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, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-287) Add in HTTP support for new listeners

by Mark Little (JIRA)

Add in HTTP support for new listeners ------------------------------------- Key: JBESB-287 URL: http://jira.jboss.com/jira/browse/JBESB-287 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.0 Reporter: Mark Little Assigned To: Mark Little Fix For: 5.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

19 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-286) Fix JMS Listener Manager Integration test

by Mark Little (JIRA)

Fix JMS Listener Manager Integration test ----------------------------------------- Key: JBESB-286 URL: http://jira.jboss.com/jira/browse/JBESB-286 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: ESB Core, Testing Affects Versions: 4.0 Reporter: Mark Little Assigned To: Mark Little Priority: Minor Fix For: 5.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

19 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-677) Control the time waiting to get an connection

by Poyan (JIRA)

Control the time waiting to get an connection ------------------------------------------------ Key: JBMESSAGING-677 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-677 Project: JBoss Messaging Issue Type: Feature Request Components: JMS Client Manager Reporter: Poyan Assigned To: Ovidiu Feodorov Priority: Optional Fix For: 1.2.0.Beta1 Using the SpyConnectionFactory to get to JMS queues. This is done because of various firewall issues. We have a list of ports that we try to connect to. When a firewall is in between the client and the JBoss server the timeout is extremely long. Following small example show how the connection is made: Properties properties = new Properties(); properties.setProperty(UILServerILFactory.SERVER_IL_FACTORY_KEY, UILServerILFactory.SERVER_IL_FACTORY); properties.setProperty(UILServerILFactory.CLIENT_IL_SERVICE_KEY, UILServerILFactory.CLIENT_IL_SERVICE); properties.setProperty(UILServerILFactory.UIL_ADDRESS_KEY, thisIp); properties.setProperty(UILServerILFactory.UIL_PORT_KEY, thisPort); QueueConnectionFactory conFactory = new SpyConnectionFactory(properties); _myQConnection = conFactory.createQueueConnection(); _testSession = _myQConnection.createQueueSession(false, Session.AUTO_ACKNOWLEDGE); We whant to control the time it will wait for the "createQueueConnection" call We want to control the time client are waiting to get a connection. We have try to set -Dorg.jboss.mq.il.uil2.retryCount=1 form the client, but it still to long waiting, -- 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, 7 months

4
6
0 / 0

[JBoss JIRA] Created: (JBESB-284) Increase DB support matrix for listeners

by Mark Little (JIRA)

Increase DB support matrix for listeners ---------------------------------------- Key: JBESB-284 URL: http://jira.jboss.com/jira/browse/JBESB-284 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Reporter: Mark Little Assigned To: Mark Little Fix For: 5.0 Qualify against MySQL, Oracle and HSQL (if possible). -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-224) ESB aware listeners

by Mark Little (JIRA)

ESB aware listeners ------------------- Key: JBESB-224 URL: http://jira.jboss.com/jira/browse/JBESB-224 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: ESB Core Reporter: Mark Little Assigned To: Esteban Schifman Fix For: 4.0 RC1 We'll leave the old approach to listeners/actionprocessors in place until everything has been converted to the new approach. Ideally we would like to have all old code removed by the RC, but we need a realistic staging to the approach. Therefore, we will take 3 implementations (JMS, file and SQL) and make sure they are converted for the RC and used by the trailblazer. If there is time, we'll look at all of the others too. -- 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, 7 months

1
4
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-438) Preference Values whose length is greater than 255 characters cannot be saved

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-438?page=all ] Julien Viet updated JBPORTAL-438: --------------------------------- Fix Version/s: (was: 2.6.Alpha1) > Preference Values whose length is greater than 255 characters cannot be saved > ----------------------------------------------------------------------------- > > Key: JBPORTAL-438 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-438 > Project: JBoss Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Portal Portlet > Affects Versions: 2.0 Final, 2.0 Branch, 2.4 Final, 2.2 Branch > Environment: Windows 2000, JBAS 4.02 > Reporter: Dennis Meers > > If you create a portlet that supports EDIT mode and a logged-in user edits a preference, if the value they put in has more than 255 chars, an error occurs. This is because the table that saves user preference values (jbp_user_pref_value) has a column called 'jbp_value' that is defined as 'VARCHAR(255)'. > I don't know if the portlet spec defines how many characters are allowed in a preference value, but 255 characters seems small for some portlets. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-825) Usability improvements in Admin UI

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-825?page=all ] Julien Viet updated JBPORTAL-825: --------------------------------- Fix Version/s: 2.6.Beta1 (was: 2.6.Alpha1) > Usability improvements in Admin UI > ---------------------------------- > > Key: JBPORTAL-825 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-825 > Project: JBoss Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Portal Core > Affects Versions: 2.6.Alpha1 > Reporter: Roy Russo > Assigned To: Roy Russo > Fix For: 2.6.Beta1 > > > Address usability issues with interface redesign, tooltips, and help mode in management portlet. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-467) Login page needs to use the theme of the requested portal

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-467?page=all ] Julien Viet updated JBPORTAL-467: --------------------------------- Fix Version/s: (was: 2.6.Alpha1) > Login page needs to use the theme of the requested portal > --------------------------------------------------------- > > Key: JBPORTAL-467 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-467 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal Core > Affects Versions: 2.2 Final > Reporter: Martin Holzner > > The Login.jsp that the web.xml's form login points to is in the portal-server.war. > A call to this jsp does not go through any of the stacks in the portal core, and hence there is no portal or page object available to determine the currently set property for the selected theme. As a result, the Login jsp cannot be styled in synch with the rest of the portal. > In the context of having a synchronized look and feel throughout a portal, the login needs to be able to select the same theme as the portal that was requested, so that the login fits seemlessly into the UI flow. -- 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, 7 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 December 2006