• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Deploying 5.2 and 5.4 on Windows
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Deploying 5.2 and 5.4 on Windows


  • Subject: Re: Deploying 5.2 and 5.4 on Windows
  • From: Chuck Hill <email@hidden>
  • Date: Thu, 18 Jun 2009 17:29:40 -0700

Please keep messages on the list.


On Jun 18, 2009, at 4:40 PM, Thomas Wedderburn-Bisshop wrote:

Thanks, Chuck, I'll give that a try.

Now a supplementary question:

Since I don't yet have access to the Windows deployment machine, I'd like to make sure I can deploy when I get to it. The current system uses the standard WO 5.2 deployment with JavaMonitor. My naive plan is to build a 5.4 app in WOLips, fully bundled with all WO frameworks, and just deploy it via JavaMonitor. That worked well on a different machine that was running WO 5.3. Will that work with 5.2?

I don't recall any JavaMonitor or wotaskd changes that would prevent this from working.



Chuck



On 19/06/2009, at 6:51 AM, Chuck Hill wrote:


On Jun 18, 2009, at 12:03 AM, Thomas Wedderburn-Bisshop wrote:

I have a customer with a WO 5.2 application deployed on Windows with Java 1.4, talking to MS SQl Server 2000. After upgrading the JDBC driver so it can talk to MS SQL Server 2008 database, it can access the database in the usual way, but can no longer access stored procedures via rawRowsForStoredProcedureNamed().

I suggested trying a new WO 5.4 application to see if it handles the newer JDBC driver any better.

However, of course they want the old application to keep running as we test the new app, and WO 5.4 requires Java 1.5. Is it possible to deploy a new WO app in Java 1.5 on Windows without disturbing the old 5.2 app?

Any thoughts are welcome.

Regards
Thomas

It should not be a problem. Windows makes it easy (far, far too easy) to have multiple JVMs installed. Just edit the classpath file in the .woa (.woa/Contents/Windows/CLSSPATH.TXT) to have the fully qualified path name for


# JVM              == java

That looks like a comment or commented out line, but it is NOT. You want

# JVM              == c:/foo/bar/my/java


Chuck

--
Chuck Hill             Senior Consultant / VP Development

Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/products/practical_webobjects










-- Chuck Hill Senior Consultant / VP Development

Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/products/practical_webobjects







_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Prev by Date: Re: WO Frameworks Location & Multiple Versions
  • Next by Date: strange inheritance problem
  • Previous by thread: Re: Missing WOString
  • Next by thread: strange inheritance problem
  • Index(es):
    • Date
    • Thread