2011/8/9 David Carver <dcar...@intalio.com> > ** > I brought down the WSDL for the EventBrokerService but this really seems to > be incomplete. > > There are no type definitions and none of the messages are point to any > types. This makes code generation and generating a client a bit more > difficult. I'm attaching the WSDL that was returned from the > EventBrokerService. > > Is there an existing Java library that is known to work with the service > that can be used outside of WSO2? >
you can use the wsdl given in this location[1]. We need to fix EventBrokerservice to show correct wsdl. you can use org.wso2.carbon.event.client.stub jar as the library file. You can down load the WSO2 MB from here[1]. and please have a look at the wsclient sample. thanks, Amila. [1] https://svn.wso2.org/repos/wso2/trunk/carbon/service-stubs/org.wso2.carbon.event.client.stub/src/main/resources/eventing-new.wsdl > > > Dave > > On 08/08/2011 03:23 PM, Senaka Fernando wrote: > > Hi Dave, > > Yes there is a WS-API as defined in the WS-Eventing specification - which > can be used for this purpose. The endpoint is > https://localhost:9443/services/EventBrokerService, and the WSDL can be > found at https://localhost:9443/services/EventBrokerService?wsdl. You will > not see the WSDL unless you set "HideAdminServiceWSDLs" to "false" in > repository/conf/carbon.xml. > > Thanks, > Senaka. > > On Tue, Aug 9, 2011 at 12:38 AM, David Carver <dcar...@intalio.com> wrote: > >> I'm starting work on the Turmeric SOA interfaces into the WSO2 Governance >> Registry 4.0. One of the options in our WSDL is the ability to subscribe, >> update, and unsubscribe for Notification of changes or lifecycle movements >> of a service. >> >> I'm looking at the Developer's guide, and see that there is an OSGI API >> Interface, however described here: >> >> >> https://wso2.org/project/registry/4.0.0/docs/developer_guide/osgi_support.html#registry_eventing_service >> >> I also know that the Eventing/Notification implementation is based on the >> WS-Eventing/Notification specification, but I don't see a way to call or >> access this either through the RemoteRegistry API or the WS-API. >> >> Is there a way to access the OSGI API through a web service, Restful >> Service, or Remote Registry with out having to create a OSGI plugin? I'm >> trying to keep the number of layers and customizations down to a minimum. >> >> Dave >> >> _______________________________________________ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > > > > -- > *Senaka Fernando* > Product Manager - WSO2 Governance Registry; > Associate Technical Lead; WSO2 Inc.; http://wso2.com* > Member; Apache Software Foundation; http://apache.org > > E-mail: senaka AT wso2.com > **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 > Linked-In: http://linkedin.com/in/senakafernando > > *Lean . Enterprise . Middleware > > > _______________________________________________ > Carbon-dev mailing > listCarbon-dev@wso2.orghttp://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
