Hi,
Just to be clear. You can have identically named methods in different
service interfaces provided the service interfaces are in different
packages. This problem has occurred in the PM model because both service
interfaces are in the same package.
Cheers
Craig
On 26/09/2012 11:58, Flauw, Marc wrote:
> Hi Craig,
>
> The assumption from the meta-model so far was that the methods are unique per service interface, but following our chat, I understand your point and I agree to the change. We will just have to document it in the JOSIF Guidebook.
>
> Best regards
>
> Marc
>
> -----Original Message-----
> From: Craig Gallen [mailto:gal...@go...] On Behalf Of Craig Gallen (opennms)
> Sent: Wednesday, September 26, 2012 12:50 PM
> To: Flauw, Marc
> Cc: openoss-devel; pierre gauthier; Craig Gallen (OpenNMS)
> Subject: Problem with PM model conflicting method signatures
>
> Marc,
>
> I have found a fundamental problem of clashing method signatures in the TIP_PM_Mon_Model which only shows up when you try and compile the wsdl.
> Both the
>
> org.tmforum.tip.cbe.perf.mon.coll.AdhocCollectionService
> and the
> org.tmforum.tip.cbe.perf.mon.coll.MeasurementCollectionJobService
> are in the same name space and have methods called getTrackingRecords() with different signatures.
>
> This means that both generate conflicting getTrackingRecordsRequest and getTrackingRecordsResponse elements in the same xsd namespace
>
> The problem is that these generated objects have different attributes and when passed through WSDL2JAVA, we end up with two conflicting objects called
> org.tmforum.xml.tip.cbe.perf.mon.coll.GetTrackingRecordsRequest
> which overwrite each other.
>
> The only solution I can see is to change one or both of the signature names in the model i.e.
>
> change getTrackingRecords to getAdhocCollectionTrackingRecords in AdhocCollectionService change getTrackingRecords to getMeasurementCollectionTrackingRecords in MeasurementCollectionJobService
>
> What do you think?
>
> Craig
>
>
>
>
>
|
