This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Changing "Project Properties -> Run -> Server" to "Tomcat" causes Netbeans to clobber existing an context.xml file. I am expecting Netbeans to leave existing context.xml files alone or modify them without discarding existing data.
Thuy, can you please evaluate this issue ? thanks
To help us debug the issue, could you give more info such as - from which server you changed to tomcat server? - which version of tomcat server are you using - content of the context.xml file before and after it was modified when changing server Better yet, could you attached your web app, if possible, for us to replicate.
I believe I switched from Glassfish v2 to Tomcat 6.0.18. I will try creating a minimal testcase for you in the coming days in case you can't reproduce this without me. My context.xml file reads: <?xml version="1.0" encoding="UTF-8"?> <Context antiJARLocking="true" path="/adcaster/v1"> <Resource auth="Container" name="jdbc/adcaster" type="javax.sql.DataSource" password="password" driverClassName="com.mysql.jdbc.Driver" removeAbandoned="true" logAbandoned="true" username="username" url="jdbc:mysql://localhost:3307/adcaster1" initialSize="0" maxActive="10" maxIdle="0" maxWait="3000" poolPreparedStatements="true" maxOpenPreparedStatements="50" removeAbandonedTimeout="120"/> </Context>
There are some aditional info from the user - is this issue still INCOMPLETE or are we able to do something with it?
What is the NetBeans version? Is it 6.5 or 6.7? What is the project type? Web or maven? I can't reproduce the issue neither with trunk nor with 6.5.1. When I change the server all values except path are preserved.
This used to be in web, 6.5. I just checked and it seems to be fixed in 6.5.1.