[jira] Commented: (TRINIDAD-1471) Portlet 2.0 Support for Trinidad

[ https://issues.apache.org/jira/browse/TRINIDAD-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708144#action_12708144 ] Scott O'Bryan commented on TRINIDAD-1471: - Here is what this projec

[jira] Created: (TRINIDAD-1471) Portlet 2.0 Support for Trinidad

: 1.2.12-core Reporter: Scott O'Bryan Assignee: Scott O'Bryan We need to add support for a Portlet 2.0 container and Bridge in Trinidad. Currently there are a number of issues which should be addressed with this ticket: * PPR should be enabled for Portlet 2.0 cont

Re: Trinidad 1.0.x

Thomas, the latest Trinidad 1.0.x branch is still avaialble. It's been tagged. Although it's still supported it's no longer under active development. If you need access to the trunk, it's in the svn branches and code can be modified/updated in that branch. I don't think we're opposed to fut

[jira] Created: (TRINIDAD-1457) Need the ability to bypass the Cache on ResourceServlet

Affects Versions: 1.2.11-core Reporter: Scott O'Bryan Assignee: Scott O'Bryan By default the ResourceServlet caches all content. While this is generally correct, it is not always correct for custom ResourceServlet Extensions. -- This message is aut

Re: [TRINIDAD] Portlet 2.0 compatibility

Yes I agree Matthias. Anyone else have a contrary opinion? Matthias Wessendorf wrote: On Tue, Apr 21, 2009 at 10:23 AM, Scott O'Bryan wrote: Hey everyone, I completed a migration to Trinidad to allow it to work with either Portlet 1.0 or Portlet 2.0. Portlet 2.0 containers will su

[TRINIDAD] Portlet 2.0 compatibility

Hey everyone, I completed a migration to Trinidad to allow it to work with either Portlet 1.0 or Portlet 2.0. Portlet 2.0 containers will support AJAX. So here is my problem. In order to support extra functionality of Portlet 2.0, I need to compile against a Portlet 2.0 container. Most of

[jira] Reopened: (TRINIDAD-1258) GenericEntry allows invalid locale parameter - XSS vulnerability in LocaleInfoScriptlet

[ https://issues.apache.org/jira/browse/TRINIDAD-1258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott O'Bryan reopened TRINIDAD-1258: - Caused a regression in functionality > GenericEntry allows invalid locale p

[jira] Commented: (TRINIDAD-1258) GenericEntry allows invalid locale parameter - XSS vulnerability in LocaleInfoScriptlet

[ https://issues.apache.org/jira/browse/TRINIDAD-1258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688997#action_12688997 ] Scott O'Bryan commented on TRINIDAD-1258: - This patch caused a r

[jira] Commented: (TRINIDAD-1428) Closing Dialogs cause java.lang.IllegalStateException: Invalid index - Server Exception during PPR

[ https://issues.apache.org/jira/browse/TRINIDAD-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683078#action_12683078 ] Scott O'Bryan commented on TRINIDAD-1428: - I did make some changes to

Re: Issue with ResourceServlet

I sent this on my iphone, but I didn't see it come through so I'll resend... I don't buy usecase (b) and (c). In J2EE, each thread will do one piece of work at a time. The thread *SHOULD* complete before it starts another. It is true that multiple threads may hit a single class instance at

Re: Issue with ResourceServlet

I'm not sure I understand this issue actually. A thread can only perform one task at a time, so your third scenario should be impossiblebecause the FacesContext should be unbound before the thread processes another task. Are you using IBM's vm? Sent from my iPhone On Mar 12, 2009, at 2:3

[jira] Resolved: (TRINIDAD-1373) New Dialog Return code does not work if there are no launchParameters returned

[ https://issues.apache.org/jira/browse/TRINIDAD-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott O'Bryan resolved TRINIDAD-1373. - Resolution: Fixed Fix Version/s: (was: 1.2.11

[jira] Reopened: (TRINIDAD-1373) New Dialog Return code does not work if there are no launchParameters returned

[ https://issues.apache.org/jira/browse/TRINIDAD-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott O'Bryan reopened TRINIDAD-1373: - There is an error in the checked in logic which prevents the redirect in some cases

Re: [Vote] Trinidad 1.2.11 release

+1 Cagatay Civici wrote: +1 On Feb 23, 2009, at 11:02 AM, Bruno Aranda wrote: +1 2009/2/23 Andrew Robinson > +1 On Sun, Feb 22, 2009 at 6:51 PM, Matt Cooper mailto:mcoo...@apache.org>> wrote: +1 On Sun, Feb 22, 2009 at 7:25 AM

Re: 1.2.11-SNAPSHOT dependencies

Get with it Matthias.. Sheesh! :) Matthias Wessendorf wrote: Hi Felix, I know, but I hadn't had a chance to continue on the release. My plan is to get this done over the weekend. -Matthias On Wed, Feb 18, 2009 at 10:31 PM, Felix Roethenbacher wrote: Hi The following modules still have

Re: [Portlet Bridge] 2.0 alpha source download links aren't working

My bad. I'll fix the site.. :) Kito Mann wrote: FYI, the Portlet Bridge 2.0 source links yield 404 Not Found (for both .tar.gz and .zip): http://myfaces.apache.org/portlet-bridge/download.html. --- Kito D. Mann -- Author, JavaServer Faces in Action http://twitter.com/kito99 http://twitter.co

[jira] Updated: (TRINIDAD-1217) in portals stylesheet generated in the producer even when skin matches and suppress is true

[ https://issues.apache.org/jira/browse/TRINIDAD-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott O'Bryan updated TRINIDAD-1217: Resolution: Fixed Fix Version/s: 1.0.9-core 1.2.9

[jira] Updated: (TRINIDAD-961) NON-FUNCTIONAL PARTIALTRIGGERS FOR TABLE COLUMN HEADER/FOOTER

[ https://issues.apache.org/jira/browse/TRINIDAD-961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott O'Bryan updated TRINIDAD-961: --- Resolution: Fixed Status: Resolved (was: Patch Available) > NON-FU

[jira] Resolved: (TRINIDAD-1287) Threadlocal system does not clean up on init

[ https://issues.apache.org/jira/browse/TRINIDAD-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott O'Bryan resolved TRINIDAD-1287. - Resolution: Fixed Fix Version/s: 1.2.10-core > Threadlocal system

[jira] Resolved: (TRINIDAD-1398) Mobile Dialog return does not work with PPR

[ https://issues.apache.org/jira/browse/TRINIDAD-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott O'Bryan resolved TRINIDAD-1398. - Resolution: Fixed Fix Version/s: 1.2.12-core This was caused by is inpro

[jira] Resolved: (TRINIDAD-1399) TrinidadFilterImpl.isReturningFromDialog is not returning the correct result

[ https://issues.apache.org/jira/browse/TRINIDAD-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott O'Bryan resolved TRINIDAD-1399. - Resolution: Fixed Fix Version/s: 1.2.12-core This was caused because we

[jira] Created: (TRINIDAD-1399) TrinidadFilterImpl.isReturningFromDialog is not returning the correct result

Trinidad Issue Type: Bug Affects Versions: 1.2.11-core Reporter: Scott O'Bryan Assignee: Scott O'Bryan The TrinidadFilterImpl.isReturningFromDialog is no longer returning the correct result. -- This message is automatically generated by JIRA. - You

[jira] Created: (TRINIDAD-1398) Mobile Dialog return does not work with PPR

Reporter: Scott O'Bryan New mobile dialog return code does not work with PPR. This is caused by the redirect which is now issued on a dialog return. Essentially when the code issues a redrect in an XHR request, the redirect happens and expects and xml response. The int

[jira] Commented: (TRINIDAD-328) Handle Dialogs in Portal

[ https://issues.apache.org/jira/browse/TRINIDAD-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673332#action_12673332 ] Scott O'Bryan commented on TRINIDAD-328: There have actually been som

[jira] Created: (TRINIDAD-1394) Portlet and Portlet Bridge API's should be marked as optional

Type: Improvement Components: Portlet Affects Versions: 1.2.11-core Reporter: Scott O'Bryan Assignee: Scott O'Bryan Priority: Minor Currently Trinidad is dependent on the Portlet and Portlet Bridge API's. These libraries are marked

[jira] Resolved: (TRINIDAD-1377) ActionRequest not properly detected.

[ https://issues.apache.org/jira/browse/TRINIDAD-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott O'Bryan resolved TRINIDAD-1377. - Resolution: Fixed Fix Version/s: 1.2.11-core Patch applied and should

[jira] Resolved: (TRINIDAD-1383) Update to support latest changes in portlet-bridge.

[ https://issues.apache.org/jira/browse/TRINIDAD-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott O'Bryan resolved TRINIDAD-1383. - Resolution: Fixed Patch applied and should be in the 1.2.11-core release of Tri

[jira] Resolved: (TRINIDAD-1351) On a redirect the URL is not being properly encoded for portals.

[ https://issues.apache.org/jira/browse/TRINIDAD-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott O'Bryan resolved TRINIDAD-1351. - Resolution: Fixed Patch applied and should be in the 1.2.11-core release of Tri

[jira] Resolved: (TRINIDAD-1376) NullPointerException because RequestContext released after action request.

[ https://issues.apache.org/jira/browse/TRINIDAD-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott O'Bryan resolved TRINIDAD-1376. - Resolution: Fixed Fix Version/s: 1.2.11-core Patch applied and should

[jira] Commented: (TRINIDAD-1376) NullPointerException because RequestContext released after action request.

[ https://issues.apache.org/jira/browse/TRINIDAD-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673092#action_12673092 ] Scott O'Bryan commented on TRINIDAD-1376: - We should move this to the

[jira] Resolved: (TRINIDAD-1371) JAWS: layout tables incorrectly identified as data tables

[ https://issues.apache.org/jira/browse/TRINIDAD-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott O'Bryan resolved TRINIDAD-1371. - Resolution: Fixed Fix Version/s: 1.2.11-core 1.0.11

[jira] Commented: (TRINIDAD-1389) multiple browser tab should not share same session state

[ https://issues.apache.org/jira/browse/TRINIDAD-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671269#action_12671269 ] Scott O'Bryan commented on TRINIDAD-1389: - Matthias, if your talking

Re: myfaces 2.0 source zip

I think, Simon, that they are talking about allowing this again due to the inactivity. I was going to commit some patches to it for the bridge stuff but was told that it may be prudent to hold off. It might be time to revisit this discussion. Scott Michael Concini wrote: Thanks. I understa

Re: [TRINIDAD] Portlet API and Portlet Bridge API Dependencies

't mind to have a dependency on the portlet-bridge-api. I didn't get it that he only meant a compile-time dependency and not a runtime dependency. Should the dependencies on this API's be marked as optional in the pom.xml to make this clear? - Felix Scott O'Bryan wrote: The

Re: [TRINIDAD] Portlet API and Portlet Bridge API Dependencies

I guess the base bug TRINIDAD-1276 has a link to all the other bugs where the discussion has popped up. Scott O'Bryan wrote: The most recent discussion about this was on TRINIDAD-1377 and some of the connected bugs. Felix has been very instrumental in helping to diagnose and fix some o

Re: [TRINIDAD] Portlet API and Portlet Bridge API Dependencies

s is no longer an important feature, I do agree with Felix that the code within Trinidad would become a LOT cleaner. I for one think allowing these api's to be optional during runtime is important. But I only get one vote. :) Scott Matthias Wessendorf wrote: On Tue, Feb 3, 200

Re: [TRINIDAD] Portlet API and Portlet Bridge API Dependencies

s is no longer an important feature, I do agree with Felix that the code within Trinidad would become a LOT cleaner. I for one think allowing these api's to be optional during runtime is important. But I only get one vote. :) Scott Matthias Wessendorf wrote: On Tue, Feb 3, 200

[jira] Commented: (TRINIDAD-1383) Update to support latest changes in portlet-bridge.

[ https://issues.apache.org/jira/browse/TRINIDAD-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670179#action_12670179 ] Scott O'Bryan commented on TRINIDAD-1383: - Please test this using the

[jira] Commented: (TRINIDAD-1377) ActionRequest not properly detected.

[ https://issues.apache.org/jira/browse/TRINIDAD-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670177#action_12670177 ] Scott O'Bryan commented on TRINIDAD-1377: - BTW- I understand the re

[TRINIDAD] Portlet API and Portlet Bridge API Dependencies

Hey all, First off, I would like to thank the people recently who have shown an interrest in running Trindiad with Portlet environment. I've had a laundry list of things to do as of late and, in true community fashion, you are helping me evolve Trinidad to comply with the latest bridge. Yay!

[jira] Commented: (TRINIDAD-1377) ActionRequest not properly detected.

[ https://issues.apache.org/jira/browse/TRINIDAD-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670144#action_12670144 ] Scott O'Bryan commented on TRINIDAD-1377: - I've tested it. And

[jira] Commented: (TRINIDAD-1351) On a redirect the URL is not being properly encoded for portals.

[ https://issues.apache.org/jira/browse/TRINIDAD-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670135#action_12670135 ] Scott O'Bryan commented on TRINIDAD-1351: - This will be merged in afte

[jira] Commented: (TRINIDAD-1376) NullPointerException because RequestContext released after action request.

[ https://issues.apache.org/jira/browse/TRINIDAD-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670129#action_12670129 ] Scott O'Bryan commented on TRINIDAD-1376: - For this issue I have

[jira] Commented: (TRINIDAD-1383) Update to support latest changes in portlet-bridge.

[ https://issues.apache.org/jira/browse/TRINIDAD-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670128#action_12670128 ] Scott O'Bryan commented on TRINIDAD-1383: - Looking at this a bit clo

[jira] Commented: (TRINIDAD-1383) Update to support latest changes in portlet-bridge.

[ https://issues.apache.org/jira/browse/TRINIDAD-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670126#action_12670126 ] Scott O'Bryan commented on TRINIDAD-1383: - Cool. Nice Patch Felix. I

[jira] Commented: (TRINIDAD-1377) ActionRequest not properly detected.

[ https://issues.apache.org/jira/browse/TRINIDAD-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668999#action_12668999 ] Scott O'Bryan commented on TRINIDAD-1377: - I'm going to need

[jira] Commented: (TRINIDAD-1376) NullPointerException because RequestContext released after action request.

[ https://issues.apache.org/jira/browse/TRINIDAD-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668994#action_12668994 ] Scott O'Bryan commented on TRINIDAD-1376: - Actually this issue is a li

Re: Configurator / GlobalConfiguratorImpl

ironment? According to the spec the portlet-bridge might - after an initial action request - send one or more render requests. How does the GlobalConfigurator knows when the last render request has been processed? Thanks for your explanations. - Felix Scott O'Bryan wrote: Felix,

[jira] Commented: (TRINIDAD-1377) ActionRequest not properly detected.

[ https://issues.apache.org/jira/browse/TRINIDAD-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667508#action_12667508 ] Scott O'Bryan commented on TRINIDAD-1377: - Sorry, I don't *MI

[jira] Commented: (TRINIDAD-1377) ActionRequest not properly detected.

[ https://issues.apache.org/jira/browse/TRINIDAD-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667507#action_12667507 ] Scott O'Bryan commented on TRINIDAD-1377: - I see. It works for me bec

[jira] Commented: (TRINIDAD-1376) NullPointerException because RequestContext released after action request.

[ https://issues.apache.org/jira/browse/TRINIDAD-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667506#action_12667506 ] Scott O'Bryan commented on TRINIDAD-1376: - The RenderKitDecorator lo

[jira] Commented: (TRINIDAD-1377) ActionRequest not properly detected.

[ https://issues.apache.org/jira/browse/TRINIDAD-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667505#action_12667505 ] Scott O'Bryan commented on TRINIDAD-1377: - Yeah, I don't the bri

[jira] Reopened: (TRINIDAD-1377) ActionRequest not properly detected.

[ https://issues.apache.org/jira/browse/TRINIDAD-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott O'Bryan reopened TRINIDAD-1377: - > ActionRequest not properly

[jira] Commented: (TRINIDAD-1377) ActionRequest not properly detected.

[ https://issues.apache.org/jira/browse/TRINIDAD-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667463#action_12667463 ] Scott O'Bryan commented on TRINIDAD-1377: - Action "type" r

Re: Configurator / GlobalConfiguratorImpl

Felix, The global configurator is not a typical configurator. In a normal Portlet 1.0 environment, there is no guarentee that request scope is preserved between action and render. So yes, the GlobalConfigurator gets called for each request (action and then render). Under the covers, it mak

[jira] Commented: (TRINIDAD-1376) NullPointerException because RequestContext released after action request.

[ https://issues.apache.org/jira/browse/TRINIDAD-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667318#action_12667318 ] Scott O'Bryan commented on TRINIDAD-1376: - The RequestContext

[jira] Commented: (TRINIDAD-1377) ActionRequest not properly detected.

[ https://issues.apache.org/jira/browse/TRINIDAD-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667316#action_12667316 ] Scott O'Bryan commented on TRINIDAD-1377: - Please read the documentati

[jira] Created: (TRINIDAD-1373) New Dialog Return code does not work if there are no launchParameters returned

Trinidad Issue Type: Bug Affects Versions: 1.2.11-core Reporter: Scott O'Bryan Assignee: Scott O'Bryan The code for the dialog return was rewritten recently to support mobile usecases and Weblogic. While this code works fine in launchPara

[ANNOUNCE] Release of Apache MyFaces Portetlet Bridge 2.0.0 Alpha

e=Html&version=12312992 Enjoy! Scott O'Bryan

Re: [VOTE] Support new JSR for the Portlet 2.0 Bidge for JavaServer Faces 1.2

+1 Scott O'Bryan wrote: Hey community, Oracle is trying to open up a new JSR for the Portlet 2.0 Bridge. Originally this was part of the JSR-301 but there was a slight misunderstanding of the intentions of the specs regarding release dates. To make a long story short, instead of

[VOTE] Support new JSR for the Portlet 2.0 Bidge for JavaServer Faces 1.2

Apache shouldn't support the JCP Thanks, Scott O'Bryan

[RESULTS] Release of MyFaces Portlet Bridge 2.0.0-alpha

The vote for the release of the MyFaces Portlet Bridge 2.0.0-alpha release has passed! Results +1(4): Scott O'Bryan, Matthias Wessendorf, Grant Smith, Michael Freedman +0 (0) -1(0) I'll get the artifacts generated and deployed. Thanks! Scott

Re: [VOTE] Release of MyFaces Portlet Bridge 2.0.0-alpha

+1 Matthias Wessendorf wrote: +1 On Wed, Jan 14, 2009 at 4:37 PM, Scott O'Bryan wrote: Okay, I made the changes to the tag and the trunk and uploaded some new artifacts. The NOTICE and LICENSE is now included in all of the files. I also removed an extra TLD and did some houseke

Re: [VOTE] Release of MyFaces Portlet Bridge 2.0.0-alpha

Tue, Jan 13, 2009 at 9:37 AM, Scott O'Bryan wrote: Hi, I'm trying to release the first alpha release of the MyFaces Portlet Bridge 2.0.0 and am now beginning the formal vote. This tag represents an early implementation of a bridge for the Portlet 2.0 specification and is intended f

Re: [VOTE] Release of MyFaces Portlet Bridge 2.0.0-alpha

Good call Matthias, I'll get that fixed immediately. I thought it was there but apparently I missed checking it in. Matthias Wessendorf wrote: On Tue, Jan 13, 2009 at 9:37 AM, Scott O'Bryan wrote: Hi, I'm trying to release the first alpha release of the MyFaces Portlet B

[VOTE] Release of MyFaces Portlet Bridge 2.0.0-alpha

Hi, I'm trying to release the first alpha release of the MyFaces Portlet Bridge 2.0.0 and am now beginning the formal vote. This tag represents an early implementation of a bridge for the Portlet 2.0 specification and is intended for testing interoperability with Portlet 2.0 enabled portals

[Announce] Release of Apache MyFaces Portlet Bridge 1.0.0 Beta

tes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310733&styleName=Html&version=12313058 Enjoy! Scott O'Bryan

[jira] Updated: (TRINIDAD-1203) DATE SELECTION IN INPUTDATE ON BLACKBERRY THROWS VIEWEXPIREDEXCEPTION

[ https://issues.apache.org/jira/browse/TRINIDAD-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott O'Bryan updated TRINIDAD-1203: Resolution: Fixed Fix Version/s: 1.2.11-core Status: Resolved

[jira] Commented: (TRINIDAD-1203) DATE SELECTION IN INPUTDATE ON BLACKBERRY THROWS VIEWEXPIREDEXCEPTION

[ https://issues.apache.org/jira/browse/TRINIDAD-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660971#action_12660971 ] Scott O'Bryan commented on TRINIDAD-1203: - If people need this back

[jira] Updated: (TRINIDAD-1203) DATE SELECTION IN INPUTDATE ON BLACKBERRY THROWS VIEWEXPIREDEXCEPTION

[ https://issues.apache.org/jira/browse/TRINIDAD-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott O'Bryan updated TRINIDAD-1203: Status: Patch Available (was: Open) > DATE SELECTION IN INPUTDATE ON BLACKBERR

[jira] Commented: (TRINIDAD-1203) DATE SELECTION IN INPUTDATE ON BLACKBERRY THROWS VIEWEXPIREDEXCEPTION

[ https://issues.apache.org/jira/browse/TRINIDAD-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659988#action_12659988 ] Scott O'Bryan commented on TRINIDAD-1203: - This patch required some r

[jira] Updated: (TRINIDAD-1203) DATE SELECTION IN INPUTDATE ON BLACKBERRY THROWS VIEWEXPIREDEXCEPTION

[ https://issues.apache.org/jira/browse/TRINIDAD-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott O'Bryan updated TRINIDAD-1203: Status: Open (was: Patch Available) > DATE SELECTION IN INPUTDATE ON BLACKBERR

[RESULTS] Release of MyFaces Portlet Bridge 1.0.0-beta

Thanks everyone who voted on this release. I allowed some extra time because of the holiday season but feel that the vote can now be closed. The vote passed with the following results: +1: Matthias Wessendorf, Scott O'Bryan, Cagatay Civici, Michael Freedman, and Hazem Saleh No +0

Re: [VOTE] Release of MyFaces Portlet Bridge 1.0.0-beta

+1 Matthias Wessendorf wrote: +1 On Fri, Dec 19, 2008 at 2:10 AM, Scott O'Bryan wrote: Hi, I'm trying to release the first beta release of the MyFaces Portlet Bridge 1.0.0 and am now beginning the formal vote. The MyFaces Portlet Bridge 1.0 would like to move into it

[VOTE] Release of MyFaces Portlet Bridge 1.0.0-beta

Hi, I'm trying to release the first beta release of the MyFaces Portlet Bridge 1.0.0 and am now beginning the formal vote. The MyFaces Portlet Bridge 1.0 would like to move into it's first "beta" release. This tag represents the last remaining comments to the JSR-301 EG from its Public Revi

Re: JCP process issues

Interesting blog. I will say however that although the JCP "allows" much of this to happen, most of it depends on the EG. JSR-301 for instance has taken community feedback and the spec was written hand in hand with the prototype. While I too lost some arguments or would have liked some m

Re: Requirements for skinning module

Simon Lessard wrote: Also, for portlets, we have a styleClassMap where we map a renderer's skin selectors to a portlet skin selector, like af|inputText::content - portlet-form, for example. That one is a hard one. Although falling into jsf-portlet bridge scope, the spec would hav

Re: [jira] Resolved: (PORTLETBRIDGE-47) BridgeImpl pass PortletConfig instance to FacesContextFactory instead PortletContext

No doubt, I think he's been holding out on us. :) Kito Mann wrote: Busy day, Michael? :-) On Tue, Dec 9, 2008 at 2:05 PM, Michael Freedman (JIRA) mailto:dev@myfaces.apache.org>> wrote: [ https://issues.apache.org/jira/browse/PORTLETBRIDGE-47?page=com.atlassian.jira.plugin.syst

[RESULTS] Release of Portlet Bridge 1.0.0-alpha-3

Okay, we're finally closing this. The release vote passed with the following results: +1: Leonardo Uribe, Scott O'Bryan, Matthias Wessendorf, and Michael Freedman +0: None -1: None I'll copy the artifacts to the respository, update the website, and come up with the relea

Re: [VOTE] Release of Portlet Bridge 1.0.0-alpha-3

y idea about when this artifacts could be released? If no idea, I'll start release procedure for myfaces archetypes the next days. regards Leonardo Uribe regards Leonardo Uribe On Mon, Nov 24, 2008 at 6:57 PM, Scott O'Bryan <[EMAIL PROTECTED] <mailto:[EMAIL PRO

Re: [Portlet Bridge] Re: Portlet 2.0 branch

Yup. Kito Mann wrote: On Tue, Nov 25, 2008 at 6:38 PM, Scott O'Bryan <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: Are you looking for the bridge? I think the 2.0 is pretty out of date but I think Mike is getting ready to check in some initial code. Okay.

Re: Portlet 2.0 branch

Are you looking for the bridge? I think the 2.0 is pretty out of date but I think Mike is getting ready to check in some initial code. Scott Kito Mann wrote: So, I was looking around the source tree, and I can't quite see where the code for Portlet 2.0 is. I see a Portlet 2.0 branch, but it s

Re: svn commit: r720358 - in /myfaces/portlet-bridge/core/tags/portlet-bridge-1.0.0-alpha-3: api/src/main/resources/META-INF/NOTICE.txt impl/src/main/resources/META-INF/NOTICE.txt

You're totally right Mike.. I'll be more descriptive in the future.. :) Mike Kienenberger wrote: Just a comment that "Sameo" isn't useful if someone doesn't see this in the context of the previous commit. On Mon, Nov 24, 2008 at 7:02 PM, <[EMAIL PROTECTED]> wrote: Author: sobryan Date: M

[jira] Commented: (PORTLETBRIDGE-48) IllegalStateException in Websphere Portal.

[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650393#action_12650393 ] Scott O'Bryan commented on PORTLETBRIDGE-48: Go ahead and c

Re: [VOTE] Release of Portlet Bridge 1.0.0-alpha-3

er the required because we're fairly confident we can get it sorted out pretty quick. The only artifact this will change will likely be the notice. :) Thanks, Scott Scott O'Bryan wrote: +1 Leonardo Uribe wrote: +1 regards Leonardo Uribe On Mon, Oct 27, 2008 at 11:23 AM, Scott O&

Re: [Trinidad] 1-Rerendering components with a4j 2- JBoss Portal

We've never had much luck getting these two technologies to work together. Scott Ricardo P. wrote: Hi ,my name is Ricardo, I'm from Brazil. I am recently working with Jboss Rich-faces and Apache Trinidad, I had some problems with incompatibilities between rich-face's AJAX and Trinidad's AJAX

[RESULTS] Release of Trinidad Plugins 1.2.8

Vote passed with 7 +1 votes from: Andrew Robinson Matthias Wessendorf Scott O'Bryan Grant Smith Cagatay Civici Matt Cooper Bruno Aranda No +0 or -1 votes. Wow.. That was painless. :) Thanks to everyone, I'll distribute the artifacts, update the documents, and send out a

[jira] Created: (TRINIDAD-1287) Threadlocal system does not clean up on init

Reporter: Scott O'Bryan Assignee: Scott O'Bryan TRINIDAD-1273 introduced a system to clean up threadlocals at the end of the request. Some frameworks using this system to store threadlocals are getting assigned during the configurator init. When

Re: [VOTE] Release of Trinidad Plugins 1.2.8

) -Andrew On Tue, Nov 4, 2008 at 3:20 PM, Scott O'Bryan <[EMAIL PROTECTED]> wrote: Hi, I was running the needed tasks to get the 1.2.8 release of the Apache MyFaces Trinidad Maven 2 Plugins. The artifacts are deployed to my private Apache account ([1]). Please take a look at the &

[VOTE] Release of Trinidad Plugins 1.2.8

Hi, I was running the needed tasks to get the 1.2.8 release of the Apache MyFaces Trinidad Maven 2 Plugins. The artifacts are deployed to my private Apache account ([1]). Please take a look at the "1.2.8" artifacts and vote. How to test those JARs ? Use the stage repo inside your pom.xml fil

Re: [Trinidad] ResponseWriterDecorator - proposal to move to public API

-1 to this. ResponseWriterWrapper was introduced in JSF 1.2 which means that this package, going forward, should be largely obsolete. It is only useful for JSF 1.1 and IMO, those people can make (and maintain) their own decorator. Scott Jeanne Waldman wrote: Hi there, I'm wondering what p

Re: [VOTE] Release of Portlet Bridge 1.0.0-alpha-3

y confident we can get it sorted out pretty quick. The only artifact this will change will likely be the notice. :) Thanks, Scott Scott O'Bryan wrote: +1 Leonardo Uribe wrote: +1 regards Leonardo Uribe On Mon, Oct 27, 2008 at 11:23 AM, Scott O'Bryan <[EMAIL PROTECTE

Re: Facelets & Trinidad

Log a Jira ticket. Sent from my iPhone On Oct 30, 2008, at 2:38 AM, Havelka Tomáš <[EMAIL PROTECTED]> wrote: Hi, I want to ask: "Is there a chance, that functionality from UIXComponentTag will be placed anywhere else (for example in UIXComponentBase)?" Why am I asking? Facelets dos

Re: [VOTE] Release of Portlet Bridge 1.0.0-alpha-3

ike I updated PORTLETBRIDGE-48 https://issues.apache.org/jira/browse/PORTLETBRIDGE-48 with information about the origin of the call to setRequestCharacterEncoding(). Hth, Felix Scott O'Bryan wrote: Wow. for some reason it truncated by response. Here it is again.. Good catch Felix, I think th

Re: [VOTE] Release of Portlet Bridge 1.0.0-alpha-3

n't recall what the resolution was from the EG on this issue. Do we have it resolved? If so, do we have an ETA on when this can be moved into main? Scott On Tue, Oct 28, 2008 at 6:16 PM, Scott O'Bryan <[EMAIL PROTECTED]> wrote: > Good catch Felix, I think this is going to ha

Re: [VOTE] Release of Portlet Bridge 1.0.0-alpha-3

+1 Leonardo Uribe wrote: +1 regards Leonardo Uribe On Mon, Oct 27, 2008 at 11:23 AM, Scott O'Bryan <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: Hi, I'm trying to release the MyFaces Portlet Bridge Master 1.0.0-alpha-3. This release was creat

[VOTE] Release of Portlet Bridge 1.0.0-alpha-3

Hi, I'm trying to release the MyFaces Portlet Bridge Master 1.0.0-alpha-3. This release was created in order to support the latest JSR-301 Public Review so that it may be tested by developers during the review process. This is still an alpha release because there is currently no testing of

Re: [VOTE] Release of Portlet Bridge 1.0.0-alpha-3

Leonardo Uribe wrote: On Tue, Oct 21, 2008 at 7:40 PM, Leonardo Uribe <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: On Tue, Oct 21, 2008 at 6:52 PM, Scott O'Bryan <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wro

Re: [VOTE] Release of Portlet Bridge 1.0.0-alpha-3

e. Scott Leonardo Uribe wrote: On Tue, Oct 21, 2008 at 7:40 PM, Leonardo Uribe <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: On Tue, Oct 21, 2008 at 6:52 PM, Scott O'Bryan <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: Leonardo,

Re: [VOTE] Release of Portlet Bridge 1.0.0-alpha-3

ts correct (for all cases) that we didn't find the Token which is why we write a log message. -Mike- Scott O'Bryan wrote: Hey Leo, this could be related to the state-saving issue with MyFaces that I posted to the dev list about a month

<    2   3   4   5   6   7   8   9   10   11   >