• 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: WO5.4 and Java Client
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: WO5.4 and Java Client


  • Subject: Re: WO5.4 and Java Client
  • From: John Pollard <email@hidden>
  • Date: Wed, 31 Oct 2007 12:38:54 +0000

Hi Anjo,

I am not quite clear on what you are saying. I am not concerned about the Java interface for which we happen to use JFormDesigner at present. I really want to know whether the EOF / distribution jars are deprecated - the ones that let me write code on the client side, almost as if I were coding on the server side. Here is the list of jars that I currently load onto the client via jnlp:

    <jar href="JavaFoundation.jar" />
    <jar href="JavaEOControl.jar" />
    <jar href="JavaEOApplication.jar" />
    <jar href="JavaEOInterface.jar" />
    <jar href="JavaEOInterfaceSwing.jar" />
    <jar href="JavaEODistribution.jar" />
    <jar href="wojavaclient.jar" />

We may not actually use / need all of these as we are not using the NIB system, but most are needed. I am not sure if some of these are actually the same jar as on the server side, but wojavaclient.jar is client only.

Thanks
John

On 31 Oct 2007, at 12:25, Anjo Krank wrote:

The D2JC stuff still works if you replace the binary in the assistant package with a normal WO launch script. IB is pretty much dead for WO dev, but you can code your own components or write some GUI editor for it (or reuse the stuff other editors create for you).

Cheers, Anjo

Am 31.10.2007 um 08:39 schrieb John Pollard:

Deprecations in WO5.4:

Java Client Nib based applications
Direct to JavaClient based applications

Does this mean the end of Java Client full stop? We use Java Client but NOT Nibs or Direct To. Our Java interface is pure swing.

What we do depend on is basically the distributed EOF functionality to cache the object graph on the client side for run- time efficiency and ease of programming in traversing the object graph and executing queries in client side code. Am I clutching at straws in hoping that core client side jars will live on even if Nib-based interfaces / direct to are on the way out (no problem for us)?

Thanks,
John


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40logicunited.com


This email sent to email@hidden


_______________________________________________ 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: WO5.4 and Java Client
      • From: Anjo Krank <email@hidden>
References: 
 >WO5.4 and Java Client (From: John Pollard <email@hidden>)
 >Re: WO5.4 and Java Client (From: Anjo Krank <email@hidden>)

  • Prev by Date: Re: WO5.4 and Java Client
  • Next by Date: Re: State of the Union
  • Previous by thread: Re: WO5.4 and Java Client
  • Next by thread: Re: WO5.4 and Java Client
  • Index(es):
    • Date
    • Thread