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.
The server port setting in the project properties has no effect when using V3. Peter, what do you think that should be done with it (for GF), just disable?
Something along those lines, with some extra text explaining why it is disabled. Note that when debugging on GlassFish, it actually does use that setting (running on 3000++) I was intending to take care of this.
Peter wrote: > Note that when debugging on GlassFish, > it actually does use that setting (running on 3000++) Here is what I think you mean by "running on 3000++). Let me know if I am close. "Note that the Server Port setting does not have an effect on what port the IDE uses to start the GlassFish application server, nor on what port the IDE uses in the URL that it sends to the browser, except when you run an application using the Debug Project action. When you use the Debug Project action, the IDE uses Server Port setting (such as 8080, or 3000). If the specified port is available, the IDE will use that port for running the server, otherwise the IDE increments the port by one until it finds a free port." Note, this info goes in the online help so we should define how it should work so I can get that in the help. Thanks
That is correct, though since you begin with "Note that...", I must assume the context is appropriate. Overall, I'm not sure to what level I would like to educate the user on the technical issues of the V3 integration. Ideally, the user should not know or care about how V3 is integrated or why we made certain choices. It should simply work. However, for 6.5, debug and non-debug modes are different due to technical limitations of the current Rails Debugger module (no attach functionality). So non-debug mode runs against the full V3 server, similar to how the user would run in production if they use V3. Debug mode runs on a streamlined Grizzly/JRuby stack. Technically this restricts debugging to a subset of rails applications that do not use JavaEE facilities, but it is doubtful this will have an impact in practice.
In answer to Peter's question about contect... There is a Properties manager for Rails application that has several fields, two of which are server and port. This is what this bug is about. If you click the Help button you get a help topic that tells you about how to fill out the fields. Below is the text in the online help for the Port text field. Peter wrote "Overall, I'm not sure to what level I would like to educate the user on the technical issues of the V3 integration. Ideally, the user should not know or care about how V3 is integrated or why we made certain choices. It should simply work." Also, it seems you guys might disable this field for GlassFish. Thus, the online help for the Server Port Number in the Properties Manager will say the following. If you want me to say something about GlassFish, let me know: "Server Port Number. For the WEBrick and Mongrel servers, use this text box to specify the starting point for finding a free port. When the specified port is available, the IDE uses that port for running the server, otherwise the IDE increments the port by one until it finds a free port."
I cannot tell if this is resolved or should have a lower priority than 3... Please update the issue with more info.
lowering to p4
this is not fixed...
This has too low priority to be addressed now. I would like to accept debug settings from domain.xml in the future but we have no plans to support rails project properties. Closing this bug.