Home » Language IDEs » ServerTools (WTP) » Using J2EE 'server' as a pre-deployment test environment
| Using J2EE 'server' as a pre-deployment test environment [message #207277] |
Mon, 21 January 2008 21:46  |
 John J. Barton
Messages: 311
Registered: July 2009 |
Senior Member |
|
|
I've tried various combinations of configurations in the Server function
of WTP without finding the one that would be ideal for me.
I want to run with eclipse against a Tomcat installation, test the
service, then stop the server and do svn commit on the Tomcat tree to
commit the new deployment. On the customer machine I just want to svn
update to get the new version. This gives minimal time on the customer
machine and good overlap between test and deploy environments.
I tried using server settings "Use Tomcat installation", but something
that WTP does corrupts the directory that svn needs. The tree cannot be
committed after WTP works on it.
The best, and it's not very good, that I have is to test, go over to
Tomcat install, delete the servlet, go back to eclipse, export .war,
commit svn. At least the customer site has the update-run experience.
I suppose I could go back to uploading war files in to the test and
customer machines, but that is so tedious...
Any other approaches/ideas?
Thanks,
John
|
|
|
| Re: Using J2EE 'server' as a pre-deployment test environment [message #207280 is a reply to message #207277] |
Tue, 22 January 2008 13:22  |
Larry Isaacs
Messages: 1354
Registered: July 2009 |
Senior Member |
|
|
John J Barton wrote:
> I've tried various combinations of configurations in the Server function
> of WTP without finding the one that would be ideal for me.
>
> I want to run with eclipse against a Tomcat installation, test the
> service, then stop the server and do svn commit on the Tomcat tree to
> commit the new deployment. On the customer machine I just want to svn
> update to get the new version. This gives minimal time on the customer
> machine and good overlap between test and deploy environments.
>
> I tried using server settings "Use Tomcat installation", but something
> that WTP does corrupts the directory that svn needs. The tree cannot be
> committed after WTP works on it.
>
> The best, and it's not very good, that I have is to test, go over to
> Tomcat install, delete the servlet, go back to eclipse, export .war,
> commit svn. At least the customer site has the update-run experience.
>
> I suppose I could go back to uploading war files in to the test and
> customer machines, but that is so tedious...
>
> Any other approaches/ideas?
> Thanks,
> John
Do you know what it is about the changes that causes svn to be unwilling
to commit the tree?
Cheers,
Larry
|
|
|
| Re: Using J2EE 'server' as a pre-deployment test environment [message #207285 is a reply to message #207280] |
Tue, 22 January 2008 18:54 |
John J. Barton
Messages: 311
Registered: July 2009 |
Senior Member |
|
|
Larry Isaacs wrote:
> John J Barton wrote:
>> I've tried various combinations of configurations in the Server
>> function of WTP without finding the one that would be ideal for me.
>>
>> I want to run with eclipse against a Tomcat installation, test the
>> service, then stop the server and do svn commit on the Tomcat tree to
>> commit the new deployment. On the customer machine I just want to svn
>> update to get the new version. This gives minimal time on the customer
>> machine and good overlap between test and deploy environments.
>>
>> I tried using server settings "Use Tomcat installation", but something
>> that WTP does corrupts the directory that svn needs. The tree cannot
>> be committed after WTP works on it.
>>
>> The best, and it's not very good, that I have is to test, go over to
>> Tomcat install, delete the servlet, go back to eclipse, export .war,
>> commit svn. At least the customer site has the update-run experience.
>>
>> I suppose I could go back to uploading war files in to the test and
>> customer machines, but that is so tedious...
>>
>> Any other approaches/ideas?
>> Thanks,
>> John
>
> Do you know what it is about the changes that causes svn to be unwilling
> to commit the tree?
>
No, it actually surprised me, I often delete directories under svn and
it just says they are missing. But then I can't say I've deleted then
added a new directory of the same name but without the .svn control files.
I suppose I could add an ant build to copy the tomcat .svn files into
the webapp folder every time I publish. Of course then I could just do
the whole job that way.
> Cheers,
> Larry
|
|
|
| Re: Using J2EE 'server' as a pre-deployment test environment [message #207349 is a reply to message #207285] |
Wed, 23 January 2008 17:32 |
Larry Isaacs
Messages: 1354
Registered: July 2009 |
Senior Member |
|
|
John J Barton wrote:
> Larry Isaacs wrote:
>> John J Barton wrote:
>>> I've tried various combinations of configurations in the Server
>>> function of WTP without finding the one that would be ideal for me.
>>>
>>> I want to run with eclipse against a Tomcat installation, test the
>>> service, then stop the server and do svn commit on the Tomcat tree
>>> to commit the new deployment. On the customer machine I just want to
>>> svn update to get the new version. This gives minimal time on the
>>> customer machine and good overlap between test and deploy environments.
>>>
>>> I tried using server settings "Use Tomcat installation", but
>>> something that WTP does corrupts the directory that svn needs. The
>>> tree cannot be committed after WTP works on it.
>>>
>>> The best, and it's not very good, that I have is to test, go over to
>>> Tomcat install, delete the servlet, go back to eclipse, export .war,
>>> commit svn. At least the customer site has the update-run experience.
>>>
>>> I suppose I could go back to uploading war files in to the test and
>>> customer machines, but that is so tedious...
>>>
>>> Any other approaches/ideas?
>>> Thanks,
>>> John
>>
>> Do you know what it is about the changes that causes svn to be
>> unwilling to commit the tree?
>>
>
> No, it actually surprised me, I often delete directories under svn and
> it just says they are missing. But then I can't say I've deleted then
> added a new directory of the same name but without the .svn control files.
>
> I suppose I could add an ant build to copy the tomcat .svn files into
> the webapp folder every time I publish. Of course then I could just do
> the whole job that way.
What is happening is that publishing the module means "synchronizing"
the published content with what is in the project. If files and folders
are found at the destination which don't have an equivalent resource in
your project, the assumption is that this resource did exist in the
project and was deleted. As a result, those files and folders get
deleted from the destination in order to achieve "synchronization".
If you were to import the svn files and folders into the WebContent
portion of the project and published once, then publishing would leave
these files alone in subsequent publishes as long as the file wasn't
changed in Eclipse. Only if you ran the "Clean..." command from the
Servers view context menu would the Eclipse files overwrite the
destination files. Perhaps that approach would be preferable to your
current alternatives.
Larry
>
>> Cheers,
>> Larry
|
|
|
Goto Forum:
Current Time: Sat Apr 20 04:27:09 GMT 2024
Powered by FUDForum. Page generated in 0.03047 seconds |
] 
Search
Help
Register
Login
Home
