On Tuesday, July 24, 2007, 4:35:06 PM, Francisco [EMAIL PROTECTED] wrote:
No, not BS, simply that the issue you have is so fundamental[1] while
the info you give is so limited that there's nothing that anyone can
do to help. Your follow-up didn't add anything significant, so you
didn't get any
Thanks, the issue was due to local platform (Win XP) and has nothing to do
with wicket as far as I'm concern.
And works fine when provide the machines IP address instead of the machine
name. This sure looks like a DNS resolution issue all local and nothing to
do with wicket.
Thanks again,
f(t)
I see the questions didn't have anything to do with it.
just protocol bs...
anyways.
f(t)
On 7/20/07, Francisco Diaz Trepat - gmail [EMAIL PROTECTED]
wrote:
Tomcat, ie7, safari, and firefox. and wicket 1.3 beta 2.
On 7/20/07, Sean Sullivan [EMAIL PROTECTED] wrote:
Which web browser?
Hi has anyone has had this problem before?
I have a page and everything works fine. but when I click on a link at the
home page only works (goes to the page) if I am at localhost:// etc. even on
my own computer.
f(t)
-
This
Which web browser? Which version of wicket? Which app server?
On 7/20/07, Francisco Diaz Trepat - gmail [EMAIL PROTECTED]
wrote:
Hi has anyone has had this problem before?
I have a page and everything works fine. but when I click on a link at the
home page only works (goes to the page)
Tomcat, ie7, safari, and firefox. and wicket 1.3 beta 2.
On 7/20/07, Sean Sullivan [EMAIL PROTECTED] wrote:
Which web browser? Which version of wicket? Which app server?
On 7/20/07, Francisco Diaz Trepat - gmail [EMAIL PROTECTED]
wrote:
Hi has anyone has had this problem before?
