[jira] Updated: (WICKET-1428) AutoLinkResolver Does Not Resolve Relative Links Correctly

2008-03-16 Thread Eelco Hillenius (JIRA)

 [ 
https://issues.apache.org/jira/browse/WICKET-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eelco Hillenius updated WICKET-1428:


Issue Type: New Feature  (was: Bug)

../ has never been supported, and the main reason for that is/ was that it is 
more difficult to assume which class loader is used. I'm not sure if it really 
is a problem we can't overcome though, so we could make this a feature request.

 AutoLinkResolver Does Not Resolve Relative Links Correctly
 --

 Key: WICKET-1428
 URL: https://issues.apache.org/jira/browse/WICKET-1428
 Project: Wicket
  Issue Type: New Feature
  Components: wicket
Affects Versions: 1.3.2
Reporter: James Carman

 Suppose I have a package structure like this:
 com.mycompany.myproject
 --- module1
 --- page
 - Page1.html
 --- module2
 --- page
 - Page2.html
 If I want to autolink from Page1.html to Page2.html, it would look like:
 wicket:link
  a href=../../module2/page/Page2.htmlClick Here!/a
 /wicket:link
 This is not working, however.  The AutoLinkResolver spits out a warning 
 message:
 WARN  - AutoLinkResolver   - Did not find corresponding java class: 
 .module2.page.Page2

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (WICKET-1428) AutoLinkResolver Does Not Resolve Relative Links Correctly

2008-03-16 Thread James Carman (JIRA)

[ 
https://issues.apache.org/jira/browse/WICKET-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12579219#action_12579219
 ] 

James Carman commented on WICKET-1428:
--

Ok, you're right, the Javadocs specifically say the href URL must be relative 
to the package containing the associated page.  However, one might argue that 
../../blah/blah is indeed a relative URL.  Either way, I've attached the 
patch.  I don't care if you treat it as a bug or an enhancement request.  It'd 
be nice if this worked properly.  Thanks.

 AutoLinkResolver Does Not Resolve Relative Links Correctly
 --

 Key: WICKET-1428
 URL: https://issues.apache.org/jira/browse/WICKET-1428
 Project: Wicket
  Issue Type: New Feature
  Components: wicket
Affects Versions: 1.3.2
Reporter: James Carman
 Attachments: WICKET-1428.patch


 Suppose I have a package structure like this:
 com.mycompany.myproject
 --- module1
 --- page
 - Page1.html
 --- module2
 --- page
 - Page2.html
 If I want to autolink from Page1.html to Page2.html, it would look like:
 wicket:link
  a href=../../module2/page/Page2.htmlClick Here!/a
 /wicket:link
 This is not working, however.  The AutoLinkResolver spits out a warning 
 message:
 WARN  - AutoLinkResolver   - Did not find corresponding java class: 
 .module2.page.Page2

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (WICKET-1428) AutoLinkResolver and Parent-Relative (../) Links

2008-03-16 Thread James Carman (JIRA)

 [ 
https://issues.apache.org/jira/browse/WICKET-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

James Carman updated WICKET-1428:
-

Summary: AutoLinkResolver and Parent-Relative (../) Links  (was: 
AutoLinkResolver Does Not Resolve Relative Links Correctly)

 AutoLinkResolver and Parent-Relative (../) Links
 

 Key: WICKET-1428
 URL: https://issues.apache.org/jira/browse/WICKET-1428
 Project: Wicket
  Issue Type: New Feature
  Components: wicket
Affects Versions: 1.3.2
Reporter: James Carman
 Attachments: WICKET-1428.patch


 Suppose I have a package structure like this:
 com.mycompany.myproject
 --- module1
 --- page
 - Page1.html
 --- module2
 --- page
 - Page2.html
 If I want to autolink from Page1.html to Page2.html, it would look like:
 wicket:link
  a href=../../module2/page/Page2.htmlClick Here!/a
 /wicket:link
 This is not working, however.  The AutoLinkResolver spits out a warning 
 message:
 WARN  - AutoLinkResolver   - Did not find corresponding java class: 
 .module2.page.Page2

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.