|
Home > Archive > WebSphere Portal Server > April 2007 > Documentation for web.xml??
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Documentation for web.xml??
|
|
|
| I'm running RSA7 & WPS6 and I'm hoping someone can point me to some documentation to help me tweak my web.xml to cut down on server restarts. As it is I need to restart the project for any change I make, but I also need to restart the server for any chan
ges to javascript files and my stylesheet.
If the answer to my problem doesn't lie in the web.xml I'd like to hear that also.
Thanks
John
| |
|
| I hope you are using Run on Server on a local machine, if that is the case then it should work with the simple refresh of the browser also.
So, u need to publish it once to the server and then after that a browser witl open with that portlet in it, u can carry on with ur changes (limited to jsp and Java file changes) and then refresh the browser to see ur changes in the browser itself, u need
not publish again.
The other thing u should do it set the "Never publish automatically" as the default option in the server configuration of the server that u created in RAD. THis would prevent the auto publish of the project whenever any change is done in the project and w
ould be major help to u.
Hope it helps,
Kapil.
| |
|
|
Thanks Kapil
I am using "Run on Server" on a local machine, but every change requires that I right click on the project under the server and select "Restart projectEAR".
Under RAD 6 this was something I had to do intermittently, but using RSA 7 I have to do it for every change to a jsp or Java file. An interesting aside; the "Add Remove Projects..." selection on the right-click context menu of the server does nothing. I
n RAD 6 it opened a dialog that allowed me to add or remove a project. RSA 7, nothing.
I also have "Never publish automatically" selected in the server configuration. It doesn't help prevent restarts but it does keep the server from restarting every time you made a change. When not turned on, RSA would sometimes (not exaggerating) hang as
you typed because it was trying to re-publish.
As for actually restarting the server: I need to do that every time a change is made to any sort of 'static' file. I don't mind restarting after changes to xml files (faces-config.xml, portlet.xml, web.xml, the database mapping xml files), I'm familiar w
ith that behaviour from RAD 6 & WPS 5.1. My new frustration is with things like style sheets and javascript files. I don't understand why a server restart is required for changes to these files. I wouldn't be too upset if it was only a project restart.
Something else that is interesting: When we first started using this technology we would also need to restart the server on changes to *.properties files. Eventually this stopped, now properties files only require a project re-start, but we don't know
WHY this changed.
So I'm hoping that there might be a setting in the web.xml that decides how these files are served to the client. If I knew more about what arguments could be put in the file I might be able to find something that could help me out.
Thanks again
|
|
|
|
|