× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.