November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-866) PojoCache sensor example broken

by Rajesh Rajasekaran (JIRA)

PojoCache sensor example broken ------------------------------- Key: JBCACHE-866 URL: http://jira.jboss.com/jira/browse/JBCACHE-866 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.ALPHA1 Reporter: Rajesh Rajasekaran Assigned To: Manik Surtani Fix For: 2.0.0.ALPHA1 bsh % sourceRelative("aop.bsh"); // Error: // Uncaught Exception: Method Invocation this.interpreter.source : at Line: 19 : in file: /bsh/commands/sourceRelative.bsh : this .interpreter .source ( path , this .caller .namespace ) Called from method: sourceRelative : at Line: 1 : in file: <unknown file> : sourceRelative ( "aop.bsh" ) Target exception: Sourced file: C:\Documents and Settings\rrajasekaran\Desktop\cache-release-2.0\JBossCache-all-2.0.0.ALPHA1\examples\PojoCache\sensor\aop.bsh : Class: PojoCache not found in namespace : at Line: 9 : in file: C:\Documents and Settings\rrajasekaran\Desktop\cache-release-2.0\JBossCache-all-2.0.0.ALPHA1\examples\PojoCache\sensor\aop.bsh : PojoCache bsh % sourceRelative("aop2.bsh"); // Error: // Uncaught Exception: Method Invocation this.interpreter.source : at Line: 19 : in file: /bsh/commands/sourceRelative.bsh : this .interpreter .source ( path , this .caller .namespace ) Called from method: sourceRelative : at Line: 1 : in file: <unknown file> : sourceRelative ( "aop2.bsh" ) Target exception: Sourced file: C:\Documents and Settings\rrajasekaran\Desktop\cache-release-2.0\JBossCache-all-2.0.0.ALPHA1\examples\PojoCache\sensor\aop2.bsh : Class: PojoCache not found in namespace : at Line: 9 : in file: C:\Documents and Settings\rrajasekaran\Desktop\cache-release-2.0\JBossCache-all-2.0.0.ALPHA1\examples\PojoCache\sensor\aop2.bsh : PojoCache -- 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, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-864) PojoCache loadtime example broken

by Rajesh Rajasekaran (JIRA)

PojoCache loadtime example broken --------------------------------- Key: JBCACHE-864 URL: http://jira.jboss.com/jira/browse/JBCACHE-864 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.ALPHA1 Reporter: Rajesh Rajasekaran Assigned To: Manik Surtani Fix For: 2.0.0.ALPHA1 examples\PojoCache\loadtime\build.xml uses an undefined property ${lib} Should be ${cache_lib} from build.properties -- 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, 8 months

3
2
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-859) Suport portlet which use GET method in forms.

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-859?page=all ] Julien Viet updated JBPORTAL-859: --------------------------------- Complexity: High (was: Medium) > Suport portlet which use GET method in forms. > --------------------------------------------- > > Key: JBPORTAL-859 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-859 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal WSRP > Affects Versions: 2.4 Final > Reporter: Chris Laprun > Assigned To: Chris Laprun > Original Estimate: 3 days > Remaining Estimate: 3 days > > We probably need to add an element similar to remotable to the jboss portlet descriptors... > From WSRP spec (10.2.4 Method=get in HTML forms): > User-Agents often throw away any query string from the URL indicated with the form's action attribute when generating the URL they will activate when the form's method is "get". This is the simplest means for them to generate a valid query string. The difficulty this causes is that Consumer's often prefer to store the information they will use when a portlet URL is activated as query string parameters. As a result, Portlets that include HTML forms with method=get in their markup MUST specify usesMethodGet as "true" in their PortletDescription. Consumers choosing to use such Portlets need to format their portlet URLs such that portlet URL activations are processed correctly, regardless of whether Consumer or Producer URL writing is in use. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-859) Suport portlet which use GET method in forms.

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-859?page=all ] Julien Viet updated JBPORTAL-859: --------------------------------- Fix Version/s: (was: 2.6.Alpha1) Out of 2.6 scope, no much value in that. For now JSR 168 does not allow it. > Suport portlet which use GET method in forms. > --------------------------------------------- > > Key: JBPORTAL-859 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-859 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal WSRP > Affects Versions: 2.4 Final > Reporter: Chris Laprun > Assigned To: Chris Laprun > Original Estimate: 3 days > Remaining Estimate: 3 days > > We probably need to add an element similar to remotable to the jboss portlet descriptors... > From WSRP spec (10.2.4 Method=get in HTML forms): > User-Agents often throw away any query string from the URL indicated with the form's action attribute when generating the URL they will activate when the form's method is "get". This is the simplest means for them to generate a valid query string. The difficulty this causes is that Consumer's often prefer to store the information they will use when a portlet URL is activated as query string parameters. As a result, Portlets that include HTML forms with method=get in their markup MUST specify usesMethodGet as "true" in their PortletDescription. Consumers choosing to use such Portlets need to format their portlet URLs such that portlet URL activations are processed correctly, regardless of whether Consumer or Producer URL writing is in use. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBREM-636) Remove ServerInvokerCallbackHandler's dependence on initial InvocationRequest for listerner id.

by Ron Sigal (JIRA)

Remove ServerInvokerCallbackHandler's dependence on initial InvocationRequest for listerner id. ----------------------------------------------------------------------------------------------- Key: JBREM-636 URL: http://jira.jboss.com/jira/browse/JBREM-636 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta1 (Bluto) Reporter: Ron Sigal Assigned To: Ron Sigal Priority: Minor Fix For: 2.2.0.Beta1 (Bluto) Currently, ServerInvokerCallbackHandler is initialized with the InvocationRequest that led to its creation, and thereafter, whenever the ServerInvokerCallbackHandler's id (which is the sessionId plus optional listenerId) is needed, the requestPayload map of the InvocationRequest is queried for the sessionId and listenerId. The problem is that in the http transport, CoyoteInvoker creates a requestPayload map which is partially backed by the org.apache.coyote.Request, which is subject to change from invocation to invocation. -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-325) Message selectors and subscriptions

by kevin armano (JIRA)

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-275) Move Selector processing IN the Channel

by kevin armano (JIRA)

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-599) add a validation in a taskform of the websale example

by David Lloyd (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-599?page=all ] David Lloyd resolved JBPM-599. ------------------------------ Fix Version/s: jBPM 3.2 alpha 2 Resolution: Done Added a minimum=1 validator for the quantity field in websale. > add a validation in a taskform of the websale example > ----------------------------------------------------- > > Key: JBPM-599 > URL: http://jira.jboss.com/jira/browse/JBPM-599 > Project: JBoss jBPM > Issue Type: Task > Components: Web Interface > Reporter: Tom Baeyens > Assigned To: David Lloyd > Fix For: jBPM 3.2 alpha 2 > > > the new task form mechanism should be able to handle validations with JSF/facelets. > the goal of this issue is to introduce a validation in one of the websale taskforms. This should be done with only using input included in the process archive. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-599) add a validation in a taskform of the websale example

by David Lloyd (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-599?page=comments#action_12347497 ] David Lloyd commented on JBPM-599: ---------------------------------- I am taking this to mean that the validations will exist only on the process forms. > add a validation in a taskform of the websale example > ----------------------------------------------------- > > Key: JBPM-599 > URL: http://jira.jboss.com/jira/browse/JBPM-599 > Project: JBoss jBPM > Issue Type: Task > Components: Web Interface > Reporter: Tom Baeyens > Assigned To: David Lloyd > > the new task form mechanism should be able to handle validations with JSF/facelets. > the goal of this issue is to introduce a validation in one of the websale taskforms. This should be done with only using input included in the process archive. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-786) Leaking database connections due to context not closing on some pages

by David Lloyd (JIRA)

Leaking database connections due to context not closing on some pages --------------------------------------------------------------------- Key: JBPM-786 URL: http://jira.jboss.com/jira/browse/JBPM-786 Project: JBoss jBPM Issue Type: Bug Components: Training Affects Versions: jBPM 3.2 alpha 1 Reporter: David Lloyd Assigned To: David Lloyd Fix For: jBPM 3.2 alpha 2 The current phase listener closes the context after the render response (6) phase. However sometimes the response is complete before this phase is arrived at, so close will never be called. The fix is to check the "response complete" flag in the JSF FacesContext in the afterPhase method. -- 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, 8 months

1
1
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 2006