You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@synapse.apache.org by "Asankha C. Perera" <as...@wso2.com> on 2008/05/02 07:15:28 UTC

Re: Port not advertised

Wayne

Can you attach the WSDL and the synapse.xml you use?

asankha

Wayne Keenan wrote:
> Hi,
>
> When advertising the OSSJ FaultReporting 1.0 WSDL I need the 1st port but I
> have to comment out the second port as only the 'last' one in the list is
> ever published.
>
>   <wsdl:service name="JVTAlarmCreationSessionWebService">
>         <wsdl:port name="JVTAlarmCreationSessionWSPort"
>             binding="fmWS-v1-0:JVTAlarmCreationSessionSoapBinding">
>             <soap:address location="
> http://localhost/JVTAlarmCreationSessionWebService/JVTAlarmCreationSession"
> />
>         </wsdl:port>
>         <!--<wsdl:port name="SubscriptionManagerPort"
> binding="fmWS-v1-0:SubscriptionManagerSoapBinding">
>             <soap:address location="
> http://localhost/JVTAlarmCreationSessionWebService/SubscriptionManager"/>
>         </wsdl:port>-->
>     </wsdl:service>
>
>
> Has anyone seen this behaviour before?  Should I be specifying a Synapse
> config option or is this potentially a Axis2 issue?
>
> Thanks
> Wayne
>
>

Re: Port not advertised

Posted by Wayne Keenan <wa...@gmail.com>.

Hi,

Please find the WSDL and Syanpse config attached, thanks for looking at
this.

browsing to the Axis2 service view only shows:

Deployed servicesJVTAlarmCreationSession<http://localhost:8080/soap/JVTAlarmCreationSession?wsdl>Available
operations

   - ResumeSubscription
   - PauseSubscription
   - Unsubscribe
   - Renew


I would have expected to see the other port, and when I comment out the port
realted to the above , e.g.:

        <!-- <wsdl:port name="SubscriptionManagerPort"
binding="fmWS-v1-0:SubscriptionManagerSoapBinding">
            <soap:address location="
http://localhost/JVTAlarmCreationSessionWebService/SubscriptionManager"/>
        </wsdl:port> -->


I see the other port:


Deployed servicesJVTAlarmCreationSession<http://localhost:8080/soap/JVTAlarmCreationSession?wsdl>Available
operations

   - getEventDescriptor
   - getManagedEntityTypes
   - getUpdateProcedureTypes
   - update
   - getAlarmsByKeys
   - getAlarmsByTemplate
   - getSupportedOptionalOperations
   - getEventTypes
   - query
   - getNamedQueryTypes
   - createAlarmByValue
   - createAlarmsByValues
   - getAlarmSpecificInfoTypes
   - getVersion

All the best
Wayne



On Fri, May 2, 2008 at 6:15 AM, Asankha C. Perera <as...@wso2.com> wrote:

> Wayne
>
> Can you attach the WSDL and the synapse.xml you use?
>
> asankha
>
>
> Wayne Keenan wrote:
>
> > Hi,
> >
> > When advertising the OSSJ FaultReporting 1.0 WSDL I need the 1st port
> > but I
> > have to comment out the second port as only the 'last' one in the list
> > is
> > ever published.
> >
> >  <wsdl:service name="JVTAlarmCreationSessionWebService">
> >        <wsdl:port name="JVTAlarmCreationSessionWSPort"
> >            binding="fmWS-v1-0:JVTAlarmCreationSessionSoapBinding">
> >            <soap:address location="
> >
> > http://localhost/JVTAlarmCreationSessionWebService/JVTAlarmCreationSession
> > "
> > />
> >        </wsdl:port>
> >        <!--<wsdl:port name="SubscriptionManagerPort"
> > binding="fmWS-v1-0:SubscriptionManagerSoapBinding">
> >            <soap:address location="
> > http://localhost/JVTAlarmCreationSessionWebService/SubscriptionManager
> > "/>
> >        </wsdl:port>-->
> >    </wsdl:service>
> >
> >
> > Has anyone seen this behaviour before?  Should I be specifying a Synapse
> > config option or is this potentially a Axis2 issue?
> >
> > Thanks
> > Wayne
> >
> >
> >
>