[Dev] Siddhi custom output attribute aggregator for CEP is not working
Hi,
I'm trying to write a siddhi custom output attribute aggregator for CEP. I
wrote the following 2 classes and created the jar file with extension
Name=ext1 and function Name=StdDev_sample.
StdDevOutputAttributeAggregatorSample
StdDevOutputAttributeAggregatorSampleFactory
And then I added the jar file to CEP_HOME/repository/components/lib and
then added the fully qualified class name as
org.wso2.siddhi.extension.StdDevOutputAttributeAggregatorSampleFactory to
CEP_HOME/repository/conf/siddhi.
But when i try to use the extension in CEP i get the following error.
No extension exist for OutputAttributeExtension{extensionName='ext1',
functionName='StdDev_sample', rename='std'}
Thank you.
--
Nishali Wijesinghe
Intern - Engineering
WSO2, Inc.
lean.enterprise.middleware.
Tel: +94716913495
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Siddhi custom output attribute aggregator for CEP is not working
Hi all,
I was using a previously used package with different extension class name
to deploy the extension. I now tried it with a different package and now it
is working.
Thank you
Nishali
On Thu, Oct 30, 2014 at 1:52 PM, Damith Wickramasinghe dami...@wso2.com
wrote:
Hi Nishali,
Sometimes you will get this error If you have same package name with
different extension class names. Its a known error in OSGI. Please check
whether you have multiple extensions in a same package.
eg: org.wso2.cep.extOne and org.wso2.cep.extTwo will throw you the error
when you try to deploy extTwo extension.
Thanks,
Damith.
On Thu, Oct 30, 2014 at 1:30 PM, Nishali Wijesinghe nisha...@wso2.com
wrote:
Hi,
I'm trying to write a siddhi custom output attribute aggregator for CEP.
I wrote the following 2 classes and created the jar file with extension
Name=ext1 and function Name=StdDev_sample.
StdDevOutputAttributeAggregatorSample
StdDevOutputAttributeAggregatorSampleFactory
And then I added the jar file to CEP_HOME/repository/components/lib and
then added the fully qualified class name as
org.wso2.siddhi.extension.StdDevOutputAttributeAggregatorSampleFactory to
CEP_HOME/repository/conf/siddhi.
But when i try to use the extension in CEP i get the following error.
No extension exist for OutputAttributeExtension{extensionName='ext1',
functionName='StdDev_sample', rename='std'}
Thank you.
--
Nishali Wijesinghe
Intern - Engineering
WSO2, Inc.
lean.enterprise.middleware.
Tel: +94716913495
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Software Engineer
WSO2 Inc.; http://wso2.com
http://www.google.com/url?q=http%3A%2F%2Fwso2.comsa=Dsntz=1usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg
lean.enterprise.middleware
mobile: *+94728671315 %2B94728671315*
--
Nishali Wijesinghe
Intern - Engineering
WSO2, Inc.
lean.enterprise.middleware.
Tel: +94716913495
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Siddhi custom output attribute aggregator for CEP is not working
Hi seshika,
Yes, now it is working.
Thanks
Nishali
On Thu, Oct 30, 2014 at 2:11 PM, Seshika Fernando sesh...@wso2.com wrote:
Sorry. Ignore my response, I replied before I saw the entire thread.
On Thu, Oct 30, 2014 at 2:10 PM, Seshika Fernando sesh...@wso2.com
wrote:
Hi Nishali,
Couple of questions.
1. Have you added the SiddhiExtension Annotation to your Factory class?
2.Can you provide your siddhi query syntax which uses this function?
seshika
On Thu, Oct 30, 2014 at 1:30 PM, Nishali Wijesinghe nisha...@wso2.com
wrote:
Hi,
I'm trying to write a siddhi custom output attribute aggregator for
CEP. I wrote the following 2 classes and created the jar file with
extension Name=ext1 and function Name=StdDev_sample.
StdDevOutputAttributeAggregatorSample
StdDevOutputAttributeAggregatorSampleFactory
And then I added the jar file to CEP_HOME/repository/components/lib
and then added the fully qualified class name as
org.wso2.siddhi.extension.StdDevOutputAttributeAggregatorSampleFactory to
CEP_HOME/repository/conf/siddhi.
But when i try to use the extension in CEP i get the following error.
No extension exist for OutputAttributeExtension{extensionName='ext1',
functionName='StdDev_sample', rename='std'}
Thank you.
--
Nishali Wijesinghe
Intern - Engineering
WSO2, Inc.
lean.enterprise.middleware.
Tel: +94716913495
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Nishali Wijesinghe
Intern - Engineering
WSO2, Inc.
lean.enterprise.middleware.
Tel: +94716913495
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DEV] WSDL error when writing the carbon component
; Rest of the code is same as above. When I use this file to do a maven build, it works fine without any errors. Thanks, Regards, Nishali On Fri, Oct 3, 2014 at 12:15 PM, Shiva Balachandran sh...@wso2.com wrote: Hi Nishali, Please share your wsdl file with us. One of your tags in the file is not bound. Thanks On Fri, Oct 3, 2014 at 11:24 AM, Supun Muthutantrige sup...@wso2.com wrote: Hii Nishali, Just check your wsdl again. It seems there is a problem in saving it. Try to save it from the browser as a wsdl file instead of copying and then saving in a different file. Regards *Supun Rasitha Muthutantrige* *supunrWSO2 Inc: http://wso2.com http://wso2.com lean.enterprise.middleware* *Mobile: 0758374608* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Shiva Balachandran Software Engineer WSO2 Inc. Mobile - +94 774445788 -- Nishali Wijesinghe Intern - Engineering WSO2, Inc. lean.enterprise.middleware. Tel: +94716913495 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DEV] WSDL error when writing the carbon component
yes, it is resolved now, that must be the reason for it. Thanks a lot, Nishali On Fri, Oct 3, 2014 at 2:06 PM, Shiva Balachandran sh...@wso2.com wrote: So this is resolved right? I'm guessing those attributes are hidden in the browser view, and are re-factored and added to the document when it is saved. On Fri, Oct 3, 2014 at 1:31 PM, Nishali Wijesinghe nisha...@wso2.com wrote: Hi Shiva, This what I got when I copied the wsdl file directly from the web browser. wsdl:definitions targetNamespace=http://mgt.order.carbon.wso2.org wsdl:documentationOrderProcessor/wsdl:documentation wsdl:types xs:schema xmlns:ax299=http://data.mgt.order.carbon.wso2.org/xsd; attributeFormDefault=qualified elementFormDefault=qualified targetNamespace=http://mgt.order.carbon.wso2.org; xs:import namespace= http://data.mgt.order.carbon.wso2.org/xsd/ xs:element name=getOrder xs:complexType xs:sequence/ /xs:complexType /xs:element xs:element name=getOrderResponse xs:complexType xs:sequence xs:element maxOccurs=unbounded minOccurs=0 name=return nillable=true type=ax298:Order/ /xs:sequence /xs:complexType /xs:element /xs:schema xs:schema attributeFormDefault=qualified elementFormDefault=qualified targetNamespace= http://data.mgt.order.carbon.wso2.org/xsd; xs:complexType name=Order xs:sequence xs:element minOccurs=0 name=ID type=xs:int/ xs:element minOccurs=0 name=price type=xs:double/ xs:element minOccurs=0 name=quantity type=xs:int/ xs:element minOccurs=0 name=type nillable=true type=xs:string/ /xs:sequence /xs:complexType /xs:schema /wsdl:types wsdl:message name=getOrderRequest wsdl:part name=parameters element=ns:getOrder/ /wsdl:message wsdl:message name=getOrderResponse wsdl:part name=parameters element=ns:getOrderResponse/ /wsdl:message wsdl:portType name=OrderProcessorPortType wsdl:operation name=getOrder wsdl:input message=ns:getOrderRequest wsaw:Action=urn:getOrder/ wsdl:output message=ns:getOrderResponse wsaw:Action=urn:getOrderResponse/ /wsdl:operation /wsdl:portType wsdl:binding name=OrderProcessorSoap11Binding type=ns:OrderProcessorPortType soap:binding transport=http://schemas.xmlsoap.org/soap/http; style=document/ wsdl:operation name=getOrder soap:operation soapAction=urn:getOrder style=document/ wsdl:input soap:body use=literal/ /wsdl:input wsdl:output soap:body use=literal/ /wsdl:output /wsdl:operation /wsdl:binding wsdl:binding name=OrderProcessorSoap12Binding type=ns:OrderProcessorPortType soap12:binding transport=http://schemas.xmlsoap.org/soap/http; style=document/ wsdl:operation name=getOrder soap12:operation soapAction=urn:getOrder style=document/ wsdl:input soap12:body use=literal/ /wsdl:input wsdl:output soap12:body use=literal/ /wsdl:output /wsdl:operation /wsdl:binding wsdl:binding name=OrderProcessorHttpBinding type=ns:OrderProcessorPortType http:binding verb=POST/ wsdl:operation name=getOrder http:operation location=getOrder/ wsdl:input mime:content type=text/xml part=parameters/ /wsdl:input wsdl:output mime:content type=text/xml part=parameters/ /wsdl:output /wsdl:operation /wsdl:binding wsdl:service name=OrderProcessor wsdl:port name=OrderProcessorHttpsSoap11Endpoint binding=ns:OrderProcessorSoap11Binding soap:address location= https://10.100.4.38:9443/services/OrderProcessor.OrderProcessorHttpsSoap11Endpoint/ / /wsdl:port wsdl:port name=OrderProcessorHttpsSoap12Endpoint binding=ns:OrderProcessorSoap12Binding soap12:address location= https://10.100.4.38:9443/services/OrderProcessor.OrderProcessorHttpsSoap12Endpoint/ / /wsdl:port wsdl:port name=OrderProcessorHttpsEndpoint binding=ns:OrderProcessorHttpBinding http:address location= https://10.100.4.38:9443/services/OrderProcessor.OrderProcessorHttpsEndpoint/ / /wsdl:port /wsdl:service /wsdl:definitions This didn't work. But then I saved the web page as a separate wsdl file in the desktop (as mentioned by Supun above). The definition tag of that file is as follows. wsdl:definitions xmlns:wsdl=http
[Dev] [DEV] WSDL error when writing the carbon component
Hi All, When I try to write a carbon component, the WSDL file which generates from the server component is as follows. wsdl:definitions targetNamespace=http://mgt.order.carbon.wso2.org; wsdl:documentationOrderProcessor/wsdl:documentation wsdl:types xs:schema attributeFormDefault=qualified elementFormDefault=qualified targetNamespace= http://mgt.order.carbon.wso2.org; xs:import namespace=http://data.mgt.order.carbon.wso2.org/xsd/ xs:element name=getOrder But when I try to do a maven build from the service stub, I get the following error. [INFO] Executing tasks [java] Retrieving document at 'src/main/resources/OrderProcessor.wsdl'. [java] [Fatal Error] OrderProcessor.wsdl:1:70: The prefix wsdl for element wsdl:definitions is not bound. [java] Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL I appreciate you help in in this matter. Thank you, Regards, Nishali -- Nishali Wijesinghe Intern - Engineering WSO2, Inc. lean.enterprise.middleware. Tel: +94716913495 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
