Re: Changes of html-files are not directly available - need to re-deploy

[Riyad Kalla <rk...@gmail.com>]

Joachim,

Troubleshooting redeployment issues can be maddening. The *very first*
thing you have to rule out is that the file is actually getting placed
on disk in the deployed location. I don't know how NetBeans handles
it's deployments, if it points Tomcat at the internal project and runs
"in place" or if it actually copies out the project contents on-disk
to some deployed location.

Regardless, find the deployed location. Go change your HTML, save it,
then using a file explorer, go to the deployed location and manually
open the file that is in the deployed location (e.g. using Gedit on
Ubuntu) and confirm that those changes are in that HTML.

If they are, then the issue would be with Wicket polling and seeing
the changes and reloading them. If you don't see the changes, then the
issue is with NetBeans either not placing the files in the right
location or not being *Able to* place them -- i.e. a permission
problem (That running as root should have addressed).

NOTE: 1 last thing, I don't know how you are running Tomcat, but if
you are running it externally make sure it's running as the same user
as NetBeans. Othertiwse you could run into a silly situation of
NetBeans writing out files as "root" and Tomcat trying to read/load
the deployed files but not having read-perms on those "root-owned"
files.

Just want to avoid weirdness.

-R

On Tue, Feb 9, 2010 at 1:33 PM, Joachim Rohde
<ma...@joachimrohde.com> wrote:
> First of all: I asked this question already at
> http://www.coderanch.com/t/481846/Application-Frameworks/Application-Frameworks/Wicket-Changes-html-files-are
> where no one could help me.
>
> To my problem:
>
> I have here a little bug which is completly weird in my opinion.
> Usually when you are changing a html-file, you just need to save it and it
> is directly available in the browser after a refresh. But this behaviour is
> not working in my environment. I always have to deploy the complete project.
> It is not a problem of my project. I verified this by trying the exactly
> same project and also the quickstart from the official Wicket site on a
> different machine where it works as expected. So it must be somewhere in my
> configuration but I cannot figured it out where / what / why.
>
> Machine one, where it is not working runs on Ubuntu 9.10, IDE is Netbeans
> 6.8 with Maven 2.2.1, server is a Tomcat 6.0.24 (also tried Tomcat 6.0.18
> and also Jetty).
> Machine two, where it is working runs on Windows XP, IDE is Netbeans 6.7.1
> with Maven 2.2.1, server is a Tomcat 6.0.18.
>
> I am definitely running the development mode (verified this also by calling
> Application.get().getConfigurationType()). I tried the Wicket versions
> 1.4.4, 1.4.5 and 1.4.6. All the same. On the Ubuntu-System it's not working.
> I also tried already to start Netbeans as root-user on the Linux-system,
> just in case some access rights on my file-system are not sufficient.
> Without any change in the result.
>
> Only thing I found while searching was
> http://markmail.org/message/fqpioxh7dir67ttj#query:wicket%20html%20refresh+page:1+mid:ca74uawyqzjyj5v5+state:results
> where a mismatched dependency was the problem. But this does not seem to be
> my problem. In JIRA I couldn't find anything related.
>
> Anyone else encountered this problem? And even if not, I'm also open for
> blue shots what I might try because I have no clue what might cause this
> behaviour. Or anyone knows in which class the code for the reloading
> resides? I haven't found it yet, after a quick glance at the wicket sources.
> Help here is really appreciated. Thanks in advance for any comments.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: Changes of html-files are not directly available - need to re-deploy

[Joachim Rohde <ma...@joachimrohde.com>]

I found out what was wrong. Quite a rookie mistake: I relied on my IDE. 
As I mentioned I am using Netbeans where I have installed the Wicket 
plugin 
(http://plugins.netbeans.org/PluginPortal/faces/PluginDetailPage.jsp?pluginid=3586). 
It was the plugin which was copying the HTML files to the correct 
(server) folder after saving changes. And this behaviour is broken in 
Netbeans 6.8. In Netbeans 6.7.1 the plugin is working perfectly. I guess 
I didn't realize that the plugin is not compatible with NB 6.8 because 
on one hand the rest of the plugin seems to work perfectly (at least the 
parts that I am using) and on the other hand I was working the last 
weeks more on the backend of my project so that I didn't realize after 
the upgrade of Netbeans that not everything was working as expected. For 
now I'm using Netbeans 6.7.1 again.
Thanks for the help.


Am 09.02.2010 21:38, schrieb Riyad Kalla:
> Joachim,
>
> Troubleshooting redeployment issues can be maddening. The *very first*
> thing you have to rule out is that the file is actually getting placed
> on disk in the deployed location. I don't know how NetBeans handles
> it's deployments, if it points Tomcat at the internal project and runs
> "in place" or if it actually copies out the project contents on-disk
> to some deployed location.
>
> Regardless, find the deployed location. Go change your HTML, save it,
> then using a file explorer, go to the deployed location and manually
> open the file that is in the deployed location (e.g. using Gedit on
> Ubuntu) and confirm that those changes are in that HTML.
>
> If they are, then the issue would be with Wicket polling and seeing
> the changes and reloading them. If you don't see the changes, then the
> issue is with NetBeans either not placing the files in the right
> location or not being *Able to* place them -- i.e. a permission
> problem (That running as root should have addressed).
>
> NOTE: 1 last thing, I don't know how you are running Tomcat, but if
> you are running it externally make sure it's running as the same user
> as NetBeans. Othertiwse you could run into a silly situation of
> NetBeans writing out files as "root" and Tomcat trying to read/load
> the deployed files but not having read-perms on those "root-owned"
> files.
>
> Just want to avoid weirdness.
>
> -R
>
> On Tue, Feb 9, 2010 at 1:33 PM, Joachim Rohde
> <ma...@joachimrohde.com>  wrote:
>    
>> First of all: I asked this question already at
>> http://www.coderanch.com/t/481846/Application-Frameworks/Application-Frameworks/Wicket-Changes-html-files-are
>> where no one could help me.
>>
>> To my problem:
>>
>> I have here a little bug which is completly weird in my opinion.
>> Usually when you are changing a html-file, you just need to save it and it
>> is directly available in the browser after a refresh. But this behaviour is
>> not working in my environment. I always have to deploy the complete project.
>> It is not a problem of my project. I verified this by trying the exactly
>> same project and also the quickstart from the official Wicket site on a
>> different machine where it works as expected. So it must be somewhere in my
>> configuration but I cannot figured it out where / what / why.
>>
>> Machine one, where it is not working runs on Ubuntu 9.10, IDE is Netbeans
>> 6.8 with Maven 2.2.1, server is a Tomcat 6.0.24 (also tried Tomcat 6.0.18
>> and also Jetty).
>> Machine two, where it is working runs on Windows XP, IDE is Netbeans 6.7.1
>> with Maven 2.2.1, server is a Tomcat 6.0.18.
>>
>> I am definitely running the development mode (verified this also by calling
>> Application.get().getConfigurationType()). I tried the Wicket versions
>> 1.4.4, 1.4.5 and 1.4.6. All the same. On the Ubuntu-System it's not working.
>> I also tried already to start Netbeans as root-user on the Linux-system,
>> just in case some access rights on my file-system are not sufficient.
>> Without any change in the result.
>>
>> Only thing I found while searching was
>> http://markmail.org/message/fqpioxh7dir67ttj#query:wicket%20html%20refresh+page:1+mid:ca74uawyqzjyj5v5+state:results
>> where a mismatched dependency was the problem. But this does not seem to be
>> my problem. In JIRA I couldn't find anything related.
>>
>> Anyone else encountered this problem? And even if not, I'm also open for
>> blue shots what I might try because I have no clue what might cause this
>> behaviour. Or anyone knows in which class the code for the reloading
>> resides? I haven't found it yet, after a quick glance at the wicket sources.
>> Help here is really appreciated. Thanks in advance for any comments.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>>      
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
>
> Eingehende eMail ist virenfrei.
> Von AVG überprüft - www.avg.de
> Version: 9.0.733 / Virendatenbank: 271.1.1/2677 - Ausgabedatum: 02/09/10 08:35:00
>
>    


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org