August 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBAS-1711) HTMLAdaptorServlet updateAttributes bug?

by Kenny MacLeod (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1711?page=comments#action_12372324 ] Kenny MacLeod commented on JBAS-1711: ------------------------------------- Yeah, OK. I think should get fixed somehow, though, it can be quiie annoying to not be able to clear the attribute values without having to enter dummy whitespace. > HTMLAdaptorServlet updateAttributes bug? > ---------------------------------------- > > Key: JBAS-1711 > URL: http://jira.jboss.com/jira/browse/JBAS-1711 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Management services > Affects Versions: JBossAS-3.2.7 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1 Final, JBossAS-4.0.1 SP1 > Reporter: SourceForge User > Priority: Minor > > SourceForge Submitter: raja05 . > UpdateAttributes method in HtmlAdaptorServlet has a > section of code something like > while( paramNames.hasMoreElements() ) > { > String param = (String) paramNames.nextElement(); > if( param.equals("name") || > param.equals("action") ) > continue; > String value = request.getParameter(param); > log.trace("name="+param+", value='"+value+"'"); > // Ignore null values, these are empty > write-only fields > if( value == null || value.length() == 0 ) > continue; > attributes.put(param, value); > } > The check for value == null || value.length() == 0 is > kind of wrong for my case. > Im trying to use a XMBean that would store the values > from the JMX-Console to a filestore that i have created > using Properties.load(not the > ObjectStreamPersistenceManager but something along the > line that uses the Property.save to store the data in a > name=value fashion). > The problem im getting is that if i want to clear out > any of the attributes that have been set already, the > above code comes to the check of value.length() == 0 > and since its blank, just moves to the next request > param. I would like to remove this check from there so > that even though i blank out my value, i need that to > get persisted. > Please let me know if you need a detailed explanation > or if the above is not clear > I just need the value.length() == 0 check removed but > not sure if thats going to cause an issue somewhere else. > Thanks a bunch > Raja -- 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

18 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-1711) HTMLAdaptorServlet updateAttributes bug?

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1711?page=comments#action_12372319 ] Dimitris Andreadis commented on JBAS-1711: ------------------------------------------ I think the side effect of what you want, would be to re-set to null all values that are empty, not just the one you alter. > HTMLAdaptorServlet updateAttributes bug? > ---------------------------------------- > > Key: JBAS-1711 > URL: http://jira.jboss.com/jira/browse/JBAS-1711 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Management services > Affects Versions: JBossAS-3.2.7 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1 Final, JBossAS-4.0.1 SP1 > Reporter: SourceForge User > Priority: Minor > > SourceForge Submitter: raja05 . > UpdateAttributes method in HtmlAdaptorServlet has a > section of code something like > while( paramNames.hasMoreElements() ) > { > String param = (String) paramNames.nextElement(); > if( param.equals("name") || > param.equals("action") ) > continue; > String value = request.getParameter(param); > log.trace("name="+param+", value='"+value+"'"); > // Ignore null values, these are empty > write-only fields > if( value == null || value.length() == 0 ) > continue; > attributes.put(param, value); > } > The check for value == null || value.length() == 0 is > kind of wrong for my case. > Im trying to use a XMBean that would store the values > from the JMX-Console to a filestore that i have created > using Properties.load(not the > ObjectStreamPersistenceManager but something along the > line that uses the Property.save to store the data in a > name=value fashion). > The problem im getting is that if i want to clear out > any of the attributes that have been set already, the > above code comes to the check of value.length() == 0 > and since its blank, just moves to the next request > param. I would like to remove this check from there so > that even though i blank out my value, i need that to > get persisted. > Please let me know if you need a detailed explanation > or if the above is not clear > I just need the value.length() == 0 check removed but > not sure if thats going to cause an issue somewhere else. > Thanks a bunch > Raja -- 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

18 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-1711) HTMLAdaptorServlet updateAttributes bug?

by Kenny MacLeod (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1711?page=comments#action_12372315 ] Kenny MacLeod commented on JBAS-1711: ------------------------------------- 18 months since last comment. Can we add this back on the roadmap, please, it's a trivial fix. > HTMLAdaptorServlet updateAttributes bug? > ---------------------------------------- > > Key: JBAS-1711 > URL: http://jira.jboss.com/jira/browse/JBAS-1711 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Management services > Affects Versions: JBossAS-3.2.7 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1 Final, JBossAS-4.0.1 SP1 > Reporter: SourceForge User > Priority: Minor > > SourceForge Submitter: raja05 . > UpdateAttributes method in HtmlAdaptorServlet has a > section of code something like > while( paramNames.hasMoreElements() ) > { > String param = (String) paramNames.nextElement(); > if( param.equals("name") || > param.equals("action") ) > continue; > String value = request.getParameter(param); > log.trace("name="+param+", value='"+value+"'"); > // Ignore null values, these are empty > write-only fields > if( value == null || value.length() == 0 ) > continue; > attributes.put(param, value); > } > The check for value == null || value.length() == 0 is > kind of wrong for my case. > Im trying to use a XMBean that would store the values > from the JMX-Console to a filestore that i have created > using Properties.load(not the > ObjectStreamPersistenceManager but something along the > line that uses the Property.save to store the data in a > name=value fashion). > The problem im getting is that if i want to clear out > any of the attributes that have been set already, the > above code comes to the check of value.length() == 0 > and since its blank, just moves to the next request > param. I would like to remove this check from there so > that even though i blank out my value, i need that to > get persisted. > Please let me know if you need a detailed explanation > or if the above is not clear > I just need the value.length() == 0 check removed but > not sure if thats going to cause an issue somewhere else. > Thanks a bunch > Raja -- 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

18 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3658) Remote classloading service - Redesign

by Dimitris Andreadis (JIRA)

Remote classloading service - Redesign -------------------------------------- Key: JBAS-3658 URL: http://jira.jboss.com/jira/browse/JBAS-3658 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Remoting Reporter: Dimitris Andreadis Assigned To: Tom Elrod Fix For: JBossAS-4.0.6.CR1 We need to redesign the remote classloading service such that there is more control at the deployment layer on what is exposed. I will create a forum thread where this can be discussed in more detail. Requirement 1: Provide sensible defaults, which probably means no remote classloading by default Requirement 2: Individual deployments can choose whether remote classloading is enabled and what is available remotely Requirement 3: Allow "aspects" of the deployment to enhance what can be downloaded remotely, e.g. RMI/IIOP generated proxies or AOP remoting proxies Requirement 4: Use the spec defined RMIClassloaderSPI (exposed via an MBean) to make this configurable Requirement 5: Alternate implementations, e.g. exposure of remote classloading via a servlet in Tomcat or a custom resource url that triggers the use of invokers to do remote classloading. -- 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

18 years, 11 months

3
7
0 / 0

[JBoss JIRA] Created: (JBAS-4600) Rename JBossMQ variables from jboss-messaging to jboss.messaging-mq.lib and add jboss-messaging into build-thirdparty

by Clebert Suconic (JIRA)

Rename JBossMQ variables from jboss-messaging to jboss.messaging-mq.lib and add jboss-messaging into build-thirdparty --------------------------------------------------------------------------------------------------------------------- Key: JBAS-4600 URL: http://jira.jboss.com/jira/browse/JBAS-4600 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.1.GA Reporter: Clebert Suconic Assigned To: Clebert Suconic Fix For: JBossAS-4.2.2.GA It's not possible to add jboss-messaging into thirdparty as buildmagic/modules/xml defines it as a variable name called jboss-messaging. -- 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

18 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-995) CLONE -concurrent job acquirement fails

by Edward Staub (JIRA)

CLONE -concurrent job acquirement fails --------------------------------------- Key: JBPM-995 URL: http://jira.jboss.com/jira/browse/JBPM-995 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2 Reporter: Edward Staub Assigned To: Tom Baeyens when more than 1 job executor thread is configured and concurrent async nodes are to be executed, it results in hibernate exceptions. reason: job acquirement is not synchronized well, resulting in multiple threads trying to work on the same job. -- 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

18 years, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1148) SEAM / JSF / Portlet: Compatibility problem

by JP Barbe (JIRA)

SEAM / JSF / Portlet: Compatibility problem ------------------------------------------- Key: JBPORTAL-1148 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1148 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Portlet Affects Versions: 2.6.CR1 Environment: Windows XP MyFaces 1.1.5 SEAM 1.0.1 Reporter: JP Barbe Assigned To: Julien Viet When I use a seam tag into a jsf page, I have the following exception (You can see config files after the exception): 2006-11-30 17:20:57,934 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/seam-desk]] No active conversation context java.lang.IllegalStateException: No active conversation context at org.jboss.seam.core.Process.instance(Process.java:32) at org.jboss.seam.core.TaskInstance.instance(TaskInstance.java:51) at org.jboss.seam.contexts.BusinessProcessContext.getTaskInstance(BusinessProcessContext.java:213) at org.jboss.seam.contexts.BusinessProcessContext.get(BusinessProcessContext.java:51) at org.jboss.seam.contexts.Contexts.lookupInStatefulContexts(Contexts.java:155) at org.jboss.seam.Component.getInstance(Component.java:1245) at org.jboss.seam.Component.getInstance(Component.java:1230) at org.jboss.seam.contexts.Lifecycle.resumeConversation(Lifecycle.java:328) at org.jboss.seam.jsf.AbstractSeamPhaseListener.restoreAnyConversationContext(AbstractSeamPhaseListener.java:42) at org.jboss.seam.jsf.SeamPortletPhaseListener.beforePhase(SeamPortletPhaseListener.java:51) at org.jboss.seam.jsf.SeamExtendedManagedPersistencePortletPhaseListener.beforePhase(SeamExtendedManagedPersistencePortletPhaseListener.java:37) at org.apache.myfaces.lifecycle.LifecycleImpl.informPhaseListenersBefore(LifecycleImpl.java:520) at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:342) at org.apache.myfaces.portlet.MyFacesGenericPortlet.facesRender(MyFacesGenericPortlet.java:396) at org.apache.myfaces.portlet.MyFacesGenericPortlet.doView(MyFacesGenericPortlet.java:266) at com.eads.desk.core.portlet.DeskAccessPortlet.doView(DeskAccessPortlet.java:30) at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:133) #### Here is the faces-config.xml file: <faces-config> <lifecycle> <phase-listener> org.jboss.seam.jsf.SeamExtendedManagedPersistencePortletPhaseListener </phase-listener> </lifecycle> <navigation-rule> <from-view-id>/view/deskAccess.jsp</from-view-id> <navigation-case> <from-outcome>trManager</from-outcome> <to-view-id>/view/viewTRManager.jsp</to-view-id> <redirect /> </navigation-case> </navigation-rule> <navigation-rule> <navigation-case> <from-action>#{pooledTask.assignToCurrentActor}</from-action> <from-outcome>taskAssignedToActor</from-outcome> <to-view-id>/view/viewTRManager.jsp</to-view-id> </navigation-case> </navigation-rule> </faces-config> #### web.xml: <?xml version="1.0" encoding="UTF-8"?> <web-app version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">  <listener> <listener-class>org.jboss.seam.servlet.SeamListener</listener-class> </listener> </web-app> ### I have seen an issue (Key: JBSEAM-347) but I don't anderstand the solution proposed or if a solution exists ! (http://jira.jboss.org/jira/browse/JBSEAM-347) Thanks. JP. -- 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

18 years, 11 months

2
1
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-206) Check that required fields are filled before logging in a user

by Thomas Heute (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-206?page=all ] Thomas Heute updated JBPORTAL-206: ---------------------------------- Fix Version/s: 2.8 Final > Check that required fields are filled before logging in a user > -------------------------------------------------------------- > > Key: JBPORTAL-206 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-206 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal Core > Affects Versions: 2.0.1 Final > Reporter: Thomas Heute > Fix For: 2.8 Final > > > Making sure to check that a user filled all required fields before letting him logging-in. Otherwise it should display a form with non-filled entries. > This is useful when we add a new field in the registration form. -- 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

18 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1498) Add Support for Internet Explorer's Conditional Comments

by Andy Pemberton (JIRA)

Add Support for Internet Explorer's Conditional Comments -------------------------------------------------------- Key: JBPORTAL-1498 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1498 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Theme Affects Versions: 2.6.CR1 Environment: All Reporter: Andy Pemberton Assigned To: Julien Viet Currently, JBoss Portal's theme and layout architecture relies on XML deployment descriptors for several objects. For example, the portal-theme.xml is used to create themes (javascript and css) that will be applied to layouts. The request I have is this: given the XML deployment descriptors, add in support for Internet Explorer's Conditional Comment system. Conditional Comments have been a feature of IE since IE5. Basically, Conditional Comments are specially formatted HTML comments that allow web developers to target specific markup to Internet Explorer. Typically, Conditional Comments are used to import specific Cascading Style Sheets (CSS) to HTML pages to handle IE-specific CSS defects. Currently, the lack of support for Conditional Comments is caused by the fact that Conditional Comments rely on XHTML-based comments, which are thus filtered out at the portal-theme.xml level. I considered adding this request as a defect, but decided against it as not reading in comments in an XML deployment descriptor is quite logical, and of course - IE's conditional comment system (though useful) is counter-intuitive. Reference: - http://msdn2.microsoft.com/en-us/library/ms537512.aspx -- 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

18 years, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1628) Portal bridge upgrade

by Rakesh Ajmera (JIRA)

Portal bridge upgrade --------------------- Key: JBPORTAL-1628 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1628 Project: JBoss Portal Issue Type: Support Patch Security Level: Public (Everyone can see) Affects Versions: 2.4.1 SP1 Reporter: Rakesh Ajmera There is a new version of portal-bridge available 1.0.3(http://portals.apache.org/bridges/download.html). What's the plan of upgrading jboss portal to the latest version of portal bridge? We need the bug fixes available in this 1.0.3 release, but it doesn't work with the jboss's portal-bridge-lib.jar that is packaged with jboss portal. We are using Struts bridge, that is dependent on the portals-bridges-common.jar, which in turn works with JBoss's potal-bridge-lib.jar. I upgraded the portal-bridges-common.jar with the latest version, but it didn't work with portal-bridge-lib.jar. -- 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

18 years, 11 months

2
2
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 August 2007