Re: [Dev] Include -DworkerNode=false by default in wso2server.sh startup script?

[Kasun Gajasinghe]

On Fri, Mar 7, 2014 at 1:12 PM, Sanjeewa Malalgoda wrote:

>
>
>
> On Fri, Mar 7, 2014 at 12:28 PM, Kasun Gajasinghe  wrote:
>
>>
>>
>> On Friday, March 7, 2014, Sanjeewa Malalgoda  wrote:
>>
>>>
>>>
>>>
>>> On Fri, Mar 7, 2014 at 11:47 AM, Ajith Vitharana wrote:
>>>



 On Fri, Mar 7, 2014 at 11:44 AM, Nuwan Dias  wrote:

> I think we should get rid of the 'gateway-worker' and
> 'gateway-manager' profiles and have a 'gateway' profile only. The
> worker/manager differentiation should be handled by -DworkerNode.
>

 +1. Please re-factor this, because this should be consistence with
 other products.

>>> Anyway we need 4 profiles for API manager even we moved gateway-worker
>>> and gateway-manager in to gateway.  It is make sense to have -DworkerNode
>>> property for gateway profile but if we get store, publisher and key manager
>>> profiles -DworkerNode property doesn't have any meaning. To be consistent
>>> with other products we might need to support something like this.
>>>
>>> -Dprofile=gateway -DworkerNode=true
>>>
>>> -Dprofile=gateway -DworkerNode=false
>>>
>>> -Dprofile=api-key-manager
>>>
>>>
>>> -Dprofile=api-publisher
>>>
>>> -Dprofile=api-store
>>>
>>>
>>>
>> +1. We need to treat profiles, and worker mode as two different concepts.
>> Currently, the first two scenarios does not work since if you set
>> workerNode=true, then carbon tries to start with a profile called 'worker'.
>> (this is hard-coded). Since APIM does not have that profile, start-up will
>> fail. We need to fix this.
>>
> IMO APIM should not have worker profile simply because APIM server(not
> distributed mode) could not behave as worker or manager if it is not in
> gateway node.  In APIM case default mode should be all in one server(store,
> publisher, gateway, key manager).  Can you point me how user can start
> gateway manager node with your suggestion?
>
>
Yes, my comment is a little misleading. I meant to say that we should
hard-code to start the server with the 'worker' profile if
-DworkerNode=true is set. :)


> Thanks,
> sanjeewa.
>
>
>
>>
>>
>>> If we didn't pass -DworkerNode property it should consider as management
>>> node. If you check profile creation process to support -DworkerNode=true we
>>> need to create profile named worker with following tag(and another profile
>>> named default to handle gateway manager scenario).
>>> worker
>>>
>>> Then if someone tried API manager with -DworkerNode=true it will start
>>> as *gateway worker*. If anyone started without it server will start in
>>> default profile (which is not *gateway manager*). So IMHO we cannot go
>>> for above mentioned suggestion with current profile creation process. AFAIK
>>> multi profile and worker manager profile separation will not work at the
>>> same time.
>>>
>>>
>> What I suggest is that,  if you only set the workerNode property then the
>> server should use the default profile. If the user need a different
>> profile, say gateway, then the user should set the 'profile' property along
>> with the workerNode.
>>
>
>
>>
>>
>>
>>> Thanks,
>>>
>>>
>>>
>>> sanjeewa
>>>
>>>
>>> Thanks.
>>> Ajith
>>>
>>>
>>> Thanks,
>>> NuwanD.
>>>
>>>
>>> On Fri, Mar 7, 2014 at 11:36 AM, Sanjeewa Malalgoda 
>>> wrote:
>>>
>>>
>>>
>>>
>>> On Fri, Mar 7, 2014 at 11:09 AM, Ajith Vitharana wrote:
>>>
>>> Hi KasunG,
>>>
>>>
>>> On Mon, Mar 3, 2014 at 10:40 PM, Kasun Gajasinghe wrote:
>>>
>>> Hi,
>>>
>>> Shall we $subject from Carbon 4.3.0? And then, force the users to enable
>>> workerNode mode by modifying the startup script itself, instead of passing
>>> -DworkerNode=true property via command-line?
>>>
>>> We have noticed that lot of users are passing the said property via the
>>> command-line, but they sometimes miss to set that. That might lead to lot
>>> of issues especially in DepSync. If we set as above, we can lower the human
>>> errors. WDYT?
>>>
>>>
>>> How this is applicable for AM ? Because they use different system
>>> property to start the GW worker/manager  nodes[1].
>>>
>>> [1]
>>> https://docs.wso2.org/display/AM160/Running+the+Product+on+a+Preferred+Profile
>>>
>>> When we create multiple profiles for API manager decide to add 5
>>> profiles as APIM case is bit different compared to other servers in
>>> distributed deployment. In APIM case we can set -Dprofile=gateway-worker
>>> to start up script in the same way you suggested. @KasunG please
>>> confirm, do we specifically check -DworkerNode=true for any scenario.
>>> Otherwise it will not cause to any issue.
>>>
>>> Thanks,
>>> sanjeewa.
>>>
>>>
>>> Thanks.
>>> Ajith
>>>
>>>
>>> Thanks,
>>> KasunG
>>>
>>> --
>>> *Kasun Gajasinghe*
>>> Software Engineer;
>>> WSO2 Inc.; http://wso2.com
>>>
>>>
>>>  ,
>>> *email: *
>>> *kasung AT spamfree wso2.com    ** cell: **+94 (77)
>>> 678-0813*
>>> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>>>
>>>
>>>
>>> *blog: * 
>>>
>>>
>>>
>>>
>>> --
>>>
>>> *Sanjeewa Malalgoda*
>>> 

Re: [Dev] Include -DworkerNode=false by default in wso2server.sh startup script?

[Sanjeewa Malalgoda]

On Fri, Mar 7, 2014 at 12:28 PM, Kasun Gajasinghe  wrote:

>
>
> On Friday, March 7, 2014, Sanjeewa Malalgoda  wrote:
>
>>
>>
>>
>> On Fri, Mar 7, 2014 at 11:47 AM, Ajith Vitharana  wrote:
>>
>>>
>>>
>>>
>>> On Fri, Mar 7, 2014 at 11:44 AM, Nuwan Dias  wrote:
>>>
 I think we should get rid of the 'gateway-worker' and 'gateway-manager'
 profiles and have a 'gateway' profile only. The worker/manager
 differentiation should be handled by -DworkerNode.

>>>
>>> +1. Please re-factor this, because this should be consistence with other
>>> products.
>>>
>> Anyway we need 4 profiles for API manager even we moved gateway-worker
>> and gateway-manager in to gateway.  It is make sense to have -DworkerNode
>> property for gateway profile but if we get store, publisher and key manager
>> profiles -DworkerNode property doesn't have any meaning. To be consistent
>> with other products we might need to support something like this.
>>
>> -Dprofile=gateway -DworkerNode=true
>>
>> -Dprofile=gateway -DworkerNode=false
>>
>> -Dprofile=api-key-manager
>>
>> -Dprofile=api-publisher
>>
>> -Dprofile=api-store
>>
>>
>>
> +1. We need to treat profiles, and worker mode as two different concepts.
> Currently, the first two scenarios does not work since if you set
> workerNode=true, then carbon tries to start with a profile called 'worker'.
> (this is hard-coded). Since APIM does not have that profile, start-up will
> fail. We need to fix this.
>
IMO APIM should not have worker profile simply because APIM server(not
distributed mode) could not behave as worker or manager if it is not in
gateway node.  In APIM case default mode should be all in one server(store,
publisher, gateway, key manager).  Can you point me how user can start
gateway manager node with your suggestion?

Thanks,
sanjeewa.



>
>
>> If we didn't pass -DworkerNode property it should consider as management
>> node. If you check profile creation process to support -DworkerNode=true we
>> need to create profile named worker with following tag(and another profile
>> named default to handle gateway manager scenario).
>> worker
>>
>> Then if someone tried API manager with -DworkerNode=true it will start
>> as *gateway worker*. If anyone started without it server will start in
>> default profile (which is not *gateway manager*). So IMHO we cannot go
>> for above mentioned suggestion with current profile creation process. AFAIK
>> multi profile and worker manager profile separation will not work at the
>> same time.
>>
>>
> What I suggest is that,  if you only set the workerNode property then the
> server should use the default profile. If the user need a different
> profile, say gateway, then the user should set the 'profile' property along
> with the workerNode.
>


>
>
>
>> Thanks,
>>
>> sanjeewa
>>
>>
>> Thanks.
>> Ajith
>>
>>
>> Thanks,
>> NuwanD.
>>
>>
>> On Fri, Mar 7, 2014 at 11:36 AM, Sanjeewa Malalgoda wrote:
>>
>>
>>
>>
>> On Fri, Mar 7, 2014 at 11:09 AM, Ajith Vitharana  wrote:
>>
>> Hi KasunG,
>>
>>
>> On Mon, Mar 3, 2014 at 10:40 PM, Kasun Gajasinghe wrote:
>>
>> Hi,
>>
>> Shall we $subject from Carbon 4.3.0? And then, force the users to enable
>> workerNode mode by modifying the startup script itself, instead of passing
>> -DworkerNode=true property via command-line?
>>
>> We have noticed that lot of users are passing the said property via the
>> command-line, but they sometimes miss to set that. That might lead to lot
>> of issues especially in DepSync. If we set as above, we can lower the human
>> errors. WDYT?
>>
>>
>> How this is applicable for AM ? Because they use different system
>> property to start the GW worker/manager  nodes[1].
>>
>> [1]
>> https://docs.wso2.org/display/AM160/Running+the+Product+on+a+Preferred+Profile
>>
>> When we create multiple profiles for API manager decide to add 5 profiles
>> as APIM case is bit different compared to other servers in distributed
>> deployment. In APIM case we can set -Dprofile=gateway-worker to start
>> up script in the same way you suggested. @KasunG please confirm, do we
>> specifically check -DworkerNode=true for any scenario. Otherwise it will
>> not cause to any issue.
>>
>> Thanks,
>> sanjeewa.
>>
>>
>> Thanks.
>> Ajith
>>
>>
>> Thanks,
>> KasunG
>>
>> --
>> *Kasun Gajasinghe*
>> Software Engineer;
>> WSO2 Inc.; http://wso2.com
>>
>>
>>  ,
>> *email: *
>> *kasung AT spamfree wso2.com    ** cell: **+94 (77)
>> 678-0813*
>> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>>
>>
>>
>> *blog: * 
>>
>>
>>
>>
>> --
>>
>> *Sanjeewa Malalgoda*
>> Senior Software Engineer
>> WSO2 Inc.
>> Mobile : +94713068779
>>
>>  blog
>> :http://sanjeewamalalgoda.blogspot.com/
>>
>>
>>
>
> --
> *Kasun Gajasinghe*
> Software Engineer;
> WSO2 Inc.; http://wso2.com
>
>
>  ,
> *email: *
> *kasung AT spamfree wso2.com    ** cell: **+94 (77)
> 678-0813 <%2B94%20%2877%29%20678-0813>*

Re: [Dev] Include -DworkerNode=false by default in wso2server.sh startup script?

[Kasun Gajasinghe]

On Friday, March 7, 2014, Sanjeewa Malalgoda  wrote:

>
>
>
> On Fri, Mar 7, 2014 at 11:47 AM, Ajith Vitharana 
> 
> > wrote:
>
>>
>>
>>
>> On Fri, Mar 7, 2014 at 11:44 AM, Nuwan Dias 
>> 
>> > wrote:
>>
>>> I think we should get rid of the 'gateway-worker' and 'gateway-manager'
>>> profiles and have a 'gateway' profile only. The worker/manager
>>> differentiation should be handled by -DworkerNode.
>>>
>>
>> +1. Please re-factor this, because this should be consistence with other
>> products.
>>
> Anyway we need 4 profiles for API manager even we moved gateway-worker and
> gateway-manager in to gateway.  It is make sense to have -DworkerNode
> property for gateway profile but if we get store, publisher and key manager
> profiles -DworkerNode property doesn't have any meaning. To be consistent
> with other products we might need to support something like this.
>
> -Dprofile=gateway -DworkerNode=true
>
> -Dprofile=gateway -DworkerNode=false
>
> -Dprofile=api-key-manager
>
> -Dprofile=api-publisher
>
> -Dprofile=api-store
>
>
>
+1. We need to treat profiles, and worker mode as two different concepts.
Currently, the first two scenarios does not work since if you set
workerNode=true, then carbon tries to start with a profile called 'worker'.
(this is hard-coded). Since APIM does not have that profile, start-up will
fail. We need to fix this.



> If we didn't pass -DworkerNode property it should consider as management
> node. If you check profile creation process to support -DworkerNode=true we
> need to create profile named worker with following tag(and another profile
> named default to handle gateway manager scenario).
> worker
>
> Then if someone tried API manager with -DworkerNode=true it will start as 
> *gateway
> worker*. If anyone started without it server will start in default
> profile (which is not *gateway manager*). So IMHO we cannot go for above
> mentioned suggestion with current profile creation process. AFAIK multi
> profile and worker manager profile separation will not work at the same
> time.
>
>
What I suggest is that,  if you only set the workerNode property then the
server should use the default profile. If the user need a different
profile, say gateway, then the user should set the 'profile' property along
with the workerNode.




> Thanks,
> sanjeewa
>
>
> Thanks.
> Ajith
>
>
> Thanks,
> NuwanD.
>
>
> On Fri, Mar 7, 2014 at 11:36 AM, Sanjeewa Malalgoda wrote:
>
>
>
>
> On Fri, Mar 7, 2014 at 11:09 AM, Ajith Vitharana  wrote:
>
> Hi KasunG,
>
>
> On Mon, Mar 3, 2014 at 10:40 PM, Kasun Gajasinghe  wrote:
>
> Hi,
>
> Shall we $subject from Carbon 4.3.0? And then, force the users to enable
> workerNode mode by modifying the startup script itself, instead of passing
> -DworkerNode=true property via command-line?
>
> We have noticed that lot of users are passing the said property via the
> command-line, but they sometimes miss to set that. That might lead to lot
> of issues especially in DepSync. If we set as above, we can lower the human
> errors. WDYT?
>
>
> How this is applicable for AM ? Because they use different system property
> to start the GW worker/manager  nodes[1].
>
> [1]
> https://docs.wso2.org/display/AM160/Running+the+Product+on+a+Preferred+Profile
>
> When we create multiple profiles for API manager decide to add 5 profiles
> as APIM case is bit different compared to other servers in distributed
> deployment. In APIM case we can set -Dprofile=gateway-worker to start
> up script in the same way you suggested. @KasunG please confirm, do we
> specifically check -DworkerNode=true for any scenario. Otherwise it will
> not cause to any issue.
>
> Thanks,
> sanjeewa.
>
>
> Thanks.
> Ajith
>
>
> Thanks,
> KasunG
>
> --
> *Kasun Gajasinghe*
> Software Engineer;
> WSO2 Inc.; http://wso2.com
>
>
>  ,
> *email: *
> *kasung AT spamfree wso2.com    ** cell: **+94 (77)
> 678-0813*
> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>
>
>
> *blog: * 
>
>
>
>
> --
>
> *Sanjeewa Malalgoda*
> Senior Software Engineer
> WSO2 Inc.
> Mobile : +94713068779
>
>  blog
> :http://sanjeewamalalgoda.blogspot.com/
>
>
>

-- 
*Kasun Gajasinghe*
Software Engineer;
WSO2 Inc.; http://wso2.com


 ,
*email: *
*kasung AT spamfree wso2.com   ** cell: **+94 (77)
678-0813*
*linked-in: *http://lk.linkedin.com/in/gajasinghe



*blog: **http://kasunbg.org* 



*twitter: **http://twitter.com/kasunbg* 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to view the commit details in AppFactory cloud preview

[Sohani Weerasinghe]

In Gitblit select the repositories tab and then select the relevant
application from the application list then you can find the commit details
under commits tab.

Regards,
Sohani

Sohani Weerasinghe
Software Engineer
WSO2, Inc: http://wso2.com

Mobile  : +94 716439774
Blog :http://christinetechtips.blogspot.com/
Twitter  : https://twitter.com/sohanichristine


On Fri, Mar 7, 2014 at 12:04 PM, Susinda Perera  wrote:

> Any possibility of $subject?
>
> --
> *Susinda Perera*
> Software Engineer
> Mobile:(+94)716049075
>
> WSO2 Inc. http://wso2.com/
> Tel : 94 11 214 5345 Fax :94 11 2145300
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Include -DworkerNode=false by default in wso2server.sh startup script?

[Sanjeewa Malalgoda]

On Fri, Mar 7, 2014 at 11:47 AM, Ajith Vitharana  wrote:

>
>
>
> On Fri, Mar 7, 2014 at 11:44 AM, Nuwan Dias  wrote:
>
>> I think we should get rid of the 'gateway-worker' and 'gateway-manager'
>> profiles and have a 'gateway' profile only. The worker/manager
>> differentiation should be handled by -DworkerNode.
>>
>
> +1. Please re-factor this, because this should be consistence with other
> products.
>
Anyway we need 4 profiles for API manager even we moved gateway-worker and
gateway-manager in to gateway.  It is make sense to have -DworkerNode
property for gateway profile but if we get store, publisher and key manager
profiles -DworkerNode property doesn't have any meaning. To be consistent
with other products we might need to support something like this.

-Dprofile=gateway -DworkerNode=true

-Dprofile=gateway -DworkerNode=false

-Dprofile=api-key-manager

-Dprofile=api-publisher

-Dprofile=api-store


If we didn't pass -DworkerNode property it should consider as management
node. If you check profile creation process to support -DworkerNode=true we
need to create profile named worker with following tag(and another profile
named default to handle gateway manager scenario).
worker

Then if someone tried API manager with -DworkerNode=true it will start
as *gateway
worker*. If anyone started without it server will start in default profile
(which is not *gateway manager*). So IMHO we cannot go for above mentioned
suggestion with current profile creation process. AFAIK multi profile and
worker manager profile separation will not work at the same time.

Thanks,
sanjeewa


> Thanks.
> Ajith
>
>>
>> Thanks,
>> NuwanD.
>>
>>
>> On Fri, Mar 7, 2014 at 11:36 AM, Sanjeewa Malalgoda wrote:
>>
>>>
>>>
>>>
>>> On Fri, Mar 7, 2014 at 11:09 AM, Ajith Vitharana wrote:
>>>
 Hi KasunG,


 On Mon, Mar 3, 2014 at 10:40 PM, Kasun Gajasinghe wrote:

> Hi,
>
> Shall we $subject from Carbon 4.3.0? And then, force the users to
> enable workerNode mode by modifying the startup script itself, instead of
> passing -DworkerNode=true property via command-line?
>
> We have noticed that lot of users are passing the said property via
> the command-line, but they sometimes miss to set that. That might lead to
> lot of issues especially in DepSync. If we set as above, we can lower the
> human errors. WDYT?
>

 How this is applicable for AM ? Because they use different system
 property to start the GW worker/manager  nodes[1].

 [1]
 https://docs.wso2.org/display/AM160/Running+the+Product+on+a+Preferred+Profile

>>> When we create multiple profiles for API manager decide to add 5
>>> profiles as APIM case is bit different compared to other servers in
>>> distributed deployment. In APIM case we can set -Dprofile=gateway-worker
>>> to start up script in the same way you suggested. @KasunG please
>>> confirm, do we specifically check -DworkerNode=true for any scenario.
>>> Otherwise it will not cause to any issue.
>>>
>>> Thanks,
>>> sanjeewa.
>>>

 Thanks.
 Ajith

>
> Thanks,
> KasunG
>
> --
> *Kasun Gajasinghe*
> Software Engineer;
> WSO2 Inc.; http://wso2.com
>
>
>  ,
> *email: *
> *kasung AT spamfree wso2.com    ** cell: **+94 (77)
> 678-0813 <%2B94%20%2877%29%20678-0813>*
> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>
>
>
> *blog: **http://kasunbg.org* 
>
>
>
> *twitter: **http://twitter.com/kasunbg* 
>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Ajith Vitharana.
 WSO2 Inc. - http://wso2.org
 Email  :  aji...@wso2.com
 Mobile : +94772217350


>>>
>>>
>>> --
>>>
>>> *Sanjeewa Malalgoda*
>>> Senior Software Engineer
>>> WSO2 Inc.
>>> Mobile : +94713068779
>>>
>>>  blog
>>> :http://sanjeewamalalgoda.blogspot.com/
>>>
>>>
>>>
>>
>>
>> --
>> Nuwan Dias
>>
>> Senior Software Engineer - WSO2, Inc. http://wso2.com
>>  email : nuw...@wso2.com
>> Phone : +94 777 775 729
>>
>
>
>
> --
> Ajith Vitharana.
> WSO2 Inc. - http://wso2.org
> Email  :  aji...@wso2.com
> Mobile : +94772217350
>
>


-- 

*Sanjeewa Malalgoda*
Senior Software Engineer
WSO2 Inc.
Mobile : +94713068779

 blog
:http://sanjeewamalalgoda.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] How to view the commit details in AppFactory cloud preview

[Susinda Perera]

Any possibility of $subject?

-- 
*Susinda Perera*
Software Engineer
Mobile:(+94)716049075

WSO2 Inc. http://wso2.com/
Tel : 94 11 214 5345 Fax :94 11 2145300
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Exposing the Activiti REST API

[Afkham Azeez]

Instead of that class, for privileged operations, you should use
PrivilegedCarbonContext.


On Fri, Mar 7, 2014 at 11:22 AM, Chathura Ekanayake wrote:

>
> Hi Subash,
>
> There seem to be no class named SuperTenantCarbonContext. We can get
> CarbonContext using CarbonContext.getCurrentContext(), but getOSGiService(...)
> method is not available from this.
>
> Regards,
> Chathura
>
>
> On Fri, Mar 7, 2014 at 10:57 AM, Subash Chaturanga wrote:
>
>> Hi Chathura,
>> You can access OSGi services from CC. I am not sure if this has changed
>> very recently. Unless you can do it as follows.
>>
>>  service=()
>> SuperTenantCarbonContext.getCurrentContext().getOSGiService(> OSGIServiceInterfaceName>.class);
>>
>>
>> On Fri, Mar 7, 2014 at 10:36 AM, Chathura Ekanayake wrote:
>>
>>>
>>> Hi Sagara,
>>>
>>> If we deploy it as a web application, is there a way to access OSGi
>>> services within it?
>>> As we don't package it as a bundle, a BundleContext object is not
>>> available for the webapp, so it is not possible get references to OSGi
>>> services. Is there a way to deploy a webapp as a bundle?
>>>
>>> Regards,
>>> Chathura
>>>
>>>
>>>
>>> On Thu, Mar 6, 2014 at 1:49 PM, Sagara Gunathunga wrote:
>>>



 On Thu, Mar 6, 2014 at 12:15 PM, Chathura Ekanayake 
 wrote:

>
> Hi All,
>
> Activiti has a Restlet based comprehensive REST API to expose all BPMN
> related functions. As we are planning to have a REST API for BPMN, we can
> integrate this Activiti REST module in Carbon. Could I get feedback on the
> following items regarding this integration:
>
> Restlet vs JAX-RS:
> Should we integrate the Restlet based Activiti API or should we write
> a new JAX-RS based REST module? I think it is better to use the Activiti
> REST module as it allows us to migrate easily with new Activiti versions.
>

 IMHO if Activiti REST module can cater all of our BPMN requirements
 then rewriting is not required at least at this point.


>
> Integrating the Activiti Restlet based API:
> If we decide to integrate the Activiti REST module, we have to expose
> the Restlet servlet to handle REST requests. One option is to register 
> this
> servlet in repository/conf/tomcat/web.xml, which exposes this on the same
> port as admin services. However, we have to keep these servlet 
> registration
> entries in the web.xml, even though the BPMN component is not deployed.
> Another option is to start a separate server (if this is possible in
> Carbon) for Activiti REST and register the Restlet servlet in that server.
>

 Can't we just deploy above module as a web application with own context
 path as mention in this post[1] ?  If you look at OAuth endpoint in IS/APIM
 we used this approach additionally some of future AS integration will use
 this approach.

 [1] -
 http://bpmn20inaction.blogspot.com/2013/02/activiti-in-action-updates-part-1.html

 Thanks !

>
> Thoughts...
>
> Regards,
> Chathura
>
>
>


 --
 Sagara Gunathunga

 Senior Technical Lead; WSO2, Inc.;  http://wso2.com
 V.P Apache Web Services;http://ws.apache.org/
 Linkedin; http://www.linkedin.com/in/ssagara
 Blog ;  http://ssagara.blogspot.com


>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Thanks
>> /subash
>>
>> *Subash Chaturanga*
>> Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com
>>
>> email: sub...@wso2.com
>> blog:  http://subashsdm.blogspot.com/
>> twitter: @subash89
>> phone: +9477 2225922
>> Lean . Enterprise . Middleware
>>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* *
*email: **az...@wso2.com* 
* cell: +94 77 3320919 blog: **http://blog.afkham.org*
*twitter: **http://twitter.com/afkham_azeez*
* linked-in: **http://lk.linkedin.com/in/afkhamazeez
*

*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Include -DworkerNode=false by default in wso2server.sh startup script?

[Ajith Vitharana]

On Fri, Mar 7, 2014 at 11:44 AM, Nuwan Dias  wrote:

> I think we should get rid of the 'gateway-worker' and 'gateway-manager'
> profiles and have a 'gateway' profile only. The worker/manager
> differentiation should be handled by -DworkerNode.
>

+1. Please re-factor this, because this should be consistence with other
products.

Thanks.
Ajith

>
> Thanks,
> NuwanD.
>
>
> On Fri, Mar 7, 2014 at 11:36 AM, Sanjeewa Malalgoda wrote:
>
>>
>>
>>
>> On Fri, Mar 7, 2014 at 11:09 AM, Ajith Vitharana  wrote:
>>
>>> Hi KasunG,
>>>
>>>
>>> On Mon, Mar 3, 2014 at 10:40 PM, Kasun Gajasinghe wrote:
>>>
 Hi,

 Shall we $subject from Carbon 4.3.0? And then, force the users to
 enable workerNode mode by modifying the startup script itself, instead of
 passing -DworkerNode=true property via command-line?

 We have noticed that lot of users are passing the said property via the
 command-line, but they sometimes miss to set that. That might lead to lot
 of issues especially in DepSync. If we set as above, we can lower the human
 errors. WDYT?

>>>
>>> How this is applicable for AM ? Because they use different system
>>> property to start the GW worker/manager  nodes[1].
>>>
>>> [1]
>>> https://docs.wso2.org/display/AM160/Running+the+Product+on+a+Preferred+Profile
>>>
>> When we create multiple profiles for API manager decide to add 5 profiles
>> as APIM case is bit different compared to other servers in distributed
>> deployment. In APIM case we can set -Dprofile=gateway-worker to start
>> up script in the same way you suggested. @KasunG please confirm, do we
>> specifically check -DworkerNode=true for any scenario. Otherwise it will
>> not cause to any issue.
>>
>> Thanks,
>> sanjeewa.
>>
>>>
>>> Thanks.
>>> Ajith
>>>

 Thanks,
 KasunG

 --
 *Kasun Gajasinghe*
 Software Engineer;
 WSO2 Inc.; http://wso2.com


  ,
 *email: *
 *kasung AT spamfree wso2.com    ** cell: **+94 (77)
 678-0813 <%2B94%20%2877%29%20678-0813>*
 *linked-in: *http://lk.linkedin.com/in/gajasinghe



 *blog: **http://kasunbg.org* 



 *twitter: **http://twitter.com/kasunbg* 




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


>>>
>>>
>>> --
>>> Ajith Vitharana.
>>> WSO2 Inc. - http://wso2.org
>>> Email  :  aji...@wso2.com
>>> Mobile : +94772217350
>>>
>>>
>>
>>
>> --
>>
>> *Sanjeewa Malalgoda*
>> Senior Software Engineer
>> WSO2 Inc.
>> Mobile : +94713068779
>>
>>  blog
>> :http://sanjeewamalalgoda.blogspot.com/
>>
>>
>>
>
>
> --
> Nuwan Dias
>
> Senior Software Engineer - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>



-- 
Ajith Vitharana.
WSO2 Inc. - http://wso2.org
Email  :  aji...@wso2.com
Mobile : +94772217350
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Include -DworkerNode=false by default in wso2server.sh startup script?

[Nuwan Dias]

I think we should get rid of the 'gateway-worker' and 'gateway-manager'
profiles and have a 'gateway' profile only. The worker/manager
differentiation should be handled by -DworkerNode.

Thanks,
NuwanD.


On Fri, Mar 7, 2014 at 11:36 AM, Sanjeewa Malalgoda wrote:

>
>
>
> On Fri, Mar 7, 2014 at 11:09 AM, Ajith Vitharana  wrote:
>
>> Hi KasunG,
>>
>>
>> On Mon, Mar 3, 2014 at 10:40 PM, Kasun Gajasinghe wrote:
>>
>>> Hi,
>>>
>>> Shall we $subject from Carbon 4.3.0? And then, force the users to enable
>>> workerNode mode by modifying the startup script itself, instead of passing
>>> -DworkerNode=true property via command-line?
>>>
>>> We have noticed that lot of users are passing the said property via the
>>> command-line, but they sometimes miss to set that. That might lead to lot
>>> of issues especially in DepSync. If we set as above, we can lower the human
>>> errors. WDYT?
>>>
>>
>> How this is applicable for AM ? Because they use different system
>> property to start the GW worker/manager  nodes[1].
>>
>> [1]
>> https://docs.wso2.org/display/AM160/Running+the+Product+on+a+Preferred+Profile
>>
> When we create multiple profiles for API manager decide to add 5 profiles
> as APIM case is bit different compared to other servers in distributed
> deployment. In APIM case we can set -Dprofile=gateway-worker to start
> up script in the same way you suggested. @KasunG please confirm, do we
> specifically check -DworkerNode=true for any scenario. Otherwise it will
> not cause to any issue.
>
> Thanks,
> sanjeewa.
>
>>
>> Thanks.
>> Ajith
>>
>>>
>>> Thanks,
>>> KasunG
>>>
>>> --
>>> *Kasun Gajasinghe*
>>> Software Engineer;
>>> WSO2 Inc.; http://wso2.com
>>>
>>>
>>>  ,
>>> *email: *
>>> *kasung AT spamfree wso2.com    ** cell: **+94 (77)
>>> 678-0813 <%2B94%20%2877%29%20678-0813>*
>>> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>>>
>>>
>>>
>>> *blog: **http://kasunbg.org* 
>>>
>>>
>>>
>>> *twitter: **http://twitter.com/kasunbg* 
>>>
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Ajith Vitharana.
>> WSO2 Inc. - http://wso2.org
>> Email  :  aji...@wso2.com
>> Mobile : +94772217350
>>
>>
>
>
> --
>
> *Sanjeewa Malalgoda*
> Senior Software Engineer
> WSO2 Inc.
> Mobile : +94713068779
>
>  blog
> :http://sanjeewamalalgoda.blogspot.com/
>
>
>


-- 
Nuwan Dias

Senior Software Engineer - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Include -DworkerNode=false by default in wso2server.sh startup script?

[Sanjeewa Malalgoda]

On Fri, Mar 7, 2014 at 11:09 AM, Ajith Vitharana  wrote:

> Hi KasunG,
>
>
> On Mon, Mar 3, 2014 at 10:40 PM, Kasun Gajasinghe  wrote:
>
>> Hi,
>>
>> Shall we $subject from Carbon 4.3.0? And then, force the users to enable
>> workerNode mode by modifying the startup script itself, instead of passing
>> -DworkerNode=true property via command-line?
>>
>> We have noticed that lot of users are passing the said property via the
>> command-line, but they sometimes miss to set that. That might lead to lot
>> of issues especially in DepSync. If we set as above, we can lower the human
>> errors. WDYT?
>>
>
> How this is applicable for AM ? Because they use different system property
> to start the GW worker/manager  nodes[1].
>
> [1]
> https://docs.wso2.org/display/AM160/Running+the+Product+on+a+Preferred+Profile
>
When we create multiple profiles for API manager decide to add 5 profiles
as APIM case is bit different compared to other servers in distributed
deployment. In APIM case we can set -Dprofile=gateway-worker to start
up script in the same way you suggested. @KasunG please confirm, do we
specifically check -DworkerNode=true for any scenario. Otherwise it will
not cause to any issue.

Thanks,
sanjeewa.

>
> Thanks.
> Ajith
>
>>
>> Thanks,
>> KasunG
>>
>> --
>> *Kasun Gajasinghe*
>> Software Engineer;
>> WSO2 Inc.; http://wso2.com
>>
>>
>>  ,
>> *email: *
>> *kasung AT spamfree wso2.com    ** cell: **+94 (77)
>> 678-0813 <%2B94%20%2877%29%20678-0813>*
>> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>>
>>
>>
>> *blog: **http://kasunbg.org* 
>>
>>
>>
>> *twitter: **http://twitter.com/kasunbg* 
>>
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Ajith Vitharana.
> WSO2 Inc. - http://wso2.org
> Email  :  aji...@wso2.com
> Mobile : +94772217350
>
>


-- 

*Sanjeewa Malalgoda*
Senior Software Engineer
WSO2 Inc.
Mobile : +94713068779

 blog
:http://sanjeewamalalgoda.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Updates for BPMN Admin UI

[Amal Gunatilake]

Hi Nandika,

I attached the patches to following jira :
https://wso2.org/jira/browse/BPS-471

Thank you  & Best regards,

*Amal Gunatilake*
 Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware


On Thu, Mar 6, 2014 at 9:18 PM, Nandika Jayawardana wrote:

> Hi Amal,
>
> Please create a jira and attach the patch to the jira.
>
> Regards
> Nandika
>
>
> On Thu, Mar 6, 2014 at 5:50 PM, Amal Gunatilake  wrote:
>
>> Hi Chathura,
>>
>> As we discussed before I updated some functionality in the back-end
>> server code which is needed for BPMN Admin UI. Please apply the attached
>> patch after reviewing with your changes.
>>
>> Thank you  & Best regards,
>>
>> *Amal Gunatilake*
>>  Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Nandika Jayawardana
> Senior Technical Lead
> WSO2 Inc ; http://wso2.com
> lean.enterprise.middleware
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Exposing the Activiti REST API

[Chathura Ekanayake]

Hi Subash,

There seem to be no class named SuperTenantCarbonContext. We can get
CarbonContext using CarbonContext.getCurrentContext(), but getOSGiService(...)
method is not available from this.

Regards,
Chathura


On Fri, Mar 7, 2014 at 10:57 AM, Subash Chaturanga  wrote:

> Hi Chathura,
> You can access OSGi services from CC. I am not sure if this has changed
> very recently. Unless you can do it as follows.
>
>  service=()
> SuperTenantCarbonContext.getCurrentContext().getOSGiService( OSGIServiceInterfaceName>.class);
>
>
> On Fri, Mar 7, 2014 at 10:36 AM, Chathura Ekanayake wrote:
>
>>
>> Hi Sagara,
>>
>> If we deploy it as a web application, is there a way to access OSGi
>> services within it?
>> As we don't package it as a bundle, a BundleContext object is not
>> available for the webapp, so it is not possible get references to OSGi
>> services. Is there a way to deploy a webapp as a bundle?
>>
>> Regards,
>> Chathura
>>
>>
>>
>> On Thu, Mar 6, 2014 at 1:49 PM, Sagara Gunathunga wrote:
>>
>>>
>>>
>>>
>>> On Thu, Mar 6, 2014 at 12:15 PM, Chathura Ekanayake 
>>> wrote:
>>>

 Hi All,

 Activiti has a Restlet based comprehensive REST API to expose all BPMN
 related functions. As we are planning to have a REST API for BPMN, we can
 integrate this Activiti REST module in Carbon. Could I get feedback on the
 following items regarding this integration:

 Restlet vs JAX-RS:
 Should we integrate the Restlet based Activiti API or should we write a
 new JAX-RS based REST module? I think it is better to use the Activiti REST
 module as it allows us to migrate easily with new Activiti versions.

>>>
>>> IMHO if Activiti REST module can cater all of our BPMN requirements then
>>> rewriting is not required at least at this point.
>>>
>>>

 Integrating the Activiti Restlet based API:
 If we decide to integrate the Activiti REST module, we have to expose
 the Restlet servlet to handle REST requests. One option is to register this
 servlet in repository/conf/tomcat/web.xml, which exposes this on the same
 port as admin services. However, we have to keep these servlet registration
 entries in the web.xml, even though the BPMN component is not deployed.
 Another option is to start a separate server (if this is possible in
 Carbon) for Activiti REST and register the Restlet servlet in that server.

>>>
>>> Can't we just deploy above module as a web application with own context
>>> path as mention in this post[1] ?  If you look at OAuth endpoint in IS/APIM
>>> we used this approach additionally some of future AS integration will use
>>> this approach.
>>>
>>> [1] -
>>> http://bpmn20inaction.blogspot.com/2013/02/activiti-in-action-updates-part-1.html
>>>
>>> Thanks !
>>>

 Thoughts...

 Regards,
 Chathura



>>>
>>>
>>> --
>>> Sagara Gunathunga
>>>
>>> Senior Technical Lead; WSO2, Inc.;  http://wso2.com
>>> V.P Apache Web Services;http://ws.apache.org/
>>> Linkedin; http://www.linkedin.com/in/ssagara
>>> Blog ;  http://ssagara.blogspot.com
>>>
>>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks
> /subash
>
> *Subash Chaturanga*
> Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com
>
> email: sub...@wso2.com
> blog:  http://subashsdm.blogspot.com/
> twitter: @subash89
> phone: +9477 2225922
> Lean . Enterprise . Middleware
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] Developer Studio 3.6.0 RC 1 Released!

[Kavith Lokuhewage]

Hi,

I had the same issue with kepler in ubuntu 13.10. The solution in the stack
overflow (mentioned by Isuru) worked for me also.

I created a .desktop file as below.

[Desktop Entry]
Version=4.3.0
Name=Eclipse
Comment=IDE for all seasons
#Exec=/home/Kavith/eclipse/eclipse
Exec=env UBUNTU_MENUPROXY=0 /home/Kavith/eclipse/eclipse
Icon=/home/Kavith/eclipse/icon.xpm
Terminal=false
Type=Application
Categories=Utility;Application

Thanks.


On Fri, Mar 7, 2014 at 10:17 AM, Aruna Karunarathna  wrote:

> Hi all,
>
> I've also experienced the same when using eclipse
> eclipse-jee-kepler-SR2-linux-gtk-x86_64 in Ubuntu 13.10. I think this is
> something to do with unity.
>
> As Jasintha suggested using GNOME solved the problem.
>
> Regards,
>
>
> On Fri, Mar 7, 2014 at 10:09 AM, Jasintha Dasanayake wrote:
>
>>  This also can be resolved by using GNOME instead of having unity(this is
>> the default shell).
>>
>> /Jasintha
>>
>>
>> On Fri, Mar 7, 2014 at 9:34 AM, Daya Attapattu  wrote:
>>
>>> I encountered this bug when running eclipse on Ubuntu 13.10.  It can be
>>> fixed though.  I followed the instructions on that stackoverfolw posting.
>>> That didn't immediately fix it for me.  I had to set "env 
>>> UBUNTU_MENUPROXY=0"
>>> on ~/.local/share/applications/eclipse.desktop too.
>>>
>>> - Daya
>>>
>>>
>>>
>>> On Fri, Mar 7, 2014 at 9:14 AM, Lahiru Gamage  wrote:
>>>
 Yeah... That can be the issue. Hopefully in 14.04 it will be fixed.
 Anyway we will need to tackle this as some customer can use Ubuntu 13.10.

 Go with older Eclipse? Juno doesn't has this issue.

 Wdyt?

 Thanks.


 On Thu, Mar 6, 2014 at 7:11 PM, Ramindu Deshapriya 
 wrote:

> Hi Lahiru,
>
> Are you using Ubuntu 13.10? This is am issue with Eclipse.
>
> http://stackoverflow.com/questions/19452390/eclipse-menus-dont-show-up-after-upgrading-to-ubuntu-13-10
>
> Hope this helps.
>
> On Mar 7, 2014 3:10 AM, "Lahiru Gamage"  wrote:
> >
> > Hi Susinda,
> >
> > I tried Developer studio with Eclipse provided. (Linux 64 bit).
> Cannot get the menu items down. E.g. "Developer Studio" Menu item.
> >
> > Thanks.
> >
> >
> >
> > On Thu, Mar 6, 2014 at 5:52 AM, Susinda Perera 
> wrote:
> >>
> >>
> >> Hi All,
> >>
> >> We have WSO2 Developer Studio 3.6.0 RC 1 ready to be downloaded at
> [1] and installed eclipse distributions available at [2]. This release is
> mainly focused on migrating Developer Studio to Eclipse Kepler. And
> additionally includes following bug fixes, improvements and tasks.
> >>
> >>
> >> Bug Fixes
> >> [TOOLS-1107] - "Show in registry browser" option should be disabled
> for resources that are not in the registry.
> >> [TOOLS-1323] - Mediator palette scrolling is not intuitive
> >> [TOOLS-1472] - Rule Mediator does not deserialize correctly
> >> [TOOLS-1665] - Developer Studio JAX-WS Service Project, project
> name does not update with selection of wsdl file
> >> [TOOLS-1745] - AF login dialog save credintial label cannot see
> completly
> >> [TOOLS-1972] - When add/remove case to switch mediator sizes of
> inner cases get reduced and additional arrow is appear in the input
> connector side
> >> [TOOLS-1973] - when delete and undo a complex mediator - An
> exception occured
> >> [TOOLS-2030] - Cannot create Dynamic Endpoints
> >> [TOOLS-2059] - Three clicks are required to edit the description of
> a mediator
> >> [TOOLS-2189] - Deleting a proxy service either from DevStudio or
> the file system doesn't update pom.xml
> >> [TOOLS-2228] - flow is get lost when delete the drop mediator
> >> [TOOLS-2269] - New Registry Handler Creation Wizard layout is not
> displaying properly
> >> [TOOLS-2292] - Create new registry aspect class wizard fails to
> complete
> >> [TOOLS-2310] - Save pom.xml on Project Import to fix the artifacts
> ordering issue
> >> [TOOLS-2313] - HTTP and Template endpoints get Address endpoint
> icon when drag and drop from Endpoint palette group
> >> [TOOLS-2319] - Template wizard creates a useless WSDL EP when
> either WSDL url, service or port is invalid
> >> [TOOLS-2323] - DBLookup and DBReport have the same icon in tool
> palette
> >> [TOOLS-2325] - All available message stores in the workspace are
> not displaying in the properties view of the Store mediator
> >> [TOOLS-2330] - SQL Statement Configuration window's Parameters and
> Results tables have not aligned properly
> >> [TOOLS-2331] - In Clone Mediator's target configuration dialog, the
> table is non editable
> >> [TOOLS-2332] - In Rule Mediator's fact configuration dialog, the
> table has not aligned properly
> >> [TOOLS-2333] - In Endpoint's properties window, Value and Type
> columns should swap
> >> [TOOLS-2336] - Schedu

Re: [Dev] Include -DworkerNode=false by default in wso2server.sh startup script?

[Ajith Vitharana]

Hi KasunG,


On Mon, Mar 3, 2014 at 10:40 PM, Kasun Gajasinghe  wrote:

> Hi,
>
> Shall we $subject from Carbon 4.3.0? And then, force the users to enable
> workerNode mode by modifying the startup script itself, instead of passing
> -DworkerNode=true property via command-line?
>
> We have noticed that lot of users are passing the said property via the
> command-line, but they sometimes miss to set that. That might lead to lot
> of issues especially in DepSync. If we set as above, we can lower the human
> errors. WDYT?
>

How this is applicable for AM ? Because they use different system property
to start the GW worker/manager  nodes[1].

[1]
https://docs.wso2.org/display/AM160/Running+the+Product+on+a+Preferred+Profile

Thanks.
Ajith

>
> Thanks,
> KasunG
>
> --
> *Kasun Gajasinghe*
> Software Engineer;
> WSO2 Inc.; http://wso2.com
>
>
>  ,
> *email: *
> *kasung AT spamfree wso2.com    ** cell: **+94 (77)
> 678-0813 <%2B94%20%2877%29%20678-0813>*
> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>
>
>
> *blog: **http://kasunbg.org* 
>
>
>
> *twitter: **http://twitter.com/kasunbg* 
>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ajith Vitharana.
WSO2 Inc. - http://wso2.org
Email  :  aji...@wso2.com
Mobile : +94772217350
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] IS 4.7.0 Milestone 3 Released!

[Dulanja Liyanage]

That's very weird. Can you please share the conf directory?


On Thu, Mar 6, 2014 at 11:15 PM, Lahiru Gamage  wrote:

> BTW.
>
> I did not add any Mysql datasource, this is a fresh pack of IS M3.
>
> Thanks.
>
>
> On Thu, Mar 6, 2014 at 10:17 AM, Lahiru Gamage  wrote:
>
>> Hi Dulanja,
>>
>> I tried to start M3 in a windows machine. It gave me error at [1].
>>
>> I did not change any config before running. Should I?
>>
>> Thanks.
>>
>> [1]
>>
>> [2014-03-06 10:14:19,104] ERROR
>> {org.wso2.carbon.user.core.util.DatabaseUtil} -  Database Error - Could not
>> create connection to database server. Attempted reconnect 3 times.
>>  Giving up.
>> com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException:
>> Could not create connection to database server. Attempted reconnect 3
>> times. Giving up.
>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>> Method)
>> at
>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
>> at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
>> at com.mysql.jdbc.Util.getInstance(Util.java:386)
>> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1014)
>> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:988)
>> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:974)
>> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:919)
>> at
>> com.mysql.jdbc.ConnectionImpl.connectWithRetries(ConnectionImpl.java:2299)
>> at
>> com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2220)
>> at com.mysql.jdbc.ConnectionImpl.(ConnectionImpl.java:813)
>> at com.mysql.jdbc.JDBC4Connection.(JDBC4Connection.java:47)
>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>> Method)
>> at
>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
>> at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
>> at
>> com.mysql.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:399)
>> at
>> com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:334)
>> at
>> org.apache.tomcat.jdbc.pool.PooledConnection.connectUsingDriver(PooledConnection.java:278)
>> at
>> org.apache.tomcat.jdbc.pool.PooledConnection.connect(PooledConnection.java:182)
>> at
>> org.apache.tomcat.jdbc.pool.ConnectionPool.createConnection(ConnectionPool.java:701)
>> at
>> org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(ConnectionPool.java:635)
>> at
>> org.apache.tomcat.jdbc.pool.ConnectionPool.getConnection(ConnectionPool.java:188)
>> at
>> org.apache.tomcat.jdbc.pool.DataSourceProxy.getConnection(DataSourceProxy.java:127)
>> at
>> org.wso2.carbon.user.core.claim.dao.ClaimDAO.getDialectCount(ClaimDAO.java:158)
>> at
>> org.wso2.carbon.user.core.common.DefaultRealm.populateProfileAndClaimMaps(DefaultRealm.java:411)
>> at
>> org.wso2.carbon.user.core.common.DefaultRealm.init(DefaultRealm.java:101)
>> at
>> org.wso2.carbon.user.core.common.DefaultRealmService.initializeRealm(DefaultRealmService.java:223)
>> at
>> org.wso2.carbon.user.core.common.DefaultRealmService.(DefaultRealmService.java:101)
>> at
>> org.wso2.carbon.user.core.common.DefaultRealmService.(DefaultRealmService.java:114)
>> at
>> org.wso2.carbon.user.core.internal.Activator.startDeploy(Activator.java:69)
>> at
>> org.wso2.carbon.user.core.internal.BundleCheckActivator.start(BundleCheckActivator.java:61)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
>> at java.security.AccessController.doPrivileged(Native Method)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
>> at
>> org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:390)
>> at
>> org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1176)
>> at
>> org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559)
>> at
>> org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544)
>> at
>> or

[Dev] GSoC 2014 : Implement Registry Extension (RXT) 2.0 + Associated UI support

[Iresha Udayangani]

Hi all,


I'm Iresha Udayangani, a 3rd year undergraduate of department of
Electronic and Telecommunication Engineering, University of Moratuwa,
Sri Lanka. I went through the list of WSO2 project ideas for GSOC

2014. Proposal 1: Implement Registry Extension (RXT) 2.0 + Associated

UI support seemed to be quite interesting and match my past
experiences.

I was able to download wso2greg-4.6.0, then run it. I went through
some of the reference documents/webinars and uploaded a couple of rxt
files(person.rxt, project.rxt) in Extensions->Artifact Types ->Add new
Artifacts and got familiar with their functionality.

As far as I can understand the project expects the following,

[1] A new RXT format should be defined using JSON, instead of the
current XML Structure, so that existing JSPs might need few
alterations in order to render UIs based on the new JSON format.
JSON seems to be more efficient and browser friendly compared to XML.

[2] Instead of user manually configuring/creating the XML structure
(RXT definition) the project expects to automatically generate the RXT
definition from a UI template.

[3] When adding a new Artifact type, user can be provided with a new
UI where it contains basic fields to be filled (such as artifactType,
singularLabel, pluralLabel, storagePath etc. ) and few custom elements
(to add UI columns, content fields) instead of the current XML editor,
where user needs a bit of programming background to configure things.
After the user successfully configured the new artifact, the RXT
format can be generated using the information provided in the previous
step. An editor can be provided  for the advanced users as well.

I'm a bit struggling in understanding  some of the project
deliverables and trying to find the code samples, where it needs to be
modified. It would be much helpful if anyone could help me out with
more details.

Thanks,
Iresha.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Exposing the Activiti REST API

[Subash Chaturanga]

Hi Chathura,
You can access OSGi services from CC. I am not sure if this has changed
very recently. Unless you can do it as follows.

 service=()
SuperTenantCarbonContext.getCurrentContext().getOSGiService(.class);


On Fri, Mar 7, 2014 at 10:36 AM, Chathura Ekanayake wrote:

>
> Hi Sagara,
>
> If we deploy it as a web application, is there a way to access OSGi
> services within it?
> As we don't package it as a bundle, a BundleContext object is not
> available for the webapp, so it is not possible get references to OSGi
> services. Is there a way to deploy a webapp as a bundle?
>
> Regards,
> Chathura
>
>
>
> On Thu, Mar 6, 2014 at 1:49 PM, Sagara Gunathunga  wrote:
>
>>
>>
>>
>> On Thu, Mar 6, 2014 at 12:15 PM, Chathura Ekanayake wrote:
>>
>>>
>>> Hi All,
>>>
>>> Activiti has a Restlet based comprehensive REST API to expose all BPMN
>>> related functions. As we are planning to have a REST API for BPMN, we can
>>> integrate this Activiti REST module in Carbon. Could I get feedback on the
>>> following items regarding this integration:
>>>
>>> Restlet vs JAX-RS:
>>> Should we integrate the Restlet based Activiti API or should we write a
>>> new JAX-RS based REST module? I think it is better to use the Activiti REST
>>> module as it allows us to migrate easily with new Activiti versions.
>>>
>>
>> IMHO if Activiti REST module can cater all of our BPMN requirements then
>> rewriting is not required at least at this point.
>>
>>
>>>
>>> Integrating the Activiti Restlet based API:
>>> If we decide to integrate the Activiti REST module, we have to expose
>>> the Restlet servlet to handle REST requests. One option is to register this
>>> servlet in repository/conf/tomcat/web.xml, which exposes this on the same
>>> port as admin services. However, we have to keep these servlet registration
>>> entries in the web.xml, even though the BPMN component is not deployed.
>>> Another option is to start a separate server (if this is possible in
>>> Carbon) for Activiti REST and register the Restlet servlet in that server.
>>>
>>
>> Can't we just deploy above module as a web application with own context
>> path as mention in this post[1] ?  If you look at OAuth endpoint in IS/APIM
>> we used this approach additionally some of future AS integration will use
>> this approach.
>>
>> [1] -
>> http://bpmn20inaction.blogspot.com/2013/02/activiti-in-action-updates-part-1.html
>>
>> Thanks !
>>
>>>
>>> Thoughts...
>>>
>>> Regards,
>>> Chathura
>>>
>>>
>>>
>>
>>
>> --
>> Sagara Gunathunga
>>
>> Senior Technical Lead; WSO2, Inc.;  http://wso2.com
>> V.P Apache Web Services;http://ws.apache.org/
>> Linkedin; http://www.linkedin.com/in/ssagara
>> Blog ;  http://ssagara.blogspot.com
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks
/subash

*Subash Chaturanga*
Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com

email: sub...@wso2.com
blog:  http://subashsdm.blogspot.com/
twitter: @subash89
phone: +9477 2225922
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Exposing the Activiti REST API

[Chathura Ekanayake]

Hi Sagara,

If we deploy it as a web application, is there a way to access OSGi
services within it?
As we don't package it as a bundle, a BundleContext object is not available
for the webapp, so it is not possible get references to OSGi services. Is
there a way to deploy a webapp as a bundle?

Regards,
Chathura



On Thu, Mar 6, 2014 at 1:49 PM, Sagara Gunathunga  wrote:

>
>
>
> On Thu, Mar 6, 2014 at 12:15 PM, Chathura Ekanayake wrote:
>
>>
>> Hi All,
>>
>> Activiti has a Restlet based comprehensive REST API to expose all BPMN
>> related functions. As we are planning to have a REST API for BPMN, we can
>> integrate this Activiti REST module in Carbon. Could I get feedback on the
>> following items regarding this integration:
>>
>> Restlet vs JAX-RS:
>> Should we integrate the Restlet based Activiti API or should we write a
>> new JAX-RS based REST module? I think it is better to use the Activiti REST
>> module as it allows us to migrate easily with new Activiti versions.
>>
>
> IMHO if Activiti REST module can cater all of our BPMN requirements then
> rewriting is not required at least at this point.
>
>
>>
>> Integrating the Activiti Restlet based API:
>> If we decide to integrate the Activiti REST module, we have to expose the
>> Restlet servlet to handle REST requests. One option is to register this
>> servlet in repository/conf/tomcat/web.xml, which exposes this on the same
>> port as admin services. However, we have to keep these servlet registration
>> entries in the web.xml, even though the BPMN component is not deployed.
>> Another option is to start a separate server (if this is possible in
>> Carbon) for Activiti REST and register the Restlet servlet in that server.
>>
>
> Can't we just deploy above module as a web application with own context
> path as mention in this post[1] ?  If you look at OAuth endpoint in IS/APIM
> we used this approach additionally some of future AS integration will use
> this approach.
>
> [1] -
> http://bpmn20inaction.blogspot.com/2013/02/activiti-in-action-updates-part-1.html
>
> Thanks !
>
>>
>> Thoughts...
>>
>> Regards,
>> Chathura
>>
>>
>>
>
>
> --
> Sagara Gunathunga
>
> Senior Technical Lead; WSO2, Inc.;  http://wso2.com
> V.P Apache Web Services;http://ws.apache.org/
> Linkedin; http://www.linkedin.com/in/ssagara
> Blog ;  http://ssagara.blogspot.com
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] Developer Studio 3.6.0 RC 1 Released!

[Aruna Karunarathna]

Hi all,

I've also experienced the same when using eclipse
eclipse-jee-kepler-SR2-linux-gtk-x86_64 in Ubuntu 13.10. I think this is
something to do with unity.

As Jasintha suggested using GNOME solved the problem.

Regards,


On Fri, Mar 7, 2014 at 10:09 AM, Jasintha Dasanayake wrote:

>  This also can be resolved by using GNOME instead of having unity(this is
> the default shell).
>
> /Jasintha
>
>
> On Fri, Mar 7, 2014 at 9:34 AM, Daya Attapattu  wrote:
>
>> I encountered this bug when running eclipse on Ubuntu 13.10.  It can be
>> fixed though.  I followed the instructions on that stackoverfolw posting.
>> That didn't immediately fix it for me.  I had to set "env UBUNTU_MENUPROXY=0"
>> on ~/.local/share/applications/eclipse.desktop too.
>>
>> - Daya
>>
>>
>>
>> On Fri, Mar 7, 2014 at 9:14 AM, Lahiru Gamage  wrote:
>>
>>> Yeah... That can be the issue. Hopefully in 14.04 it will be fixed.
>>> Anyway we will need to tackle this as some customer can use Ubuntu 13.10.
>>>
>>> Go with older Eclipse? Juno doesn't has this issue.
>>>
>>> Wdyt?
>>>
>>> Thanks.
>>>
>>>
>>> On Thu, Mar 6, 2014 at 7:11 PM, Ramindu Deshapriya 
>>> wrote:
>>>
 Hi Lahiru,

 Are you using Ubuntu 13.10? This is am issue with Eclipse.

 http://stackoverflow.com/questions/19452390/eclipse-menus-dont-show-up-after-upgrading-to-ubuntu-13-10

 Hope this helps.

 On Mar 7, 2014 3:10 AM, "Lahiru Gamage"  wrote:
 >
 > Hi Susinda,
 >
 > I tried Developer studio with Eclipse provided. (Linux 64 bit).
 Cannot get the menu items down. E.g. "Developer Studio" Menu item.
 >
 > Thanks.
 >
 >
 >
 > On Thu, Mar 6, 2014 at 5:52 AM, Susinda Perera 
 wrote:
 >>
 >>
 >> Hi All,
 >>
 >> We have WSO2 Developer Studio 3.6.0 RC 1 ready to be downloaded at
 [1] and installed eclipse distributions available at [2]. This release is
 mainly focused on migrating Developer Studio to Eclipse Kepler. And
 additionally includes following bug fixes, improvements and tasks.
 >>
 >>
 >> Bug Fixes
 >> [TOOLS-1107] - "Show in registry browser" option should be disabled
 for resources that are not in the registry.
 >> [TOOLS-1323] - Mediator palette scrolling is not intuitive
 >> [TOOLS-1472] - Rule Mediator does not deserialize correctly
 >> [TOOLS-1665] - Developer Studio JAX-WS Service Project, project name
 does not update with selection of wsdl file
 >> [TOOLS-1745] - AF login dialog save credintial label cannot see
 completly
 >> [TOOLS-1972] - When add/remove case to switch mediator sizes of
 inner cases get reduced and additional arrow is appear in the input
 connector side
 >> [TOOLS-1973] - when delete and undo a complex mediator - An
 exception occured
 >> [TOOLS-2030] - Cannot create Dynamic Endpoints
 >> [TOOLS-2059] - Three clicks are required to edit the description of
 a mediator
 >> [TOOLS-2189] - Deleting a proxy service either from DevStudio or the
 file system doesn't update pom.xml
 >> [TOOLS-2228] - flow is get lost when delete the drop mediator
 >> [TOOLS-2269] - New Registry Handler Creation Wizard layout is not
 displaying properly
 >> [TOOLS-2292] - Create new registry aspect class wizard fails to
 complete
 >> [TOOLS-2310] - Save pom.xml on Project Import to fix the artifacts
 ordering issue
 >> [TOOLS-2313] - HTTP and Template endpoints get Address endpoint icon
 when drag and drop from Endpoint palette group
 >> [TOOLS-2319] - Template wizard creates a useless WSDL EP when either
 WSDL url, service or port is invalid
 >> [TOOLS-2323] - DBLookup and DBReport have the same icon in tool
 palette
 >> [TOOLS-2325] - All available message stores in the workspace are not
 displaying in the properties view of the Store mediator
 >> [TOOLS-2330] - SQL Statement Configuration window's Parameters and
 Results tables have not aligned properly
 >> [TOOLS-2331] - In Clone Mediator's target configuration dialog, the
 table is non editable
 >> [TOOLS-2332] - In Rule Mediator's fact configuration dialog, the
 table has not aligned properly
 >> [TOOLS-2333] - In Endpoint's properties window, Value and Type
 columns should swap
 >> [TOOLS-2336] - Scheduled task serialization fails when Task
 properties dialog is cancelled
 >> [TOOLS-2338] - Cannot import files from system when creating
 Registry resources when there is no extensions
 >> [TOOLS-2345] - When a custom mediator is created and added in to a
 CApp through dev studio custom mediator is listed last in the
 artifiacts.xml file in CApp
 >> [TOOLS-2346] - services.xml file not get updated when creating a new
 Axis2 Service class
 >> [TOOLS-2347] - Cannot drop a 'Drop' mediator into switch mediator
 case or default branches
 >> [TOOLS-2349] - [ESB] Custom task properties get 

Re: [Dev] [Architecture] Developer Studio 3.6.0 RC 1 Released!

[Jasintha Dasanayake]

 This also can be resolved by using GNOME instead of having unity(this is
the default shell).

/Jasintha


On Fri, Mar 7, 2014 at 9:34 AM, Daya Attapattu  wrote:

> I encountered this bug when running eclipse on Ubuntu 13.10.  It can be
> fixed though.  I followed the instructions on that stackoverfolw posting.
> That didn't immediately fix it for me.  I had to set "env UBUNTU_MENUPROXY=0"
> on ~/.local/share/applications/eclipse.desktop too.
>
> - Daya
>
>
>
> On Fri, Mar 7, 2014 at 9:14 AM, Lahiru Gamage  wrote:
>
>> Yeah... That can be the issue. Hopefully in 14.04 it will be fixed.
>> Anyway we will need to tackle this as some customer can use Ubuntu 13.10.
>>
>> Go with older Eclipse? Juno doesn't has this issue.
>>
>> Wdyt?
>>
>> Thanks.
>>
>>
>> On Thu, Mar 6, 2014 at 7:11 PM, Ramindu Deshapriya wrote:
>>
>>> Hi Lahiru,
>>>
>>> Are you using Ubuntu 13.10? This is am issue with Eclipse.
>>>
>>> http://stackoverflow.com/questions/19452390/eclipse-menus-dont-show-up-after-upgrading-to-ubuntu-13-10
>>>
>>> Hope this helps.
>>>
>>> On Mar 7, 2014 3:10 AM, "Lahiru Gamage"  wrote:
>>> >
>>> > Hi Susinda,
>>> >
>>> > I tried Developer studio with Eclipse provided. (Linux 64 bit). Cannot
>>> get the menu items down. E.g. "Developer Studio" Menu item.
>>> >
>>> > Thanks.
>>> >
>>> >
>>> >
>>> > On Thu, Mar 6, 2014 at 5:52 AM, Susinda Perera 
>>> wrote:
>>> >>
>>> >>
>>> >> Hi All,
>>> >>
>>> >> We have WSO2 Developer Studio 3.6.0 RC 1 ready to be downloaded at
>>> [1] and installed eclipse distributions available at [2]. This release is
>>> mainly focused on migrating Developer Studio to Eclipse Kepler. And
>>> additionally includes following bug fixes, improvements and tasks.
>>> >>
>>> >>
>>> >> Bug Fixes
>>> >> [TOOLS-1107] - "Show in registry browser" option should be disabled
>>> for resources that are not in the registry.
>>> >> [TOOLS-1323] - Mediator palette scrolling is not intuitive
>>> >> [TOOLS-1472] - Rule Mediator does not deserialize correctly
>>> >> [TOOLS-1665] - Developer Studio JAX-WS Service Project, project name
>>> does not update with selection of wsdl file
>>> >> [TOOLS-1745] - AF login dialog save credintial label cannot see
>>> completly
>>> >> [TOOLS-1972] - When add/remove case to switch mediator sizes of inner
>>> cases get reduced and additional arrow is appear in the input connector side
>>> >> [TOOLS-1973] - when delete and undo a complex mediator - An exception
>>> occured
>>> >> [TOOLS-2030] - Cannot create Dynamic Endpoints
>>> >> [TOOLS-2059] - Three clicks are required to edit the description of a
>>> mediator
>>> >> [TOOLS-2189] - Deleting a proxy service either from DevStudio or the
>>> file system doesn't update pom.xml
>>> >> [TOOLS-2228] - flow is get lost when delete the drop mediator
>>> >> [TOOLS-2269] - New Registry Handler Creation Wizard layout is not
>>> displaying properly
>>> >> [TOOLS-2292] - Create new registry aspect class wizard fails to
>>> complete
>>> >> [TOOLS-2310] - Save pom.xml on Project Import to fix the artifacts
>>> ordering issue
>>> >> [TOOLS-2313] - HTTP and Template endpoints get Address endpoint icon
>>> when drag and drop from Endpoint palette group
>>> >> [TOOLS-2319] - Template wizard creates a useless WSDL EP when either
>>> WSDL url, service or port is invalid
>>> >> [TOOLS-2323] - DBLookup and DBReport have the same icon in tool
>>> palette
>>> >> [TOOLS-2325] - All available message stores in the workspace are not
>>> displaying in the properties view of the Store mediator
>>> >> [TOOLS-2330] - SQL Statement Configuration window's Parameters and
>>> Results tables have not aligned properly
>>> >> [TOOLS-2331] - In Clone Mediator's target configuration dialog, the
>>> table is non editable
>>> >> [TOOLS-2332] - In Rule Mediator's fact configuration dialog, the
>>> table has not aligned properly
>>> >> [TOOLS-2333] - In Endpoint's properties window, Value and Type
>>> columns should swap
>>> >> [TOOLS-2336] - Scheduled task serialization fails when Task
>>> properties dialog is cancelled
>>> >> [TOOLS-2338] - Cannot import files from system when creating Registry
>>> resources when there is no extensions
>>> >> [TOOLS-2345] - When a custom mediator is created and added in to a
>>> CApp through dev studio custom mediator is listed last in the
>>> artifiacts.xml file in CApp
>>> >> [TOOLS-2346] - services.xml file not get updated when creating a new
>>> Axis2 Service class
>>> >> [TOOLS-2347] - Cannot drop a 'Drop' mediator into switch mediator
>>> case or default branches
>>> >> [TOOLS-2349] - [ESB] Custom task properties get serialized for empty
>>> property names and values too
>>> >> [TOOLS-2350] - Some Mediators and Endpoints are not in the
>>> alphabetical order in the tool pallet
>>> >> [TOOLS-2355] - It is allowing to add Respond and Loopback Mediators
>>> inside a mediator when they are already present in the mediator flow
>>> >> [TOOLS-2356] - It is allowing to add Respond and Loopback Mediators
>>> in the middle of the mediat

Re: [Dev] [Architecture] Developer Studio 3.6.0 RC 1 Released!

[Daya Attapattu]

I encountered this bug when running eclipse on Ubuntu 13.10.  It can be
fixed though.  I followed the instructions on that stackoverfolw posting.
That didn't immediately fix it for me.  I had to set "env UBUNTU_MENUPROXY=0"
on ~/.local/share/applications/eclipse.desktop too.

- Daya



On Fri, Mar 7, 2014 at 9:14 AM, Lahiru Gamage  wrote:

> Yeah... That can be the issue. Hopefully in 14.04 it will be fixed. Anyway
> we will need to tackle this as some customer can use Ubuntu 13.10.
>
> Go with older Eclipse? Juno doesn't has this issue.
>
> Wdyt?
>
> Thanks.
>
>
> On Thu, Mar 6, 2014 at 7:11 PM, Ramindu Deshapriya wrote:
>
>> Hi Lahiru,
>>
>> Are you using Ubuntu 13.10? This is am issue with Eclipse.
>>
>> http://stackoverflow.com/questions/19452390/eclipse-menus-dont-show-up-after-upgrading-to-ubuntu-13-10
>>
>> Hope this helps.
>>
>> On Mar 7, 2014 3:10 AM, "Lahiru Gamage"  wrote:
>> >
>> > Hi Susinda,
>> >
>> > I tried Developer studio with Eclipse provided. (Linux 64 bit). Cannot
>> get the menu items down. E.g. "Developer Studio" Menu item.
>> >
>> > Thanks.
>> >
>> >
>> >
>> > On Thu, Mar 6, 2014 at 5:52 AM, Susinda Perera 
>> wrote:
>> >>
>> >>
>> >> Hi All,
>> >>
>> >> We have WSO2 Developer Studio 3.6.0 RC 1 ready to be downloaded at [1]
>> and installed eclipse distributions available at [2]. This release is
>> mainly focused on migrating Developer Studio to Eclipse Kepler. And
>> additionally includes following bug fixes, improvements and tasks.
>> >>
>> >>
>> >> Bug Fixes
>> >> [TOOLS-1107] - "Show in registry browser" option should be disabled
>> for resources that are not in the registry.
>> >> [TOOLS-1323] - Mediator palette scrolling is not intuitive
>> >> [TOOLS-1472] - Rule Mediator does not deserialize correctly
>> >> [TOOLS-1665] - Developer Studio JAX-WS Service Project, project name
>> does not update with selection of wsdl file
>> >> [TOOLS-1745] - AF login dialog save credintial label cannot see
>> completly
>> >> [TOOLS-1972] - When add/remove case to switch mediator sizes of inner
>> cases get reduced and additional arrow is appear in the input connector side
>> >> [TOOLS-1973] - when delete and undo a complex mediator - An exception
>> occured
>> >> [TOOLS-2030] - Cannot create Dynamic Endpoints
>> >> [TOOLS-2059] - Three clicks are required to edit the description of a
>> mediator
>> >> [TOOLS-2189] - Deleting a proxy service either from DevStudio or the
>> file system doesn't update pom.xml
>> >> [TOOLS-2228] - flow is get lost when delete the drop mediator
>> >> [TOOLS-2269] - New Registry Handler Creation Wizard layout is not
>> displaying properly
>> >> [TOOLS-2292] - Create new registry aspect class wizard fails to
>> complete
>> >> [TOOLS-2310] - Save pom.xml on Project Import to fix the artifacts
>> ordering issue
>> >> [TOOLS-2313] - HTTP and Template endpoints get Address endpoint icon
>> when drag and drop from Endpoint palette group
>> >> [TOOLS-2319] - Template wizard creates a useless WSDL EP when either
>> WSDL url, service or port is invalid
>> >> [TOOLS-2323] - DBLookup and DBReport have the same icon in tool palette
>> >> [TOOLS-2325] - All available message stores in the workspace are not
>> displaying in the properties view of the Store mediator
>> >> [TOOLS-2330] - SQL Statement Configuration window's Parameters and
>> Results tables have not aligned properly
>> >> [TOOLS-2331] - In Clone Mediator's target configuration dialog, the
>> table is non editable
>> >> [TOOLS-2332] - In Rule Mediator's fact configuration dialog, the table
>> has not aligned properly
>> >> [TOOLS-2333] - In Endpoint's properties window, Value and Type columns
>> should swap
>> >> [TOOLS-2336] - Scheduled task serialization fails when Task properties
>> dialog is cancelled
>> >> [TOOLS-2338] - Cannot import files from system when creating Registry
>> resources when there is no extensions
>> >> [TOOLS-2345] - When a custom mediator is created and added in to a
>> CApp through dev studio custom mediator is listed last in the
>> artifiacts.xml file in CApp
>> >> [TOOLS-2346] - services.xml file not get updated when creating a new
>> Axis2 Service class
>> >> [TOOLS-2347] - Cannot drop a 'Drop' mediator into switch mediator case
>> or default branches
>> >> [TOOLS-2349] - [ESB] Custom task properties get serialized for empty
>> property names and values too
>> >> [TOOLS-2350] - Some Mediators and Endpoints are not in the
>> alphabetical order in the tool pallet
>> >> [TOOLS-2355] - It is allowing to add Respond and Loopback Mediators
>> inside a mediator when they are already present in the mediator flow
>> >> [TOOLS-2356] - It is allowing to add Respond and Loopback Mediators in
>> the middle of the mediator flow
>> >> [TOOLS-2357] - Maven-Car-Depoy-Plugin is unable to undeploy CAR files
>> with Maven
>> >> [TOOLS-2358] - Icon should change in the warning messages of ESB
>> Graphical Editor
>> >> [TOOLS-2367] - Maven Build profile properties updated in only endpoint
>> artifact but not 

Re: [Dev] [Architecture] Developer Studio 3.6.0 RC 1 Released!

[Isuru Perera]

Hi,


On Fri, Mar 7, 2014 at 9:14 AM, Lahiru Gamage  wrote:

> Yeah... That can be the issue. Hopefully in 14.04 it will be fixed. Anyway
> we will need to tackle this as some customer can use Ubuntu 13.10.
>
Yes. It will be fixed as Ubuntu 14.04 will drop support for global menus in
Unity.

>
> Go with older Eclipse? Juno doesn't has this issue.
>
There is a workaround for that issue. So, no need to go for an older
version.

>
> Wdyt?
>
> Thanks.
>
>
> On Thu, Mar 6, 2014 at 7:11 PM, Ramindu Deshapriya wrote:
>
>> Hi Lahiru,
>>
>> Are you using Ubuntu 13.10? This is am issue with Eclipse.
>>
>> http://stackoverflow.com/questions/19452390/eclipse-menus-dont-show-up-after-upgrading-to-ubuntu-13-10
>>
>> Hope this helps.
>>
>> On Mar 7, 2014 3:10 AM, "Lahiru Gamage"  wrote:
>> >
>> > Hi Susinda,
>> >
>> > I tried Developer studio with Eclipse provided. (Linux 64 bit). Cannot
>> get the menu items down. E.g. "Developer Studio" Menu item.
>> >
>> > Thanks.
>> >
>> >
>> >
>> > On Thu, Mar 6, 2014 at 5:52 AM, Susinda Perera 
>> wrote:
>> >>
>> >>
>> >> Hi All,
>> >>
>> >> We have WSO2 Developer Studio 3.6.0 RC 1 ready to be downloaded at [1]
>> and installed eclipse distributions available at [2]. This release is
>> mainly focused on migrating Developer Studio to Eclipse Kepler. And
>> additionally includes following bug fixes, improvements and tasks.
>> >>
>> >>
>> >> Bug Fixes
>> >> [TOOLS-1107] - "Show in registry browser" option should be disabled
>> for resources that are not in the registry.
>> >> [TOOLS-1323] - Mediator palette scrolling is not intuitive
>> >> [TOOLS-1472] - Rule Mediator does not deserialize correctly
>> >> [TOOLS-1665] - Developer Studio JAX-WS Service Project, project name
>> does not update with selection of wsdl file
>> >> [TOOLS-1745] - AF login dialog save credintial label cannot see
>> completly
>> >> [TOOLS-1972] - When add/remove case to switch mediator sizes of inner
>> cases get reduced and additional arrow is appear in the input connector side
>> >> [TOOLS-1973] - when delete and undo a complex mediator - An exception
>> occured
>> >> [TOOLS-2030] - Cannot create Dynamic Endpoints
>> >> [TOOLS-2059] - Three clicks are required to edit the description of a
>> mediator
>> >> [TOOLS-2189] - Deleting a proxy service either from DevStudio or the
>> file system doesn't update pom.xml
>> >> [TOOLS-2228] - flow is get lost when delete the drop mediator
>> >> [TOOLS-2269] - New Registry Handler Creation Wizard layout is not
>> displaying properly
>> >> [TOOLS-2292] - Create new registry aspect class wizard fails to
>> complete
>> >> [TOOLS-2310] - Save pom.xml on Project Import to fix the artifacts
>> ordering issue
>> >> [TOOLS-2313] - HTTP and Template endpoints get Address endpoint icon
>> when drag and drop from Endpoint palette group
>> >> [TOOLS-2319] - Template wizard creates a useless WSDL EP when either
>> WSDL url, service or port is invalid
>> >> [TOOLS-2323] - DBLookup and DBReport have the same icon in tool palette
>> >> [TOOLS-2325] - All available message stores in the workspace are not
>> displaying in the properties view of the Store mediator
>> >> [TOOLS-2330] - SQL Statement Configuration window's Parameters and
>> Results tables have not aligned properly
>> >> [TOOLS-2331] - In Clone Mediator's target configuration dialog, the
>> table is non editable
>> >> [TOOLS-2332] - In Rule Mediator's fact configuration dialog, the table
>> has not aligned properly
>> >> [TOOLS-2333] - In Endpoint's properties window, Value and Type columns
>> should swap
>> >> [TOOLS-2336] - Scheduled task serialization fails when Task properties
>> dialog is cancelled
>> >> [TOOLS-2338] - Cannot import files from system when creating Registry
>> resources when there is no extensions
>> >> [TOOLS-2345] - When a custom mediator is created and added in to a
>> CApp through dev studio custom mediator is listed last in the
>> artifiacts.xml file in CApp
>> >> [TOOLS-2346] - services.xml file not get updated when creating a new
>> Axis2 Service class
>> >> [TOOLS-2347] - Cannot drop a 'Drop' mediator into switch mediator case
>> or default branches
>> >> [TOOLS-2349] - [ESB] Custom task properties get serialized for empty
>> property names and values too
>> >> [TOOLS-2350] - Some Mediators and Endpoints are not in the
>> alphabetical order in the tool pallet
>> >> [TOOLS-2355] - It is allowing to add Respond and Loopback Mediators
>> inside a mediator when they are already present in the mediator flow
>> >> [TOOLS-2356] - It is allowing to add Respond and Loopback Mediators in
>> the middle of the mediator flow
>> >> [TOOLS-2357] - Maven-Car-Depoy-Plugin is unable to undeploy CAR files
>> with Maven
>> >> [TOOLS-2358] - Icon should change in the warning messages of ESB
>> Graphical Editor
>> >> [TOOLS-2367] - Maven Build profile properties updated in only endpoint
>> artifact but not all
>> >> Improvements
>> >> [TOOLS-1422] - Support both Dynamic Endpoints and Service URIs in
>> Callout mediator

Re: [Dev] [Architecture] Developer Studio 3.6.0 RC 1 Released!

[Lahiru Gamage]

Yeah... That can be the issue. Hopefully in 14.04 it will be fixed. Anyway
we will need to tackle this as some customer can use Ubuntu 13.10.

Go with older Eclipse? Juno doesn't has this issue.

Wdyt?

Thanks.


On Thu, Mar 6, 2014 at 7:11 PM, Ramindu Deshapriya wrote:

> Hi Lahiru,
>
> Are you using Ubuntu 13.10? This is am issue with Eclipse.
>
> http://stackoverflow.com/questions/19452390/eclipse-menus-dont-show-up-after-upgrading-to-ubuntu-13-10
>
> Hope this helps.
>
> On Mar 7, 2014 3:10 AM, "Lahiru Gamage"  wrote:
> >
> > Hi Susinda,
> >
> > I tried Developer studio with Eclipse provided. (Linux 64 bit). Cannot
> get the menu items down. E.g. "Developer Studio" Menu item.
> >
> > Thanks.
> >
> >
> >
> > On Thu, Mar 6, 2014 at 5:52 AM, Susinda Perera  wrote:
> >>
> >>
> >> Hi All,
> >>
> >> We have WSO2 Developer Studio 3.6.0 RC 1 ready to be downloaded at [1]
> and installed eclipse distributions available at [2]. This release is
> mainly focused on migrating Developer Studio to Eclipse Kepler. And
> additionally includes following bug fixes, improvements and tasks.
> >>
> >>
> >> Bug Fixes
> >> [TOOLS-1107] - "Show in registry browser" option should be disabled for
> resources that are not in the registry.
> >> [TOOLS-1323] - Mediator palette scrolling is not intuitive
> >> [TOOLS-1472] - Rule Mediator does not deserialize correctly
> >> [TOOLS-1665] - Developer Studio JAX-WS Service Project, project name
> does not update with selection of wsdl file
> >> [TOOLS-1745] - AF login dialog save credintial label cannot see
> completly
> >> [TOOLS-1972] - When add/remove case to switch mediator sizes of inner
> cases get reduced and additional arrow is appear in the input connector side
> >> [TOOLS-1973] - when delete and undo a complex mediator - An exception
> occured
> >> [TOOLS-2030] - Cannot create Dynamic Endpoints
> >> [TOOLS-2059] - Three clicks are required to edit the description of a
> mediator
> >> [TOOLS-2189] - Deleting a proxy service either from DevStudio or the
> file system doesn't update pom.xml
> >> [TOOLS-2228] - flow is get lost when delete the drop mediator
> >> [TOOLS-2269] - New Registry Handler Creation Wizard layout is not
> displaying properly
> >> [TOOLS-2292] - Create new registry aspect class wizard fails to complete
> >> [TOOLS-2310] - Save pom.xml on Project Import to fix the artifacts
> ordering issue
> >> [TOOLS-2313] - HTTP and Template endpoints get Address endpoint icon
> when drag and drop from Endpoint palette group
> >> [TOOLS-2319] - Template wizard creates a useless WSDL EP when either
> WSDL url, service or port is invalid
> >> [TOOLS-2323] - DBLookup and DBReport have the same icon in tool palette
> >> [TOOLS-2325] - All available message stores in the workspace are not
> displaying in the properties view of the Store mediator
> >> [TOOLS-2330] - SQL Statement Configuration window's Parameters and
> Results tables have not aligned properly
> >> [TOOLS-2331] - In Clone Mediator's target configuration dialog, the
> table is non editable
> >> [TOOLS-2332] - In Rule Mediator's fact configuration dialog, the table
> has not aligned properly
> >> [TOOLS-2333] - In Endpoint's properties window, Value and Type columns
> should swap
> >> [TOOLS-2336] - Scheduled task serialization fails when Task properties
> dialog is cancelled
> >> [TOOLS-2338] - Cannot import files from system when creating Registry
> resources when there is no extensions
> >> [TOOLS-2345] - When a custom mediator is created and added in to a CApp
> through dev studio custom mediator is listed last in the artifiacts.xml
> file in CApp
> >> [TOOLS-2346] - services.xml file not get updated when creating a new
> Axis2 Service class
> >> [TOOLS-2347] - Cannot drop a 'Drop' mediator into switch mediator case
> or default branches
> >> [TOOLS-2349] - [ESB] Custom task properties get serialized for empty
> property names and values too
> >> [TOOLS-2350] - Some Mediators and Endpoints are not in the alphabetical
> order in the tool pallet
> >> [TOOLS-2355] - It is allowing to add Respond and Loopback Mediators
> inside a mediator when they are already present in the mediator flow
> >> [TOOLS-2356] - It is allowing to add Respond and Loopback Mediators in
> the middle of the mediator flow
> >> [TOOLS-2357] - Maven-Car-Depoy-Plugin is unable to undeploy CAR files
> with Maven
> >> [TOOLS-2358] - Icon should change in the warning messages of ESB
> Graphical Editor
> >> [TOOLS-2367] - Maven Build profile properties updated in only endpoint
> artifact but not all
> >> Improvements
> >> [TOOLS-1422] - Support both Dynamic Endpoints and Service URIs in
> Callout mediator
> >> [TOOLS-1689] - Usability improvements in the Property fields for ESB
> Graphical Editor
> >> [TOOLS-2277] - Do not allow to add mediators after Respond or Loopback
> mediator
> >> [TOOLS-2326] - In the CallTemplate mediator's properties window,
> Value/Expression and Parameter Type columns should swap
> >> [TOOLS-2353] - Provide a mechanism 

[Dev] The location of the latest released source about wso2 product.

[stevegyc]

Hi 

Recently I am trying to build the latest released version of DSS, BPS, ESB, 
BRS, 
I check out source from the location 
"https://svn.wso2.org/repos/wso2/carbon/platform/tags/turing-chunk07/";.

Question 1: 
Is it the location of latest released source of wso2?

Question 2:
 What is the different between the soucrce in 
"https://svn.wso2.org/repos/wso2/carbon/platform/tags/";, 
"https://svn.wso2.org/repos/wso2/carbon/platform/branches/"; and 
"https://svn.wso2.org/repos/wso2/carbon/platform/trunk/";?

Question 3:
 I noticed that BRS is still on the base of carbon 4.0.3, I want to know when 
it will be updated to base on 4.2.0?

Question 4: 
If I need to only build DSS, BPS, ESB, BRS at one time, what is the best method 
to do it?

Question 5: 
BRS2.0.0 is compatible with the other 3 products(DSS 3.1.1, BPS 3.2.0, ESB 
4.8.1)?

I have also posted this title to 
http://stackoverflow.com/questions/22240187/the-location-of-the-latest-released-source-about-wso2-product
 .





stevegyc___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] Developer Studio 3.6.0 RC 1 Released!

[Isuru Perera]

Hi,

On Fri, Mar 7, 2014 at 3:08 AM, Lahiru Gamage  wrote:

> Hi Susinda,
>
> I tried Developer studio with Eclipse provided. (Linux 64 bit). Cannot get
> the menu items down. E.g. "Developer Studio" Menu item.
>
If you are using a newer Ubuntu and all menus behaves the same way,
following can be the issue.

http://stackoverflow.com/questions/19452390/eclipse-menus-dont-show-up-after-upgrading-to-ubuntu-13-10

>
> Thanks.
>
>
>
> On Thu, Mar 6, 2014 at 5:52 AM, Susinda Perera  wrote:
>
>>
>> Hi All,
>>
>> We have WSO2 Developer Studio 3.6.0 RC 1 ready to be downloaded at [1]
>> and installed eclipse distributions available at [2]. This release is
>> mainly focused on migrating Developer Studio to Eclipse Kepler. And
>> additionally includes following bug fixes, improvements and tasks.
>>
>>
>> Bug Fixes
>>
>>- [TOOLS-1107 ] - "Show in
>>registry browser" option should be disabled for resources that are not in
>>the registry.
>>- [TOOLS-1323 ] - Mediator
>>palette scrolling is not intuitive
>>- [TOOLS-1472 ] - Rule
>>Mediator does not deserialize correctly
>>- [TOOLS-1665 ] - Developer
>>Studio JAX-WS Service Project, project name does not update with selection
>>of wsdl file
>>- [TOOLS-1745 ] - AF login
>>dialog save credintial label cannot see completly
>>- [TOOLS-1972 ] - When
>>add/remove case to switch mediator sizes of inner cases get reduced and
>>additional arrow is appear in the input connector side
>>- [TOOLS-1973 ] - when
>>delete and undo a complex mediator - An exception occured
>>- [TOOLS-2030 ] - Cannot
>>create Dynamic Endpoints
>>- [TOOLS-2059 ] - Three
>>clicks are required to edit the description of a mediator
>>- [TOOLS-2189 ] - Deleting a
>>proxy service either from DevStudio or the file system doesn't update
>>pom.xml
>>- [TOOLS-2228 ] - flow is
>>get lost when delete the drop mediator
>>- [TOOLS-2269 ] - New
>>Registry Handler Creation Wizard layout is not displaying properly
>>- [TOOLS-2292 ] - Create new
>>registry aspect class wizard fails to complete
>>- [TOOLS-2310 ] - Save
>>pom.xml on Project Import to fix the artifacts ordering issue
>>- [TOOLS-2313 ] - HTTP and
>>Template endpoints get Address endpoint icon when drag and drop from
>>Endpoint palette group
>>- [TOOLS-2319 ] - Template
>>wizard creates a useless WSDL EP when either WSDL url, service or port is
>>invalid
>>- [TOOLS-2323 ] - DBLookup
>>and DBReport have the same icon in tool palette
>>- [TOOLS-2325 ] - All
>>available message stores in the workspace are not displaying in the
>>properties view of the Store mediator
>>- [TOOLS-2330 ] - SQL
>>Statement Configuration window's Parameters and Results tables have not
>>aligned properly
>>- [TOOLS-2331 ] - In Clone
>>Mediator's target configuration dialog, the table is non editable
>>- [TOOLS-2332 ] - In Rule
>>Mediator's fact configuration dialog, the table has not aligned properly
>>- [TOOLS-2333 ] - In
>>Endpoint's properties window, Value and Type columns should swap
>>- [TOOLS-2336 ] - Scheduled
>>task serialization fails when Task properties dialog is cancelled
>>- [TOOLS-2338 ] - Cannot
>>import files from system when creating Registry resources when there is no
>>extensions
>>- [TOOLS-2345 ] - When a
>>custom mediator is created and added in to a CApp through dev studio 
>> custom
>>mediator is listed last in the artifiacts.xml file in CApp
>>- [TOOLS-2346 ] -
>>services.xml file not get updated when creating a new Axis2 Service class
>>- [TOOLS-2347 ] - Cannot
>>drop a 'Drop' mediator into switch mediator case or default branches
>>- [TOOLS-2349 ] - [ESB]
>>Custom task properti

Re: [Dev] [Architecture] Developer Studio 3.6.0 RC 1 Released!

[Ramindu Deshapriya]

Hi Lahiru,

Are you using Ubuntu 13.10? This is am issue with Eclipse.
http://stackoverflow.com/questions/19452390/eclipse-menus-dont-show-up-after-upgrading-to-ubuntu-13-10

Hope this helps.

On Mar 7, 2014 3:10 AM, "Lahiru Gamage"  wrote:
>
> Hi Susinda,
>
> I tried Developer studio with Eclipse provided. (Linux 64 bit). Cannot
get the menu items down. E.g. "Developer Studio" Menu item.
>
> Thanks.
>
>
>
> On Thu, Mar 6, 2014 at 5:52 AM, Susinda Perera  wrote:
>>
>>
>> Hi All,
>>
>> We have WSO2 Developer Studio 3.6.0 RC 1 ready to be downloaded at [1]
and installed eclipse distributions available at [2]. This release is
mainly focused on migrating Developer Studio to Eclipse Kepler. And
additionally includes following bug fixes, improvements and tasks.
>>
>>
>> Bug Fixes
>> [TOOLS-1107] - "Show in registry browser" option should be disabled for
resources that are not in the registry.
>> [TOOLS-1323] - Mediator palette scrolling is not intuitive
>> [TOOLS-1472] - Rule Mediator does not deserialize correctly
>> [TOOLS-1665] - Developer Studio JAX-WS Service Project, project name
does not update with selection of wsdl file
>> [TOOLS-1745] - AF login dialog save credintial label cannot see completly
>> [TOOLS-1972] - When add/remove case to switch mediator sizes of inner
cases get reduced and additional arrow is appear in the input connector side
>> [TOOLS-1973] - when delete and undo a complex mediator - An exception
occured
>> [TOOLS-2030] - Cannot create Dynamic Endpoints
>> [TOOLS-2059] - Three clicks are required to edit the description of a
mediator
>> [TOOLS-2189] - Deleting a proxy service either from DevStudio or the
file system doesn't update pom.xml
>> [TOOLS-2228] - flow is get lost when delete the drop mediator
>> [TOOLS-2269] - New Registry Handler Creation Wizard layout is not
displaying properly
>> [TOOLS-2292] - Create new registry aspect class wizard fails to complete
>> [TOOLS-2310] - Save pom.xml on Project Import to fix the artifacts
ordering issue
>> [TOOLS-2313] - HTTP and Template endpoints get Address endpoint icon
when drag and drop from Endpoint palette group
>> [TOOLS-2319] - Template wizard creates a useless WSDL EP when either
WSDL url, service or port is invalid
>> [TOOLS-2323] - DBLookup and DBReport have the same icon in tool palette
>> [TOOLS-2325] - All available message stores in the workspace are not
displaying in the properties view of the Store mediator
>> [TOOLS-2330] - SQL Statement Configuration window's Parameters and
Results tables have not aligned properly
>> [TOOLS-2331] - In Clone Mediator's target configuration dialog, the
table is non editable
>> [TOOLS-2332] - In Rule Mediator's fact configuration dialog, the table
has not aligned properly
>> [TOOLS-2333] - In Endpoint's properties window, Value and Type columns
should swap
>> [TOOLS-2336] - Scheduled task serialization fails when Task properties
dialog is cancelled
>> [TOOLS-2338] - Cannot import files from system when creating Registry
resources when there is no extensions
>> [TOOLS-2345] - When a custom mediator is created and added in to a CApp
through dev studio custom mediator is listed last in the artifiacts.xml
file in CApp
>> [TOOLS-2346] - services.xml file not get updated when creating a new
Axis2 Service class
>> [TOOLS-2347] - Cannot drop a 'Drop' mediator into switch mediator case
or default branches
>> [TOOLS-2349] - [ESB] Custom task properties get serialized for empty
property names and values too
>> [TOOLS-2350] - Some Mediators and Endpoints are not in the alphabetical
order in the tool pallet
>> [TOOLS-2355] - It is allowing to add Respond and Loopback Mediators
inside a mediator when they are already present in the mediator flow
>> [TOOLS-2356] - It is allowing to add Respond and Loopback Mediators in
the middle of the mediator flow
>> [TOOLS-2357] - Maven-Car-Depoy-Plugin is unable to undeploy CAR files
with Maven
>> [TOOLS-2358] - Icon should change in the warning messages of ESB
Graphical Editor
>> [TOOLS-2367] - Maven Build profile properties updated in only endpoint
artifact but not all
>> Improvements
>> [TOOLS-1422] - Support both Dynamic Endpoints and Service URIs in
Callout mediator
>> [TOOLS-1689] - Usability improvements in the Property fields for ESB
Graphical Editor
>> [TOOLS-2277] - Do not allow to add mediators after Respond or Loopback
mediator
>> [TOOLS-2326] - In the CallTemplate mediator's properties window,
Value/Expression and Parameter Type columns should swap
>> [TOOLS-2353] - Provide a mechanism to define a custom GroupId and a
version to be used across all artifacts
>> [TOOLS-2359] - Provide an option to upgrade maven plugin versions when
migrating projects between different Developer Studio versions
>> Task
>> [TOOLS-2335] - Increase the priority of Mediator Project (Class
Mediator) in Capp artifact ordering
>>
>>
>>
>> Your feedback is most welcome. Please report issues at [3] and specify
the affect version as 3.6.0 RC1.
>>
>>
>> [1] -
http://builder1.us1.wso2.

Re: [Dev] Developer Studio 3.6.0 RC 1 Released!

[Lahiru Gamage]

Hi Susinda,

I tried Developer studio with Eclipse provided. (Linux 64 bit). Cannot get
the menu items down. E.g. "Developer Studio" Menu item.

Thanks.



On Thu, Mar 6, 2014 at 5:52 AM, Susinda Perera  wrote:

>
> Hi All,
>
> We have WSO2 Developer Studio 3.6.0 RC 1 ready to be downloaded at [1] and
> installed eclipse distributions available at [2]. This release is mainly
> focused on migrating Developer Studio to Eclipse Kepler. And additionally 
> includes
> following bug fixes, improvements and tasks.
>
>
> Bug Fixes
>
>- [TOOLS-1107 ] - "Show in
>registry browser" option should be disabled for resources that are not in
>the registry.
>- [TOOLS-1323 ] - Mediator
>palette scrolling is not intuitive
>- [TOOLS-1472 ] - Rule
>Mediator does not deserialize correctly
>- [TOOLS-1665 ] - Developer
>Studio JAX-WS Service Project, project name does not update with selection
>of wsdl file
>- [TOOLS-1745 ] - AF login
>dialog save credintial label cannot see completly
>- [TOOLS-1972 ] - When
>add/remove case to switch mediator sizes of inner cases get reduced and
>additional arrow is appear in the input connector side
>- [TOOLS-1973 ] - when delete
>and undo a complex mediator - An exception occured
>- [TOOLS-2030 ] - Cannot
>create Dynamic Endpoints
>- [TOOLS-2059 ] - Three
>clicks are required to edit the description of a mediator
>- [TOOLS-2189 ] - Deleting a
>proxy service either from DevStudio or the file system doesn't update
>pom.xml
>- [TOOLS-2228 ] - flow is get
>lost when delete the drop mediator
>- [TOOLS-2269 ] - New
>Registry Handler Creation Wizard layout is not displaying properly
>- [TOOLS-2292 ] - Create new
>registry aspect class wizard fails to complete
>- [TOOLS-2310 ] - Save
>pom.xml on Project Import to fix the artifacts ordering issue
>- [TOOLS-2313 ] - HTTP and
>Template endpoints get Address endpoint icon when drag and drop from
>Endpoint palette group
>- [TOOLS-2319 ] - Template
>wizard creates a useless WSDL EP when either WSDL url, service or port is
>invalid
>- [TOOLS-2323 ] - DBLookup
>and DBReport have the same icon in tool palette
>- [TOOLS-2325 ] - All
>available message stores in the workspace are not displaying in the
>properties view of the Store mediator
>- [TOOLS-2330 ] - SQL
>Statement Configuration window's Parameters and Results tables have not
>aligned properly
>- [TOOLS-2331 ] - In Clone
>Mediator's target configuration dialog, the table is non editable
>- [TOOLS-2332 ] - In Rule
>Mediator's fact configuration dialog, the table has not aligned properly
>- [TOOLS-2333 ] - In
>Endpoint's properties window, Value and Type columns should swap
>- [TOOLS-2336 ] - Scheduled
>task serialization fails when Task properties dialog is cancelled
>- [TOOLS-2338 ] - Cannot
>import files from system when creating Registry resources when there is no
>extensions
>- [TOOLS-2345 ] - When a
>custom mediator is created and added in to a CApp through dev studio custom
>mediator is listed last in the artifiacts.xml file in CApp
>- [TOOLS-2346 ] -
>services.xml file not get updated when creating a new Axis2 Service class
>- [TOOLS-2347 ] - Cannot drop
>a 'Drop' mediator into switch mediator case or default branches
>- [TOOLS-2349 ] - [ESB]
>Custom task properties get serialized for empty property names and values
>too
>- [TOOLS-2350 ] - Some
>Mediators and Endpoints are not in the alphabetical order in the tool 
> pallet
>- [TOOLS-2355 ] - It is
>allowing to add Respond and Loopback Mediators inside a mediator 

Re: [Dev] IS 4.7.0 Milestone 3 Released!

[Lahiru Gamage]

BTW.

I did not add any Mysql datasource, this is a fresh pack of IS M3.

Thanks.


On Thu, Mar 6, 2014 at 10:17 AM, Lahiru Gamage  wrote:

> Hi Dulanja,
>
> I tried to start M3 in a windows machine. It gave me error at [1].
>
> I did not change any config before running. Should I?
>
> Thanks.
>
> [1]
>
> [2014-03-06 10:14:19,104] ERROR
> {org.wso2.carbon.user.core.util.DatabaseUtil} -  Database Error - Could not
> create connection to database server. Attempted reconnect 3 times.
>  Giving up.
> com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException:
> Could not create connection to database server. Attempted reconnect 3
> times. Giving up.
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
> at com.mysql.jdbc.Util.getInstance(Util.java:386)
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1014)
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:988)
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:974)
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:919)
> at
> com.mysql.jdbc.ConnectionImpl.connectWithRetries(ConnectionImpl.java:2299)
> at
> com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2220)
> at com.mysql.jdbc.ConnectionImpl.(ConnectionImpl.java:813)
> at com.mysql.jdbc.JDBC4Connection.(JDBC4Connection.java:47)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
> at
> com.mysql.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:399)
> at
> com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:334)
> at
> org.apache.tomcat.jdbc.pool.PooledConnection.connectUsingDriver(PooledConnection.java:278)
> at
> org.apache.tomcat.jdbc.pool.PooledConnection.connect(PooledConnection.java:182)
> at
> org.apache.tomcat.jdbc.pool.ConnectionPool.createConnection(ConnectionPool.java:701)
> at
> org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(ConnectionPool.java:635)
> at
> org.apache.tomcat.jdbc.pool.ConnectionPool.getConnection(ConnectionPool.java:188)
> at
> org.apache.tomcat.jdbc.pool.DataSourceProxy.getConnection(DataSourceProxy.java:127)
> at
> org.wso2.carbon.user.core.claim.dao.ClaimDAO.getDialectCount(ClaimDAO.java:158)
> at
> org.wso2.carbon.user.core.common.DefaultRealm.populateProfileAndClaimMaps(DefaultRealm.java:411)
> at
> org.wso2.carbon.user.core.common.DefaultRealm.init(DefaultRealm.java:101)
> at
> org.wso2.carbon.user.core.common.DefaultRealmService.initializeRealm(DefaultRealmService.java:223)
> at
> org.wso2.carbon.user.core.common.DefaultRealmService.(DefaultRealmService.java:101)
> at
> org.wso2.carbon.user.core.common.DefaultRealmService.(DefaultRealmService.java:114)
> at
> org.wso2.carbon.user.core.internal.Activator.startDeploy(Activator.java:69)
> at
> org.wso2.carbon.user.core.internal.BundleCheckActivator.start(BundleCheckActivator.java:61)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
> at
> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:390)
> at
> org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1176)
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559)
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544)
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457)
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)
> at
> 

Re: [Dev] IS 4.7.0 Milestone 3 Released!

[Lahiru Gamage]

Hi Dulanja,

I tried to start M3 in a windows machine. It gave me error at [1].

I did not change any config before running. Should I?

Thanks.

[1]

[2014-03-06 10:14:19,104] ERROR
{org.wso2.carbon.user.core.util.DatabaseUtil} -  Database Error - Could not
create connection to database server. Attempted reconnect 3 times.
 Giving up.
com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Could
not create connection to database server. Attempted reconnect 3 times.
Giving up.
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
at com.mysql.jdbc.Util.getInstance(Util.java:386)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1014)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:988)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:974)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:919)
at
com.mysql.jdbc.ConnectionImpl.connectWithRetries(ConnectionImpl.java:2299)
at
com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2220)
at com.mysql.jdbc.ConnectionImpl.(ConnectionImpl.java:813)
at com.mysql.jdbc.JDBC4Connection.(JDBC4Connection.java:47)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
at
com.mysql.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:399)
at
com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:334)
at
org.apache.tomcat.jdbc.pool.PooledConnection.connectUsingDriver(PooledConnection.java:278)
at
org.apache.tomcat.jdbc.pool.PooledConnection.connect(PooledConnection.java:182)
at
org.apache.tomcat.jdbc.pool.ConnectionPool.createConnection(ConnectionPool.java:701)
at
org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(ConnectionPool.java:635)
at
org.apache.tomcat.jdbc.pool.ConnectionPool.getConnection(ConnectionPool.java:188)
at
org.apache.tomcat.jdbc.pool.DataSourceProxy.getConnection(DataSourceProxy.java:127)
at
org.wso2.carbon.user.core.claim.dao.ClaimDAO.getDialectCount(ClaimDAO.java:158)
at
org.wso2.carbon.user.core.common.DefaultRealm.populateProfileAndClaimMaps(DefaultRealm.java:411)
at
org.wso2.carbon.user.core.common.DefaultRealm.init(DefaultRealm.java:101)
at
org.wso2.carbon.user.core.common.DefaultRealmService.initializeRealm(DefaultRealmService.java:223)
at
org.wso2.carbon.user.core.common.DefaultRealmService.(DefaultRealmService.java:101)
at
org.wso2.carbon.user.core.common.DefaultRealmService.(DefaultRealmService.java:114)
at
org.wso2.carbon.user.core.internal.Activator.startDeploy(Activator.java:69)
at
org.wso2.carbon.user.core.internal.BundleCheckActivator.start(BundleCheckActivator.java:61)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
at java.security.AccessController.doPrivileged(Native Method)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
at
org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:390)
at
org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1176)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.os

Re: [Dev] Updates for BPMN Admin UI

[Nandika Jayawardana]

Hi Amal,

Please create a jira and attach the patch to the jira.

Regards
Nandika


On Thu, Mar 6, 2014 at 5:50 PM, Amal Gunatilake  wrote:

> Hi Chathura,
>
> As we discussed before I updated some functionality in the back-end server
> code which is needed for BPMN Admin UI. Please apply the attached patch
> after reviewing with your changes.
>
> Thank you  & Best regards,
>
> *Amal Gunatilake*
>  Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Nandika Jayawardana
Senior Technical Lead
WSO2 Inc ; http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Developer Studio 3.6.0 RC 1 Released!

[Susinda Perera]

Hi All,

We have WSO2 Developer Studio 3.6.0 RC 1 ready to be downloaded at [1] and
installed eclipse distributions available at [2]. This release is mainly
focused on migrating Developer Studio to Eclipse Kepler. And
additionally includes
following bug fixes, improvements and tasks.


Bug Fixes

   - [TOOLS-1107 ] - "Show in
   registry browser" option should be disabled for resources that are not in
   the registry.
   - [TOOLS-1323 ] - Mediator
   palette scrolling is not intuitive
   - [TOOLS-1472 ] - Rule Mediator
   does not deserialize correctly
   - [TOOLS-1665 ] - Developer
   Studio JAX-WS Service Project, project name does not update with selection
   of wsdl file
   - [TOOLS-1745 ] - AF login
   dialog save credintial label cannot see completly
   - [TOOLS-1972 ] - When
   add/remove case to switch mediator sizes of inner cases get reduced and
   additional arrow is appear in the input connector side
   - [TOOLS-1973 ] - when delete
   and undo a complex mediator - An exception occured
   - [TOOLS-2030 ] - Cannot create
   Dynamic Endpoints
   - [TOOLS-2059 ] - Three clicks
   are required to edit the description of a mediator
   - [TOOLS-2189 ] - Deleting a
   proxy service either from DevStudio or the file system doesn't update
   pom.xml
   - [TOOLS-2228 ] - flow is get
   lost when delete the drop mediator
   - [TOOLS-2269 ] - New Registry
   Handler Creation Wizard layout is not displaying properly
   - [TOOLS-2292 ] - Create new
   registry aspect class wizard fails to complete
   - [TOOLS-2310 ] - Save pom.xml
   on Project Import to fix the artifacts ordering issue
   - [TOOLS-2313 ] - HTTP and
   Template endpoints get Address endpoint icon when drag and drop from
   Endpoint palette group
   - [TOOLS-2319 ] - Template
   wizard creates a useless WSDL EP when either WSDL url, service or port is
   invalid
   - [TOOLS-2323 ] - DBLookup and
   DBReport have the same icon in tool palette
   - [TOOLS-2325 ] - All available
   message stores in the workspace are not displaying in the properties view
   of the Store mediator
   - [TOOLS-2330 ] - SQL Statement
   Configuration window's Parameters and Results tables have not aligned
   properly
   - [TOOLS-2331 ] - In Clone
   Mediator's target configuration dialog, the table is non editable
   - [TOOLS-2332 ] - In Rule
   Mediator's fact configuration dialog, the table has not aligned properly
   - [TOOLS-2333 ] - In Endpoint's
   properties window, Value and Type columns should swap
   - [TOOLS-2336 ] - Scheduled
   task serialization fails when Task properties dialog is cancelled
   - [TOOLS-2338 ] - Cannot import
   files from system when creating Registry resources when there is no
   extensions
   - [TOOLS-2345 ] - When a custom
   mediator is created and added in to a CApp through dev studio custom
   mediator is listed last in the artifiacts.xml file in CApp
   - [TOOLS-2346 ] - services.xml
   file not get updated when creating a new Axis2 Service class
   - [TOOLS-2347 ] - Cannot drop a
   'Drop' mediator into switch mediator case or default branches
   - [TOOLS-2349 ] - [ESB] Custom
   task properties get serialized for empty property names and values too
   - [TOOLS-2350 ] - Some
   Mediators and Endpoints are not in the alphabetical order in the tool pallet
   - [TOOLS-2355 ] - It is
   allowing to add Respond and Loopback Mediators inside a mediator when they
   are already present in the mediator flow
   - [TOOLS-2356 ] - It is
   allowing to add Respond and Loopback Mediators in the middle of the
   mediator flow
   - [TOOLS-2357 ] -
   Maven-Car-Depoy-Plugin is unable to undeploy CAR files with Maven
   - [TOOLS-2358 

Re: [Dev] Please add realvent repos of Product-ESB in jenkins

[Vanjikumaran Sivajothy]

Thanks you KasunG for quick respond!


On Thu, Mar 6, 2014 at 4:21 PM, Kasun Gajasinghe  wrote:

> Hi Vanji,
>
> Added a jenkins job for the repo, and triggered a new build. [2]
>
> [2] http://54.84.136.218:8080/jenkins/job/product-esb/
>
> Regards,
> KasunG
>
>
> On Thu, Mar 6, 2014 at 4:17 PM, Vanjikumaran Sivajothy wrote:
>
>> Hi
>>
>> Please add [1] into the current builder machine,
>>
>>
>> [1] https://github.com/wso2/product-esb
>>
>> BR\
>>
>> --
>> Sivajothy Vanjikumaran
>> *Senior Software Engineer*
>> *Integration Technologies Team*
>> *WSO2 Inc. http://wso2.com *
>> *Mobile:(+94)777219209*
>> *Mobile USA:**(+1)918 813 2403*
>> [image: Facebook]  [image:
>> Twitter]  [image: 
>> LinkedIn] 
>> [image:
>> Blogger]  [image: 
>> SlideShare]
>>
>> This communication may contain privileged or other
>> confidential information and is intended exclusively for the addressee/s.
>> If you are not the intended recipient/s, or believe that you may
>> have received this communication in error, please reply to the
>> sender indicating that fact and delete the copy you received and in
>> addition, you should not print, copy, re-transmit, disseminate, or
>> otherwise use the information contained in this communication.
>> Internet communications cannot be guaranteed to be timely, secure, error
>> or virus-free. The sender does not accept liability for any errors
>> or omissions
>>
>
>
>
> --
> *Kasun Gajasinghe*
> Software Engineer;
> WSO2 Inc.; http://wso2.com
>
>
>  ,
> *email: *
> *kasung AT spamfree wso2.com    ** cell: **+94 (77)
> 678-0813 <%2B94%20%2877%29%20678-0813>*
> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>
>
>
> *blog: **http://kasunbg.org* 
>
>
>
> *twitter: **http://twitter.com/kasunbg* 
>
>
>
>


-- 
Sivajothy Vanjikumaran
*Senior Software Engineer*
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com *
*Mobile:(+94)777219209*
*Mobile USA:**(+1)918 813 2403*
[image: Facebook]  [image:
Twitter] [image:
LinkedIn] 
[image:
Blogger]  [image:
SlideShare]

This communication may contain privileged or other confidential information
and is intended exclusively for the addressee/s. If you are not the
intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print,
copy, re-transmit, disseminate, or otherwise use the information contained
in this communication. Internet communications cannot be guaranteed to be
timely, secure, error or virus-free. The sender does not accept liability
for any errors or omissions
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please add realvent repos of Product-ESB in jenkins

[Kasun Gajasinghe]

Hi Vanji,

Added a jenkins job for the repo, and triggered a new build. [2]

[2] http://54.84.136.218:8080/jenkins/job/product-esb/

Regards,
KasunG


On Thu, Mar 6, 2014 at 4:17 PM, Vanjikumaran Sivajothy wrote:

> Hi
>
> Please add [1] into the current builder machine,
>
>
> [1] https://github.com/wso2/product-esb
>
> BR\
>
> --
> Sivajothy Vanjikumaran
> *Senior Software Engineer*
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com *
> *Mobile:(+94)777219209*
> *Mobile USA:**(+1)918 813 2403*
> [image: Facebook]  [image: 
> Twitter] [image:
> LinkedIn]  
> [image:
> Blogger]  [image: 
> SlideShare]
>
> This communication may contain privileged or other
> confidential information and is intended exclusively for the addressee/s.
> If you are not the intended recipient/s, or believe that you may
> have received this communication in error, please reply to the
> sender indicating that fact and delete the copy you received and in
> addition, you should not print, copy, re-transmit, disseminate, or
> otherwise use the information contained in this communication.
> Internet communications cannot be guaranteed to be timely, secure, error
> or virus-free. The sender does not accept liability for any errors
> or omissions
>



-- 
*Kasun Gajasinghe*
Software Engineer;
WSO2 Inc.; http://wso2.com


 ,
*email: *
*kasung AT spamfree wso2.com    ** cell: **+94 (77)
678-0813*
*linked-in: *http://lk.linkedin.com/in/gajasinghe



*blog: **http://kasunbg.org* 



*twitter: **http://twitter.com/kasunbg* 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please add realvent repos of Product-ESB in jenkins

[Vanjikumaran Sivajothy]

Hi

Please add [1] into the current builder machine,


[1] https://github.com/wso2/product-esb

BR\

-- 
Sivajothy Vanjikumaran
*Senior Software Engineer*
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com *
*Mobile:(+94)777219209*
*Mobile USA:**(+1)918 813 2403*
[image: Facebook]  [image:
Twitter] [image:
LinkedIn] 
[image:
Blogger]  [image:
SlideShare]

This communication may contain privileged or other confidential information
and is intended exclusively for the addressee/s. If you are not the
intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print,
copy, re-transmit, disseminate, or otherwise use the information contained
in this communication. Internet communications cannot be guaranteed to be
timely, secure, error or virus-free. The sender does not accept liability
for any errors or omissions
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Create wso2-commons-vfs in GIT

[Vanjikumaran Sivajothy]

Hi sagara,

No we are not trying to create the Orbit repo!

Commons-vfs currently resides in the dependency folder in the platform and
we are going to make some changes on that.

If not to create new repo in GIT! what is the correct process of making
changes in code?


BR\
1G


On Thu, Mar 6, 2014 at 3:42 PM, Sagara Gunathunga  wrote:

>
>
> Eranda/Vanji,
>
> What is this new repo ? we have agreed that  we no longer create any
> repos. Are you trying to create Orbit repo if so this is not the correct
> approach.
>
> Thanks !
>
>
> On Thu, Mar 6, 2014 at 3:32 PM, Eranda Sooriyabandara wrote:
>
>> done [1].
>>
>> thanks
>> Eranda
>>
>> [1]. https://github.com/wso2/wso2-commons-vfs
>>
>>
>> On Thu, Mar 6, 2014 at 3:25 PM, Vanjikumaran Sivajothy wrote:
>>
>>> Hi Eranda,
>>>
>>> We need the $subject to change the version of the latest jsch and jcifs
>>> versions.
>>>
>>> Currently we have name convention as in [1], Please take the necessary
>>> action to create the repository in the git.
>>>
>>>
>>> [1]
>>> https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/dependencies/commons-vfs/
>>>
>>> Thanks
>>> BR
>>> --
>>> Sivajothy Vanjikumaran
>>> *Senior Software Engineer*
>>> *Integration Technologies Team*
>>> *WSO2 Inc. http://wso2.com *
>>> *Mobile:(+94)777219209*
>>> *Mobile USA:**(+1)918 813 2403*
>>> [image: Facebook]  [image:
>>> Twitter]  [image: 
>>> LinkedIn] 
>>> [image:
>>> Blogger]  [image: 
>>> SlideShare]
>>>
>>> This communication may contain privileged or other
>>> confidential information and is intended exclusively for the addressee/s.
>>> If you are not the intended recipient/s, or believe that you may
>>> have received this communication in error, please reply to the
>>> sender indicating that fact and delete the copy you received and in
>>> addition, you should not print, copy, re-transmit, disseminate, or
>>> otherwise use the information contained in this communication.
>>> Internet communications cannot be guaranteed to be timely, secure, error
>>> or virus-free. The sender does not accept liability for any errors
>>> or omissions
>>>
>>
>>
>>
>> --
>>
>> *Eranda Sooriyabandara*Senior Software Engineer;
>>  Integration Technologies Team;
>> WSO2 Inc.; http://wso2.com
>> Lean . Enterprise . Middleware
>>
>> E-mail: eranda AT wso2.com
>> Mobile: +94 716 472 816
>> Linked-In: http://www.linkedin.com/in/erandasooriyabandara
>> Blog: http://emsooriyabandara.blogspot.com/
>>
>>
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Sagara Gunathunga
>
> Senior Technical Lead; WSO2, Inc.;  http://wso2.com
> V.P Apache Web Services;http://ws.apache.org/
> Linkedin; http://www.linkedin.com/in/ssagara
> Blog ;  http://ssagara.blogspot.com
>
>


-- 
Sivajothy Vanjikumaran
*Senior Software Engineer*
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com *
*Mobile:(+94)777219209*
*Mobile USA:**(+1)918 813 2403*
[image: Facebook]  [image:
Twitter] [image:
LinkedIn] 
[image:
Blogger]  [image:
SlideShare]

This communication may contain privileged or other confidential information
and is intended exclusively for the addressee/s. If you are not the
intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print,
copy, re-transmit, disseminate, or otherwise use the information contained
in this communication. Internet communications cannot be guaranteed to be
timely, secure, error or virus-free. The sender does not accept liability
for any errors or omissions
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How can I subscribe multi-tenant cartridge?

[Quang Cường Vũ]

And could you explain more detail about step 2,3.. I can't understand. How
long the documentation will fix? Very thank. I am stuck for long time.


On Thu, Mar 6, 2014 at 5:16 PM, Sajith Kariyawasam  wrote:

>
>
>
> On Thu, Mar 6, 2014 at 2:02 PM, Quang Cường Vũ wrote:
>
>> Hi.
>>
>> Following documenation:
>>
>> Step 1:
>>
>> Download and extract wso2s2--1.0.0.zip to the server.
>> s2demo-single-node-installer- is inside wso2s2-
>>
>> ==> I can't find file name in s2demo-single-node-installer- inside. :(
>>
>
> That's what I mentioned in my previous response that this seems to be a
> documentation issue,  (We will fix it soon)
>
> Instead of  s2demo-single-node-installer- please  execute setup.sh
> script.
>
>
>
>>
>> Step  2, 3: I can't understand :(
>>
>>
>> On Thu, Mar 6, 2014 at 2:19 PM, chris snow  wrote:
>>
>>> Are you stuck at a particular step in the document?
>>>
>>>
>>> On Wed, Mar 5, 2014 at 10:10 AM, Quang Cường Vũ 
>>> wrote:
>>> > Yes.
>>> > AFAIK, this carbon cartridge is base cartridge to create WSO2 product
>>> > cartridge like Application Server cartridge but I can't understand
>>> > documentation: Create multi tenant cartridge.
>>> > https://docs.wso2.org/display/Stratos200/Cartridge+Development+Guide
>>> >
>>> >
>>> >
>>> > On Wed, Mar 5, 2014 at 4:59 PM, Sajith Kariyawasam 
>>> wrote:
>>> >>
>>> >> Hi Quang,
>>> >>
>>> >> With Stratos 2.0 release we already provided a pre-configured
>>> Application
>>> >> server cartridge, which you can find in [1]
>>> >>
>>> >> Did you try with that one?  Did you face any issue working with that
>>> >> cartridge?
>>> >>
>>> >> Thanks,
>>> >> Sajith
>>> >>
>>> >> [1]
>>> >>
>>> http://dist.wso2.org/downloads/stratos/2.0.0/misc/cartridges/carbon-cartridge-amd64.img.zip
>>> >>
>>> >>
>>> >> On Wed, Mar 5, 2014 at 3:11 PM, Quang Cường Vũ 
>>> >> wrote:
>>> >>>
>>> >>> Hi.
>>> >>> Some one in dev team can help me how to create Application server
>>> >>> cartridge for Stratos 2.0?
>>> >>>
>>> >>>
>>> >>>
>>> >>> On Wed, Mar 5, 2014 at 3:08 PM, Quang Cường Vũ 
>>> >>> wrote:
>>> 
>>>  Hi Sajith
>>> 
>>>  Readme.tx inside wso2s2-openstack-1.0.1 folder is guide for
>>> installation
>>>  Stratos. I want to create WSO2 product cartridge for Stratos 2.0
>>> 
>>> 
>>> 
>>>  On Wed, Mar 5, 2014 at 3:01 PM, Sajith Kariyawasam >> >
>>>  wrote:
>>> >
>>> > Hi Quang,
>>> >
>>> > This seems to be a documentation issue. It should have meant the
>>> > setup.sh script inside wso2s2- folder.
>>> >
>>> > Please refer the README.txt which is inside wso2s2-openstack-1.0.1
>>> > folder.
>>> >
>>> > Thanks,
>>> > Sajith
>>> >
>>> >
>>> > On Wed, Mar 5, 2014 at 12:59 PM, Quang Cường Vũ <
>>> vucuon...@gmail.com>
>>> > wrote:
>>> >>
>>> >>
>>> >> Hi.
>>> >> I can't understand guide in documentation to create WSO2 Product
>>> >> Cartridge
>>> >>
>>> https://docs.wso2.org/display/Stratos200/Cartridge+Development+Guide
>>> >>
>>> >> Carbon Cartridges
>>> >>
>>> >> WSO2 product Cartridge creation is automated using a Puppet.
>>> Defining
>>> >> a new Cartridge type can be done as follows:
>>> >>
>>> >> Step 1 - Define a new Cartridge type using Puppet.
>>> >>
>>> >> For more information go to
>>> >> http://docs.puppetlabs.com/puppet/2.7/reference/
>>> >>
>>> >> Step 2 - Setup S2 and Puppet in the IaaS.
>>> >>
>>> >> Download and extract wso2s2--1.0.0.zip to the server.
>>> >> s2demo-single-node-installer- is inside wso2s2-
>>> >>
>>> >> Execute the following commands, to run the automated
>>> installer:
>>> >> chmod +x s2demo-single-node-installer-
>>> >> ./s2demo-single-node-installer-
>>> >>
>>> >> This will create /mnt/puppet/stratos2 folder.
>>> >>
>>> >> Step 3 - Add definitions and configurations of the new Cartridge
>>> type
>>> >> in the Puppet master.
>>> >>
>>> >> Define a new puppet class extending the stratos.pp
>>> >> (/mnt/puppet/stratos2/manifests/classes/stratos.pp).
>>> >> stratos.pp contains all the common functionalities related to
>>> >> Carbon servers.
>>> >> Create a modules and template directory in
>>> >> /mnt/puppet/stratos2/{modules,templates}
>>> >>
>>> >> modules directory should contain the static files
>>> (e.g.,static
>>> >> configuration files, external JARs.), in the folder location
>>> defined in the
>>> >> corresponding .pp class.
>>> >>
>>> >> template directory should contain files with variables
>>> that
>>> >> can be submitted to changes (e.g., carbon servers axis2.xml,
>>> carbon.xml
>>> >> etc.), in the folder location defined in the corresponding .pp
>>> class.
>>> >>
>>> >> Create a node definition in the nodes.pp file.
>>> >> Add the new class to the node definition.
>>> >>
>>> >>
>>> >>

Re: [Dev] How can I subscribe multi-tenant cartridge?

[Sajith Kariyawasam]

On Thu, Mar 6, 2014 at 2:02 PM, Quang Cường Vũ  wrote:

> Hi.
>
> Following documenation:
>
> Step 1:
>
> Download and extract wso2s2--1.0.0.zip to the server.
> s2demo-single-node-installer- is inside wso2s2-
>
> ==> I can't find file name in s2demo-single-node-installer- inside. :(
>

That's what I mentioned in my previous response that this seems to be a
documentation issue,  (We will fix it soon)

Instead of  s2demo-single-node-installer- please  execute setup.sh
script.



>
> Step  2, 3: I can't understand :(
>
>
> On Thu, Mar 6, 2014 at 2:19 PM, chris snow  wrote:
>
>> Are you stuck at a particular step in the document?
>>
>>
>> On Wed, Mar 5, 2014 at 10:10 AM, Quang Cường Vũ 
>> wrote:
>> > Yes.
>> > AFAIK, this carbon cartridge is base cartridge to create WSO2 product
>> > cartridge like Application Server cartridge but I can't understand
>> > documentation: Create multi tenant cartridge.
>> > https://docs.wso2.org/display/Stratos200/Cartridge+Development+Guide
>> >
>> >
>> >
>> > On Wed, Mar 5, 2014 at 4:59 PM, Sajith Kariyawasam 
>> wrote:
>> >>
>> >> Hi Quang,
>> >>
>> >> With Stratos 2.0 release we already provided a pre-configured
>> Application
>> >> server cartridge, which you can find in [1]
>> >>
>> >> Did you try with that one?  Did you face any issue working with that
>> >> cartridge?
>> >>
>> >> Thanks,
>> >> Sajith
>> >>
>> >> [1]
>> >>
>> http://dist.wso2.org/downloads/stratos/2.0.0/misc/cartridges/carbon-cartridge-amd64.img.zip
>> >>
>> >>
>> >> On Wed, Mar 5, 2014 at 3:11 PM, Quang Cường Vũ 
>> >> wrote:
>> >>>
>> >>> Hi.
>> >>> Some one in dev team can help me how to create Application server
>> >>> cartridge for Stratos 2.0?
>> >>>
>> >>>
>> >>>
>> >>> On Wed, Mar 5, 2014 at 3:08 PM, Quang Cường Vũ 
>> >>> wrote:
>> 
>>  Hi Sajith
>> 
>>  Readme.tx inside wso2s2-openstack-1.0.1 folder is guide for
>> installation
>>  Stratos. I want to create WSO2 product cartridge for Stratos 2.0
>> 
>> 
>> 
>>  On Wed, Mar 5, 2014 at 3:01 PM, Sajith Kariyawasam 
>>  wrote:
>> >
>> > Hi Quang,
>> >
>> > This seems to be a documentation issue. It should have meant the
>> > setup.sh script inside wso2s2- folder.
>> >
>> > Please refer the README.txt which is inside wso2s2-openstack-1.0.1
>> > folder.
>> >
>> > Thanks,
>> > Sajith
>> >
>> >
>> > On Wed, Mar 5, 2014 at 12:59 PM, Quang Cường Vũ <
>> vucuon...@gmail.com>
>> > wrote:
>> >>
>> >>
>> >> Hi.
>> >> I can't understand guide in documentation to create WSO2 Product
>> >> Cartridge
>> >>
>> https://docs.wso2.org/display/Stratos200/Cartridge+Development+Guide
>> >>
>> >> Carbon Cartridges
>> >>
>> >> WSO2 product Cartridge creation is automated using a Puppet.
>> Defining
>> >> a new Cartridge type can be done as follows:
>> >>
>> >> Step 1 - Define a new Cartridge type using Puppet.
>> >>
>> >> For more information go to
>> >> http://docs.puppetlabs.com/puppet/2.7/reference/
>> >>
>> >> Step 2 - Setup S2 and Puppet in the IaaS.
>> >>
>> >> Download and extract wso2s2--1.0.0.zip to the server.
>> >> s2demo-single-node-installer- is inside wso2s2-
>> >>
>> >> Execute the following commands, to run the automated installer:
>> >> chmod +x s2demo-single-node-installer-
>> >> ./s2demo-single-node-installer-
>> >>
>> >> This will create /mnt/puppet/stratos2 folder.
>> >>
>> >> Step 3 - Add definitions and configurations of the new Cartridge
>> type
>> >> in the Puppet master.
>> >>
>> >> Define a new puppet class extending the stratos.pp
>> >> (/mnt/puppet/stratos2/manifests/classes/stratos.pp).
>> >> stratos.pp contains all the common functionalities related to
>> >> Carbon servers.
>> >> Create a modules and template directory in
>> >> /mnt/puppet/stratos2/{modules,templates}
>> >>
>> >> modules directory should contain the static files
>> (e.g.,static
>> >> configuration files, external JARs.), in the folder location
>> defined in the
>> >> corresponding .pp class.
>> >>
>> >> template directory should contain files with variables that
>> >> can be submitted to changes (e.g., carbon servers axis2.xml,
>> carbon.xml
>> >> etc.), in the folder location defined in the corresponding .pp
>> class.
>> >>
>> >> Create a node definition in the nodes.pp file.
>> >> Add the new class to the node definition.
>> >>
>> >>
>> >> Step 4 - Install the Puppet agent in an IaaS instance and create an
>> >> AMI.
>> >>
>> >> For more information see Setting up Puppet Agent.
>> >> I can't find any folder s2demo-single-node-installer- inside
>> >> wso2s2-. I download wso2s2-openstack-1.0.1
>> >>
>> >>
>> >>
>> >> Could you show me more detail? thanks?
>> >>
>> >>
>> >>>

Re: [Dev] Create wso2-commons-vfs in GIT

[Sagara Gunathunga]

Eranda/Vanji,

What is this new repo ? we have agreed that  we no longer create any repos.
Are you trying to create Orbit repo if so this is not the correct approach.

Thanks !


On Thu, Mar 6, 2014 at 3:32 PM, Eranda Sooriyabandara wrote:

> done [1].
>
> thanks
> Eranda
>
> [1]. https://github.com/wso2/wso2-commons-vfs
>
>
> On Thu, Mar 6, 2014 at 3:25 PM, Vanjikumaran Sivajothy wrote:
>
>> Hi Eranda,
>>
>> We need the $subject to change the version of the latest jsch and jcifs
>> versions.
>>
>> Currently we have name convention as in [1], Please take the necessary
>> action to create the repository in the git.
>>
>>
>> [1]
>> https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/dependencies/commons-vfs/
>>
>> Thanks
>> BR
>> --
>> Sivajothy Vanjikumaran
>> *Senior Software Engineer*
>> *Integration Technologies Team*
>> *WSO2 Inc. http://wso2.com *
>> *Mobile:(+94)777219209*
>> *Mobile USA:**(+1)918 813 2403*
>> [image: Facebook]  [image:
>> Twitter]  [image: 
>> LinkedIn] 
>> [image:
>> Blogger]  [image: 
>> SlideShare]
>>
>> This communication may contain privileged or other
>> confidential information and is intended exclusively for the addressee/s.
>> If you are not the intended recipient/s, or believe that you may
>> have received this communication in error, please reply to the
>> sender indicating that fact and delete the copy you received and in
>> addition, you should not print, copy, re-transmit, disseminate, or
>> otherwise use the information contained in this communication.
>> Internet communications cannot be guaranteed to be timely, secure, error
>> or virus-free. The sender does not accept liability for any errors
>> or omissions
>>
>
>
>
> --
>
> *Eranda Sooriyabandara*Senior Software Engineer;
> Integration Technologies Team;
> WSO2 Inc.; http://wso2.com
> Lean . Enterprise . Middleware
>
> E-mail: eranda AT wso2.com
> Mobile: +94 716 472 816
> Linked-In: http://www.linkedin.com/in/erandasooriyabandara
> Blog: http://emsooriyabandara.blogspot.com/
>
>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sagara Gunathunga

Senior Technical Lead; WSO2, Inc.;  http://wso2.com
V.P Apache Web Services;http://ws.apache.org/
Linkedin; http://www.linkedin.com/in/ssagara
Blog ;  http://ssagara.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Create wso2-commons-vfs in GIT

[Eranda Sooriyabandara]

done [1].

thanks
Eranda

[1]. https://github.com/wso2/wso2-commons-vfs


On Thu, Mar 6, 2014 at 3:25 PM, Vanjikumaran Sivajothy wrote:

> Hi Eranda,
>
> We need the $subject to change the version of the latest jsch and jcifs
> versions.
>
> Currently we have name convention as in [1], Please take the necessary
> action to create the repository in the git.
>
>
> [1]
> https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/dependencies/commons-vfs/
>
> Thanks
> BR
> --
> Sivajothy Vanjikumaran
> *Senior Software Engineer*
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com *
> *Mobile:(+94)777219209*
> *Mobile USA:**(+1)918 813 2403*
> [image: Facebook]  [image: 
> Twitter] [image:
> LinkedIn]  
> [image:
> Blogger]  [image: 
> SlideShare]
>
> This communication may contain privileged or other
> confidential information and is intended exclusively for the addressee/s.
> If you are not the intended recipient/s, or believe that you may
> have received this communication in error, please reply to the
> sender indicating that fact and delete the copy you received and in
> addition, you should not print, copy, re-transmit, disseminate, or
> otherwise use the information contained in this communication.
> Internet communications cannot be guaranteed to be timely, secure, error
> or virus-free. The sender does not accept liability for any errors
> or omissions
>



-- 

*Eranda Sooriyabandara*Senior Software Engineer;
Integration Technologies Team;
WSO2 Inc.; http://wso2.com
Lean . Enterprise . Middleware

E-mail: eranda AT wso2.com
Mobile: +94 716 472 816
Linked-In: http://www.linkedin.com/in/erandasooriyabandara
Blog: http://emsooriyabandara.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Create wso2-commons-vfs in GIT

[Vanjikumaran Sivajothy]

Hi Eranda,

We need the $subject to change the version of the latest jsch and jcifs
versions.

Currently we have name convention as in [1], Please take the necessary
action to create the repository in the git.


[1]
https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/dependencies/commons-vfs/

Thanks
BR
-- 
Sivajothy Vanjikumaran
*Senior Software Engineer*
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com *
*Mobile:(+94)777219209*
*Mobile USA:**(+1)918 813 2403*
[image: Facebook]  [image:
Twitter] [image:
LinkedIn] 
[image:
Blogger]  [image:
SlideShare]

This communication may contain privileged or other confidential information
and is intended exclusively for the addressee/s. If you are not the
intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print,
copy, re-transmit, disseminate, or otherwise use the information contained
in this communication. Internet communications cannot be guaranteed to be
timely, secure, error or virus-free. The sender does not accept liability
for any errors or omissions
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How can I subscribe multi-tenant cartridge?

[Quang Cường Vũ]

Hi.

Following documenation:

Step 1:

Download and extract wso2s2--1.0.0.zip to the server.
s2demo-single-node-installer- is inside wso2s2-

==> I can't find file name in s2demo-single-node-installer- inside. :(

Step  2, 3: I can't understand :(


On Thu, Mar 6, 2014 at 2:19 PM, chris snow  wrote:

> Are you stuck at a particular step in the document?
>
> On Wed, Mar 5, 2014 at 10:10 AM, Quang Cường Vũ 
> wrote:
> > Yes.
> > AFAIK, this carbon cartridge is base cartridge to create WSO2 product
> > cartridge like Application Server cartridge but I can't understand
> > documentation: Create multi tenant cartridge.
> > https://docs.wso2.org/display/Stratos200/Cartridge+Development+Guide
> >
> >
> >
> > On Wed, Mar 5, 2014 at 4:59 PM, Sajith Kariyawasam 
> wrote:
> >>
> >> Hi Quang,
> >>
> >> With Stratos 2.0 release we already provided a pre-configured
> Application
> >> server cartridge, which you can find in [1]
> >>
> >> Did you try with that one?  Did you face any issue working with that
> >> cartridge?
> >>
> >> Thanks,
> >> Sajith
> >>
> >> [1]
> >>
> http://dist.wso2.org/downloads/stratos/2.0.0/misc/cartridges/carbon-cartridge-amd64.img.zip
> >>
> >>
> >> On Wed, Mar 5, 2014 at 3:11 PM, Quang Cường Vũ 
> >> wrote:
> >>>
> >>> Hi.
> >>> Some one in dev team can help me how to create Application server
> >>> cartridge for Stratos 2.0?
> >>>
> >>>
> >>>
> >>> On Wed, Mar 5, 2014 at 3:08 PM, Quang Cường Vũ 
> >>> wrote:
> 
>  Hi Sajith
> 
>  Readme.tx inside wso2s2-openstack-1.0.1 folder is guide for
> installation
>  Stratos. I want to create WSO2 product cartridge for Stratos 2.0
> 
> 
> 
>  On Wed, Mar 5, 2014 at 3:01 PM, Sajith Kariyawasam 
>  wrote:
> >
> > Hi Quang,
> >
> > This seems to be a documentation issue. It should have meant the
> > setup.sh script inside wso2s2- folder.
> >
> > Please refer the README.txt which is inside wso2s2-openstack-1.0.1
> > folder.
> >
> > Thanks,
> > Sajith
> >
> >
> > On Wed, Mar 5, 2014 at 12:59 PM, Quang Cường Vũ  >
> > wrote:
> >>
> >>
> >> Hi.
> >> I can't understand guide in documentation to create WSO2 Product
> >> Cartridge
> >>
> https://docs.wso2.org/display/Stratos200/Cartridge+Development+Guide
> >>
> >> Carbon Cartridges
> >>
> >> WSO2 product Cartridge creation is automated using a Puppet.
> Defining
> >> a new Cartridge type can be done as follows:
> >>
> >> Step 1 - Define a new Cartridge type using Puppet.
> >>
> >> For more information go to
> >> http://docs.puppetlabs.com/puppet/2.7/reference/
> >>
> >> Step 2 - Setup S2 and Puppet in the IaaS.
> >>
> >> Download and extract wso2s2--1.0.0.zip to the server.
> >> s2demo-single-node-installer- is inside wso2s2-
> >>
> >> Execute the following commands, to run the automated installer:
> >> chmod +x s2demo-single-node-installer-
> >> ./s2demo-single-node-installer-
> >>
> >> This will create /mnt/puppet/stratos2 folder.
> >>
> >> Step 3 - Add definitions and configurations of the new Cartridge
> type
> >> in the Puppet master.
> >>
> >> Define a new puppet class extending the stratos.pp
> >> (/mnt/puppet/stratos2/manifests/classes/stratos.pp).
> >> stratos.pp contains all the common functionalities related to
> >> Carbon servers.
> >> Create a modules and template directory in
> >> /mnt/puppet/stratos2/{modules,templates}
> >>
> >> modules directory should contain the static files
> (e.g.,static
> >> configuration files, external JARs.), in the folder location
> defined in the
> >> corresponding .pp class.
> >>
> >> template directory should contain files with variables that
> >> can be submitted to changes (e.g., carbon servers axis2.xml,
> carbon.xml
> >> etc.), in the folder location defined in the corresponding .pp
> class.
> >>
> >> Create a node definition in the nodes.pp file.
> >> Add the new class to the node definition.
> >>
> >>
> >> Step 4 - Install the Puppet agent in an IaaS instance and create an
> >> AMI.
> >>
> >> For more information see Setting up Puppet Agent.
> >> I can't find any folder s2demo-single-node-installer- inside
> >> wso2s2-. I download wso2s2-openstack-1.0.1
> >>
> >>
> >>
> >> Could you show me more detail? thanks?
> >>
> >>
> >> On Wed, Mar 5, 2014 at 1:31 PM, Quang Cường Vũ  >
> >> wrote:
> >>>
> >>> Ok, nice thanks :)
> >>>
> >>>
> >>> On Wed, Mar 5, 2014 at 12:23 PM, Udara Liyanage 
> >>> wrote:
> 
>  Hi,
> 
>  Carbon cartridge is made for hosting carbon products such as
>  Application Server, ESB, BPS However carbon cartridge you
> mentioned is a
>  base cartridge for carbon pr

Re: [Dev] Exposing the Activiti REST API

[Sagara Gunathunga]

On Thu, Mar 6, 2014 at 12:15 PM, Chathura Ekanayake wrote:

>
> Hi All,
>
> Activiti has a Restlet based comprehensive REST API to expose all BPMN
> related functions. As we are planning to have a REST API for BPMN, we can
> integrate this Activiti REST module in Carbon. Could I get feedback on the
> following items regarding this integration:
>
> Restlet vs JAX-RS:
> Should we integrate the Restlet based Activiti API or should we write a
> new JAX-RS based REST module? I think it is better to use the Activiti REST
> module as it allows us to migrate easily with new Activiti versions.
>

IMHO if Activiti REST module can cater all of our BPMN requirements then
rewriting is not required at least at this point.


>
> Integrating the Activiti Restlet based API:
> If we decide to integrate the Activiti REST module, we have to expose the
> Restlet servlet to handle REST requests. One option is to register this
> servlet in repository/conf/tomcat/web.xml, which exposes this on the same
> port as admin services. However, we have to keep these servlet registration
> entries in the web.xml, even though the BPMN component is not deployed.
> Another option is to start a separate server (if this is possible in
> Carbon) for Activiti REST and register the Restlet servlet in that server.
>

Can't we just deploy above module as a web application with own context
path as mention in this post[1] ?  If you look at OAuth endpoint in IS/APIM
we used this approach additionally some of future AS integration will use
this approach.

[1] -
http://bpmn20inaction.blogspot.com/2013/02/activiti-in-action-updates-part-1.html

Thanks !

>
> Thoughts...
>
> Regards,
> Chathura
>
>
>


-- 
Sagara Gunathunga

Senior Technical Lead; WSO2, Inc.;  http://wso2.com
V.P Apache Web Services;http://ws.apache.org/
Linkedin; http://www.linkedin.com/in/ssagara
Blog ;  http://ssagara.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev