Jason,
This seems like bug in Warbler. Best place to report would be to post it
on user_at_jruby.codehaus.org and open a JIRA ticket at
http://kenai.com/projects/warbler/pages/Home.
Is there particular reason you want to use Warbler? With GlassFish v3
you dont need to package your app as a WAR file. All you need to do the
following using glassfish v3:
$ asadmin deploy --property jruby.home=/path-to-jrubyinstallation
yourRailsAppDir/
Check out latest glassfish v3 promotion from
http://download.java.net/glassfish/v3/promoted/glassfish-v3-b74b.zip and
simply directory deploy your app.
-vivek.
On 12/2/09 8:46 AM, glassfish_at_javadesktop.org wrote:
> Well thar seems to have been the problem my app is now working after:
>
> 1. jruby -S warble war
>
> 2. copying
>
> app/vendor/gem/gem_name/.specification
> to
> WEB-INF/vendor/gems/gem_name/.specification
>
> for each gem and then doing a
>
> 3. jruby -S warble war:jar
>
> 4. deploy the war to the glassfish server.
>
> What i don't understand is how anyone can get warble working out of the box when using gems? Either no one is using warbler for rails, or they are copying the gem files into their projects, or they are not using any gems, or I am doing something wrong.
>
> BTW I am using warbler (0.9.14) which i believe is the current version.
>
> any insights?
>
> Jason.
> [Message sent by forum member 'jasonfs' ]
>
> http://forums.java.net/jive/thread.jspa?messageID=374315
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>