Ok... thanks Andrew. Your response makes sense.

Bobby

P.S. The documentation that I was referring to can be found here:
http://java.sun.com/j2ee/javaserverfaces/1.1_01/docs/tlddocs/

P.S.S. I checked the documentation that you were referencing and it actually states the following for the target attrib "target (h:commandLink only)"... it wraps so it's not immediately apparent that the two lines go together. :)



On 12/7/05, Andrew Robinson < [EMAIL PROTECTED]> wrote:
That is correct. The navigation just says where and if it should be a
redirect or not, it will output the content on the current stream.
There is no way that the server can target a new window for example
(without _javascript_ in the onload). The browser must open a new
window, then load a given URL in that window. Since it is browser
controlled, the JSF navigation class has no control over this, the
control is handled by the JSF controls.

As for the target attribute, I found the reference at this site's
documentation, it may be incorrect:
http://www.horstmann.com/corejsf/jsf-tags.html

On 12/7/05, Bobby Rosenberger <[EMAIL PROTECTED]> wrote:
> After reading your email, I checked the documentation and see no reference
> to a "target" attrib for the h:commandButton... but my question is
> specifically about using the jsf navigation mechanism (ie. faces-config.xml
> ). As I stated, I can open a new window using other methods.
>
> Here's a statement to which I'd like a true or false response:
>
> There is no way to open a new browser window using the default JSF
> navigation mechanism (ie. using the "navigation-rule" tag in the
> faces-config.xml file).
>
> I believe the answer is "True". Am I correct?
>
> Thanks,
>
> Bobby
>
>  On 12/7/05, Andrew Robinson <[EMAIL PROTECTED]> wrote:
> > Any of these should work:
> >
> > <h:outputLink target="_new" value="url"><h:outputText
> > value="text"></h:outputLink>
> > <h:commandLink target="_new" value="link name"/>
> > <h:commandButton target="_new" value="button text" type="submit"/>
> >
> > I am not sure what output the target creates. If it uses "target" then
> > beware of XHTML strict as the target attribute is only to be found in
> > the transitional (or loose?). On a side note, any know why XHTML
> > strict is removing all frame, iframe, and window support? What is the
> > recommended way in XHTML for including sub-pages?
> >
> > -Andrew
> >
> > On 12/7/05, Bobby Rosenberger < [EMAIL PROTECTED]> wrote:
> > > Hey Andrew,
> > >
> > > Thanks for the response, (jenia looks interesting) but my current
> problem
> > > space is more basic. I'm mainly concerned with the mechanics of opening
> a
> > > 'new' browser window. Once the window is open it is largely independent
> - in
> > > the sense that it no longer needs to communicate with the 'desktop'
> page.
> > > Analogous to opening eclipse from a desktop.
> > >
> > > Bobby
> > >
> > >
> > > On 12/7/05, Andrew Robinson < [EMAIL PROTECTED]> wrote:
> > > > If you have a look at Jenia4Faces, there is a popup library that is
> > > > meant to integrate child windows into the JSF framework. You may want
> > > > to have a look to see if that fits your needs. If you are concerned
> > > > about multiple windows interfering with each other in a server saved
> > > > state you may also want to look at JBoss-Seam for their "conversation
> > > > state" support that allows windows to have their own state on the
> > > > server (it is not quite that simple, but it is the basic affect).
> > > >
> > > > Jenia is located here: http://www.jenia.org/
> > > >
> > > > -Andrew
> > > >
> > > > On 12/7/05, Bobby Rosenberger < [EMAIL PROTECTED]> wrote:
> > > > > Hey All,
> > > > >
> > > > > I think I know the answer to this, but I'd like to get confirmation.
> > > > >
> > > > > I have a 'desktop-like' page with icons that users click on to open
> new
> > > > > windows. These windows are more than popup windows, they are
> full-blown
> > > > > pages with tabbed interfaces, etc. I'm currently under the
> impression
> > > that I
> > > > > have to handle opening a new window from my desktop page 'outside'
> the
> > > > > standard JSF navigation mechanism (using faces-config.xml ) and so,
> am
> > > using
> > > > > _javascript_ to achieve this.
> > > > >
> > > > > I have no problem doing this, I just wanted to make sure that I
> hadn't
> > > > > missed something. I consider it a benefit to have all possible
> > > navigation
> > > > > branches in an xml file - making it easier to obtain a graphical
> > > > > representation of page flow.
> > > > >
> > > > > Thanks,
> > > > > Bobby
> > > > >
> > > >
> > >
> > >
> >
>
>

Reply via email to