| At line 36 changed 2 lines. |
| When users create WSDL file using "ns/wsdl" as part of the WSDL namespace URI, |
| the JBI WSDL shared library should be able to support it. |
| Another problem we are trying to solve here is that when users create WSDL file |
| using "ns/wsdl" as part of the WSDL namespace URI, the JBI WSDL shared library |
| should be able to support it. |
| At line 42 changed 1 line. |
| For WSDL shared library API backward compatibility, the deprecated API methods should be identified by comparing JBI public WSDL API interfaces between the versions before and after the WSDL upgrade. These deprecated API methods will be implemented and will be added back to WSDL shared library. |
| For WSDL shared library API backward compatibility, the deprecated API methods |
| should be identified by comparing JBI public WSDL API interfaces between the |
| versions before and after the WSDL upgrade. These deprecated API methods will |
| be implemented and will be added back to WSDL shared library. |
| At line 44 changed 1 line. |
| For WSDL namespace URI forward compatibility, more than one WSDL files should be created with "ns/wsdl" as part of namespace, and should be tested with JBI WSDL shared library. The code level changes should be determined by the testing results. |
| For WSDL namespace URI forward compatibility, more than one WSDL files should be |
| created with "ns/wsdl" as part of namespace, and should be tested with JBI WSDL |
| shared library. The code level changes should be determined by the testing |
| results. |
| At line 56 changed 1 line. |
| Backward compatibility with 2004/08 from a parsing standpoint was considered, but we decided not to implement it at this time, since it may take much more time and we may benifit too much from it. |
| Backward compatibility with 2004/08 from a parsing standpoint was considered, |
| but we decided not to implement it at this time, since it may take much more |
| time and we may benifit too much from it. |
| At line 60 changed 2 lines. |
| No new interfaces will be introduced, but the JBI public WSDL interfaces under |
| open-esb/runtime/base.src/com/sun/jbi/wsdl2 should be comapred between the versions before and after the WSDL upgrade in order to identify the deprecated methods. |
| No new interfaces will be introduced, but the JBI public WSDL interfaces under |
| open-esb/runtime/base.src/com/sun/jbi/wsdl2 should be comapred between the |
| versions before and after the WSDL upgrade in order to identify the deprecated |
| methods. |
| At line 65 changed 1 line. |
| There may be some information required in the JBI developer guide about the deprecated methods which will be add back to the WSDL shared library. |
| There may be some information required in the JBI developer guide about the |
| deprecated methods which will be add back to the WSDL shared library. |
| At line 67 changed 1 line. |
| We may also would like to mention in the doc that the WSDL shared library is going to support the current version of WSDL namespace URI which is "2006/01/wsdl", as well as the upcoming one which is "ns/wsdl". |
| We may also would like to mention in the doc that the WSDL shared library is |
| going to support the current version of WSDL namespace URI which |
| is "2006/01/wsdl", as well as the upcoming one which is "ns/wsdl". |
| At line 83 changed 1 line. |
| None if we do not implement the backward compatibility with 2004/08 from a parsing standpoint. |
| None if we do not implement the backward compatibility with 2004/08 from a |
| parsing standpoint. |
| At line 93 changed 1 line. |
| 5. Reference Documents: |
| 5. Reference Documents: |