Win a copy of Beginning Java 17 Fundamentals: Object-Oriented Programming in Java 17 this week in the Java in General forum!

Thomas Hatley

+ Follow
since Aug 29, 2004
Cows and Likes
Total received
In last 30 days
Total given
Total received
Received in last 30 days
Total given
Given in last 30 days
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Thomas Hatley

Greetings Jothi -

Not sure if you're still having issues with this, but if you're doing a standard build/package where the war is being put into the <project_home>/target folder, I'd suggest removing the optional <warFile> element and allowing the tomcat-plugin to use the default settings. This seems to work quite well for me, using a mvn clean tomcat:redeploy will build and push up the new war. Which reminds me, using the 'clean' goal prior to any build is a good practice to get into, as it assures that you're getting the freshest bits.

My current configuration is:

Keep in mind that by default the tomcat-plugin will expect your manager login to be "admin' "<blank>", in other words the user is 'admin' and there is no password set....these are configured in the <tomcat_home>/conf/tomcat-users.xml file.

Hope this helps someone!
12 years ago
Noticed that RPC style service was used - seems to be the easy way out of some (at times) difficult issues surrounding current web service implementations.

Web services best practices is moving away from RPC and towards doc/literal to allow better compatability with non-Java clients. In fact, Axis2 is about ready for it's 1.0 release (currently at 0.95) and the entire premise of Axis2 is to provide more support for doc/literal and to meet industry standards better than previously with RPC.

As a developer who is just finishing a project which exposes a Java-based service to .Net consumers/clients, I found that the many quick-n-easy tutorials of RPC services returning simple types seemed to do Java developers more of an injustice rather than provide examples of services which are compatible with Java clients rather than any clients seems to set the beginning developers up for failure shortly down the road whent their help desk phone rings saying "a new .Net company can't digest our what?" and the beaming-proudly-just-a-minute-ago developer is totally lost.

I think more articles focusing on current standards for web servcies are better suited to JavaRanch readers/memebers...
15 years ago