beta udpate center. This will allow you to deploy your Rails application
> Erno Mononen wrote:
>> Hi Paul,
>>
>> Paul Fraser wrote:
>>> Netbeans JRuby Complete 200804011203 Ubuntu Hardy Heron 8.04
>>> Installed Glassfish V3 plugin and Glassfish Version 3 Gem
>>> Glassfish V3 does not appear in server list.
>>
>> Probably a bug, please file it against serverplugins/glassfish_v3 (it
>> might get reassigned then to ruby/rails depending on where the root
>> cause is).
>>
>>>
>>> I am somewhat confused (again) as to the procedure for setting up a
>>> system using glassfish v3 to serve JRuby Rails project developed in
>>> Netbeans.
>>> Goldspike, Warbler, Grizzly... how do they fit in. Then Tomcat,
>>> Apache and what else !!
>>>
>>> Any assistance in this pursuit would be appreciated.
>>> A simple listing of the procedure would be a delight...If in fact the
>>> aim is achievable..at this time.
>>
>> I can understand the confusion, there is not that much info /
>> documentation out there on these things yet. Arun Gupta has some very
>> informative blog entries on deploying JRuby Rails applications to
>> GlassFish, I'd recommend checking it out if you're not familiar with
>> it yet:
>>
>>
http://weblogs.java.net/blog/arungupta/ (you might want to search for
>> Rails entries).
>>
>> This article is also a good read:
>>
http://developers.sun.com/appserver/reference/techart/rails_gf/>>
>> Let me also try to summarize some of the above:
>>
>> If you want to deploy a JRuby Rails application to GlassFish, you have
>> two options: 1) WAR-based mode and 2) directory based mode. If using
>> the former mode, you need either GoldSpike or Warbler for creating a
>> war file from your Rails application. If the former, you don't need
>> either, you just point the server to the application directory.
>>
>> As for how this all works in NetBeans:
>>
>> For GlassFish V2, you need to create a war file and then deploy it
>> manually. NetBeans bundles the GoldSpike plugin for creating the war
>> file, deploying it means copying it to the autodeploy directory on the
>> server.
>>
>> For V3, after installing the V3 plugin the server should be available
>> in the list of servers and then using it is similar to using WEBrick /
>> Mongrel. It will use the directory based mode, so there is no need to
>> create a war file and no additional deployment step. If you're having
>> troubles with this scenario, please do file issues so that we can
>> resolve them. You can also deploy to V3 using the WAR based mode
>> similarly as with V2 if you like.
>>
>> Apache and/or Tomcat don't need to be involved in any of this in any
>> way - you can deploy WAR files to Tomcat too, and you can always front
>> your server with Apache, but it is by no means necessary when using
>> GlassFish.
>>
>> HTH,
>> Erno
> Thanks Erno,
>
> The problem I am finding is that the netbeans, jruby, glassfish world is
> advancing at a rapid pace and the blogs, videos etc. all get out of date
> very quickly, and some of the old advice is causing the confusion. For
> instance Arun Gupta's bloggings are excellent, but most reference to
> glassfish is command line stuff. I don't know how many wikis and blogs I
> have read trying to get the story for glassfish/netbeans.
> I could only find in one place the knowledge that the glassfish V3 gem
> is a cut down version of the full server and that is all that is needed
> in netbeans/rails.
> Your explanations are most welcome and clear the air considerably.
>
> Paul Fraser
>
> P.S. Trying to use the latest is either for the very clever or the very
> stupid :-\
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
dev-unsubscribe@...
> For additional commands, e-mail:
dev-help@...
>