Regardless, no one is forcing to use Java 9. Stay with Java 6 if you like.
On Sep 18, 2014 5:38 PM, "Joseph Pachod" wrote:
> We agree with your statement, our worry was more whether we could still
> compile our code against WO java 1.5 jars. Looks like it as well in the end.
>
> 2014-09-18 18:22
We agree with your statement, our worry was more whether we could still
compile our code against WO java 1.5 jars. Looks like it as well in the end.
2014-09-18 18:22 GMT+02:00 Ramsey Gurley :
> My understanding is that Java 9 will still be able to run Java 5 bytecode,
> it just won’t be able to c
My understanding is that Java 9 will still be able to run Java 5 bytecode, it
just won’t be able to compile for Java 5 and below. WO should still work fine
on new deployments.
On Sep 18, 2014, at 2:36 AM, Joseph Pachod wrote:
> Hi
>
> We're discussing how we/wonder could/would handle a new Ja
Hopefully in Hamburg, Germany, late April 2015.
- Mail original -
De: "Ken Anderson"
À: "Andrus Adamchik"
Cc: "Pascal Robert" , "WebObjects Development"
, "Patrick Robinson"
Envoyé: Jeudi 18 Septembre 2014 10:55:22
Objet: Re: Access to EOF/WebObjects source files - plan for the future?
Speaking of which, do we have a time or location yet?
On Sep 18, 2014, at 10:53 AM, Andrus Adamchik wrote:
>
> On Sep 18, 2014, at 5:44 PM, Pascal Robert wrote:
>
>> If you use ERRest, Andrus also have a REST framework
>> (https://github.com/nhl/link-rest) that works with Cayenne.
>
> Maybe
On Sep 18, 2014, at 5:44 PM, Pascal Robert wrote:
> If you use ERRest, Andrus also have a REST framework
> (https://github.com/nhl/link-rest) that works with Cayenne.
Maybe you guys can invite me to WOWODC next year - I can do LinkRest
presentation. It is good stuff and is quickly evolving to
I am. It is great for server-side HTML generation. Though of course server-side
HTML use is shrinking. More and more UI is 100% client-side, so I'd concentrate
on the backend REST services. For which I am using LinkRest - something that
Pascal just mentioned.
Andrus
On Sep 18, 2014, at 4:23 PM
I have looked at Tapestry, and so far it's nice. It have a very basic D2W
system (mostly for attributes ordering), so if you like the power of D2W, it's
not a solution.
If you use ERRest, Andrus also have a REST framework
(https://github.com/nhl/link-rest) that works with Cayenne.
- Mail o
Hi Andrus,
Are you still also using (and happy with) Apache Tapestry?
Just curious,
- Patrick
On Sep 18, 2014, at 7:41 AM, Andrus Adamchik wrote:
> WO in its binary form miraculously survived Java evolution for so many years.
> Not knowing the details of Java 9, I can't say what the next wo
Joseph,
We just have the binaries for WO and that is not going to change.
Should we lose binary compatibility in a future JVM release, WO will no longer
work. That’s an “if”, so, no way to tell.
Andrus has been working on Cayenne for a very long time, and it’s a viable
replacement for EOF. F
Hi Andrus
Thanks for the answer
Well, migration is a topic on its own, which I didn't intend to cover here,
only to know whether such a move would be needed. And if so, btw, what
about the WebObject part ? Any migration plan for it ?
But before having to go this far : would we be able to "patch/
WO in its binary form miraculously survived Java evolution for so many years.
Not knowing the details of Java 9, I can't say what the next workaround will
be, but I know there will be one :)
But seriously, you should probably start looking at Apache Cayenne or other
alternatives. You may check
Hi
We're discussing how we/wonder could/would handle a new Java version not
being backward compatible in regard to source code, as it has been rumored
to be the plan for Java 9.
As far as I've found, the source code of EOF/WebObjects is closed source,
not accessible and not modifiable. Is this ri
13 matches
Mail list logo
