[ 
https://issues.apache.org/jira/browse/VELTOOLS-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464547
 ] 

Nathan Bubna commented on VELTOOLS-64:
--------------------------------------

John (or others),

Were you ever able to make any headway on this issue?  So far as i can tell, 
this can only be due to different HttpServletRequest.getContextPath() 
implementations.  The portion of the URL in question comes from that call alone 
(see StrutsLinkTool.setAction()->StrutsUtils.getActionMappingURL()).   I'm not 
sure if the behavior of getContextPath() can be affected by Tomcat/Geronimo 
configuration or why/how this could be different.   All i am fairly sure about 
is that it could be rather ugly to try and compensate for such things in 
VelocityTools.   I could be talked into accept patches with special-case code 
that can watch for this, so long as it avoided new dependencies.  However, i'm 
not going to go around myself and test how all the various containers implement 
the J2EE/JEE specs. :(

Unless someone wants to whip up a patch or has better info than i do, i'm going 
to resolve this as WON'T FIX.

> Geronimo 1.1.1 with Tomcat install fails to render links correctly
> ------------------------------------------------------------------
>
>                 Key: VELTOOLS-64
>                 URL: https://issues.apache.org/jira/browse/VELTOOLS-64
>             Project: Velocity Tools
>          Issue Type: Bug
>          Components: VelocityStruts
>    Affects Versions: 1.2
>            Reporter: John Eichelsdorfer
>            Priority: Critical
>             Fix For: 1.3
>
>
> I have been using VelocityTools for years and have a project successfully 
> running in production on standalone Tomcat 5.5.  When I run the same war file 
> on Geronimo 1.1.1, links do not render correctly.  Geronimo also uses a 5.5 
> version of Tomcat in the standard distribution I am using.
> I am using Velocity 1.5 beta 1 and VelocityTools 1.2 from Maven.
> Given the following code that is parsed into a main file:
> <a 
> href="$link.setAction('/pub/jobpost/list/submit').addQueryData("c","$!countrySel").addQueryData("r","$!pop.popId")">$!pop.popName
>  Jobs</a>
> On Tomcat 5.5 standalone get:
>       http://www.jobbank.com/action/pub/jobpost/list/submit?c=US&r=CA
> On Geronimo 1.1.1 with the same war file, we get:
>       http://action/pub/jobpost/list/submit?c=US&r=CA
> The only difference obviously is the lack of domain name.  Other links seem 
> to work correctly that are referenced with an absolute path. For example:
>      <a href="/action/exec/resume/choice/setup"  title="Click here">    shows 
> the correct hostname in the front.
> I was using a non-beta velocity, but moved up to using the beta to rule out 
> this being the issue.   I also did a search on the Geronimo distribution for 
> any other file matching "velocity" but came up empty.
> I am not in a rush for this fix, but I think it is important to know that it 
> will work in a next 1.5 Velocity release else people will be constantly using 
> snapshots rather then a steady 1.5 build if this is where the problem lies.
> I am hoping it is somehow just a configuration issue, though I am using the 
> most basic Geronimo setup.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to