Community
Participate
Working Groups
Has there been any work on the WebSphere 6.1 server plugin? Is there a plan to implement one?
Created attachment 53156 [details] Build path fix for WebSphere App Server 6.1 I've been trying to hack together a fix for this problem, but I keep running into bugs. This only gives you the ability to define a WebSphere 6.1 runtime and build projects against it. At this point, it cannot start or stop the server because an error is encountered in META-INF/ws-server-components.xml.
Has there been any progress on supporting WebSphere 6.1? When is this support expected (what version of Eclipse/WTP)?
This is a valid request, but since there has been no resource to work on this I am adding the helpwanted keyword to request help from the community.
Created attachment 95764 [details] Proposed patch for a serverdef for WebSphere6.1 This is a patch for a serverdef for WebSphere6.1 that uses the external commandline scripts for start/stop. Only tested on windows, but it should be similar for other platforms.
Hi, I would be very interested in fix for WAS 6.1 that users could pick up via the "New | Server" dialog. I tried stubbing the jars in bug# 247974 to get past server creation but starting the server fails as described above. I will try Eric's patch and advise. thank you michael(att)eclipselink.org
Created attachment 118383 [details] Proposed patch for a serverdef for WebSphere6.1 (updated) Updated diff against the latest code in cvs
Is there any News about this?
Hi, Any progress made concerning this issue?
There's any development regarding this issue? Please, any one can answer this?
Hi, we've tried to use the Eric's patch with Eclipse 3.5 and Websphere 6.1. However, it's not working for us. We did the following: 1) Checked out "org.eclipse.jst.server.websphere.core" from the repository. 2) Applied the patch by running "Team->Apply Patch" 3) Exported the project over "export->Plugin Development->Deployable plugins and fragments" as jar-file. 4) Extracted the jar-file 5) Copied the directory to eclipse/plugins (replaced the old directory) 6) Started Eclipse with eclipse -clean When we try to create a new Server via "new->Server" there are no Websphere Server to choose from. There is no IBM group anymore. Could someoene give us a hint what we did wrong? Perhaps someone could give a more detailed explanation how to install the patch, please? Thanks a lot
(In reply to comment #10) > Hi, > > we've tried to use the Eric's patch with Eclipse 3.5 and Websphere 6.1. > However, it's not working for us. Forget it, it won't work. Two months ago I tried the same... The reason why you don't see any WebSphere servers to choose from is because the plugin OSGI bundle is not loaded at startup. It's not loaded because the version number in your "new" plugin is the same as in the "old" version - the patch doesn't update it. Once I increased the version number and built the plugin again the servers showed up. HOWEVER, even with that fix the plugin is broken. I analyzed the code in the patch and came to the conclusion that it should never have worked. Either Eric Norman submit only half of his changes in the patch or...I simply don't know. Besides, the config in the patch circumvents one step in the server configuration wizard and has WTP invoke the WebSphere batch file(! Windows only) to start the server. Hence, it wouldn't be a cross platform solution anyway i.e. it would never have made it into the WTP code base. I invested many hours trying to put it right but eventually gave up. Nevertheless, I think I was close as I managed to configure the environment variables and the classpath to be the same as the ones used in the Windows batch files. Yet during server start WebSphere crashed with some obscure error. The launcher complained about one of the countless config files in the WebSphere home directory. I sought help on the WTP mailing list and I got directed to the IBM WebSphere support. As I don't have a support agreement with IBM there's no way I could open a ticket for that. If anyone is interested I could create an attachment with my patch. Maybe this could give someone with sufficient WebSphere know-how a head start.
Hi Marcel, I'm interested also by an integration between WAS6.1 and Eclipse 3.5. Could you give me the lastest patch to make some tests? Thanks a lot, (In reply to comment #11) > (In reply to comment #10) > > Hi, > > > > we've tried to use the Eric's patch with Eclipse 3.5 and Websphere 6.1. > > However, it's not working for us. > Forget it, it won't work. Two months ago I tried the same... > The reason why you don't see any WebSphere servers to choose from is because > the plugin OSGI bundle is not loaded at startup. It's not loaded because the > version number in your "new" plugin is the same as in the "old" version - the > patch doesn't update it. Once I increased the version number and built the > plugin again the servers showed up. > HOWEVER, even with that fix the plugin is broken. I analyzed the code in the > patch and came to the conclusion that it should never have worked. Either Eric > Norman submit only half of his changes in the patch or...I simply don't know. > Besides, the config in the patch circumvents one step in the server > configuration wizard and has WTP invoke the WebSphere batch file(! Windows > only) to start the server. Hence, it wouldn't be a cross platform solution > anyway i.e. it would never have made it into the WTP code base. > I invested many hours trying to put it right but eventually gave up. > Nevertheless, I think I was close as I managed to configure the environment > variables and the classpath to be the same as the ones used in the Windows > batch files. Yet during server start WebSphere crashed with some obscure error. > The launcher complained about one of the countless config files in the > WebSphere home directory. I sought help on the WTP mailing list and I got > directed to the IBM WebSphere support. As I don't have a support agreement with > IBM there's no way I could open a ticket for that. > If anyone is interested I could create an attachment with my patch. Maybe this > could give someone with sufficient WebSphere know-how a head start.
Created attachment 158400 [details] latest patch for WAS 6.1 I don't think the WebSphere61_ExternalServerBehaviour class is actually necessary. It's part of Eric Norman's original patch, though. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=160220#c11 (my comment #11 from 2010-01-14) for detailed information
(In reply to comment #13) > Created an attachment (id=158400) [details] > latest patch for WAS 6.1 > > I don't think the WebSphere61_ExternalServerBehaviour class is actually > necessary. It's part of Eric Norman's original patch, though. > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=160220#c11 (my comment #11 > from 2010-01-14) for detailed information WebSphere61_ExternalServerBehaviour is necessary, you need to put it as attribute value for attribute 'behaviourClass' into extension 'org.eclipse.wst.server.core.serverTypes' for websphere 6.1, without it server state is not correctly updated.
