• 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: Auto Open Client Application isn't
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Auto Open Client Application isn't


  • Subject: Re: Auto Open Client Application isn't
  • From: Lachlan Deck <email@hidden>
  • Date: Fri, 25 Jan 2008 07:38:04 +1100

On 25/01/2008, at 5:19 AM, David Avendasora wrote:

On Jan 24, 2008, at 12:47 PM, Daryl Lee wrote:

On Jan 23, 2008, at 7:35 PM, David Avendasora wrote:

There also needs to be a ClasspathClient.txt file there. Just the launch script isn't enough. I just copied it from a different working app, but that obviously isn't the "Right Way" to do it. The contents are very straight-forward (see below) and seems to contain only the paths to the frameworks required by the client (hence the filename, I guess :). Is there a way to have this generated by WOLips or Ant?

I'm sure there is. That classpath file is relatively static and depending on where you put your custom frameworks (in or out of the .woa bundle) you might not have to modify it at all.

I'm assuming that Xcode generated this on-the-fly at build-time as I can't find it anywhere but in a Xcode-built app. Also of interest is the fact that if the ClasspathClient.txt file exists, WO uses that instead of whatever the normal source for it is.


The interesting thing is that unless you add your client-side class jar file to, it no longer just finds them in build/MyApp.woa/ Contents/WebServerResources/Java. You have to add them to this file. So it's a kind-of cascading effect that if you want Auto Open Client Application to work, you have to also change the way you manage your client-side class path to using the ClasspathClient.txt file, which means adding some way of generating this file. I'd rather not just rely on it being static, because sooner or later I'll change something (add a client-side framework like JBND) and then it will take a while for me to figure out why the client doesn't see it.

I guess the trick is to find a list of the WO frameworks required by the client-side of Java Client apps, add on any WebServerResources/Java jars.

Anybody have any suggestions?

Perhaps your build target call some target post-build that could (re) generate the ClasspathClient.txt file based on the project's dependencies...


with regards,
--

Lachlan Deck



_______________________________________________
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


  • Follow-Ups:
    • Re: Auto Open Client Application isn't
      • From: David Avendasora <email@hidden>
References: 
 >Auto Open Client Application isn't (From: David Avendasora <email@hidden>)
 >Re: Auto Open Client Application isn't (From: Xavier Destombes <email@hidden>)
 >Re: Auto Open Client Application isn't (From: Daryl Lee <email@hidden>)
 >Re: Auto Open Client Application isn't (From: David Avendasora <email@hidden>)
 >Re: Auto Open Client Application isn't (From: Daryl Lee <email@hidden>)
 >Re: Auto Open Client Application isn't (From: David Avendasora <email@hidden>)

  • Prev by Date: Re: new session on each request
  • Next by Date: Re: Auto Open Client Application isn't
  • Previous by thread: Re: wojavaclient.jar in WO5.4
  • Next by thread: Re: Auto Open Client Application isn't
  • Index(es):
    • Date
    • Thread