[DavyBSG]

Hi,

Two queries for you….

While trying to deploy my war file so that it is accessible using the URL “http://localhost:myport/” I have managed to aquire a second instance of the app server connector as per the screen shot attached. Can someone please tell me how to get rid of this as there should only be 1 instance. If I try to start the second one, I get the error as per the attached screenshot.

Also, I am unable to deploy the project so that the web app is accessible with a context-root of “/”. Our production application works off the URL “http://host:port/index.jsp” but if I try to set this up witha project called MyProject, the IDE will generate a folder below the auto-deply directory called MyProject and I can only access the app via the URL http://host:port/MyProject/index.jsp. Even if i set the context-root to “/” for the project, I still cannot get this to work. Can you tell me what I need to do to get this working please?

IDE version Version: 8.6M1, Build id: 8.6M1-20100525
Web Server – Sun Java System Web Server 7 U8

Was unable to attach image so here is the error message

An internal error occurred during: “Launching Sun Java System Webserver 7.x”.

java.lang.IllegalArgumentException: classToLaunch cannot be null
at org.eclipse.jdt.launching.VMRunnerConfiguration.<init>(VMRunnerConfiguration.java:49)
at com.genuitec.eclipse.wdt.jsp.debug.MyEclipseLaunchConfigurationDelegate.launch(Unknown Source)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:866)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1069)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Thanks
David

[support-shalini]

David,
It looks like you have enabled a launch configuration. Can you go to Run > Run Configurations from the main menu and delete the launch configuration that you are not using?

To Set the context root to “/”, right click on your project, and from the context menu select Properties > MyEclipse > Web and in the “Context Root” tab, change the value of “Web Context-Root” to “/”
Let me know if that helps.

[DavyBSG]

Hi Shalini,

Thank you for your email. In relation to the second issue, I had already tried what you have suggested. In my original email I said that “Even if i set the context-root to “/” for the project, I still cannot get this to work. “. The steps I am following are

1. Install MyEclipse
2. Install Sun JSWS 7 U8 and use the Admin Console to set up new virtual server running on port 8100
3. Create new web project called “TestProject” in MyEclipse
4. Set the context root to “/” for this new project – Properties > MyEclipse > Web and in the “Context Root” tab, change the value of “Web Context-Root” to “/”

5. Configure Sun JSWS in MyEclipse
6. Deploy TestProject to new virtual server on Sun JSWS as an exploded app
7. MyEclipse created new directory called TestProject under the auto-deploy directory in Sun JSWS
8. Start Sun JSWS and request http://localhost:8100/index.jsp
9. Results in http 404 error
10. Request http://localhost:8100/TestProject/index.jsp
11. Page is served correctly

I also tried to deploy to a custom location and picked the Sun JSWS auto-deploy directory as the target.
This time the web app was deployed with ../auto-deploy/ as the root but requesting http://localhost:8100/index.jsp
resulted in an error again.

Thanks
David

[support-shalini]

David,
I shall escalate this issue to the dev team member. They will get back to you on this.

[DavyBSG]

Hi,

This has been open for a month now. Can you confirm if anyone has looked into this since the last update?
Thanks
David

[Brian Fernandes]

David,

I apologize for the delayed response, we evaluated this issue a month ago but the developer forgot to post a reply on the thread. The evaluation at that time led me to believe that deployment of this sort was not possible, on the contrary, we do support root deployment in MyEclipse.

My team will re-evaluate this problem, but the earliest time at which if a fix will be available will be in 9.0M2 or 8.6.0b, which is about a month out. Have you been able to deploy to the server root with manual deployment or using some other tools?

[DavyBSG]

Hi Brian,

Thank you for your response.

To answer your question, root deployment works fine when done via the SJSWS admin console. It only fails when done via MyEclipse IDE.

I guess it’s a bit frustrating as this feature request has been open for over a year now
– Originally added 30th July 2009 – and despite promises of delivery in several releases (8.5, 8.5M2, 8.5 GA, 8.6 GA..), it still does not work.

Based on the above, it is pretty clear that we are WAY down the priority list for requested features. I realize that the license fees paid are tiny but I still believe that we should be clearly informed as to whether or not our feature requests
are being dealt with in their entirety.

Regardless of the SLA, in my opinion 14 months is an unacceptable length of time to be waiting for a feature request to be implemented and I’m sure you can understand my frustration. Sure there are bugs in every release but basic functionality such as one-click debugging and root context deployment should be primary functional requirements of any IDE in my opinion and should not be missed in preliminary development iterations.

I am prepared to wait for 9.0M2 or 8.6.0b and would hope that after the release we can finally close off this request.

Regards
David

[Brian Fernandes]

David,

Thanks for the confirmation on root deployment.

In response to your other issues, I’m sure you realize that we can’t afford to implement everything our users ask us for. In fact, the entry we have for SJSWS support in our feature list lists only one user (you); I made the decision to support it when higher priority goals were met. We started development in Jan 2010 and delivered the first version for 8.5M2. If you look at your thread, we did not commit to supporting this server (other than submitting it for consideration as a new feature) until I stated it was in development in Jan this year.

I agree that both one click debugging and root deployment should not have been missing in a GA release. However, I had the choice to either axe the entire feature or release what we had working and I chose the latter. We fixed the debugging in the next possible release.

Based on the above, it is pretty clear that we are WAY down the priority list for requested features. I realize that the license fees paid are tiny but I still believe that we should be clearly informed as to whether or not our feature requests
are being dealt with in their entirety.

Yes, SJSWS is a lower priority feature and due to some fundamental differences in how this server works as compared to other servers, has actually been a very expensive feature too, especially considering the low demand for support. I agree that adequate communication between the MyEclipse team and our users is lacking and I will try make sure issues like this one can be better reported and tracked. I will update this thread with the development of this feature through the 9.0M2 release.

I realize that missing capabilities are frustrating, so I appreciate your patience and support in bringing this feature to maturity.

Best

[DavyBSG]

Thanks for the update Brian.

I agree that transparancy of progress is important in situations like this. Also, your efforts to accomodate our feature request are very much appreciated.
regards
David

[Author]

Posts