CS 2 compatibility

8 views
Skip to first unread message

spills

unread,
Jun 1, 2011, 10:39:56 AM6/1/11
to ColdSpring-Users
I was wondering if CS 2 is Railo 3.3.xxx compatible with ORM support?
I am definitely pumped after seeing some the updates including closure
support, very cool!

Thanks

Brian Kotek

unread,
Jun 1, 2011, 11:21:54 AM6/1/11
to coldspri...@googlegroups.com
Mark can confirm, but my expectation would be that he is doing all of his development and testing on Adobe CF 9.01. It will probably fall to Railo users to pull it down, test it, and identify any problems (ideally with patches). He's already doing a ton of work and I don't think it's realistic to expect him to test it on Railo or BlueDragon and work around issues on those platforms on top of everything else that he's doing. So, I'd say give it a shot and report back!

Brian


 


--
You received this message because you are subscribed to the Google Groups "ColdSpring-Users" group.
To post to this group, send email to coldspri...@googlegroups.com.
To unsubscribe from this group, send email to coldspring-use...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/coldspring-users?hl=en.


Barney Boisvert

unread,
Jun 1, 2011, 11:31:20 AM6/1/11
to coldspri...@googlegroups.com
I did some work on Railo compatibility at cf.objective, and it mostly
works. However, there is a showstopper bug with the way Railo
implements component metadata. Neither server did it wrong, but they
did do it differently, and CS2 depends on the ACF implementation.
There is a ticket in against Railo for it, but for the meantime, it
won't work. Changing the CS2 implementation to not rely on ACF-style
component metadata would also be possible, but it seems likely Railo
will fix it before anyone gets around to porting the CS2
implementation (since I know Mark won't be doing it).

There are also some issues with Java collections, which CS2 uses under
the hood in a couple places. Railo behaves like a JEE app (and uses
Java-style zero-based indexing), while ACF does tries to extend it's
one-based indexing down to the Java layer (and partially succeeds).
So there's a bit of incompatibility between the two, below the CFML
layer.

cheers,
barneyb

--
Barney Boisvert
bboi...@gmail.com
http://www.barneyb.com/

spills

unread,
Jun 1, 2011, 2:44:38 PM6/1/11
to ColdSpring-Users
>....  However, there is a showstopper bug with the way Railo
> implements component metadata.  Neither server did it wrong, but they
> did do it differently, and CS2 depends on the ACF implementation.
> There is a ticket in against Railo for it, but for the meantime, it
> won't work.  

Do you by chance remember the ticket description as I looked at open
tickets on Railo Jira and not sure if I saw any open tickets that
would relate to this so if a ticket needs to be open .....
I guess as Brian says I will download and see what breaks.

> (and uses Java-style zero-based indexing), while ACF does tries to extend it's
> one-based indexing down to the Java layer (and partially succeeds).
>

Not being a Java expert but sounds relativity easy to create a Railo
implementation but, I am sure it is more complicated than you say.

I could run all the unit tests(not sure if they are available?) with
latest Railo version and see what dies.

spills

unread,
Jun 1, 2011, 2:52:09 PM6/1/11
to ColdSpring-Users
>. It will probably fall to Railo users to pull it down, test it, and identify any problems (ideally with
> patches). He's already doing a ton of work and I don't think it's realistic
> to expect him to test it on Railo or BlueDragon and work around issues on
> those platforms on top of everything else that he's doing.

First, Railo compatibility is listed on Trac as being available in
alpha 2 so that is what prompted my original inquiry.

Second, I am happy to put time to help on a project like this where I
can help(see next).

Third, this is a smart list of people with a great deal of experience
and capabilities beyond mine that I have learned from over the years
so ... be gentle, I bruise easily.

Thanks to Mark and everyone else on this project because, I could not
imagine developing application without CS.

Spills

Barney Boisvert

unread,
Jun 1, 2011, 3:32:03 PM6/1/11
to coldspri...@googlegroups.com
> I could run all the unit tests(not sure if they are available?) with
> latest Railo version and see what dies.

Yup, they're available in the project root. Mark merged in my
compatibility changes a week ago, so make sure you pull from a current
repo.

> Not being a Java expert but sounds relativity easy to create a Railo
> implementation but, I am sure it is more complicated than you say.

The collections-related issues should be pretty isolated and have good
test coverage, so hack away! The metadata one is a bit more
fundamental in what it underlies, and solving it in a platform-neutral
way has potential performance implications as well as future
maintainability implications, so definitely best done with much
involvement from Mark (at least discussion, not necessarily code).

> Do you by chance remember the ticket description

I don't know the Railo ticket number; I only know it's there because
Mark told me he'd submitted it and it hadn't yet been resolved.

cheers,
barneyb

Sean Corfield

unread,
Jun 1, 2011, 5:08:07 PM6/1/11
to coldspri...@googlegroups.com
On Wed, Jun 1, 2011 at 8:31 AM, Barney Boisvert <bboi...@gmail.com> wrote:
> I did some work on Railo compatibility at cf.objective, and it mostly
> works.  However, there is a showstopper bug with the way Railo
> implements component metadata.

Fixed in the Railo 3.3 stream. I need to upgrade World Singles from
3.2 to 3.3 so we can attempt to upgrade from CS1.2 to CS2 (again).

> There are also some issues with Java collections, which CS2 uses under
> the hood in a couple places.  Railo behaves like a JEE app (and uses
> Java-style zero-based indexing), while ACF does tries to extend it's
> one-based indexing down to the Java layer (and partially succeeds).

Interesting. I hadn't noticed that. I'm surprised ACF tries to
override the underlying Java behavior - that seems a bit dangerous.
--
Sean A Corfield -- (904) 302-SEAN
An Architect's View -- http://corfield.org/
World Singles, LLC. -- http://worldsingles.com/
Railo Technologies, Inc. -- http://www.getrailo.com/

"Perfection is the enemy of the good."
-- Gustave Flaubert, French realist novelist (1821-1880)

Barney Boisvert

unread,
Jun 1, 2011, 5:37:28 PM6/1/11
to coldspri...@googlegroups.com
On Wed, Jun 1, 2011 at 2:08 PM, Sean Corfield <seanco...@gmail.com> wrote:
> Interesting. I hadn't noticed that. I'm surprised ACF tries to
> override the underlying Java behavior - that seems a bit dangerous.

I didn't delve into it much beyond noticing the tests all failed with
off-by-one bugs. So I'm not sure of the specifics, but they were in
CS2's internal collections classes. I have run into other
discrepancies between ACF's collections and the Railo ones in certain
cases, and just sort of assumed it was another manifestation of the
same issue.

cheers,
barneyb

Mark Mandel

unread,
Jun 1, 2011, 5:56:27 PM6/1/11
to coldspri...@googlegroups.com
Ah interesting! Will have to look into that further for sure!

Just plugging away at writing documentation for CS2 :) fun fun. and then we can do an actual release of Alpha1.

Volunteers welcome! Plenty of stuff to write that doesn't need a knowledge of CS2 internals for sure.

Mark

--
You received this message because you are subscribed to the Google Groups "ColdSpring-Users" group.
To post to this group, send email to coldspri...@googlegroups.com.
To unsubscribe from this group, send email to coldspring-use...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/coldspring-users?hl=en.




--
E: mark....@gmail.com
T: http://www.twitter.com/neurotic
W: www.compoundtheory.com

cf.Objective(ANZ) - Nov 17, 18 - Melbourne Australia
http://www.cfobjective.com.au

Hands-on ColdFusion ORM Training
www.ColdFusionOrmTraining.com
Reply all
Reply to author
Forward
0 new messages