Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 167535

Summary: MAX tries to do a getResourcePropertyDocument when establishing a connection
Product: z_Archived Reporter: Andrew Eberbach <aeberbac>
Component: TPTP.monitoringAssignee: Balan Subramanian <bsubram>
Status: CLOSED FIXED QA Contact: Bhanu Prathap V <bhanu.prathap>
Severity: major    
Priority: P1 CC: bsubram, davidmelgar
Version: unspecifiedKeywords: plan
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
Do MEX instead of getResourcePropertyDocument on connect
none
Do MEX or look for SG specific property instead of doing getResourcePropertyDocument
none
Do MEX or look for SG specific property instead of doing getResourcePropertyDocument none

Description Andrew Eberbach CLA 2006-12-12 00:20:59 EST 
This method is optional and causes MAX to fail to connect to resources that are actually valid. A suggested fix is simply removing the call from MuseRuntime in the org.eclipse.tptp.monitoring.managedagent.wsdm.muse plugin.
Comment 1 Balan Subramanian CLA 2007-01-15 22:44:02 EST 
*** Bug 167275 has been marked as a duplicate of this bug. ***
Comment 2 Dave Smith CLA 2007-02-06 16:37:09 EST 
Target to iteration 2 as per Balan's spreadsheet.
Comment 3 Bhanu Prathap V CLA 2007-03-14 02:45:45 EDT 
Could not connect MAX, So unable to verify 
Build: tptpaide-2007-03-09-05-00-00
Comment 4 Balan Subramanian CLA 2007-04-26 20:15:14 EDT 
Created attachment 65130 [details]
Do MEX instead of getResourcePropertyDocument on connect
Comment 5 Balan Subramanian CLA 2007-04-26 20:35:01 EDT 
Created attachment 65131 [details]
Do MEX or look for SG specific property instead of doing getResourcePropertyDocument
Comment 6 Balan Subramanian CLA 2007-04-26 20:35:08 EDT 
Created attachment 65132 [details]
Do MEX or look for SG specific property instead of doing getResourcePropertyDocument
Comment 7 Balan Subramanian CLA 2007-04-26 20:37:38 EDT 
MAX no longer uses getResourcePropertyDocument to check if it can connect/ping the WSDM resource. Instead it,
a) checks to see if this is a SG by looking for a SG specific property. If no exception is thrown, it assumes the endpoint can be looked at using MAX
b) if a fails, then it checks to see if the resource supports MEX. Only resources (other than SGs) that support MEX are viewable through the MAX.

Also if MAX does b it saves the WSDL it gets through MEX so that it doesn't have to get it again to inspect the WSDL.
Comment 8 Bhanu Prathap V CLA 2007-05-03 06:28:48 EDT 
Verified - fixed
Build: TPTP-4.4.0-200705021157
Comment 9 Bhanu Prathap V CLA 2007-05-03 06:29:08 EDT 
Verified - fixed
Build: TPTP-4.4.0-200705021157