Re: WebSphere Test Environment in 6.0

Heh, heh, good point Mark.

I would guess that there is likely a RAD for Linux.  I had WSAD V5.1 
installed on FC1 for a while. Unfortunately WDSC still has some native 
Windows stuff that would make it not run on platforms other than Windows.

As far as the install path, well,  I will admit that I know little about 
WDSC install .  It is probably the way it is in order to conform to 
Windows standards and the complex RAD install.  As I understand it with 
RAD you can have multiple products installed (WDSC being one) and they 
share plugins and install tidbits somehow.

One last thing.  I specify that the WAS config stuff gets stored in my 
workspace, I think the default for V6 is in the install .  Then just 
moving my workspace helps to resolve most path-length problems. 

Mike

Mike Hockings, P.Eng.
WebSphere Development Tools for AS/400  -  CODE/Designer & WebFacing !
IBM Canada Ltd. Laboratory 
hockings@xxxxxxxxxx 





Mark Phippard <markp@xxxxxxxxxxxxxxx> 
Sent by: wdsci-l-bounces+hockings=ca.ibm.com@xxxxxxxxxxxx
2006-06-23 16:25
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
cc

Subject
Re: [WDSCI-L] WebSphere Test Environment in 6.0






wdsci-l-bounces@xxxxxxxxxxxx wrote on 06/23/2006 04:13:09 PM:

Just to be very clear this is a Windows path length limitation (256 

chars 

I think).  Eclipse & WAS can handle long path names just fine on other 
platforms.

The work around is correct.  I create all my workspaces in 

d:\workspaces. 

 Also you can make thinks like the project name,  Web context name, JSP 
names, etc  short as they contribute to the length.

Yes, this is a Windows limitation, but lets also be a bit fair here in 
spreading the blame around.  The problem is not just the workspace 
location.  The error that was reported is actually located within the 
WebSphere runtime location (which we can only control by installing WDSC 
into a shorter path).  The reality is that this problem also existed in 
the 5.x releases and IBM has still not done anything to help the problem. 
Such as installing into a much shorter default path structure, or allowing 

us to control where the WebSphere runtime is located.

Since the problem surfaced in 5.x, I now override the install to go to 
C:\IBM\WDSC\6.0 and I also use a C:\workspaces for all my workspaces.  As 
it currently stands, the default path that IBM installs into almost 
guarantees you will run into this problem if you do not override 
something.

Since IBM cannot fix Windows, it ought to use a much shorter default path, 

and even better would be to let me install WDSC on Ubuntu or OSX.

Mark