Re: Public API's not part of JSF

Hi * The shared-impl is not really available in source. It's part of the shared. There is also a shared-tomahawk generation. Shared itself will not be released. I wrote a small wiki page on [1] about shared. @Martin: 434 ? if so, we (Sean, Wendy and me) just spoke to some portlet guys at the

who is in charge for JSR 301?

hello who is in charge for JSR 301 here? -- Arash Rajaeeyan

Re: ADFFACES-191 - help

I fixed this issue with following: (1) CoreRenderKit.returnFromDialog will render only close(): out.write(script); out.write(top.close()); out.write(/script); (2) FredJSP.service will render call of callback in onunload: String callback = 'ADFDialogReturn[ + returnId + ]();';

Re: Re: ADFFACES-191 - help

On 10/11/06, Martin Koci [EMAIL PROTECTED] wrote: I fixed this issue with following: (1) CoreRenderKit.returnFromDialog will render only close(): out.write(script); out.write(top.close()); out.write(/script); (2) FredJSP.service will render call of callback in onunload: String callback =

Re: Public API's not part of JSF

Yeah, I think I saw that. Now that myFaces is starting to get a number of very elaborate sub-projects, there is no real reason that we should have to keep re-inventing the wheel. Yet I can certainly respect wanting to keep the API package strictly JSF. Martin Marinschek wrote: Hi Scott,

Re: who is in charge for JSR 301?

I don't think we really have one yet. I can jump on that if you guys want. Michael Freedman is the Spec Lead and he is someone I work with on a regular basis. Scott Arash Rajaeeyan wrote: hello who is in charge for JSR 301 here? -- Arash Rajaeeyan

Re: [Jira] Portlet Issue

Correct. I mean it's crappy that we have to go through like 20 layers of wrappers to make this thing work right. I imagine, though, that it's going to be that way until the next Portlet Spec. Same way with Ajax. The new Portlet spec is going to have a request type specifically for Ajax.

Re: Re: MyFaces 1.2 component autogeneration (was: Trinidad JSF 1.2 status update)

Alexandr, What's wrong with faces-config.xml metadata? From our perspective, this has been a very successful source of the information needed to derive things as diverse as Javadoc, code, and TLDs (and, faces-config.xml itself). The XML is bad, annotations are great line you here a lot these

Re: Trinidad on JDK 1.4

-1 to having to worry about what retroweaver does and does not support, and I certainly don't want to have to check in to two branches regularly. Thanks, Gabrielle Bruno Bernard wrote: Scott, Maybe Trinidad does not work completly with Portlets but it seems to have some support. It seems

Re: Trinidad on JDK 1.4

-1 - ditto to Gabrielle's comment. Gabrielle Crawford wrote: -1 to having to worry about what retroweaver does and does not support, and I certainly don't want to have to check in to two branches regularly. Thanks, Gabrielle Bruno Bernard wrote: Scott, Maybe Trinidad does not work

Re: Trinidad on JDK 1.4

Scott, Thanks for the reply and the details, this is precious information since I will need to make it work. We will not be using panelTabbed and inputFile As for the portal bridge, i am using my face. This is working for me (except that i get an exception in isIE maybe related to the bug

Re: who is in charge for JSR 301?

I really really guess that the portlet guys at apache (Carsten for instance), will hook in. I bet they will, b/c -Portlet RI is Apache (Pluto) -JSF/Portlet Bridges are Apache (subproject of portals.apache.org) On 10/11/06, Arash Rajaeeyan [EMAIL PROTECTED] wrote: I see name of Apache

Re: who is in charge for JSR 301?

added Carsten On 10/11/06, Matthias Wessendorf [EMAIL PROTECTED] wrote: I really really guess that the portlet guys at apache (Carsten for instance), will hook in. I bet they will, b/c -Portlet RI is Apache (Pluto) -JSF/Portlet Bridges are Apache (subproject of portals.apache.org) On