Re: [Dev] [Calling Admin Services- DAS] Issue in deploying an Event Receiver to DAS via Admin Services

[Samitha Chathuranga]

Hi,

I worked with DAS 3.0.0 and the WSDL used for that (to generate stub via
Eclipse with Axis2) is the one hosted runtime after starting DAS Server via
?wsdl in the browser. So the error should not be due to any version
incompatibilities as I guess.

But to generate the stub via adding pom dependancy, what I used was
https://github.com/wso2/carbon-analytics-common/blob/v5.0.8/service-stubs/org.wso2.carbon.event.receiver.stub/pom.xml
, which is bit older than what you have mentioned. (anyway this worked
successfully so this difference might not count here for the error)

So the difference between the 2 stubs might have caused by that version
difference too. (if that is not because of using Eclipse Axis2 to generate
stub ) Anyway what I'm confused is my current solution which used that pom
generated stub, successfully run with DAS 3.0.0 and also DAS 3.0.1.

And the other fact is that even the .wsdl hosted by running  latest DAS,
generated a different (relative to my pom dependancy imported one) stub
class, by generating stub via Eclipse. The important difference is that
"deployWso2EventReceiverConfiguration" method had different parameters.

I feel this information is not enough to dig the issue exactly, but thanks
for the response.

On Sat, Feb 20, 2016 at 7:20 PM, Sriskandarajah Suhothayan 
wrote:

> Not sure that the issue is.
>
> We work with the WSDL provided in [1] and the sub creation is at [2]. Are
> you sure you used the proper versions when generating them?
>
> [1]
> https://github.com/wso2/carbon-analytics-common/blob/master/service-stubs/org.wso2.carbon.event.receiver.stub/src/main/resources/EventReceiverAdminService.wsdl
>
> [2]
> https://github.com/wso2/carbon-analytics-common/blob/master/service-stubs/org.wso2.carbon.event.receiver.stub/pom.xml
>
> On Sat, Feb 20, 2016 at 7:03 PM, Samitha Chathuranga 
> wrote:
>
>> Hi,
>>
>> I was able to resolve this issue via a workaround, but cannot clarify the
>> related issue with this. What I did as the workaround was, adding the 
>> "org.wso2.carbon.event.receiver.stub"
>> as a maven dependency in my project and using that stub class (
>> EventReceiverAdminServiceStub.java) to call the required Admin Service.
>> But previously what I did was generating the web service client stub by
>> using Axis2 in Eclipse by giving the giving the url of .wsdl file, after
>> starting WSO2 DAS.
>>
>> Here I found that the stub classes consumed at two occasions (Axis2
>> generated one and maven imported one) are not similar. Specially and
>> necessarily the "deployWso2EventReceiverConfiguration" method which was
>> called to deploy the Event Receiver had different signatures (parameters
>> are different) and that might be the reason for the previous exception "
>> IllegalArgumentException".
>>
>> I even compared the related .wsdl file in the carbon-analytics-commons
>> repository and the.wsdl file which was used to generate the stub with Axis2
>> with eclipse, but found no significant difference.
>>
>> So, what causes this difference in the 2 stub classes or isn't this
>> difference the issue here? Am I missing something here or is there any
>> issue related in generating client stubs via Axis2?
>>
>> Thanks and Regards.
>>
>>
>>
>> On Tue, Feb 16, 2016 at 12:15 PM, Samitha Chathuranga 
>> wrote:
>>
>>> Hi,
>>>
>>> I am trying to deploy an event receiver in DAS, via calling Admin
>>> Services, but getting an *IllegalArgumentException*. By the way I
>>> succeeded in creating an Event Stream in DAS by "EventStreamAdminService"
>>> Admin Service, and I followed the same basic procedure to call DAS's
>>> "EventReceiverAdminService", in order to deploy an Event Receiver.
>>>
>>> I set EventReceiverName, StreamNameWithVersion, EventAdapterType (to
>>> "wso2event") and a BasicInputAdapterPropertyDto property
>>> "events.duplicated.in.cluster" as key and "false" as its value for the
>>> DeployTextEventReceiverConfiguration. Does anybody has an idea on the issue?
>>> Am I missing something here?
>>>
>>> Stack trace is mentioned below.
>>>
>>> Thanks & Regards,
>>> Samitha
>>>
>>> TID: [-1234] [] [2016-02-16 11:43:11,125]  INFO
>>> {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -
>>> 'admin@carbon.super [-1234]' logged in at [2016-02-16
>>> 11:43:11,124+0530]
>>> {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil}
>>> TID: [-1234] [] [2016-02-16 11:43:11,215] ERROR
>>> {org.apache.axis2.rpc.receivers.RPCMessageReceiver} -
>>> {org.apache.axis2.rpc.receivers.RPCMessageReceiver}
>>> java.lang.IllegalArgumentException
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>> at
>>> org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
>>> at
>>> org.apache.axis

Re: [Dev] [Kubernetes Artifacts] Applying secure vault for wso2 products when building docker images

[Imesh Gunaratne]

On Sun, Feb 21, 2016 at 8:05 AM, Thanuja Uruththirakodeeswaran <
thanu...@wso2.com> wrote:

> Hi All,
>
> Currently I'm working on $subject by running cipher tool and user will be
> able to build a docker image for a wso2 product which will have secured
> password in config files.
>
> In order to do the subject, we need to add cipher-tool.properties,
> cipher-text.properties and password-tmp file templates  to puppet module. I
> thought of encrypting the passwords using the cipher tool after we execute
> puppet apply in Docker files [1].
>

Yes IMO this is the best option. Docker image build process use puppet for
configuring the product, once the configuration is done run secure vault
and secure all credentials.

When the container starts we will need to send the password either using an
environment variable (in Docker) or via a K8S secret (in K8S) and create
the password text file. Then we can start the server.

Thanks

>
> Applying secure vault while building the docker image will be easy and
> efficient way compared to  manually running the cipher tool and updating
> puppet module templates before building the docker image.
>
> I'll update this thread about the progress. Highly appreciate your
> suggestions on this.
>
> [1].
> https://github.com/wso2/kubernetes-artifacts/blob/master/wso2esb/docker/Dockerfile#L40
>
> Thanks.
>
> --
> Thanuja Uruththirakodeeswaran
> Software Engineer
> WSO2 Inc.;http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 774363167
>



-- 
*Imesh Gunaratne*
Senior Technical Lead
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: http://imesh.gunaratne.org
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Docker Images] Can't pull the wso2/as-5.2.1 docker image from docker hub

[Madhawa Perera]

Hi Pubudu,

Thank you for the info. I was able to build the docker image.

Best Regards,
Madhawa

On Fri, Feb 19, 2016 at 10:31 PM, Pubudu Gunatilaka 
wrote:

> Hi Madhawa,
>
> We don't host docker images publicly. You can build your own docker image
> following [1].
>
> [1] -
> https://github.com/wso2/kubernetes-artifacts#dockerfiles-for-wso2-products
>
> Thank you!
>
> On Fri, Feb 19, 2016 at 8:08 AM, Madhawa Perera  wrote:
>
>> Hi,
>>
>> When I tried to pull the wso2as-5.2.1 docker image from docker hub (
>> https://hub.docker.com/r/wso2/as-5.2.1/) I'm getting following message
>> saying that "Tag latest not found in repository docker.io/wso2/as-5.2.1"
>>
>> Please refer the terminal-capture below
>>
>> [image: Inline image 1]
>>
>> Any idea on what might help?
>>
>> Thank you
>> Best Regards,
>>
>> --
>> Madhawa Perera
>> *Software Engineer*
>> Mobile : +94 (0) 773655496
>> <%2B94%20%280%29%20773%20451194>
>> madha...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774079049 <%2B94772207163>
>
>


-- 
Madhawa Perera
*Software Engineer*
Mobile : +94 (0) 773655496
<%2B94%20%280%29%20773%20451194>
madha...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB/GW] Improve production system debugging capabilities of ESB (ESB Flight Recorder) Project in GSOC 2016

[Danoja Dias]

Dear Sir,

I am Danoja Dias a third year undergraduate from university of Peradeniya.
I am interested in the Project

*[ESB/GW] Improve production system debugging capabilities of ESB (ESB
Flight Recorder)*
I read about java flight recorder continuous recording and I like to
implement with java. So I think I can complete this project with the help
of mentors.

Could you please help me to continue on this project. I need some
references and steps to continue.

Thank you,
Best Regards,
Danoja Dias.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [PC][GSoC] Web (Javascript / D3) based BPMN editor to support a subset of commonly used BPMN constructs

[Isuru Wijesinghe]

Hi Natasha,

Thank you for your interest in this project. You can start looking at the
example available in [1]. This example describes templates and
relationships typically used in Business Process Model and Notation
(BPMN). Please
go through the samples mentioned in [2], [3] and [4].

[1]. http://demo.bpmn.io/
[2]. Interactive tool for creating directed graphs using D3 -
https://bl.ocks.org/cjrd/6863459
[3]. state diagram editor example  using D3 -
http://bl.ocks.org/lgersman/5311202
[4]. D3.js custom shapes - http://bl.ocks.org/explunit/4659227

Basically this BPMN editor has two sections called component-palette
section and drawing section. In component-palette section, need to be
included set of components like user task, service task, exclusive,
parallel gateways, etc [see the attached image (pallet.png)]. And then
clone the selected competent/item in the palette section when clicking on
it by the user to drawing section to model a work-flow. (see editor.jpeg)

Please do not hesitate to contact us if you have any further questions.

Thanks and Best Regards,

On Sat, Feb 20, 2016 at 6:07 PM, Natasha Wijesekare 
wrote:

> Dear Sir,
>
> I am a third year Software Engineering undergraduate at Informatics
> Institute of Technology. I would like to contribute to the open source
> community by taking part in GSoC 2016. I have gone through WSO2 GSoC
> Project Proposals for 2016 and I'm interested in contributing to Proposal
> 19: [PC] Web (Javascript / D3) based BPMN editor to support a subset of
> commonly used BPMN constructs
> 
> .
>
> Through prior experience I have been able to gather a sound knowledge in
> javascript which has helped me in developing many front-end applications.
> I'm familiar with BPMN and have experiance of designing bpmn
> processes/models to define business processes.
> Currently I'm tasked with carrying out a study about  D3 which is the
> required javascript library to create the editor.
> Please kindly make any suggestions on how I could proceed.
>
> Best Regards,
> Natasha Wijesekare
> Software Engineering Undergarduate,
> Informatice Institute of Technology, Sri Lanka
> mobile : +94771358651
>
>


-- 
Isuru Wijesinghe
*Software Engineer*
WSO2 inc : http://wso2.com
lean.enterprise.middleware
Mobile: 0710933706
isur...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Implementing Geographical based Analytics in API Manager

[Tharindu Dharmarathna]

Hi All,

We are going to implement $Subject on latest release . I want to know is
there any best way to extract Geographical location from IP . And here are
my findings of the ways of do.

[1] - http://www.geoplugin.com
Thi will retrive all the data according to the location as json

[2] - http://www.telize.com/

This is another REST API which can used to extract location.

*Thanks*
*Tharindu Dharmarathna*
Associate Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: *+94779109091*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Kubernetes Artifacts] Applying secure vault for wso2 products when building docker images

[Thanuja Uruththirakodeeswaran]

Hi All,

Currently I'm working on $subject by running cipher tool and user will be
able to build a docker image for a wso2 product which will have secured
password in config files.

In order to do the subject, we need to add cipher-tool.properties,
cipher-text.properties and password-tmp file templates  to puppet module. I
thought of encrypting the passwords using the cipher tool after we execute
puppet apply in Docker files [1].

Applying secure vault while building the docker image will be easy and
efficient way compared to  manually running the cipher tool and updating
puppet module templates before building the docker image.

I'll update this thread about the progress. Highly appreciate your
suggestions on this.

[1].
https://github.com/wso2/kubernetes-artifacts/blob/master/wso2esb/docker/Dockerfile#L40

Thanks.

-- 
Thanuja Uruththirakodeeswaran
Software Engineer
WSO2 Inc.;http://wso2.com
lean.enterprise.middleware

mobile: +94 774363167
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Running WSO2 Products on Cloud Foundry

[Imesh Gunaratne]

Hi Nanduni,

Were you able to figure out how load balancing works on CF with Docker?

Thanks

On Tue, Feb 16, 2016 at 12:23 PM, Nanduni Nimalsiri 
wrote:

> *@Lakmal*
> Thank you for the information. I will try using that.
>
> *@Chamila*
> Thank you for the details.
> It seems that the choice of buildpacks or containers depends on the
> application developer, operator, environment, requirements etc. If we
> really want to get something really fast, Cloud Foundry recommends to build
> a docker container and push it, so that we can use that container for local
> testing as well. But the drawback that lies here is that the developers
> have to know about Docker and other operations. (eg: how to write a
> Dockerfile). They say that if the developer needs to set up the environment
> instead of the operator, this approach would be perfect.
>
> Cloud Foundry suggests that buildpacks are suitable if we don't want to
> use Ubuntu, Red Hat, Fedora, CentOS or different java versions that need to
> be patched differently or else if we don't want to use different custom
> things etc. Hence the developer can focus more on application logic and
> business logic rather than running Dockerfiles. Any way, the buildpack
> approach also ends up in a container(droplet) eventually.
>
> I suppose that low maintenance cost can be achieved with buildpacks
> because this approach does not end up with very heterogenic container
> cluster where every container is really different, then we have to come up
> with different ways when we need to patch something. But with buildpacks,
> we can patch up one buildpack so that we can deploy all applications and go
> ahead. I suppose this might be a reason for mentioning it as low
> maintenance cost. I have no deep thought on this.
>
> In case of port based health checks which I have mentioned, if the Docker
> images we are pushing don't declare ports to expose, or the processes they
> run don't listen for TCP connections on the ports they expose, then they
> will fail the default 'port' health check when pushed as a CF app. If we
> turn that port-based health-check off by changing it to 'none', though, the
> image may run successfully.
>
> Hope this had been useful.
>
> Best regards,
> Nanduni.
>
>
> *Nanduni Nimalsiri*
> Software Engineering Intern, WSO2 Inc. (http://wso2.com)
> email : nand...@wso2.com
> blog : http://nanduni.blogspot.com/
> mobile : +94714114256
>
>
> On Tue, Feb 16, 2016 at 7:20 AM, Lakmal Warusawithana 
> wrote:
>
>> PS: Still private docker registry UI not configured. Currently this only
>> work in docker client, using docker registry APIs. Which is docker
>> login/push/pull
>>
>> On Tue, Feb 16, 2016 at 7:16 AM, Lakmal Warusawithana 
>> wrote:
>>
>>> Awesome! great progress Nanduni.
>>>
>>> If you want to test with private docker registry, I have setup internal
>>> private docker registry [1], you can use it for push/pull docker images. It
>>> required authentication ( your WSO2 credentials - username : email,
>>> Password: email password ). You need to do docker login first to pull/push
>>> docker images. (please note currently this is only work inside the WSO2
>>> network)
>>>
>>> Lets try CF locally.
>>>
>>>
>>> [1] https://dockerhub.private.wso2.com
>>>
>>>
>>> On Mon, Feb 15, 2016 at 11:25 PM, Nanduni Nimalsiri 
>>> wrote:
>>>
 Hi,

 I was able to deploy Docker images in Cloud Foundry with Diego. Here I
 am going to clear several facts regarding that.

 There are several approaches of integrating Docker with Cloud Foundry.
 If I summarize them, they are are follows. Each of them possesses different
 limitations.


 *Integrating Docker with Cloud Foundry*

 *1. Docker Buildpack - *Provides framework and runtime support for the
 applications. When we push an application, Cloud Foundry automatically
 detects which buildpack is required and installs it on the Droplet
 Execution Agent (DEA) where the application needs to run.

 *2. Docker Service Provider - * A service provider to expose Docker
 containers as services.

 *3. Cloud Rocker *- A project carried out by a company called 'Cloud
 Credo' which builds docker images using Cloud Foundry buildpacks. If you
 don't want to use Cloud Foundry but you want to use its buildpack system,
 this is the best choice.

 *4. Diego - *Rewrite of DEA. In a Cloud Foundry deployment without
 Diego, the Cloud Controller schedules and manages applications on the DEA
 nodes. Diego replaces the DEAs and the Health Manager, and assumes
 application scheduling and management responsibility from the Cloud
 Controller. Diego is special because it provides built-in-support for
 Docker containers.

 *5. Lattice - *Lattice is a standalone scheduler extracted from Diego
 for Docker images. If Cloud Foundry is too much, Lattice might be a
 suitable project. Lattice tries to be little simpler and easier to s

Re: [Dev] [Calling Admin Services- DAS] Issue in deploying an Event Receiver to DAS via Admin Services

[Sriskandarajah Suhothayan]

Not sure that the issue is.

We work with the WSDL provided in [1] and the sub creation is at [2]. Are
you sure you used the proper versions when generating them?

[1]
https://github.com/wso2/carbon-analytics-common/blob/master/service-stubs/org.wso2.carbon.event.receiver.stub/src/main/resources/EventReceiverAdminService.wsdl

[2]
https://github.com/wso2/carbon-analytics-common/blob/master/service-stubs/org.wso2.carbon.event.receiver.stub/pom.xml

On Sat, Feb 20, 2016 at 7:03 PM, Samitha Chathuranga 
wrote:

> Hi,
>
> I was able to resolve this issue via a workaround, but cannot clarify the
> related issue with this. What I did as the workaround was, adding the 
> "org.wso2.carbon.event.receiver.stub"
> as a maven dependency in my project and using that stub class (
> EventReceiverAdminServiceStub.java) to call the required Admin Service.
> But previously what I did was generating the web service client stub by
> using Axis2 in Eclipse by giving the giving the url of .wsdl file, after
> starting WSO2 DAS.
>
> Here I found that the stub classes consumed at two occasions (Axis2
> generated one and maven imported one) are not similar. Specially and
> necessarily the "deployWso2EventReceiverConfiguration" method which was
> called to deploy the Event Receiver had different signatures (parameters
> are different) and that might be the reason for the previous exception "
> IllegalArgumentException".
>
> I even compared the related .wsdl file in the carbon-analytics-commons
> repository and the.wsdl file which was used to generate the stub with Axis2
> with eclipse, but found no significant difference.
>
> So, what causes this difference in the 2 stub classes or isn't this
> difference the issue here? Am I missing something here or is there any
> issue related in generating client stubs via Axis2?
>
> Thanks and Regards.
>
>
>
> On Tue, Feb 16, 2016 at 12:15 PM, Samitha Chathuranga 
> wrote:
>
>> Hi,
>>
>> I am trying to deploy an event receiver in DAS, via calling Admin
>> Services, but getting an *IllegalArgumentException*. By the way I
>> succeeded in creating an Event Stream in DAS by "EventStreamAdminService"
>> Admin Service, and I followed the same basic procedure to call DAS's
>> "EventReceiverAdminService", in order to deploy an Event Receiver.
>>
>> I set EventReceiverName, StreamNameWithVersion, EventAdapterType (to
>> "wso2event") and a BasicInputAdapterPropertyDto property
>> "events.duplicated.in.cluster" as key and "false" as its value for the
>> DeployTextEventReceiverConfiguration. Does anybody has an idea on the issue?
>> Am I missing something here?
>>
>> Stack trace is mentioned below.
>>
>> Thanks & Regards,
>> Samitha
>>
>> TID: [-1234] [] [2016-02-16 11:43:11,125]  INFO
>> {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -
>> 'admin@carbon.super [-1234]' logged in at [2016-02-16 11:43:11,124+0530]
>> {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil}
>> TID: [-1234] [] [2016-02-16 11:43:11,215] ERROR
>> {org.apache.axis2.rpc.receivers.RPCMessageReceiver} -
>> {org.apache.axis2.rpc.receivers.RPCMessageReceiver}
>> java.lang.IllegalArgumentException
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606)
>> at
>> org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
>> at
>> org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
>> at
>> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
>> at
>> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>> at
>> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:173)
>> at
>> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
>> at
>> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>> at
>> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
>> at
>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
>> at
>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>> at
>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:30

Re: [Dev] [Calling Admin Services- DAS] Issue in deploying an Event Receiver to DAS via Admin Services

[Samitha Chathuranga]

Hi,

I was able to resolve this issue via a workaround, but cannot clarify the
related issue with this. What I did as the workaround was, adding the
"org.wso2.carbon.event.receiver.stub"
as a maven dependency in my project and using that stub class (
EventReceiverAdminServiceStub.java) to call the required Admin Service. But
previously what I did was generating the web service client stub by using
Axis2 in Eclipse by giving the giving the url of .wsdl file, after starting
WSO2 DAS.

Here I found that the stub classes consumed at two occasions (Axis2
generated one and maven imported one) are not similar. Specially and
necessarily the "deployWso2EventReceiverConfiguration" method which was
called to deploy the Event Receiver had different signatures (parameters
are different) and that might be the reason for the previous exception "
IllegalArgumentException".

I even compared the related .wsdl file in the carbon-analytics-commons
repository and the.wsdl file which was used to generate the stub with Axis2
with eclipse, but found no significant difference.

So, what causes this difference in the 2 stub classes or isn't this
difference the issue here? Am I missing something here or is there any
issue related in generating client stubs via Axis2?

Thanks and Regards.



On Tue, Feb 16, 2016 at 12:15 PM, Samitha Chathuranga 
wrote:

> Hi,
>
> I am trying to deploy an event receiver in DAS, via calling Admin
> Services, but getting an *IllegalArgumentException*. By the way I
> succeeded in creating an Event Stream in DAS by "EventStreamAdminService"
> Admin Service, and I followed the same basic procedure to call DAS's
> "EventReceiverAdminService", in order to deploy an Event Receiver.
>
> I set EventReceiverName, StreamNameWithVersion, EventAdapterType (to
> "wso2event") and a BasicInputAdapterPropertyDto property
> "events.duplicated.in.cluster" as key and "false" as its value for the
> DeployTextEventReceiverConfiguration. Does anybody has an idea on the issue?
> Am I missing something here?
>
> Stack trace is mentioned below.
>
> Thanks & Regards,
> Samitha
>
> TID: [-1234] [] [2016-02-16 11:43:11,125]  INFO
> {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -
> 'admin@carbon.super [-1234]' logged in at [2016-02-16 11:43:11,124+0530]
> {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil}
> TID: [-1234] [] [2016-02-16 11:43:11,215] ERROR
> {org.apache.axis2.rpc.receivers.RPCMessageReceiver} -
> {org.apache.axis2.rpc.receivers.RPCMessageReceiver}
> java.lang.IllegalArgumentException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
> at
> org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
> at
> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
> at
> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
> at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:173)
> at
> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
> at
> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
> at
> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
> at
> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at
> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at
> org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
> at
> org.apache.catal

[Dev] [VOTE] Release WSO2 Dashboard Server 2.0.0 RC1

[Tanya Madurapperuma]

Hi Devs,

This is the RC release candidate of WSO2 Dashboard Server 2.0.0

Please download DS 2.0.0 RC1 and test the functionality and vote. Vote will
be open for 72 hours or as needed.

Source & binary distribution files:
https://github.com/wso2/product-ds/releases/tag/v2.0.0-RC1

Maven staging repo:
http://maven.wso2.org/nexus/content/repositories/orgwso2ds-358/

The tag to be voted upon:
https://github.com/wso2/product-ds/tree/v2.0.0-RC1


[+] Stable - go ahead and release
[-]  Broken - do not release (explain why)

Thanks and Regards,
~ WSO2 DS Team ~

-- 
Tanya Madurapperuma

Senior Software Engineer,
WSO2 Inc. : wso2.com
Mobile : +94718184439
Blog : http://tanyamadurapperuma.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev