WC Dev Tool oddity in WCDE 5.6.1/6

[geo]

Hi Brian,

Something odd seems to occur in both 5.6.1 and 6.0 of the dev tooling.
Periodically our developers experience the following two situations.

Files are no longer able to be edited in RAD/WSAD. This has happened in
both 5.6.1 and 6.0 toolkit versioning. When you double click or otherwise
try to open the file it pops a grey content pane with a red error saying
that the file could not be opened in the window.

The other annoying one is the workspace becoming somehow disconnected from
the startup of the WC Test Server. Symptoms are starting the server and
eventually having it come back to say stopped with no visible error messages
and the server starts up. You cannot launch the internal browser since it
thinks the server is stopped, however, if you load a toolkit url
(http://localhost/webapp/wcs/stores/servlet/ConsumerDirect/index.jsp) the
page comes up fine and seems to process normally including the console log
being updated.

Since Brian is the only person on the newsgroup who seems to routinely
answer dev tool questions, I addressed this to him, but I would appreciate
direction from any/all participants.

[a***@gmail.com]

Hi Geo,

For the second issue try setting the following,
Double click your Server.. it opens a dialog:
change your connection type to use SOAP

- SOAP (More firewall compatible)
SOAP connector port: 8880

Hope it helps,
/Aritz

Post by geo
Hi Brian,
Something odd seems to occur in both 5.6.1 and 6.0 of the dev tooling.
Periodically our developers experience the following two situations.
Files are no longer able to be edited in RAD/WSAD. This has happened in
both 5.6.1 and 6.0 toolkit versioning. When you double click or otherwise
try to open the file it pops a grey content pane with a red error saying
that the file could not be opened in the window.
The other annoying one is the workspace becoming somehow disconnected from
the startup of the WC Test Server. Symptoms are starting the server and
eventually having it come back to say stopped with no visible error messages
and the server starts up. You cannot launch the internal browser since it
thinks the server is stopped, however, if you load a toolkit url
(http://localhost/webapp/wcs/stores/servlet/ConsumerDirect/index.jsp) the
page comes up fine and seems to process normally including the console log
being updated.
Since Brian is the only person on the newsgroup who seems to routinely
answer dev tool questions, I addressed this to him, but I would appreciate
direction from any/all participants.
--
George Niece
Solutions Architect
eGlobal Solutions
cel: 1-760-807-8823
AIM: GeorgeNiece
http://eGlobal-Sol.com

[Brian Lima]

Post by geo
Hi Brian,
Something odd seems to occur in both 5.6.1 and 6.0 of the dev tooling.
Periodically our developers experience the following two situations.
Files are no longer able to be edited in RAD/WSAD. This has happened in
both 5.6.1 and 6.0 toolkit versioning. When you double click or otherwise
try to open the file it pops a grey content pane with a red error saying
that the file could not be opened in the window.

Is it possible that you are changing the files using an editor outside
of RAD/WSAD? What I've seen is that if I edit some files using another
editor and RAD/WSAD doesn't know about it, strange things can happen
when you then try to open up the file in the IDE. I've seen things like
blank editors and sometimes errors messages. The fix for this situation
is to refresh the project prior to opening up the editor.

Post by geo
The other annoying one is the workspace becoming somehow disconnected from
the startup of the WC Test Server. Symptoms are starting the server and
eventually having it come back to say stopped with no visible error messages
and the server starts up. You cannot launch the internal browser since it
thinks the server is stopped, however, if you load a toolkit url
(http://localhost/webapp/wcs/stores/servlet/ConsumerDirect/index.jsp) the
page comes up fine and seems to process normally including the console log
being updated.

What do you mean by disconnected? Is this a case of you trying to start
the server and it always reports "Starting..." but clearly the server
(and application) have finished starting? If that's the case then the
workaround that I've used in the past is to change the server
communication protocol temporarily to SOAP instead of RMI. To do this
double click on the test server to open up the server configuration
editor. Locate the connection protocol section and change that to SOAP
instead of RMI. Save the changes and just right click on the server.
If the server has actually completed start up the status should change
to started within 15s or so.