|
Home > Archive > WebSphere Portal Server > May 2007 > Save and Run in RAD 7.0/Portal 6.0 Test environment
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 |
Save and Run in RAD 7.0/Portal 6.0 Test environment
|
|
|
| Hi,
i have just installed RAD 7 with WPS 6.0. I created a portlet and ran it on the 6.0 test environment.However each time i modify the Java or jsp file in the portlet i have to redeploy it using xmlaccess and restart the server. Did i miss any setting for
enabling the "Save and Run" feature of portal test environment?
| |
| Bala Labhishetty 2007-05-03, 7:22 pm |
| Hi,
Why you are using xmlaccess to deploy application in test environment? Just build the code and execute application. It will work, you can check any examples which are part of installation.
Thanks & Regards,
Bala
| |
|
| > Hi,
>
> Why you are using xmlaccess to deploy application in
> test environment? Just build the code and execute
> application. It will work, you can check any examples
> which are part of installation.
>
> Thanks & Regards,
> Bala
************************
Well but whenever i make any changes to the portlet, i have to republish the server. In RAD 6, portal used to pick up changes in Java and JSPs without publish or server restart. Am i missing something here?
Thanks
Abhishek
| |
| David Wilkerson 2007-05-04, 1:17 am |
| In RAD 7 you don't have to restart the server like you did in RAD 6.
Make the change, test the portlet app. It is as simple as it sounds.
David Wilkerson
--While I breathe I hope.
http://www.geedavid.com
For some of the best WebSphere Portal (including WebSphere Portlet Factory), Lotus Domino, Web Content Management and Workplace training see http://www.davalen.com
| |
|
| then looks like i am missing some setting. I have to restart the server every time i am making any changes to the JSP or Java file. The test environment is not picking up the changes.
Also, Once you create the portal configuration file (the one where you add your portlets and the wires), you cannot change it without destroying the whole project. This was a very simple thing to do in Portal5.1
| |
| David Wilkerson 2007-05-04, 1:21 pm |
| Hmmm... yes, it looks like something is missing.
Do you have a local instance of portal or you using the Remote Agent Controller and a sandbox server?
You might want to check the tutorials / redbooks for tips. Also WP610, the Portlet Development course.
Good luck!
--While I breathe I hope.
http://www.geedavid.com
For some of the best WebSphere Portal (including WebSphere Portlet Factory), Lotus Domino, Web Content Management and Workplace training see http://www.davalen.com
| |
|
| I have a local instance of portal.
Now I have created new portal 6 server on my machine.Then i opened the server configuration and opened the "Automatic Publishing" tab. The publishing delay time on my server was 15 sec (default). I modified it to 1 sec and now when i make any changes to t
he Java or JSP file of my portlet, it automatically republishes( after 1 sec delay) and the changes are picked up. But in RAD 6/WPS 5.1, the server republishing was not required. May be because RAD 7 doesn't have the test environment for Portal server unl
ike RAD 6/WPS 5.1.
| |
|
| Hi,
Currently, you would find that it requires a publish for it to reflect the changes to the server (instead of hot swapping). THis would reach its desired state in 7003.
To avoid all this do two things, first is switch off the automatic publish infact having a low value like 1 sec could be go against it, as this time specifies after how much time of changing artifacts is the publish going to kick off and because after th
e changes validators and builders are underway creating .class and other executables it will be incorrect to kick off the publish before that. Swithing off would ensure that no suprise publish happens on any save of artifacts.
Second is that for the time being try getting used to refresh browser whenever a static file change is done (java, jsp) instead of a publish. So, after switching off the automatic publish and once you have done the first publish (which will bring up the
browser inside RAD) just do refresh on the browser itself after changing things and hopefully it will meet ur need.
Kapil.
| |
|
| Hi Kapil,
If i switch off the automatic publishing, the changes are not picked up even when i refresh the browser.Actually,the server state gets changed to "Republish" whenever a Java or jsp file change is done.So i have to republish the server (either manually or
by auto publishing) every time i am making any file changes.
Is it this way in RAD 7 or i need to do some tweaking?
Abhishek
|
|
|
|
|