VWP migration
I migrated my app to VWP today. It took a few hours to resolve a few problems but that was probably more my fault that VWP's. The most irritating problem to solve the "Powered by Creator" component which I eventually ended up deleteing from the java and jsp source and finally managed to remove the complib.
I got my app to run in Netbeans's embedded Tomcat 5.5.17 which is the same as my production server. The NetBeans ant script now wars up my app and sends it off to Tomcat. Cool!
I've not really had many issues with the Sun Appserver in JSC except that every now and then I've got to reset the domain and my report server is tricky to install onto it. Anyway it makes sense for me to use Tomcat only. Just for reference I ran my app on Sun AppServer 9 and that went well too.
Along the way I had some out of band support from some of the Sun people. The issue they resolved was totally unrelated to any Sun or NetBeans product. What nice people!
All you folks looking for another app server -- I'd guess that with a little tinkering the ant script distributed with VWP would probably let you send off your app to Tomcat (hey why not Jetty?)
[1182 byte] By [
yossariana] at [2007-11-26 12:19:19]
# 1
hi yossarian,
Previously I had the same problem as yours, there were unresolved 'Powered by Creator' library and in my case 'Ajax library'. Could you explain how to get rid off that?
Second, how can you name your connection? I asked this in this forum before but no one answer this question. You have the chance to name the connection if you import the connection from JSC2. But if you make a new connection, netbeans doesn't give you the option.
thanks.
# 2
I used brute force :( I searched my project for "powered" and removed the Javabeans component from my page bean and the <pb: blah blah blah> tag from my jsp and the library entry and something in the manifest too.
What I ought to have done is tried to follow Edwin's instructions at http://wiki.java.net/bin/view/Javatools/AllAboutComplibs#Removing_a_Complib_Fro m_a_Projec as far as possible.
As far as naming the connection I assume you mean the DB connection? For this I did follow instructions : http://www.netbeans.org/kb/55/vwp-migration.html
Hope this helps!
# 3
Yes, DB connection. If you see the picture in http://www.netbeans.org/kb/55/vwp-migration.html , in Add Database Connection dialog box, you see that the Data Source Name field is grey ed. It means you can't change it. How do you change that? In JSC, it is possible to do so. So, I can have a lot of DSNs even for a single database. In Netbeans, the IDE just allocate the name automatically. Try it.
# 4
My JNDI names came across Ok ... no problems. Was this maybe a TP issue? Can you not just edit them in the web.xml file?
# 5
And I'm sure that after an hour or two of research i might try to change them by BRUTE FORCE! ;)
# 6
Tried it once in sessionbean1.java. But it wasn't successful. I don't want to mess up the web.xml since I don't understand it very much. I am trying to do everything visually.
# 7
VWP has a (mostly) visual web.xml editor... It's better than JSC's one...
# 8
Hi yossarian, ok. I try to evaluate the netbeans again. I hope it would be succesful this time. And also, I hope people in this forum don't get iritated when I throw a question about netbeans+vwp. I kinda like people in this forum.
# 9
Well, all the Sun folks seem to be behind the VWP product. And reading the NB users list I see a lot of the heavyweight java intellectual types throwing in their 2c... I must say I was surprised at how fast it came out of TP status.
A note on the web.xml editor ... On my system at least the non visual side of it sucks because it looks like it doesnt put a line feed between tags. But i can live with it!
Agreed, most days the JSC forum is a pleasant place. It helps a lot that Jetsons, Kish, Sakthivel et al come and impart their knowledge (and patience!)
# 10
This time the VWP didn't trigger missing data source problem. Just don't know why, but I can check on Data Source Reference node, and I find the DSN being flagged as error. I can resolve it.
But I've got problem when trying to run the project. It says there is deployment error and pointing to this line in build-impl.xml:
<nbdeploy debugmode="false" clientUrlPart="${client.urlPart}" forceRedeploy="${forceRedeploy}"/>
What seems to be the problem?
Second question: What is the password for the Tomcat admin?
# 11
Looks like the app server is having some problems redeploying your application. Does this happen the first time when you run the project or on subsequent deployments...
The admin's user name and password can be found inside
the <home-directory>/.netbeans/5.5/apache-tomcat-5.5.17_base/conf/tomcat-user s.xml
Mostly the user name is "ide". The password is usually garbled. Change that to a meaningful password and restart the server. Things should be fine.
# 12
hi deepsix,
This is the first time I run the project, and only a project that was imported from JSC2. I tried to create new project from the scratch ini netbeans and ran the project without problem. Only this imported project makes a headache. I tried to install/uninstall, delete the profile, but still no luck.
# 13
I racked my (somewhat overworked) brain today and came up with these recollections:
At some point I deleted the build directory from my project. Can't remember why.
I had a "Hello World" app running at the same time. I was going backwards and forwards between this and my app to get my app's library definitions looking the same.
I used a lot of clean and build commands
I had to restart the Tomcat at some stage.
Sorry I can't be more specific. When I get into brute force mode things get quite frenetic!
# 14
hi yossarian,you don't need to do brute force for deleting the 'powered by' component library. You can do it visually by editing the property of your project, just like the manual says.
# 15
Ohh ok!!Sorry cant be of much help in that area.. I dont know much about the migration stuff!
# 16
Yes, you're quite correct... Brute force was not the way to do it.
# 17
Do you have any trouble executing your imported project? I still can't make it run. I almost give up.
# 18
When I have some time I'll redo it and make some notes. Maybe tonight (if I have electricity :( ...) My project runs fine on the embedded Tomcat but I've not yet tested it on my production Server.Best I can do i'm afraid.
# 19
Finally..
I have managed to make my imported from JSC project running on netbeans+vwp. It's not running smoothly like what manual says, but I suspect something wrong with the embedded Tomcat. Luckily I still have my copy of tomcat 5.5.17 (currently they have 5.5.20), installed it on my pc, deploy and run the project into tomcat 5.5.17 (instead of the bundled one), and everything works fine after that.
