Hey Scott,
The NetUI tags do not have the capability to suppress the netui:html
and netui:body tag output. One thought would be to use a conditional
forward for you actions. The condition could be based on a flag
(whether it's a portal or direct request) which you set in the action
method. The forward for a direct request would either go to a template
or jsp that includes a fragment for the content within the <body> and
if it is a portal request it would just go to the page fragment for
the portlet.
Kind regards,
Carlin
On 11/16/06, Scott Symmank <[EMAIL PROTECTED]> wrote:
i have beehive pageflows that i am surfacing as a portlet.
the portal that i am using (weblogic) recommends that portlets not contain
<html><body>
tags; saying that it can cause weird css behavior.
currently, i ignore the advice if the jsp/pageflow is surfaced through both
a portlet and direct access.
does beehive have the capability to suppress the netui:html and netui:body
tags output,
or does this sound like a valid enhancement request?
<netui:html>
<head>
<title>Title</title>
</head>
<netui:body>
thanks,
scott
