Re: [Wicket-user] Bug in Wicketbench?

2006-11-13 Thread Joni Freeman
On Sun, 2006-11-12 at 20:13 +0100, Rik van der Kleij wrote:
> Hi Joni,
> 
> Do you have any idea why I'm getting the following error while  
> opening a wicketpage:
> Can't preview file. Check your wicket:preview path.
> 
> I have also wicket projects in Eclipse that do not have this error  
> but I can't understand why this happens or see any difference with a  
> project that gives this error.
> 
> Regards,
> Rik

Rik, this is probably a bug in parser which parses/combines the html
panels. However, I can't reproduce it here. Do you get any exception in
your eclipse log file? (it is located at
/.metadata/.log)

Joni


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user


Re: [Wicket-user] Bug in Wicketbench?

2006-11-12 Thread Rik van der Kleij
Hi Joni,

Do you have any idea why I'm getting the following error while  
opening a wicketpage:
Can't preview file. Check your wicket:preview path.

I have also wicket projects in Eclipse that do not have this error  
but I can't understand why this happens or see any difference with a  
project that gives this error.

Regards,
Rik


On 3-nov-2006, at 8:28, Joni Freeman wrote:

> On Fri, 2006-11-03 at 08:20 +0100, Rik van der Kleij wrote:
>>
>> Hi,
>>
>>
>> The issue is that remote debugging with Jetty and Maven from Eclipse
>> doesn't work right any more if the default editor is Wicket Editor.
>> While debugging the line of code that is executed by a thread is not
>> shown in the editor window anymore. Only the linenumber of the thread
>> is mentioned in the debug window.
>>
>>
>> Does someone recognize this behavior?
>
> Yes, this is a known bug. It is not possible to fix this easily in
> current eclipse versions. I (and some others) have reported the  
> issue to
> eclipse devs and the only news i've got from them is that they wont  
> fix
> it in 3.3. Let's hope it will be fixed at some point, though! A
> workaround is to set normal Java editor as a default editor when
> debugging.
>
> Joni
>
>
>
> -- 
> ---
> Using Tomcat but need to do more? Need to support web services,  
> security?
> Get stuff done quickly with pre-integrated technology to make your  
> job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache  
> Geronimo
> http://sel.as-us.falkag.net/sel? 
> cmd=lnk&kid=120709&bid=263057&dat=121642
> ___
> Wicket-user mailing list
> Wicket-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wicket-user


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user


Re: [Wicket-user] Bug in Wicketbench?

2006-11-02 Thread Joni Freeman
On Fri, 2006-11-03 at 08:20 +0100, Rik van der Kleij wrote:
> 
> Hi,
> 
> 
> The issue is that remote debugging with Jetty and Maven from Eclipse
> doesn't work right any more if the default editor is Wicket Editor.
> While debugging the line of code that is executed by a thread is not
> shown in the editor window anymore. Only the linenumber of the thread
> is mentioned in the debug window.
> 
> 
> Does someone recognize this behavior?

Yes, this is a known bug. It is not possible to fix this easily in
current eclipse versions. I (and some others) have reported the issue to
eclipse devs and the only news i've got from them is that they wont fix
it in 3.3. Let's hope it will be fixed at some point, though! A
workaround is to set normal Java editor as a default editor when
debugging.

Joni



-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user


[Wicket-user] Bug in Wicketbench?

2006-11-02 Thread Rik van der Kleij
Hi,The issue is that remote debugging with Jetty and Maven from Eclipse doesn't work right any more if the default editor is Wicket Editor.  While debugging the line of code that is executed by a thread is not shown in the editor window anymore. Only the linenumber of the thread is mentioned in the debug window.Does someone recognize this behavior?Regards,Rik-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user