This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 123900

Summary:	Rails WAR not getting deployed correctly
Product:	ruby	Reporter:	arungupta <arungupta>
Component:	Rails	Assignee:	Erno Mononen <emononen>
Status:	RESOLVED DUPLICATE
Severity:	blocker
Priority:	P2
Version:	6.x
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:

Description arungupta 2007-12-12 17:59:39 UTC

Using NB 6, a WAR file is created (war:standalone:create) from a Rails application but when deployed on (a fresh)
GlassFish as described at [1], then invoking localhost:8080/RailsApplication9 is showing directory structure of the
application. And invoking localhost:8080/RailsApplication9/say/hello gives a 404.

On WEBrick, localhost:3000/say/hello shows the correct view as expected.

This is also reported on my blog as a comment so more than one person has been able to reproduce it.

IIRC this used to work correctly with beta1. This is a regression.

[1] http://weblogs.java.net/blog/arungupta/archive/2007/09/jruby_on_rails_1.html

Comment 1 arungupta 2008-02-02 01:13:43 UTC

Reported again on my blog at:

http://blogs.sun.com/arungupta/entry/glassfish_jruby_and_netbeans_ruby#comments

Comment 2 Erno Mononen 2008-02-07 22:00:12 UTC

Could you attach the create WAR file here? Could be the same problem as in issue 126672, i.e. missing web.xml file. 
Possibly a goldspike issue, or rather an issue between the used Rails/JRuby/Goldspike versions. Please specify the 
exact versions of each of these that you have, and if you the cycles please try whether using Goldspike 1.4 helps. 
Thanks.

Comment 3 Erno Mononen 2008-02-08 15:03:12 UTC

This is likely a duplicate of issue 126672. The workaround is to reinstall the Goldspike plugin or create the project 
without support for WAR deployment and then install the goldspike plugin. After that you should refresh the rake 
targets and the war target will appear in the menu.

*** This issue has been marked as a duplicate of 126672 ***