×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




Thanks Justin.
Interesting to see that while the Service Entry Points view is cleared of sep info, source member(s) retain break point marks.
Another thread I saw today mentioned clearing breakpoints if and when RDi should be slow starting debug.
Definitely easier to re-load the SEP view than re-set breakpoints, and I see how leaving break-points set could be a problem.


-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Justin Taylor
Sent: Monday, November 03, 2014 9:55 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] New to SEP

You have to recreate the SEP every time you restart RDi.



-----Original Message-----
From: Gary Thompson [mailto:gthompson@xxxxxxxxxxx]
Sent: Monday, November 03, 2014 8:00 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: [WDSCI-L] New to SEP

Last week I started using a Service Entry Point for a small app I'm testing.

Today I'm surprised that my SEP view is empty, thinking it would have been saved ?

What am I missing ?

--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2026 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.