[David Orriss Jr]

I know this sounds like an odd request, but what about swapping out the ‘core’ processing source in the TCP monitor for the TCP monitor code that comes with Apache Axis? I’ve found *that* tool to actually be a bit more reliable in showing me the contents of HTML streams than the one currently part of MyEclipse… The way the tool actually is *used* I have no real complaints about, but Apache’s codebase might prove more robust in some cases. It certainly has for me.

Just a thought I had…

[Riyad Kalla]

Does the tool from axis come with a UI interface, or were you just referring to information that is spit out to a console during run time?

[David Orriss Jr]

Yes it comes with it’s own UI. A very nice one, in fact…. But I think you could probably separate the underlying engine from that UI, keep the current UI components and just recycle their engine.. That way you could keep the existing feel but use the Axis monitor engine.

[Riyad Kalla]

Thank you Dave, I’m sending the suggestion on up.

[David Orriss Jr]

Thanks.. I edited out some of the typo’s in the original posting. That’s what I get for posting when I haven’t had enough coffee.. 😉

[Author]

Posts