December 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Assigned: (JGRP-176) Asynchronous dispatching of requests in RequestCorrelator

by Bela Ban (JIRA)

[ http://jira.jboss.com/jira/browse/JGRP-176?page=all ] Bela Ban reassigned JGRP-176: ----------------------------- Assignee: Vladimir Blagojevic (was: Bela Ban) Needed for 'breaking the locks on state transfer' > Asynchronous dispatching of requests in RequestCorrelator > --------------------------------------------------------- > > Key: JGRP-176 > URL: http://jira.jboss.com/jira/browse/JGRP-176 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 2.2.8, 2.2.9, 2.2.9.1 > Reporter: Bela Ban > Assigned To: Vladimir Blagojevic > Fix For: 2.5 > > > In RequestCorrelator.handleRequest(), we call handle(Message) on the registered RequestHandler (RpcDispatcher in the case of JBossCache). > Because of http://jira.jboss.com/jira/browse/JBCACHE-326, we need to provide an asynchronous way of calling handle(Message), which doesn't need to wait for the call to return, but is notified later when the response is ready (or not at all if the call is asynchronous). > This could be implemented using a subinterface of RequestHandler (e.g. AsyncRequestHandler), and a *future*. -- 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-715) Consumer explicit property setting mechanism with GUI for property management

by Chris Laprun (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-715?page=all ] Chris Laprun updated JBPORTAL-715: ---------------------------------- Fix Version/s: 2.6.Beta1 (was: 2.6.Alpha1) More details would be appreciated... > Consumer explicit property setting mechanism with GUI for property management > ----------------------------------------------------------------------------- > > Key: JBPORTAL-715 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-715 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal WSRP > Affects Versions: 2.4 Final, 2.6 Final > Reporter: Julien Viet > Assigned To: Chris Laprun > Fix For: 2.6.Beta1 > > -- 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-770) Add constant to identify default locale when none is given for code requiring locale

by Chris Laprun (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-770?page=all ] Chris Laprun updated JBPORTAL-770: ---------------------------------- Fix Version/s: 2.6.CR1 (was: 2.6.Alpha1) > Add constant to identify default locale when none is given for code requiring locale > ------------------------------------------------------------------------------------ > > Key: JBPORTAL-770 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-770 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 2.4 Final > Reporter: Chris Laprun > Assigned To: Chris Laprun > Priority: Minor > Fix For: 2.6.CR1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > There are several spots where locales are needed and not always available. It is not clear at this point if the default locale should be Locale.ENGLISH or the user's default locale (Locale.getDefault()). Creating a constant (in PortalConstants e.g.) to encapsulate which "default" locale to use should help. -- 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-711) Producer URL templating support

by Chris Laprun (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-711?page=all ] Chris Laprun updated JBPORTAL-711: ---------------------------------- Fix Version/s: 2.6.Beta1 (was: 2.6.Alpha1) > Producer URL templating support > ------------------------------- > > Key: JBPORTAL-711 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-711 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal WSRP > Affects Versions: 2.4 Final, 2.6 Final > Reporter: Julien Viet > Assigned To: Chris Laprun > Fix For: 2.6.Beta1 > > -- 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-717) Consumer localization

by Chris Laprun (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-717?page=all ] Chris Laprun updated JBPORTAL-717: ---------------------------------- Fix Version/s: 2.6.Beta1 (was: 2.6.Alpha1) > Consumer localization > --------------------- > > Key: JBPORTAL-717 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-717 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal WSRP > Affects Versions: 2.4 Final, 2.6 Final > Reporter: Julien Viet > Assigned To: Chris Laprun > Fix For: 2.6.Beta1 > > -- 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] Resolved: (JBPORTAL-821) Find out to properly bind property descriptions to schemas

by Chris Laprun (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-821?page=all ] Chris Laprun resolved JBPORTAL-821. ----------------------------------- Resolution: Partially Completed This is fixed when using JBoss WS bundled with 4.0.5. Question is what do we do for 4.0.4? > Find out to properly bind property descriptions to schemas > ---------------------------------------------------------- > > Key: JBPORTAL-821 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-821 > Project: JBoss Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Portal WSRP > Affects Versions: 2.6 Final > Reporter: Chris Laprun > Assigned To: Chris Laprun > Priority: Minor > Fix For: 2.6.Alpha1 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > In RegistrationTestCase: > PropertyDescription regProp = new PropertyDescription("regProp", new QName("ns1:LocalizedString"), > new LocalizedString("en", null, "Registration Property"), null, null); > The second parameter of the PropertyDescription constructor is a QName indicating the XSD type of the property. However, the namespace prefix must be bound to a URN somehow. Right now, we're using a hack: ns1:LocalizedString is used since it is a WSRP-defined type. We also use ns1 as the namespace prefix since this is the prefix assigned to the WSRP type namespace which allows the WS stack to find the type. However, this is obvious that this is not the correct way to do it and this will have to be addressed 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

19 years, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-839) Support UploadContext in getMarkup

by Chris Laprun (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-839?page=all ] Chris Laprun updated JBPORTAL-839: ---------------------------------- Fix Version/s: 2.6.Beta1 (was: 2.6.Alpha1) Need to figure out usefulness of this... > Support UploadContext in getMarkup > ---------------------------------- > > Key: JBPORTAL-839 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-839 > 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 > Priority: Minor > Fix For: 2.6.Beta1 > > -- 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-835) Implement WSRPActionContext getContentLength, getReader and getInputStream correctly.

by Chris Laprun (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-835?page=all ] Chris Laprun updated JBPORTAL-835: ---------------------------------- Fix Version/s: 2.6.Beta1 (was: 2.6.Alpha1) Priority: Minor (was: Major) > Implement WSRPActionContext getContentLength, getReader and getInputStream correctly. > ------------------------------------------------------------------------------------- > > Key: JBPORTAL-835 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-835 > 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 > Priority: Minor > Fix For: 2.6.Beta1 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Right now throws UnsupportedOperationException since previous implementation was returning raw information from the SOAP request. -- 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-857) Deal with non standard Locales better

by Chris Laprun (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-857?page=all ] Chris Laprun updated JBPORTAL-857: ---------------------------------- Fix Version/s: 2.6.CR1 (was: 2.6.Alpha1) Decision must be taken on this so that we can close this issue. > Deal with non standard Locales better > ------------------------------------- > > Key: JBPORTAL-857 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-857 > 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 > Priority: Minor > Fix For: 2.6.CR1 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > Per the WSRP Spec regarding UnsupportedLocale fault: > The Portlet does not support generating markup for the requested locale. Since the Portlet is not required to generate markup in the requested locale, a Portlet returning this fault message is indicating that it processes locales in a stricter manner and has no markup for the requested locales. The Consumer can treat this as a specialization of the OperationFailed fault message and does not have to retry getting the markup in other locales. > Currently, LocaleInfo throws an IllegalArgumentException if the locale is not standard which gets wrapped into an OperationFailedFault at the handler level. We should deal with locale errors better and maybe be more lenient as to what we accept. -- 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-847) Identify common conversion methods (from Set<Mode> to String[] for ex) and put them in a utility class

by Chris Laprun (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-847?page=all ] Chris Laprun updated JBPORTAL-847: ---------------------------------- Fix Version/s: 2.6.CR1 (was: 2.6.Alpha1) > Identify common conversion methods (from Set<Mode> to String[] for ex) and put them in a utility class > ------------------------------------------------------------------------------------------------------ > > Key: JBPORTAL-847 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-847 > 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 > Priority: Optional > Fix For: 2.6.CR1 > > > There are several similar versions of such code. Try to find some time and gather all this code in a single spot. -- 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