As several recent posts by me indicated I'm struggling to port my app
built with Railo 3.1.017 for Windows to Mac, that is, making the
compiled code to work on Railo for Mac environment. Two things we
need to keep in mind:
a) the app would be bundled with Railo and run locally for one user
only;
b) buying a Mac to "play" with is an option for me.
The closest Railo for Mac version I found from the Internet is, Railo
3.1.1 from softpedia website and the guy installed this version.
Compiled Railo for Windows (3.1.017) did not work on Railo 3.1.1 for
Mac. Denny suggested replacing the 3.1.1.rc on the Mac with the
3.1.017.rc, and it did the trick, that is, the compiled code worked
except that we received missinginclude error. Due to neglect on my
own part, I forgot to ask what's the exact missing file.
During last few days... we've been wrestling it without success, error
msg was posted to this group in different threads... and I noticed
that
Railo 3.1.017 for Windows (Express) uses Resin (web server) while
Railo 3.1.1 for Mac (Express) uses Jetty and
their directory structure is different, that is, 3.1.017 uses /webapps/
ROOT for web root while 3.1.1 uses /webroot for web root
and this could be the culprit for problems of our porting efforts. I
don't understand why architecture change for essentially same version,
but that's not that important, the Important Thing is, how to make the
remaining part of the porting work? Sorry I simply don't have the
luxury to hire a consultant who knows the Railo architecture ins and
outs. I'd appreciate insightful help.
Two things we need to keep in mind:
a) the app would be bundled with Railo and run locally for one user
only;
b) buying a Mac to "play" with is an option for me.
Sorry, typo, "b) buying a Mac to "play" with is an option for me.",
meant, not an option, as indicated in other similar thread.
Put it this way, between the choices of
changing 3.1.017 from Resin to Jetty
and
changing 3.1.1 from Jetty to Resin
which one is likely doable?
fyi, the guys with Railo for Mac is a programmer as well. tks.
On Dec 6, 8:33 am, justaguy <do...@yahoo.com> wrote:
> Sorry, typo, "b) buying a Mac to "play" with is an option for me.",
> meant, not an option, as indicated in other similar thread.
You keep saying that, without explaining _why_ it's not an option. That leads folks to believe that you simply don't want to spend the money on a Mac. That, in turn, leads folks to not want to spend their time helping you, because their time is just as valuable to them as your money is to you.
As Todd said in a previous thread, you're writing software for this platform. You're selling said software. It's not at all unreasonable to expect that you'd have a way to test this software yourself rather than relying on the goodwill of others.
I work on a Mac, but I have to test sites in IE and Windows-based versions of browsers. I purchased licenses for VMWare Fusion and various flavors of Windows.
If there's another reason that buying a Mac is truly "not an option" for you, perhaps it'd be best to state that reason and put all of the conjecture to rest.