RE: [editor] error badge problems

Hi Jirka,

Sorry for the delay in replying, but I'm in the USA, and everything ground to a halt here for thanksgiving weekend.

I would say that yes, this scenario is pretty much very similar to the case I described earlier.

I'm with you: there needs to be a trigger to cause re-parsing after the WS client has been refreshed. 

I think that would sort the issue out for both cases.

Let me know if you still want me to file an issue on this.

I would be happy to have your issue filed (since it's simpler to reproduce) and re-test my versioned scenario after this one is fixed if you like.

Let me know.

Regards,
Peter.

-----Original Message-----
From: Jiri.Prox@... [Jiri.Prox@...]
Sent: Thursday, November 22, 2007 8:06 AM
To: netcat@...
Subject: Re: [60cat] [editor] error badge problems

Hi Peter,

please file an issue. I've tried to reproduce  your steps to reproduce
and found following scenario, which is probably the same as yours but a
little bit straitforward (no versioning is needed). Can you, please,
confirm it?

Steps to reproduce:
1) create webproject A with some webservice (containing operation 'op')
2) create webproject B consuming webservice from A (using  WSDL URL to
locate the webservice)
3) create  class in A calling the opearation 'op'
4) change name of operation op  in project A and re-deploy project
5) change name of op in project B is the same way
-> there are valid error badges
6) refresh WS client in B
-> error badges don't go away util classes referencing WS are opened,
building project does not help

Seem that IDE should force reparsing related files somehow, when
refreshing WS client.

Regards
Jirka

Belbin, Peter wrote:

> I'm still seeing some cases where the error badges don't work well all
> the time.
>
> I had an example today.
>
> I'll try and describe it:
>
> Project (a) is exposing a web service which project (b) consumes.
>
> project (b) has a reference to project (a)'s web service using the
> http url to the wsdl.
>
> So, everything compiles up cleanly, no problems.
>
> Now, I use cvs to merge into the trunk of project (a) some code which
> adds a new method to the web service that is being exposed.
>
> I compile and deploy this project to the server.
>
> Next, I go to project (b) and do the same thing.
>
> Now, project (b) has some updated code, and some new unit test code
> thanks to the merge.
>
> The project code and test code now shows error badges (which is ok).
>
> I take a look at one of the two test cases, and realize that I really
> need to update the web service references.
>
> Error badges are showing against some of the project source, and the
> test cases.
>
> With the test case open in the ide, I then go to the web service
> references, and do a refresh, checking the 'replace' option.
>
> At this point, I believe the project code manages to figure out that
> the web service reference has been updated, and removes the error
> badge from the project source, and the test case I have open in the ide.
>
> However, the other test case still shows the error badge.
>
> I then do a full build, and the errant error badge is still being shown.
>
> What's up with that?
>
> I open the 2nd test case, and the error badge is removed.
>
>
>
>
> *NOTICE: This electronic mail transmission may contain confidential
> information and is intended only for the person(s) named.  Any use,
> copying or disclosure by any other person is strictly prohibited. If
> you have received this transmission in error, please notify the sender
> via e-mail.*
>
>
>

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________

NOTICE: This electronic mail transmission may contain confidential information and is intended only for the person(s) named.  Any use, copying or disclosure by any other person is strictly prohibited. If you have received this transmission in error, please notify the sender via e-mail.