beehive-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "DeHamer, Brian" <>
Subject RE: TagUtils.computeURL() and dynamic module registration
Date Tue, 31 May 2005 22:48:20 GMT

Thanks for the pointer -- that's pretty close, but not everything that I
was hoping for.  The thing I like about the TagUtils.computeURL() method
is that I can pass it, among other things, a forward, an href, a page,
and an action and it will sort out all the details for me.  On any
particular call all but one of those will likely be null, but I don't
have to worry about which is which -- I just pass them all in and get
back the appropriate URL.


-----Original Message-----
From: Carlin Rogers [] 
Sent: Tuesday, May 31, 2005 3:39 PM
To: Beehive Users
Subject: Re: TagUtils.computeURL() and dynamic module registration

Hi Brian,

Yes, The org.apache.beehive.netui.pageflow.PageFlowUtils class has a
method that I think you're looking for.


Hope this helps,

DeHamer, Brian wrote:

> As part of my application I have a number of custom tags that make use

> of the org.apache.struts.taglib.TagUtils.computeURL() method to assist

> in the rendering of URLs that are generated by my tags.  Among the 
> parameters that can be specified for the computeURL() method are an 
> action name and module name -- the resulting URI will be the 
> context-relative path to the specified action in the specified module.
> This was working fine for me under vanilla Struts, however it doesn't 
> appear to work under JPF.  It appears that the problem is related to 
> the dynamic module registration that is used by the
> When the TagUtils.computeURL() method attempts to generate the URL it 
> checks to make sure that the named ModuleConfig object can be found in

> application scope -- however, under JPF, if no request has yet been 
> made against that module the ModuleConfig won't exist and computeURL()
> Does JPF provide something similar to the TagUtils.computeURL() method

> that will work for me?  If not, is there some way to force all the 
> modules to be loaded at start time?  Any suggestions/work-arounds are 
> welcome.  Thanks.
> Brian DeHamer
> Hewlett-Packard Co.

View raw message