Re: [Dev] Writing an OSGI Component to Create a Tenant during ESB Startup
tTenantBillingService"
>>>>
>>>> TenantMgtListener is available in ESB and therefore set the cardinality
>>>> to 1..n. TenantBillingService is not available in ESB and hence cardinality
>>>> is 0..1.
>>>>
>>>> Following is the implementation in the TenantInitializerComponent’s
>>>> activate method.
>>>>
>>>> TenantMgtAdminService tenantMgtAdminService = new
>>>> TenantMgtAdminService();
>>>>
>>>> TenantInfoBean tenantInfoBean = new TenantInfoBean();
>>>>
>>>> tenantInfoBean.setActive(true);
>>>>
>>>> tenantInfoBean.setAdmin("admin");
>>>>
>>>> tenantInfoBean.setAdminPassword("admin123");
>>>>
>>>> tenantInfoBean.setFirstname("Maheeka");
>>>>
>>>> tenantInfoBean.setLastname("Maheeka");
>>>>
>>>> tenantInfoBean.setEmail("ad...@maheeka.com");
>>>>
>>>> tenantInfoBean.setTenantDomain("maheeka.com");
>>>>
>>>> tenantInfoBean.setSuccessKey("");
>>>>
>>>> tenantInfoBean.setTenantId(250);
>>>>
>>>
>>> This may not work because, the tenant id is generated and returned by
>>> the tenant persister once a new tenant is persisted properly in DB. The
>>> tenant id is basically the row id in the table.
>>>
>>> Did you test this?
>>>
>>>
>>> tenantInfoBean.setUsagePlan("Demo");
>>>>
>>>> try {
>>>>
>>>> tenantMgtAdminService.addTenant(tenantInfoBean);
>>>>
>>>> log.info("Tenant added successfully");
>>>>
>>>> } catch (Exception e) {
>>>>
>>>> log.error(“Error adding tenant", e);
>>>>
>>>> }
>>>>
>>>>
>>>> However, “tenantMgtAdminService.addTenant(tenantInfoBean)” will invoke
>>>> TenantMgtServiceComponent
>>>> which is not activated by this time and thus throws a NPE.
>>>>
>>>>
>>>>1.
>>>>
>>>>Next thing we tried was using the ServerStartupObserver as
>>>>dependency to TenantInitializerComponent. However even this time
>>>>TenantMgtServiceComponent is not activated by the time
>>>>TenantInitializerComponent tries to activate. According to [1], seems
>>>> like
>>>>ServerStartupObserver only waits till the transports are started.
>>>>2.
>>>>
>>>>If we write a BundleListener [3], we could wait for the
>>>>TenantMgtServiceComponent to be active and perform addTenant. Since this
>>>>captures all bundle statuses this might not be an effective approach.
>>>>3.
>>>>
>>>>Finally, took a look at StartupFinalizerServiceComponent. This
>>>>seems to register a service after all the components are initialized as
>>>>org.apache.axis2.engine.ListenerManager. I was able to successfully
>>>>create the tenant by adding a reference to this service as below.
>>>>
>>>> * @scr.reference name="listener.manager"
>>>>
>>>> *interface="org.apache.axis2.engin
>>>> e.ListenerManager"
>>>>
>>>> *cardinality="1..1" policy="dynamic"
>>>>
>>>> *bind="setListenerManager"
>>>>
>>>> *unbind="unsetListenerManager"
>>>>
>>>>
>>>> Adding reference to org.apache.axis2.engine.ListenerManager seems to
>>>> solve the problem. However, need to verify whether there are any other
>>>> better ways to solve this problem. Or shall we proceed with this approach?
>>>> Appreciate your feedback on this.
>>>>
>>>>
>>>> Thanks Kalpa and Jayanga for helping out on the details.
>>>>
>>>> [1] https://docs.wso2.com/display/Carbon447/Server+Startup+Observer
>>>>
>>>> [2] https://github.com/wso2/carbon-kernel/blob/4.4.x/core/org.ws
>>>> o2.carbon.core/src/main/java/org/wso2/carbon/core/internal/S
>>>> tartupFinalizerServiceComponent.java#L199
>>>>
>>>> [3] http://eclipsesource.com/blogs/2013/01/23/how-to-track-lifec
>>>> ycle-changes-of-osgi-bundles/
>>>>
>>>> Thanks,
>>>>
>>>> Maheeka Jayasuriya
>>>> Senior Software Engineer
>>>> Mobile : +9450661
>>>>
>>>
>>>
>>>
>>> --
>>> *Kishanthan Thangarajah*
>>> Technical Lead,
>>> Platform Technologies Team,
>>> WSO2, Inc.
>>> lean.enterprise.middleware
>>>
>>> Mobile - +94773426635
>>> Blog - *http://kishanthan.wordpress.com
>>> <http://kishanthan.wordpress.com>*
>>> Twitter - *http://twitter.com/kishanthan
>>> <http://twitter.com/kishanthan>*
>>>
>>
>>
>>
>> --
>> *Kishanthan Thangarajah*
>> Technical Lead,
>> Platform Technologies Team,
>> WSO2, Inc.
>> lean.enterprise.middleware
>>
>> Mobile - +94773426635
>> Blog - *http://kishanthan.wordpress.com
>> <http://kishanthan.wordpress.com>*
>> Twitter - *http://twitter.com/kishanthan <http://twitter.com/kishanthan>*
>>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
--
Sanjiva Weerawarana, Ph.D.
Founder, CEO & Chief Architect; WSO2, Inc.; http://wso2.com/
email: sanj...@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345)
x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311
blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] [BPS] [UUF] Developing BPMN Explorer UI using UUF for BPS
;>>>> to be released on C5. >>>>>>> >>>>>>> We need to implement business logics in backend. For example, I need >>>>>>> to send request to backend from browser, and from backend to BPS. Is >>>>>>> there >>>>>>> functionality to achieve it in UUF? >>>>>>> >>>>>>> Any idea on this is appreciated. >>>>>>> >>>>>>> Thanks >>>>>>> Sudharma >>>>>>> >>>>>>> -- >>>>>>> Sudharma Subasinghe, >>>>>>> Software Engineer, >>>>>>> WSO2 Inc. >>>>>>> Email: sudhar...@wso2.com >>>>>>> Mobile : +94 710 565 157 <%2B94%20718%20210%20200> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Sajith Janaprasad Ariyarathna >>>>>> Software Engineer; WSO2, Inc.; http://wso2.com/ >>>>>> >>>>>> ___ >>>>>> Architecture mailing list >>>>>> architect...@wso2.org >>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>> >>>>>> >>>>> >>>> >>>> >>>> -- >>>> With regards, >>>> *Manu*ranga Perera. >>>> >>>> phone : 071 7 70 20 50 >>>> mail : m...@wso2.com >>>> >>>> ___ >>>> 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 >>> >>> >> >> >> -- >> With Regards, >> >> *Rasika Perera* >> Software Engineer >> M: +94 71 680 9060 E: rasi...@wso2.com >> LinkedIn: http://lk.linkedin.com/in/rasika90 >> >> WSO2 Inc. www.wso2.com >> lean.enterprise.middleware >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Nandika Jayawardana > WSO2 Inc ; http://wso2.com > lean.enterprise.middleware > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Sanjiva Weerawarana, Ph.D. Founder, CEO & Chief Architect; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345) x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311 blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] Introducing a model generator for DataMapper
In the first picture there's something saying "schema generator for XSD" and "schema generator for XML". I can't figure out what the latter is. On Fri, Mar 11, 2016 at 1:46 PM, Awanthika Senarath wrote: > Please find the component diagram attached, > > > Data Mapper Tool Workflow > <https://docs.google.com/a/wso2.com/drawings/d/1_MXoaIxswrmYS2E4RWzn6yov4NEfluWMSUtr82J_FAs/edit?usp=drive_web> > > > Awanthika Senarath > Software Engineer, WSO2 Inc. > Mobile: +94717681791 > > > > On Fri, Mar 11, 2016 at 12:09 PM, Awanthika Senarath > wrote: > >> >> Please find the modified class diagram attached, >> >> >> Schema Generator - Factory Implementation - Cla... >> <https://docs.google.com/a/wso2.com/drawings/d/1dAC7OMtmnUgsSAPf1Szmiq95vZSkdAI5TYyqwCUm5SY/edit?usp=drive_web> >> >> >>> >>>>> >> > > _______ > Architecture mailing list > architect...@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Sanjiva Weerawarana, Ph.D. Founder, CEO & Chief Architect; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345) x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311 blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] Dev, QA, Production
http://wso2.com/library/articles/2015/07/article-multi-environment-artifact-management-for-wso2-products-using-wso2-governance-registry/ On Sat, Feb 20, 2016 at 2:31 AM, John Q wrote: > Hello, > Which is the better approach to externalize parameters in esb artifacts, > for example, a username and password pair used within a sequence. I'm using > local-entries for this purpose. but the values of these local entries are > not the same in dev and production environments. > > Once these local entries are deployed into the server, I need to make > future deployments of sequences, proxies, etc, and prevent these local > entries to be overwritten with the local entries. > > Can any body give me some advice or guide in order to face these > deployment relative issues? > > Thanks in advice, > John > > ___ > Architecture mailing list > architect...@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Sanjiva Weerawarana, Ph.D. Founder, CEO & Chief Architect; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; office: (+1 650 745 4499 | +94 11 214 5345) x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311 blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] [C5] WSO2 Carbon Kernel 5.0.0 - M1 Release
Congratulations C5 team! Hmmm ... "legacy technologies like Axis2" .. ouch. Sanjiva. p.s.: s/GitHup/GitHub/. On Thu, Dec 12, 2013 at 1:10 PM, Sameera Jayasoma wrote: > Hi All, > > We are happy to inform you that the release of the first milestone of > Carbon kernel 5.0.0. You can download the release distribution from [1]. > > *What is Carbon Kernel 5?* > Carbon kernel 5 is the next generation of WSO2 Carbon > kernel, re-architected from the ground up with the latest technologies to > overcome the existing architectural limitations as well as to get rid of > the dependencies to the legacy technologies like Apache Axis2. > > This milestone release includes the bare minimum features for an OSGi > runtime. > > *New Features* > >- Equinox Kepler based light-weight OSGi runtime. >- New Carbon launcher implementation >- Centralized logging back-end (based on Log4j) which supports >multiple logging APIs. > > *How to contribute?* > C5 code is now available in GitHup[2]. You can clone this repository and > do a maven build from the root. If you have any suggestions or interested > in C5 discussions, please do so via *dev@wso2.org * or > *architect...@wso2.org > * mailing lists. > > Please report bugs, if any here[3] > > *Known Issues* > https://wso2.org/jira/browse/CARBON-14585?filter=11693 > > Thanks, > *C5 Team.* > > [1] > http://svn.wso2.org/repos/wso2/people/sameera/work/carbon-5.0.0/milestone-1/wso2carbon-kernel-5.0.0-SNAPSHOT.zip > [2] https://github.com/wso2/carbon-kernel > [3] https://wso2.org/jira/browse/CARBON > > -- > Sameera Jayasoma, > Architect, > > WSO2, Inc. (http://wso2.com) > email: same...@wso2.com > blog: http://sameera.adahas.org > twitter: https://twitter.com/sameerajayasoma > flickr: http://www.flickr.com/photos/sameera-jayasoma/collections > Mobile: 0094776364456 > > Lean . Enterprise . Middleware > > _______ > Architecture mailing list > architect...@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; office: +1 650 745 4499 x5700; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Fwd: [jira] [Created] (STRATOS-95) Build failure on trunk (3.0.0-SNAPSHOT)
FYI - please fix in Carbon itself (see thread on
d...@stratos.incubator.apache.org for more info).
-- Forwarded message --
From: Hadrian Zbarcea (JIRA)
Date: Tue, Oct 8, 2013 at 7:10 AM
Subject: [jira] [Created] (STRATOS-95) Build failure on trunk
(3.0.0-SNAPSHOT)
To: d...@stratos.incubator.apache.org
Hadrian Zbarcea created STRATOS-95:
--
Summary: Build failure on trunk (3.0.0-SNAPSHOT)
Key: STRATOS-95
URL: https://issues.apache.org/jira/browse/STRATOS-95
Project: Stratos
Issue Type: Bug
Affects Versions: 3.0.0 RC1
Reporter: Hadrian Zbarcea
Fix For: 3.0.0 RC1
Builds fail in org.apache.stratos.account.mgt due to a missing dependency
on javax.activation:activation:jar:1.0.2.
A quick mvn -X dependency:tree shows it as being a transitive dependency
coming from org.wso2.carbon:atlassian-jira.
{code}
[DEBUG]org.wso2.carbon:atlassian-jira:jar:1.0.0.wso2v1:compile
[...]
[DEBUG] javax.xml:jaxrpc-api:jar:1.1:compile
[DEBUG] javax.xml.soap:saaj-api:jar:1.3:compile
[DEBUG] javax.activation:activation:jar:1.0.2:compile
{code}
A simple excludes of the transitive dependency solves the problem (patch
attached). Ideally this would be done directly in carbon/atlassian-jira in
a future release and removed from here.
Cheers
--
This message was sent by Atlassian JIRA
(v6.1#6144)
--
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
650 265 8311
blog: http://sanjiva.weerawarana.org/
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Why we are refactoring the CarbonContext API Usage in the Carbon platform?
Sameera isn't CarbonContext.getCurrentContext() supposed to return the context associated with the current thread??? On Tue, Oct 1, 2013 at 11:45 AM, Sameera Jayasoma wrote: > Hi Folks, > > Some of you may be wondering why we are doing this change now. The > simplest reason is, to ensure the consistency of its usage. > > Over the past few years somehow we've ended up adding more methods to this > API and also ended up putting two different set of APIs for setting and > getting the CarbonContext object. Its not the time to check who has done > this, but its the time to properly refactor this API as well as its usages. > Following is the two sets of APIs. Carbon kernel and component developers > have used these methods interchangeably. This has caused some inconsistency > in the CarbonPlatform. We've faced many issues related to this during the > 4.2.0 release. Thats why we thought of fixing this once for all. > > > CarbonContext.getCurrentContext() > CarbonContext.getCurrentContext(MessageContext msgCtx) > CarbonContext.getCurrentContext(HttpSession session) > CarbonContext.getCurrentContext(AxisConfiguration config) > CarbonContext.getCurrentContext(ConfigurationContext ctx) > CarbonContext.getCurrentContext(ThriftSession session) > > - > *CarbonContext.getThreadLocalVariable()* > > The plan is the use the latter API from now onwards. We are deprecating > the former set of APIs. Now we need to ensure that each running Thread in > the system should have an associated CarbonContext object. > > > Thanks, > Sameera. > > -- > Sameera Jayasoma, > Architect, > > WSO2, Inc. (http://wso2.com) > email: same...@wso2.com > blog: http://sameera.adahas.org > twitter: https://twitter.com/sameerajayasoma > flickr: http://www.flickr.com/photos/sameera-jayasoma/collections > Mobile: 0094776364456 > > Lean . Enterprise . Middleware > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Introducing the Carbon Platform Release Concept
(http://wso2.com) > email: same...@wso2.com > blog: http://sameera.adahas.org > twitter: https://twitter.com/sameerajayasoma > flickr: http://www.flickr.com/photos/sameera-jayasoma/collections > Mobile: 0094776364456 > > Lean . Enterprise . Middleware > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Red or Blue ?
Guys lets stick to the colors that were designed together .. its generally not a good idea to change color of one bit because it impact other color choices. Sanjiva. On Wed, Jul 3, 2013 at 11:34 AM, Dimuthu Leelarathne wrote: > Hi, > > Please give comments. Added screenshots. > > thanks, > dimuthu > > -- > Dimuthu Leelarathne > Architect & Product Lead of App Factory > > WSO2, Inc. (http://wso2.com) > email: dimut...@wso2.com > Mobile : 0773661935 > > Lean . Enterprise . Middleware > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] [Carbon 5] Scrap front-end & back-end separation?
I agree with all of this *but*, I still don't get why the workers don't need APIs. How do we: - ask it to update itself for deployment type stuff - ask it to change some config - ask it to send BAM events to a particular place - do JMX to it etc. etc.. All of those require that the OC or the mgmt node or ADC be able to talk to the server. Maybe the communication is cluster-wide (broadcast) or maybe its point-to-point ... depends on the scenario. I am confused why we don't need some way to interact with the worker remotely. Obviously I'm missing some crucial thought here ... what is it? Sanjiva. On Fri, Mar 22, 2013 at 12:52 AM, Afkham Azeez wrote: > > > On Fri, Mar 22, 2013 at 12:47 AM, Sagara Gunathunga wrote: > >> >> >> On Fri, Mar 22, 2013 at 12:36 AM, Sameera Jayasoma wrote: >> >>> >>> >>> >>> On Thu, Mar 21, 2013 at 12:00 PM, Sagara Gunathunga wrote: >>> >>>> >>>> >>>> On Fri, Mar 22, 2013 at 12:12 AM, Afkham Azeez wrote: >>>> >>>>> >>>>> >>>>> On Fri, Mar 22, 2013 at 12:05 AM, Sameera Jayasoma >>>>> wrote: >>>>> >>>>>> See my comments inline. >>>>>> >>>>>> >>>>>> On Thu, Mar 21, 2013 at 11:25 AM, Afkham Azeez wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> On Thu, Mar 21, 2013 at 11:49 PM, Sameera Jayasoma >>>>>> > wrote: >>>>>>> >>>>>>>> Hi Azeez, >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Thu, Mar 21, 2013 at 5:49 AM, Afkham Azeez wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Thu, Mar 21, 2013 at 6:16 PM, Sanjiva Weerawarana < >>>>>>>>> sanj...@wso2.com> wrote: >>>>>>>>> >>>>>>>>>> Azeez don't we need the management API in worker nodes? I assume >>>>>>>>>> the answer is yes .. >>>>>>>>>> >>>>>>>>> >>>>>>>>> If you look at the current worker-manager separated setup, we >>>>>>>>> don't have a single instance where the management node BE or FE calls >>>>>>>>> into >>>>>>>>> the worker node BE. >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> I agree that worker nodes do not require administrative services. >>>>>>>> But for Management node, we need to maintain the BE/FE separation. I.e >>>>>>>> we >>>>>>>> need to keep the administration services as its. This would user to >>>>>>>> write >>>>>>>> their own UI layer to interact with our server. This exactly what >>>>>>>> AppFactory is doing right? In some of the project I've worked, we >>>>>>>> developed >>>>>>>> completely different UI to interact with Mgt nodes. So IMV, we still >>>>>>>> need >>>>>>>> that BE services. >>>>>>>> >>>>>>> >>>>>>> FE-BE separation means from the UI components we make service calls >>>>>>> to the BE components. What we need is management APIs. Our UI can simply >>>>>>> use these management APIs. We don't need FE-BE separation. External apps >>>>>>> can also call these management APIs. >>>>>>> >>>>>> >>>>>> Okay. so anyway we need to expose our management APIs as service >>>>>> right?. >>>>>> >>>>>> I was under the impression that FE-BE separation means a clear >>>>>> separation of UI layer from the BE layer. some how we ended up connecting >>>>>> FE layer to BE layer via web services communication. But we tried to >>>>>> connect FE to BE via Java calls via OSGi services approach. Thats didn't >>>>>> work due to some security issues. >>>>>> >>>>>> Anyway still we need to clearly separate FE components from the >>>>>> management APIs right? But we need to figure out an efficient and secure >>>>>> way to connect the FE to BE. >>>>>> >>>>> >>>>> I guess where I am getting at is, we have RESTful APIs, which will be >>>>> called by code running in the Web Browser. Yes, I am suggesting that we go >>>>> back to the old AJAX based UI model we had, but without the pain of XSLT >>>>> (in the old model). >>>>> >>>>> FE = jquery + HTML+ (Jaggery?) >>>>> BE= RESTful APIs (Jaggery?) >>>>> >>>>> FE <--- JSON --> BE >>>>> >>>> >>>> One question, what is the transport protocol which carries JSON >>>> messages from FE to BE ? >>>> >>> >>> Obviously HTTPS. :) >>> >> >> Given the fact that both FE and BE run on same JVM do we really need to >> use transport level protocols here ? isn't it make sense to use Java call >> within the JVM ? >> >> > FE (running on Web Browser) <--- JSON/HTTP --> BE (RESTful API running in > JVM) > > ___ > Architecture mailing list > architect...@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] [Carbon 5] Scrap front-end & back-end separation?
Azeez don't we need the management API in worker nodes? I assume the answer is yes .. So in that case the worker contains the runtime container logic plus a management API (running at a separate port etc. and enabled by request). The management node contains an admin app that talks to the worker nodes via the API and other means (such as ADC). Right? +1 as long as we can still ship a multi-profile distro by default where all of this is in one JVM and then you give the personalty at boot time. Sanjiva. On Thu, Mar 21, 2013 at 6:03 PM, Afkham Azeez wrote: > > > On Thu, Mar 21, 2013 at 5:56 PM, Samisa Abeysinghe wrote: > >> >> >> On Thu, Mar 21, 2013 at 3:35 PM, Afkham Azeez wrote: >> >>> With the worker-manager concept, we no longer require FE-BE separation. >>> There is no need to have FE-BE separation for the management node. So, I >>> think we can completely do away with that concept. >> >> >> But how do we separate the worker stuff from manager stuff? >> Is that not >> Manger == FE + BE >> Worker == BE >> >> > > No, FE is the front end of the management admin client. BE is the > management service/API. Worker provides the runtime to run services, apps, > processes, mediation etc. We have made the mistake of calling this runtime > as BE as well. Management nodes will not ideally require this runtime, but > we may need to have some parts of it. e.g. validating the Synapse config > will require Synapse to be in the management node. We will never have a > case where a FE talks to a BE in a worker node. When it comes to the mgt > node, there is no need for separating the FE & BE. > > >> >>> What do you guys think? >>> >>> -- >>> *Afkham Azeez* >>> Director of Architecture; WSO2, Inc.; http://wso2.com >>> Member; Apache Software Foundation; http://www.apache.org/ >>> * <http://www.apache.org/>** >>> email: **az...@wso2.com* * cell: +94 77 3320919 >>> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >>> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>> * >>> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >>> * >>> * >>> *Lean . Enterprise . Middleware* >>> >>> ___ >>> Architecture mailing list >>> architect...@wso2.org >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> Thanks, >> Samisa... >> >> Samisa Abeysinghe >> VP Engineering >> WSO2 Inc. >> http://wso2.com >> http://wso2.org >> >> >> >> ___ >> Architecture mailing list >> architect...@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > *Afkham Azeez* > Director of Architecture; WSO2, Inc.; http://wso2.com > Member; Apache Software Foundation; http://www.apache.org/ > * <http://www.apache.org/>** > email: **az...@wso2.com* * cell: +94 77 3320919 > blog: **http://blog.afkham.org* <http://blog.afkham.org>* > twitter: **http://twitter.com/afkham_azeez*<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 > > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] User Engagement Server Milestone-5 Released
.carbon.context.internal.CarbonContextDataHolder$CarbonInitialJNDIContext.bind(CarbonContextDataHolder.java:1038)
at javax.naming.InitialContext.bind(InitialContext.java:400)
at
javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:625)
at
javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:412)
... 41 more
Caused by: java.rmi.ConnectIOException: non-JRMP server at remote endpoint
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:230)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184)
at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:322)
at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:120)
... 46 more
I know its harmless but please fix for next release .. looks bad.
Sanjiva.
On Thu, Feb 28, 2013 at 8:14 PM, Madhuka Udantha wrote:
> *User Engagement Server Milestone-5 Released*
>
> The Milestone-5 of WSO2 User Engagement Server can be downloaded at [1].
> Milestone 5 mainly contains,
>
> *[Task]
> *[UEC-13 <https://wso2.org/jira/browse/UEC-13>] Make Jaggery based gadget
> deployer to be started up during the app deployment
> [UEC-50 <https://wso2.org/jira/browse/UEC-50>] Registration and Login
> with using jaggery modules
>
> *[Bug]
> *[UEC-43 <https://wso2.org/jira/browse/UEC-43>] Gadget thumbnails aren't
> visible in chrome browser
> [UEC-20 <https://wso2.org/jira/browse/UEC-20>] Quartz.SchedulerException
> when shutting down the server.
> [UEC-41 <https://wso2.org/jira/browse/UEC-41>] Store Gadget Icons have
> https://localhost URLS
> [UEC-40 <https://wso2.org/jira/browse/UEC-40>] Climate Change and Mark
> mail gadgets not working
> [UEC-18 <https://wso2.org/jira/browse/UEC-18>] Accessing
> https://my-ip:9443/ or https://my-ip:9443/carbon gives 404 error
> [UEC-37 <https://wso2.org/jira/browse/UEC-37>] jaggery deployer issue
> with host object
>
> The Milestone-5 of WSO2 User Engagement Server is early middle stage, you
> will encounter some bugs and feature limitations, we are working on
> improving these in future milestones[6].
>
>
> *References *
>
> [1] Product can be downloaded from :
> http://dist.wso2.org/milestone/gs/ues/M5/wso2ues-1.0.0-M5.zip
> [2] Portal is located at : http://{IP}:9763/portal
> [3] Store is located at : http://{IP}:9763/store/assets/gadget/
> [4] Portal dashboard : http://{IP}:9763/portal/dashboard.jag
> [5] Web based editor : http://{IP}:9763/portal/dashboard/new-page.jag
> [6] Issue Tracker: https://wso2.org/jira/browse/UEC
>
>
> -- *WSO2 User Engagement Server Team* --
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
--
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
650 265 8311
blog: http://sanjiva.weerawarana.org/
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Carbon kernel refactoring
Totally +1 .. wish I could help! On Thu, Jan 31, 2013 at 3:16 PM, Pradeep Fernando wrote: > Hi all, > > Me and azeez started on the $subject before the Dec break. The latest code > can be found here [1] > > > * Rationale and objectives: > > - there are so many bundles, even within carbon kernel and there seems to > be unnecessary granularity. > - In the future we are going to patch carbon kernel intead of kernel minor > releases. > - getting rid of not-so-kenel code. > - this is the stepping stone to C5 efforts. > > * As of now: > > - identified few core modules - user.core, registry.core, caching, > logging, datasources (but still user.core and registry.core depends on > kernel..) > - refactored the kernel, so that it only depends on registry,usercore and > datasource api s. > - carbon starts but having issues with admin services > > > * to be done: > > - refactor user.core/registry.core to be independent of carbon kernel - we > might need to change the user.api and registry.api while doing so. Right > now these modules access tenant info using carbonContext. They don't get > passed via API. > > - The UserRegistry implementation get used in modules. Not being an > interface this creates coupling between modules. > > - remove implementation classes of user.core and registry.core and come up > with simpleImpls. (may be in-memory ones) > > - Right now (after commenting out stuff), datasource components just > registers datasources against JNDI. we have to think about a proper way of > incorporating tenant datasources,replicating, etc. > > > > we need some help to complete above tasks. :) > > [1] https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/ > > thanks, > --Pradeep > > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] WSO2 Gadget Server 2.0.0 Milestone-8 Released
Guys when do we plan to rename to UEC? Sanjiva. On Sat, Dec 8, 2012 at 8:32 PM, Ruchira Wageesha wrote: > *WSO2 Gadget Server 2.0.0 Milestone-8 Released* > > Milestone-8 of WSO2 Gadget Server 2.0 can be downloaded at [1]. It is a > complete rewrite of the Gadget Server 1.0 and is powered by jaggeryjs [2]. > This is the first milestone based on the asset store, which is a generic > artifact store based on WSO2 API Manager and WSO2 Governance Registry. > > *Usage* > >1. Asset store can be found at http://localhost:9763/store >2. Gadgets can be added into store by login into carbon admin console >and navigating to Metadata > Add > Gadget link >3. HTML mockups >- http://localhost:9763/samples/intro.html (HTML5 page > with embedded gadgets) > - http://localhost:9763/samples/store.html (New gadget store theme) > - http://localhost:9763/samples/climate-change.html (HTML5 page > with embedded gadgets) > > This milestone was basically targeted towards stabilizing asset store > based GS 2.0 build. You would encounter issues in functionality and UI, > which we are fixing towards next milestones. > > Thanks & Regards, > WSO2 Gadget Server Team > > [1] http://dist.wso2.org/milestone/gs/M8/wso2gs-2.0.0-SNAPSHOT.zip > [2] http://jaggeryjs.org > > -- > *Ruchira Wageesha > Senior Software Engineer & Member, Management Committee, Development > Technologies* > *WSO2 Inc. - lean . enterprise . middleware | wso2.com* > * > email: ruch...@wso2.com, blog: ruchirawageesha.blogspot.com, mobile: +94 > 77 5493444* > > ___ > Architecture mailing list > architect...@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] GReg-4.5.3-Alpha Released .!!
Subash do we normally "announce" alphas?? :-). On Fri, Nov 23, 2012 at 3:49 AM, Subash Chaturanga wrote: > Hi all, > GReg team pleased to announce the release of GReg-4.5.3-Alpha. > > *Download GReg-4.5.3-Alpha* > You can download the alpha binary distribution at [1] and the > documentation at [2]. > > *Issues Fixed* > The fixed issues and the open issues of GReg 4.5.3 can be found at [3]. > > > [1] - > https://svn.wso2.org/repos/wso2/people/subash/greg-4.5.3-alpha/wso2greg-4.5.3.zip > [2] - > https://svn.wso2.org/repos/wso2/people/subash/greg-4.5.3-alpha/wso2greg-4.5.3-docs.zip > > [3] - > https://wso2.org/jira/browse/REGISTRY/fixforversion/10716#atl_token=U1iP0lQ-Ol&selectedTab=com.atlassian.jira.plugin.system.project%3Aversion-issues-panel > -- > > Subash Chaturanga > Software Engineer > WSO2 Inc. http://wso2.com > > email - sub...@wso2.com > phone - 077 2225922 > > > ___ > Architecture mailing list > architect...@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Improvement to SecureVault API (SecretResolverFactory.create)
On Sat, Oct 27, 2012 at 6:39 AM, Afkham Azeez wrote: > On Sat, Oct 27, 2012 at 6:25 AM, Selvaratnam Uthaiyashankar < > shan...@wso2.com> wrote: > >> Hi, >> >> Check the following API (in 3.2.2 branch.. haven't checked in 4.0.0 >> branch) >> SecretResolver >> org.wso2.securevault.SecretResolverFactory.create(OMElement configuration, >> boolean isCapLetter) >> >> >> why do we need the parameter "isCapLetter"? If it is true, it is >> searching for an element "SecureVault" and if false, it is searching for >> "secureVault" element. However, this is not a userlevel parameter. This API >> does not look good :). >> >> > !!! yes, that is an implementation detail, and should never be part os the > API! > Not only that .. this is stuff that should not be configurable. Sanjiva. -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] Shall we move JDBC/AD/LDAP UserStoreManagers out of Carbon Kernel ?
On Fri, Oct 19, 2012 at 11:34 AM, Muhammed Shariq wrote: > What is the advantage? I guess, being able to improve >>>>> them independent of having to release the kernel? >>>>> >>>> >>>> Yes... This will help IS to be released in point releases with the same >>>> Carbon kernel.. >>>> >>> >>> Then I guess IS needs to be released before any other product. Or does >>> other other products have only the admin user login? >>> >> >> The model should be; >> >> 1. Release kernel or depend on a released version of the kernel >> 2. Release components - may be a selected subset >> > > In the current component structure isn't it a bit complicated to release a > subset of components. If we want to do this, we should group the > components preferably the products. That way we should be able to release a > set of components and the corresponding product .. WDYT ?! > I'm -1 on doing this. For faster execution (I mean in the engineering sense not runtime) its critical that Carbon kernel be a totally standalone thing. Why does the proposed change challenge that? Can't we have a simple default realm like tomcat-users.xml type thing built into our user-management.xml? Then if you want more than that you need the components that give you various capabilities like LDAP, JDBC etc.. If you want full stuff you get IS. I'm sure I'm missing some crucial info :). Sanjiva. -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] XML schema for RXT & LC
Samisa if there's a schema then we can use the Eclipse editor to get content assist etc. to help edit the RXT files. On Fri, Oct 5, 2012 at 10:13 AM, Samisa Abeysinghe wrote: > > > On Fri, Oct 5, 2012 at 10:10 AM, Senaka Fernando wrote: > >> Hi Samisa, >> >> Harshana and the team is already working on getting the tool side of it >> sorted out. Also, we have a road-map item to have a add-RXT page like the >> add-LC page. >> > > Unfortunately, the story is half baked without provision of these tooling > and supporting aspects. > > I wonder what the priorities are on the road-map aspects - in the global > optima, not in the local optima. > > > >> >> Thanks, >> Senaka. >> >> >> On Fri, Oct 5, 2012 at 9:56 AM, Samisa Abeysinghe wrote: >> >>> >>> >>> On Fri, Oct 5, 2012 at 9:43 AM, Senaka Fernando wrote: >>> >>>> Hi all, >>>> >>>> I think we should improve the docs to have this as a side note or even >>>> a sample (as to how to use the XSD to generate LC or RXT). I will work on >>>> getting this done. >>>> >>> >>> Well, actually, it is neither the doc nor the schema that we should >>> have, as that is tech detail. As a user, I would not care as long as I have >>> a tool to easily define RXTs. That would solve lot of problems. >>> >>> >>> >>>> >>>> Thanks, >>>> Senaka. >>>> >>>> On Fri, Oct 5, 2012 at 9:26 AM, Eranda Sooriyabandara >>>> wrote: >>>> >>>>> Hi Samisa >>>>> >>>>> On Fri, Oct 5, 2012 at 9:19 AM, Samisa Abeysinghe wrote: >>>>> >>>>>> Do we have schema defined for $subject? >>>>>> >>>>>> I am trying to see how I could do the least work and generate the RXT >>>>>> that I want, plus the LC for that. >>>>>> >>>>>> >>>>>> Yes, they are defined. You can find them in >>>>> CARBON_HOME/repository/resource/rxt.xsd >>>>> and CARBON_HOME/repository/resource/lifecycle-config.xsd. >>>>> >>>>> thanks >>>>> Eranda >>>>> * >>>>> * >>>>> >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Senaka Fernando* >>>> Member - Integration Technologies Management Committee; >>>> Technical Lead; WSO2 Inc.; http://wso2.com* >>>> Member; Apache Software Foundation; http://apache.org >>>> >>>> E-mail: senaka AT wso2.com >>>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >>>> Linked-In: http://linkedin.com/in/senakafernando >>>> >>>> *Lean . Enterprise . Middleware >>>> >>>> Thanks, >>> Samisa... >>> >>> Samisa Abeysinghe >>> VP Engineering >>> WSO2 Inc. >>> http://wso2.com >>> http://wso2.org >>> >>> >>> >> >> >> -- >> *Senaka Fernando* >> Member - Integration Technologies Management Committee; >> Technical Lead; WSO2 Inc.; http://wso2.com* >> Member; Apache Software Foundation; http://apache.org >> >> E-mail: senaka AT wso2.com >> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >> Linked-In: http://linkedin.com/in/senakafernando >> >> *Lean . Enterprise . Middleware >> >> Thanks, > Samisa... > > Samisa Abeysinghe > VP Engineering > WSO2 Inc. > http://wso2.com > http://wso2.org > > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Creating A Custom Mediator For XSLT Transfomation : Binary Relay Enabled ESB
VudjpFbnZlbG9wZT4= >>>>>> >>>>>> >>>>>> >>>>>> .Original SOAP Message >>>>>> http://schemas.xmlsoap.org/soap/envelope/";>>>>>> xmlns:wsa="http://www.w3.org/2005/08/addressing";> >>>>>> http://localhost:9000/services/SimpleStockQuoteServiceurn:uuid:0f7403b4-c5bc-4347-8921-562f2736a2aburn:getQuote>>>>> xmlns:m0="http://services.samples >>>>>> ">IBM >>>>>> >>>>>> >>>>>> >>>>>> Transforming On Progress. >>>>>> >>>>>> ...Transformed SOAP Message... >>>>>> http://services.samples";> >>>>>> >>>>>> IBM >>>>>> >>>>>> >>>>>> >>>>>> .. >>>>>> >>>>>> ...Transformed SOAP Envelop.. >>>>>> >>>>> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>>>>>> xmlns:ns="http://ws.apache.org/commons/ns/payload >>>>>> ">PG06Z2V0UXVvdGUgeG1sbnM6bT0iaHR0cDovL3NlcnZpY2VzLnNhbXBsZXMiPgogICA8bTpyZXF1ZXN0PgogICAgICA8bTpzeW1ib2w+SUJNPC9tOnN5bWJvbD4KICAgPC9tOnJlcXVlc3Q+CjwvbTpnZXRRdW90ZT4K >>>>>> >>>>>> .. >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> *Amila Suriarachchi* >>>>> >>>>> Software Architect >>>>> WSO2 Inc. ; http://wso2.com >>>>> lean . enterprise . middleware >>>>> >>>>> phone : +94 71 3082805 >>>>> >>>>> >>>> Any suggestions to overcome this problem ? >>>> >>>> Thanks >>>> AndunSLG >>>> >>>> [1] >>>> http://wso2.org/svn/browse/wso2/carbon/platform/branches/4.0.0/dependencies/synapse/2.1.0-wso2v7/modules/core/src/main/java/org/apache/synapse/mediators/transform/XSLTMediator.java?view=markup >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Hiranya Jayathilaka >>> Mayhem Lab/RACE Lab; >>> Dept. of Computer Science, UCSB; http://cs.ucsb.edu >>> E-mail: hira...@cs.ucsb.edu ; Mobile: +1 (805) >>> 895-7443 >>> Blog: http://techfeast-hiranya.blogspot.com >>> >> >> >> >> -- >> Hiranya Jayathilaka >> Mayhem Lab/RACE Lab; >> Dept. of Computer Science, UCSB; http://cs.ucsb.edu >> E-mail: hira...@cs.ucsb.edu ; Mobile: +1 (805) >> 895-7443 >> Blog: http://techfeast-hiranya.blogspot.com >> > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Announcement] WSO2 ESB 4.5.0 released
>protocol/ Financial Information eXchange protocol and optional Health >Level-7 protocol) >- Enhanced support for the VFS (File/FTP/SFTP), JMS, Mail transports >with optional TCP/UDP transports and transport switching among any of the >above transports >- Support for message splitting & aggregation using the EIP and >service callouts >- Database lookup & store support with DBMediators with reusable >database connection pools >- WS-Eventing support >- Rule based mediation of the messages using the Drools rule engine >- Transactions support via the JMS transport and Transaction mediator >for database mediators >- Internationalized GUI management console with user management for >configuration development >- Integrated monitoring support with statistics, configurable logging >and tracing >- JMX monitoring support and JMX management capabilities like, >Graceful/Forceful shutdown/restart > > Bugs Fixed in This Release > > This release of WSO2 ESB comes with a number of bug fixes, both in the > base framework and the ESB specific components. All the issues which have > been fixed in ESB 4.5.0 are recorded at following locations: > >- Fixed ESB specific > issues<https://wso2.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=10752> >- Fixed base framework > issues<https://wso2.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=10753> > > Known Issues > > All the open issues pertaining to WSO2 ESB 4.5.0 are reported at following > locations: > >- WSO2 ESB 4.5.0 component > issues<https://wso2.org/jira/secure/IssueNavigator.jspa?requestId=10524> >- WSO2 ESB 4.5.0 base framework > issues<https://wso2.org/jira/secure/IssueNavigator.jspa?requestId=10525> > > How You Can Contribute Mailing Lists > > Join our mailing list and correspond with the developers directly. > >- Developer List : dev@wso2.org | > Subscribe| Mail >Archive <http://mail.wso2.org/mailarchive/dev/> >- User List : esb-java-u...@wso2.org | > Subscribe| Mail >Archive <http://wso2.org/mailarchive/esb-java-user/> > > Reporting Issues > > We encourage you to report issues, documentation faults and feature > requests regarding WSO2 ESB through the public ESB > JIRA<http://www.wso2.org/jira/browse/ESBJAVA>. > You can use the Carbon JIRA <http://www.wso2.org/jira/browse/CARBON> to > report any issues related to the Carbon base framework or associated Carbon > components. > Discussion Forums > > Alternatively, questions could be raised on > http://stackoverflow.com<http://stackoverflow.com/questions/tagged/wso2>. > > Support > > We are committed to ensuring that your enterprise middleware deployment is > completely supported from evaluation to production. Our unique approach > ensures that all support leverages our open development methodology and is > provided by the very same engineers who build the technology. > > For more details and to take advantage of this unique opportunity please > visit http://wso2.com/support. > > For more information about WSO2 ESB please see > http://wso2.com/products/enterprise-service-bus. > > *-- The WSO2 ESB Team --* > > -- > Cheers, > Miyuru > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] WSO2 Gadget Server 2.0 Daily build (21/08/12)
I tried this and see one gadget :). I edited repository/deployment/server/jaggeryapps/portal/index.jag and it works :-). When do we ship?! BTW I got an exception at startup (but it booted up anyway): SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [bundleresource://190.fwk1790118163/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/Users/sanjiva/Downloads/wso2gs-2.0/repository/deployment/server/webapps/ROOT/WEB-INF/lib/slf4j-jdk14-1.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. 2012-08-22 18:17:17 Full thread dump Java HotSpot(TM) 64-Bit Server VM (20.8-b03-424 mixed mode): "com.google.inject.internal.util.$Finalizer" daemon prio=5 tid=7fec14b2b800 nid=0x1176cf000 in Object.wait() [1176ce000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <7d3b2e900> (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118) - locked <7d3b2e900> (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:134) at com.google.inject.internal.util.$Finalizer.run(Finalizer.java:114) What's SLF4J? Sanjiva. On Tue, Aug 21, 2012 at 5:27 PM, Nuwan Bandara wrote: > Hi All, > > Please find the *first daily build* of WSO2 Gadget Server 2.0 [1]. This > is a complete rewrite of the Gadget Server 1.0 and is powered by jaggeryjs > [2] > > We are targeting at *GS 2.0 Milestone-1* [3] > > Once the server is started http://localhost:9763/portal will take you to > the Jaggery powered page which embeds an open social gadget. > > [1] http://people.wso2.com/~nuwan/gs2/21-08-12/wso2gs-2.0.zip > [2] http://jaggeryjs.org > [3] https://wso2.org/jira/browse/GS/fixforversion/10611 > > -- > *Thanks & Regards, > > Nuwan Bandara > Associate Technical Lead & Member, MC, Development Technologies > WSO2 Inc. - lean . enterprise . middleware | http://wso2.com > blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763 > 9629 > * > <http://www.nuwanbando.com/> > > ___ > Architecture mailing list > architect...@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] [GReg] Why Retention is not part of Registry API ?
What is "retention"? On Sun, Jun 24, 2012 at 8:14 PM, Subash Chaturanga wrote: > Hi Senaka, > > Is there any particular reason $subject ? > This has implemented directly through an admin service and the retention > concept is not moved in to registry API. > AFAIU, it is good to have retention capability to a repository as it is a > fundamental concept. > > > Thanks > -- > > Subash Chaturanga > Software Engineer > WSO2 Inc. http://wso2.com > > email - sub...@wso2.com > phone - 077 2225922 > > > ___ > Architecture mailing list > architect...@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Dev-Jaggery] JavaScript Caching in Jaggery
I can't see the advantages of option 2 ... we have to assume every bit of JS is different so its not about sharing a .class. If we can have a lazy loading + unloading scheme in place then option 1 is fine IMO. We should be able to piggyback off the webapp lazyloading stuff? Sanjiva. On Thu, Jun 21, 2012 at 6:28 PM, Ruchira Wageesha wrote: > Hi all, > > We are using Rhino's script compilation support in Jaggery product to > improve the performance of JS execution. > > When we compiled a JS file using Rhino, we can get either > >1. An object(Script) of the *.class file > - This will be kept in memory and executed when ever needed > - When n webapps of m size in a jaggery server are equally > accessed, n x m memory will be needed in order keep all webapp objects > in > memory > - If the server doesn't have enough memory, then we will have to > recompile the same webapp time to time >2. A *.class file for that script > - In this way, we can save the *.class file to the disk and load it > using a custom classloader. > - In a muti-tenant environment, we can release the memory of unused > classloaders and load the classes on demand using saved *.class files > - As per my understanding, it would be able to server n webapps of > m size using less amount of memory than above 1 by unloading unused > classloaders and loading *.class on demand > > Currently it has been implemented to work in both modes, but I am not sure > which one would be ideal for the case. > > Welcome your thoughts > > regards, > Ruchira > > -- > *Ruchira Wageesha > Senior Software Engineer & Member, Management Committee, Development > Technologies* > *WSO2 Inc. - lean . enterprise . middleware | wso2.com* > * > email: ruch...@wso2.com, blog: ruchirawageesha.blogspot.com, mobile: +94 > 77 5493444* > > > ___________ > Dev mailing list > d...@jaggeryjs.org > http://mail.jaggeryjs.org/cgi-bin/mailman/listinfo/dev > > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Redesign of JavaScript SOAP services stub
Yes but that's the limitation we need to fix! Its not too hard .. its recursive application of the same rules :). On Mon, Jun 11, 2012 at 9:04 AM, Ruchira Wageesha wrote: > In the old model, it generates functions like [1] for operations. But when > it is a service with complex types, most probably function signature would > be [2]. In [2] userInfo is the whole soap body and we need to construct it > manually. No help from the stub for soap body creation. > > [1] function saveUser(username, birthday, addressLine1, addressLine2, > city, country) > [2] function saveUser(userInfo) > > On Sun, Jun 10, 2012 at 10:48 AM, Sanjiva Weerawarana wrote: > >> Why do we need to re-invent a solution .. can the JAX-WS style binding >> model not work? What we had was a similar model in the old mashup server. >> >> W.r.t. complex schemas- I don't understand why the old model doesn't >> support complex types. Note that I'm talking about the model not the XSLT >> based implementation. >> >> Sanjiva >> >> On Fri, Jun 1, 2012 at 3:40 PM, Ruchira Wageesha wrote: >> >>> Hi All, >>> >>> We are in the process of refactoring the SOAP web service JavaScript >>> stub. Before going through that, I need to highlight few stuff and come up >>> with a proper decision/architecture about the JS stub. >>> >>> Old Stub of MS >>> = >>> Old stub was mainly writted thinking about services in MS and it >>> generated methods for each operation in a service. This was absolutely >>> simple to consume services in Mashup Server as MS didn't allow to write a >>> service with complex schemas. i.e. In MS, we have only strings, numbers, >>> dates etc. and anytype elements only. >>> >>> Following is a set of JS service method signatures that we can write in >>> MS and relavent JS stub method signatures of them. >>> >>> *scenario1* - every parameter is a string >>> >>> Operation signature : function saveUser(username, birthday, >>> addressLine1, addressLine2, city, country) >>> Stub method signature : function saveUser(username, birthday, >>> addressLine1, addressLine2, city, country) >>> >>> *scenario2* - address parameter is anytype and rest are strings >>> >>> Operation signature : function saveUser(username, birthday, address) >>> Stub method signature : function saveUser(username, birthday, address) >>> >>> Here address is an anytype and we don't have any schema over that in the >>> WSDL. i.e. We had to document about the address schema. >>> >>> >>> >>> >>> >>> >>> >>> *scenario3* - userInfo is an anytype >>> >>> Operation signature : function saveUser(userInfo) >>> Stub method signature : function saveUser(userInfo) >>> >>> Here userInfo is an anytype and WSDL contain nothing about it. i.e. We >>> had to document about userInfo schema. >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> But when it comes to non-MS services, *scenario3* would be the common >>> case and with the old stub, it won't do much as we have to manually >>> contruct the userInfo payload string and pass it to the method. >>> >>> >>> The current stub >>> = >>> >>> op = operations["saveUser"]; >>> op(userInfo); >>> >>> A Modified version of the old stub, which allows you to pass either the >>> payload XML(as in the case of old stub) or payload JSON in Badgerfish >>> notation. This doesn't matter how complex the payload is. >>> >>> Only practical use of this stub is in it's Badgerfish mode. i.e. There >>> is a method to get a sample BF JSON of the payload. Then, user only need to >>> replace the relevant values of the BF JSON. After that, BF JSON will be >>> converted back to an XML string using a util function and send to the >>> endpoint. >>> >>> Further, instead of generating top level JS methods as in the old stub, >>> those functions are accessed using operation name from the operations >>> object. The reason behind that is, we can't have exact same WS operation >>> name as the JS method name. i.e. "-" are valid in WS operation names, but >>> invalid for JS variable names. >>>
Re: [Dev] Is API Manager in Bamboo?
H I don't understand that. Having nightly builds is a hallmark of open source projects and we are not keeping to that if we don't put it in bamboo. Sanjiva. On Wed, Jun 6, 2012 at 6:19 PM, Hiranya Jayathilaka wrote: > > > On Wed, Jun 6, 2012 at 6:10 PM, Paul Fremantle wrote: > >> $subject? > > > No, it's not a part of the default build profile yet. We'll add it once > the alpha is out. > > Thanks, > Hiranya > > >> >> Paul >> >> -- >> Paul Fremantle >> CTO and Co-Founder, WSO2 >> OASIS WS-RX TC Co-chair, VP, Apache Synapse >> >> UK: +44 207 096 0336 >> US: +1 646 595 7614 >> >> blog: http://pzf.fremantle.org >> twitter.com/pzfreo >> p...@wso2.com >> >> wso2.com Lean Enterprise Middleware >> >> Disclaimer: 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, retransmit, 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 >> >> > > > -- > Hiranya Jayathilaka > Senior Technical Lead; > WSO2 Inc.; http://wso2.org > E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 > Blog: http://techfeast-hiranya.blogspot.com > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Redesign of JavaScript SOAP services stub
Why do we need to re-invent a solution .. can the JAX-WS style binding model not work? What we had was a similar model in the old mashup server. W.r.t. complex schemas- I don't understand why the old model doesn't support complex types. Note that I'm talking about the model not the XSLT based implementation. Sanjiva On Fri, Jun 1, 2012 at 3:40 PM, Ruchira Wageesha wrote: > Hi All, > > We are in the process of refactoring the SOAP web service JavaScript stub. > Before going through that, I need to highlight few stuff and come up with a > proper decision/architecture about the JS stub. > > Old Stub of MS > = > Old stub was mainly writted thinking about services in MS and it generated > methods for each operation in a service. This was absolutely simple to > consume services in Mashup Server as MS didn't allow to write a service > with complex schemas. i.e. In MS, we have only strings, numbers, dates etc. > and anytype elements only. > > Following is a set of JS service method signatures that we can write in MS > and relavent JS stub method signatures of them. > > *scenario1* - every parameter is a string > > Operation signature : function saveUser(username, birthday, addressLine1, > addressLine2, city, country) > Stub method signature : function saveUser(username, birthday, > addressLine1, addressLine2, city, country) > > *scenario2* - address parameter is anytype and rest are strings > > Operation signature : function saveUser(username, birthday, address) > Stub method signature : function saveUser(username, birthday, address) > > Here address is an anytype and we don't have any schema over that in the > WSDL. i.e. We had to document about the address schema. > > > > > > > > *scenario3* - userInfo is an anytype > > Operation signature : function saveUser(userInfo) > Stub method signature : function saveUser(userInfo) > > Here userInfo is an anytype and WSDL contain nothing about it. i.e. We had > to document about userInfo schema. > > > > > > > > > > > > But when it comes to non-MS services, *scenario3* would be the common > case and with the old stub, it won't do much as we have to manually > contruct the userInfo payload string and pass it to the method. > > > The current stub > = > > op = operations["saveUser"]; > op(userInfo); > > A Modified version of the old stub, which allows you to pass either the > payload XML(as in the case of old stub) or payload JSON in Badgerfish > notation. This doesn't matter how complex the payload is. > > Only practical use of this stub is in it's Badgerfish mode. i.e. There is > a method to get a sample BF JSON of the payload. Then, user only need to > replace the relevant values of the BF JSON. After that, BF JSON will be > converted back to an XML string using a util function and send to the > endpoint. > > Further, instead of generating top level JS methods as in the old stub, > those functions are accessed using operation name from the operations > object. The reason behind that is, we can't have exact same WS operation > name as the JS method name. i.e. "-" are valid in WS operation names, but > invalid for JS variable names. > > > When the we consider a Java stub, it makes easier to consume the WS. But, > in JS case, we need to carefuly design the JS stub. i.e. As JavaScript is a > dynamically typed langague, we don't have much choices. > > In Java stub, it might generate a UserInfo bean, Address bean etc. But in > JS case, we won't need to have seperate objects as we can pass whole > UserInfo element as a JSON. Again mapping a JSON to a highly styped schema > is very difficult and we will have to find a way to preserve original > details of the XML payload such as namespaces, sequences etc. > > So without addressing those issues, JS stubs will be useless. I am not > sure whether there will be a perfect solution. But sometimes, we might have > the old stub for simple services such as MS, and none for services with > complex schemas. > > Anyway, we need to come up with a proper design/decision. > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Setting Javascript Standards/Conventions in WSO2
We also need to educate everyone on how to write "adapters" for services in Jaggery. We've got it a bit wrong in the API Store code by using Java stubs via host objects. The right approach should be to create a Jaggery module for the service starting with a generated stub. If necessary hand wrap it into a nicer experience and then push it out as a module so anyone can use it via "require". I think some *good* samples will help. Sanjiva. On Wed, May 23, 2012 at 1:05 PM, Nuwan Bandara wrote: > Hi All, > > Writing javascript code should not be considered lightly. It is as serious > as your server code. If you write crappy code and create bugs, > comparatively they are harder to find and solve; *During code reviews > please make sure following guidelines are also met for any javascript code > written by developers. * > > As a general standard for Javascript programming, developers need to > adhere to the javascript guide *[1]* originally published by Google. > > As for tools, > >- For code sanity check - JSLint [2] or Closure Linter [3] >- Javascript documentation - JSDoc-toolkit [4] >- Unit testing - QUnit [5], JSUnit [6] >- Javascript minification - JSMin [7], YUICompressor [8], Closure >Compiler [9] > > *What you MUST do* > >- All javascript that are written need to be checked against JSList. >This is something similar to find-bugs for java. >- All scripts that are being used across the platform need to be >minified, from any of the tools mentioned above. >- Create Unit tests for code javascript code you wright, use one of >the tools above. (QUnit proves to be easier) >- Try to do documentation as much as possible and use JSDoc to >generate documentation > > I have documented there guide lines at > https://sites.google.com/a/wso2.com/engineering/standards-conventions/javascript-standards-tools. > (for internal reference) If I have missed anything please do update the > document. > > With increase use of javascript as server-side language, I believe we need > conventions and guidelines in-place. We will be creating/modifying tools > such as JSLint, JSMin, JSDoc and QUnit to be compatible with Jaggery as > well. > > [1] http://google-styleguide.googlecode.com/svn/trunk/javascriptguide.xml > [2] https://code.google.com/p/jslint4java/ > [3] https://developers.google.com/closure/utilities/ > [4] http://code.google.com/p/jsdoc-toolkit/ > [5] http://docs.jquery.com/QUnit > [6] http://www.jsunit.net/ > [7] http://code.google.com/p/jsmin-ant-task/ > [8] http://developer.yahoo.com/yui/compressor/ > [9] https://developers.google.com/closure/compiler/ > > > -- > *Thanks & Regards, > > Nuwan Bandara > Associate Technical Lead & Member, MC, Development Technologies > WSO2 Inc. - lean . enterprise . middleware | http://wso2.com > blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763 > 9629 > * > <http://www.nuwanbando.com/> > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] First-class Support for C-Apps in G-Reg
Exactly Senaka. I've been thinking more about this and I think we need to make the "application" concept a top level G-Reg RXT and make CApp into an implementation of an application. Its that same application that may be consuming various APIs etc.. I'm trying to get my thoughts into a slide deck so we can have a good discussion about it - will share it soon. Sanjiva. On Sat, May 12, 2012 at 11:54 PM, Senaka Fernando wrote: > Hi Subash, > > I believe that you are quoting a POC that we did originally. But, in the > context of a generic C-App governance implementation, > > 1. I wouldn't tie a C-App to a project. This is because a single project > could produce more than one C-App. What do you call this in Developer > Studio? > 2. I would move the C-App inside the application folder structure, making > it possible for the C-App to change/evolve along with the application. > 3. We also have some interest in tying up Application in API Store with > C-Apps, which we probably need to sort out as well (but as a part of the > G-Reg and API Store alignment stuff). > > Thanks, > Senaka. > > On Sat, May 12, 2012 at 5:08 PM, Subash Chaturanga wrote: > >> Hi all, >> Following is the screen shot of the $subject. In fact this is the front >> end view. >> >> Here, please note the newly added 3 governance artifacts. >> - Applications >> - Servers >> - Environments >> >> In brief, >> - We can add servers by giving a carbon server endpoint with credentials >> along with a suitable name. >> - And environments can be created and attach multiple servers (which >> were already created) to it. >> - Then we can create our project with multiple such environments. And >> there we should give a car file location from the repository(currently). >> >> And the car will get deployed in the given carbon server when the project >> created. >> >> Hi Senaka, >> Following will be some points to be considered if greg gonna ship with >> this functionality. >> >> - As per your suggestion, already renamed "Projecst" RXT to >> "Applications" and the location of the car file storage. >> >> * The car file is currently added through a remote client. But we can >> make it done through the application RXT. >> * And the car files currently gets stored inside >> /_system/governance/carbonapps. And when the Application evolves through a >> LC, the car file not get migrated. >> But stored in a separate place as mentioned above. If the car file not >> gonna change, it is seems OK to not to migrate it to branches with LC state >> and keep it separate. >> And as it is not likely to happen, I also don't think that's a good idea >> to keep it separate. Shall we put it >> inside/applications/myapplication_1/ >> >> Any ideas ? >> >> Please add any missing/required facts needs to be considered. >> >> >> >> Thanks >> -- >> >> Subash Chaturanga >> Software Engineer >> WSO2 Inc. http://wso2.com >> >> email - sub...@wso2.com >> phone - 077 2225922 >> >> > > > -- > *Senaka Fernando* > Product Manager - WSO2 Governance Registry; > Associate Technical Lead; WSO2 Inc.; http://wso2.com* > Member; Apache Software Foundation; http://apache.org > > E-mail: senaka AT wso2.com > **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 > Linked-In: http://linkedin.com/in/senakafernando > > *Lean . Enterprise . Middleware > > > ___ > Architecture mailing list > architect...@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] What would be the WSO2 LB product version?
Or maybe we should call it LB2 1.0? ;-) On Thu, May 10, 2012 at 3:12 PM, Sameera Jayasoma wrote: > > > On Thu, May 10, 2012 at 3:08 PM, Paul Fremantle wrote: > >> +1 for 2.0. Or should that be +2? > > > Great. We will update the version as 2.0. +2 would be perfect :) > > Thanks, > Sameera. > >> >> Paul >> >> >> On 10 May 2012 10:28, Sameera Jayasoma wrote: >> >>> >>> >>> On Tue, May 8, 2012 at 9:17 AM, Nirmal Fernando wrote: >>> >>>> >>>> >>>> On Tue, May 8, 2012 at 12:06 AM, Sameera Jayasoma wrote: >>>> >>>>> Hi Folks, >>>>> >>>>> At the moment the version is specified as 1.0.0-SNAPSHOT. We need to >>>>> change this. >>>>> >>>>> We released 1.0.0, 1.0.1, 1.0.2 versions AFAIK. But in this release we >>>>> have many more new features and enhancements. >>>>> >>>>> Shall we call 2.0? WDYT? >>>>> >>>> >>>> +1, LB has a totally new look now :) >>>> >>>> >>> Great. Shall we go ahead with 2.0? Or If you have any other concerns, >>> please holler.. >>> >>> Thanks, >>> Sameera. >>> >>>> >>>>> Thanks, >>>>> Sameera. >>>>> >>>>> -- >>>>> Sameera Jayasoma >>>>> Technical Lead >>>>> >>>>> WSO2, Inc. (http://wso2.com) >>>>> email: same...@wso2.com >>>>> blog: http://tech.jayasoma.org >>>>> >>>>> Lean . Enterprise . Middleware >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> Thanks & regards, >>>> Nirmal >>>> >>>> Software Engineer- Platform Technologies Team, WSO2 Inc. >>>> Mobile: +94715779733 >>>> Blog: http://nirmalfdo.blogspot.com/ >>>> >>> >>> >>> >>> -- >>> Sameera Jayasoma >>> Technical Lead >>> >>> WSO2, Inc. (http://wso2.com) >>> email: same...@wso2.com >>> blog: http://tech.jayasoma.org >>> >>> Lean . Enterprise . Middleware >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Paul Fremantle >> CTO and Co-Founder, WSO2 >> OASIS WS-RX TC Co-chair, VP, Apache Synapse >> >> UK: +44 207 096 0336 >> US: +1 646 595 7614 >> >> blog: http://pzf.fremantle.org >> twitter.com/pzfreo >> p...@wso2.com >> >> wso2.com Lean Enterprise Middleware >> >> Disclaimer: 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, retransmit, 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. >> >> > > > -- > Sameera Jayasoma > Technical Lead > > WSO2, Inc. (http://wso2.com) > email: same...@wso2.com > blog: http://tech.jayasoma.org > > Lean . Enterprise . Middleware > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Autoscaling with LXCs demo -2
Nirmal what you're saying and what Azeez said are not in sync. Can you guys get together and agree and then I'll try to map it to my mental model :). BTW WSO2 LB can route and LB anything not just WSO2 stuff. Its just an HTTP load balancer. Sanjiva. On Wed, May 9, 2012 at 5:56 AM, Nirmal Fernando wrote: > Hi Sanjiva, > > On Tue, May 8, 2012 at 10:38 PM, Sanjiva Weerawarana wrote: > >> Nirmal that can't be right .. the newly spawned LXC instance can be >> running anything, including PHP. > > > True that! > > That means there has to be something in that (started by rc.local) that >> talks back to our controller and allows us to manage it. > > > In the case of WSO2 servers it's to the WSO2 LB, that the newly started > server get joined. In the case of PHP, AFAIK there's a different LB. > > As per now, Controller only manages, from which adapter it should ask to > spawn the new instance, from which adapter it should ask to terminate an > existing instance. > > To be more clearer Controller talks only to Agents in each host machine, > not to the each LXC in a host machine. It's the respective LB talks with > newly spawned instances. > > Do you prefer Controller to have control over LXCs too? > > >> We need to get this terminology straight .. if that's not the agent then >> what's that code called? What does the controller outside of the host do? >> Where does it run? >> >> Sanjiva. >> >> On Tue, May 8, 2012 at 9:05 PM, Nirmal Fernando wrote: >> >>> Hi Sanjiva, >>> >>> On Tue, May 8, 2012 at 8:40 PM, Sanjiva Weerawarana wrote: >>> >>>> Yeah so Tropos is basically a new kinda IaaS and it has a controller >>>> (which is a Carbon server) which goes in the host machine and an agent >>>> (which is also a Carbon server) which goes inside the LXC itself. >>> >>> >>> Controller resides in a separate machine, and agent resides in the host >>> machine. It's the newly spawned Carbon server which resides in the LXC. >>> >>> >>>> We should make a new commons project or something and have that project >>>> take a dependency on a version of Carbon (even an old version is fine >>>> really) from Maven. >>>> >>>> Right?? >>>> >>>> Sanjiva. >>>> >>>> On Mon, May 7, 2012 at 5:51 PM, Afkham Azeez wrote: >>>> >>>>> Currently all the Tropos related code live under components/tropos. >>>>> May be we should move it to a better place in the SVN. >>>>> >>>>> On Mon, May 7, 2012 at 4:32 PM, Sanjiva Weerawarana >>>>> wrote: >>>>> >>>>>> So is Tropos effectively an IaaS (for autoscaling within a set of >>>>>> worker nodes via LXCs) .. if so we should carefully separate Tropos out >>>>>> as >>>>>> a separate project. In that case Tropos Controller is fine. >>>>>> >>>>>> Sanjiva. >>>>>> >>>>>> >>>>>> On Mon, May 7, 2012 at 9:39 AM, Afkham Azeez wrote: >>>>>> >>>>>>> Controller might not be the best term to use, but what we discussed >>>>>>> was, all this Tropos stuff is related to IaaS, and not PaaS. In PaaS, >>>>>>> controller has a special meaning as per the Gartner definition & >>>>>>> includes >>>>>>> BAM/B&M/IdentityMgt etc. For lack of a better term, I think calling this >>>>>>> Tropos controller will be OK, and there will be no confusion since this >>>>>>> is >>>>>>> at the IaaS layer. >>>>>>> >>>>>>> >>>>>>> On Mon, May 7, 2012 at 9:31 AM, Lahiru Sandaruwan >>>>>>> wrote: >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Mon, May 7, 2012 at 7:59 AM, Sanjiva Weerawarana < >>>>>>>> sanj...@wso2.com> wrote: >>>>>>>> >>>>>>>>> Damitha you guys can't take the name "Stratos Controller" .. >>>>>>>>> that's what we're using for the full group of stuff that "controls" >>>>>>>>> Stratos: manager, IS, G-Reg, BAM, B&M etc.. >>>>>>>> >>>>>>>> What we've decided in the last dem
Re: [Dev] Autoscaling with LXCs demo -2
Nirmal that can't be right .. the newly spawned LXC instance can be running anything, including PHP. That means there has to be something in that (started by rc.local) that talks back to our controller and allows us to manage it. We need to get this terminology straight .. if that's not the agent then what's that code called? What does the controller outside of the host do? Where does it run? Sanjiva. On Tue, May 8, 2012 at 9:05 PM, Nirmal Fernando wrote: > Hi Sanjiva, > > On Tue, May 8, 2012 at 8:40 PM, Sanjiva Weerawarana wrote: > >> Yeah so Tropos is basically a new kinda IaaS and it has a controller >> (which is a Carbon server) which goes in the host machine and an agent >> (which is also a Carbon server) which goes inside the LXC itself. > > > Controller resides in a separate machine, and agent resides in the host > machine. It's the newly spawned Carbon server which resides in the LXC. > > >> We should make a new commons project or something and have that project >> take a dependency on a version of Carbon (even an old version is fine >> really) from Maven. >> >> Right?? >> >> Sanjiva. >> >> On Mon, May 7, 2012 at 5:51 PM, Afkham Azeez wrote: >> >>> Currently all the Tropos related code live under components/tropos. May >>> be we should move it to a better place in the SVN. >>> >>> On Mon, May 7, 2012 at 4:32 PM, Sanjiva Weerawarana wrote: >>> >>>> So is Tropos effectively an IaaS (for autoscaling within a set of >>>> worker nodes via LXCs) .. if so we should carefully separate Tropos out as >>>> a separate project. In that case Tropos Controller is fine. >>>> >>>> Sanjiva. >>>> >>>> >>>> On Mon, May 7, 2012 at 9:39 AM, Afkham Azeez wrote: >>>> >>>>> Controller might not be the best term to use, but what we discussed >>>>> was, all this Tropos stuff is related to IaaS, and not PaaS. In PaaS, >>>>> controller has a special meaning as per the Gartner definition & includes >>>>> BAM/B&M/IdentityMgt etc. For lack of a better term, I think calling this >>>>> Tropos controller will be OK, and there will be no confusion since this is >>>>> at the IaaS layer. >>>>> >>>>> >>>>> On Mon, May 7, 2012 at 9:31 AM, Lahiru Sandaruwan wrote: >>>>> >>>>>> >>>>>> >>>>>> On Mon, May 7, 2012 at 7:59 AM, Sanjiva Weerawarana >>>>> > wrote: >>>>>> >>>>>>> Damitha you guys can't take the name "Stratos Controller" .. that's >>>>>>> what we're using for the full group of stuff that "controls" Stratos: >>>>>>> manager, IS, G-Reg, BAM, B&M etc.. >>>>>> >>>>>> What we've decided in the last demo meeting was to call this "Tropos >>>>>> controller" since the Stratos controller is given to above. >>>>>> >>>>>>> >>>>>>> Please review the slide deck on Stratos scaling and you'll see the >>>>>>> terms. We used to call that whole thing the manager but that made no >>>>>>> sense >>>>>>> because we have a thing inside called manager too. >>>>>>> >>>>>>> Sanjiva. >>>>>>> >>>>>>> On Mon, May 7, 2012 at 6:26 AM, Damitha Kumarage >>>>>>> wrote: >>>>>>> >>>>>>>> And it was discussed that we should have a controller pack as part >>>>>>>> of the release >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Damitha >>>>>>>> >>>>>>>> >>>>>>>> On Sun, May 6, 2012 at 1:43 AM, Sajith Kariyawasam >>>>>>> > wrote: >>>>>>>> >>>>>>>>> Further, we will need to investigate as to why it takes more than >>>>>>>>> expected time for the LB to receive the 'Join' message when an app >>>>>>>>> server >>>>>>>>> is started inside a container >>>>>>>>> >>>>>>>>> Also, it was suggested that we should test this with multiple >>>>>>>>> domains (not only AS, but also ESB.. etc) >>>>>>&g
Re: [Dev] Merging of products & services?
+1 to this plan .. right move IMO. Sanjiva. On Tue, May 8, 2012 at 3:13 PM, Selvaratnam Uthaiyashankar wrote: > Hi Folks, > > Samisa, Azzez and me had a chat about this and decided to go ahead > with merging. > > So, release managers, please merge the product and services, and move > the product folder to "attic". You might have to check the theme of > "super tenant". It should be same as the product theme. > > Also, we should run the integration tests as tenant mode as well. i.e. > each integration test should be run in "super tenant" mode (to test > product functionality) and "tenant" mode (to test multi-tenancy). > > Release owners and release managers, please note. > > Regards, > Shankar > > On Thu, Mar 22, 2012 at 8:05 PM, Afkham Azeez wrote: > > Have the respective product teams started looking into this? > > > > -- > > 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 > > > > > > -- > S.Uthaiyashankar > Senior Software Architect > Chair, Management Committee – Cloud Technologies > WSO2 Inc. > http://wso2.com/ - "lean . enterprise . middleware" > > Phone: +94 714897591 > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Autoscaling with LXCs demo -2
Yeah so Tropos is basically a new kinda IaaS and it has a controller (which is a Carbon server) which goes in the host machine and an agent (which is also a Carbon server) which goes inside the LXC itself. We should make a new commons project or something and have that project take a dependency on a version of Carbon (even an old version is fine really) from Maven. Right?? Sanjiva. On Mon, May 7, 2012 at 5:51 PM, Afkham Azeez wrote: > Currently all the Tropos related code live under components/tropos. May be > we should move it to a better place in the SVN. > > On Mon, May 7, 2012 at 4:32 PM, Sanjiva Weerawarana wrote: > >> So is Tropos effectively an IaaS (for autoscaling within a set of worker >> nodes via LXCs) .. if so we should carefully separate Tropos out as a >> separate project. In that case Tropos Controller is fine. >> >> Sanjiva. >> >> >> On Mon, May 7, 2012 at 9:39 AM, Afkham Azeez wrote: >> >>> Controller might not be the best term to use, but what we discussed was, >>> all this Tropos stuff is related to IaaS, and not PaaS. In PaaS, controller >>> has a special meaning as per the Gartner definition & includes >>> BAM/B&M/IdentityMgt etc. For lack of a better term, I think calling this >>> Tropos controller will be OK, and there will be no confusion since this is >>> at the IaaS layer. >>> >>> >>> On Mon, May 7, 2012 at 9:31 AM, Lahiru Sandaruwan wrote: >>> >>>> >>>> >>>> On Mon, May 7, 2012 at 7:59 AM, Sanjiva Weerawarana >>>> wrote: >>>> >>>>> Damitha you guys can't take the name "Stratos Controller" .. that's >>>>> what we're using for the full group of stuff that "controls" Stratos: >>>>> manager, IS, G-Reg, BAM, B&M etc.. >>>> >>>> What we've decided in the last demo meeting was to call this "Tropos >>>> controller" since the Stratos controller is given to above. >>>> >>>>> >>>>> Please review the slide deck on Stratos scaling and you'll see the >>>>> terms. We used to call that whole thing the manager but that made no sense >>>>> because we have a thing inside called manager too. >>>>> >>>>> Sanjiva. >>>>> >>>>> On Mon, May 7, 2012 at 6:26 AM, Damitha Kumarage wrote: >>>>> >>>>>> And it was discussed that we should have a controller pack as part of >>>>>> the release >>>>>> >>>>>> Thanks, >>>>>> Damitha >>>>>> >>>>>> >>>>>> On Sun, May 6, 2012 at 1:43 AM, Sajith Kariyawasam >>>>>> wrote: >>>>>> >>>>>>> Further, we will need to investigate as to why it takes more than >>>>>>> expected time for the LB to receive the 'Join' message when an app >>>>>>> server >>>>>>> is started inside a container >>>>>>> >>>>>>> Also, it was suggested that we should test this with multiple >>>>>>> domains (not only AS, but also ESB.. etc) >>>>>>> >>>>>>> Regarding the introductory presentation, I think its better to add >>>>>>> Agent registration part and some of the controller's functionalities >>>>>>> (persistence) so that the overall picture gets more clearer. >>>>>>> >>>>>>> >>>>>>> On Fri, May 4, 2012 at 8:52 PM, Nirmal Fernando wrote: >>>>>>> >>>>>>>> Hi All, >>>>>>>> >>>>>>>> Today we had another demo. >>>>>>>> >>>>>>>> Participants were: Azeez, Srinath, Dimuthu, Damitha, Sameera, >>>>>>>> Pradeep, Ranga, Lahiru, Sajith and myself. >>>>>>>> >>>>>>>> First we gave a brief overview of the autoscaling architecture. >>>>>>>> Then we started the demo. >>>>>>>> >>>>>>>> We were able to demo end-end (LB -> Controller --> Agent) scenario >>>>>>>> for spawning an instance (through LB sanity check) and termination of >>>>>>>> an >>>>>>>> instance (through scaling down call) within a LXC container. >>>>>>>> >>>>>>>
Re: [Dev] Autoscaling with LXCs demo -2
So is Tropos effectively an IaaS (for autoscaling within a set of worker nodes via LXCs) .. if so we should carefully separate Tropos out as a separate project. In that case Tropos Controller is fine. Sanjiva. On Mon, May 7, 2012 at 9:39 AM, Afkham Azeez wrote: > Controller might not be the best term to use, but what we discussed was, > all this Tropos stuff is related to IaaS, and not PaaS. In PaaS, controller > has a special meaning as per the Gartner definition & includes > BAM/B&M/IdentityMgt etc. For lack of a better term, I think calling this > Tropos controller will be OK, and there will be no confusion since this is > at the IaaS layer. > > > On Mon, May 7, 2012 at 9:31 AM, Lahiru Sandaruwan wrote: > >> >> >> On Mon, May 7, 2012 at 7:59 AM, Sanjiva Weerawarana wrote: >> >>> Damitha you guys can't take the name "Stratos Controller" .. that's what >>> we're using for the full group of stuff that "controls" Stratos: manager, >>> IS, G-Reg, BAM, B&M etc.. >> >> What we've decided in the last demo meeting was to call this "Tropos >> controller" since the Stratos controller is given to above. >> >>> >>> Please review the slide deck on Stratos scaling and you'll see the >>> terms. We used to call that whole thing the manager but that made no sense >>> because we have a thing inside called manager too. >>> >>> Sanjiva. >>> >>> On Mon, May 7, 2012 at 6:26 AM, Damitha Kumarage wrote: >>> >>>> And it was discussed that we should have a controller pack as part of >>>> the release >>>> >>>> Thanks, >>>> Damitha >>>> >>>> >>>> On Sun, May 6, 2012 at 1:43 AM, Sajith Kariyawasam wrote: >>>> >>>>> Further, we will need to investigate as to why it takes more than >>>>> expected time for the LB to receive the 'Join' message when an app server >>>>> is started inside a container >>>>> >>>>> Also, it was suggested that we should test this with multiple domains >>>>> (not only AS, but also ESB.. etc) >>>>> >>>>> Regarding the introductory presentation, I think its better to add >>>>> Agent registration part and some of the controller's functionalities >>>>> (persistence) so that the overall picture gets more clearer. >>>>> >>>>> >>>>> On Fri, May 4, 2012 at 8:52 PM, Nirmal Fernando wrote: >>>>> >>>>>> Hi All, >>>>>> >>>>>> Today we had another demo. >>>>>> >>>>>> Participants were: Azeez, Srinath, Dimuthu, Damitha, Sameera, >>>>>> Pradeep, Ranga, Lahiru, Sajith and myself. >>>>>> >>>>>> First we gave a brief overview of the autoscaling architecture. Then >>>>>> we started the demo. >>>>>> >>>>>> We were able to demo end-end (LB -> Controller --> Agent) scenario >>>>>> for spawning an instance (through LB sanity check) and termination of an >>>>>> instance (through scaling down call) within a LXC container. >>>>>> >>>>>> Few suggestions came up: >>>>>> >>>>>> 1. Create separate carbon instances (rather than using Appservers) >>>>>> for controller and agent. >>>>>> 2. Create a simple UI for controller to show instances spawned in >>>>>> each adapter, instances belong to a particular domain etc. >>>>>> 3. Fixing the domain related issue in AutoscaleInMediator (This arose >>>>>> with the changes in loadbalancer.conf to reflect tenant aware load >>>>>> balancing). >>>>>> 4. Fixing the routing issue using Azeez's fix to Axis2. >>>>>> 5. Make scaling up demonstrable using a back-end service which has >>>>>> some processing (or having a Thread.sleep(..) call). >>>>>> >>>>>> Please add anything I've missed! >>>>>> >>>>>> PS: We'll repeat the demo next week (hopefully with some more >>>>>> improvements next week, for Sanjiva, Paul and anyone interested). >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> Thanks & regards, >>>>>> Nirmal >>>>>> >&g
Re: [Dev] Connecting to mysql from Jaggery
On Fri, May 4, 2012 at 5:01 PM, Nuwan Bandara wrote: > > Yeah :( had no choice, The driver name is optional in JDBC4, but the > tomcat datasource IMPL has written making it mandatory. Anjana told that he > will submit a patch for that. even so, I dont think it will work in our > OSGI environment. > > SO even though its ugly to specify a java class name in a Javascript API, > we got no other option for now. > Nuwan lets write a host object then for MySQL connection specifically and put that bit inside that object. We can't have Java name visibile in Jaggery. Do we have a "server.conf" type thing in addition to per-application config? In that case we could have a way to configure DB drivers there. Having some exposure of Java in the server configuration is still criminal but not a show-stopper as putting it in the API IMO. Sanjiva. -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Autoscaling with LXCs demo -2
Damitha you guys can't take the name "Stratos Controller" .. that's what we're using for the full group of stuff that "controls" Stratos: manager, IS, G-Reg, BAM, B&M etc.. Please review the slide deck on Stratos scaling and you'll see the terms. We used to call that whole thing the manager but that made no sense because we have a thing inside called manager too. Sanjiva. On Mon, May 7, 2012 at 6:26 AM, Damitha Kumarage wrote: > And it was discussed that we should have a controller pack as part of the > release > > Thanks, > Damitha > > > On Sun, May 6, 2012 at 1:43 AM, Sajith Kariyawasam wrote: > >> Further, we will need to investigate as to why it takes more than >> expected time for the LB to receive the 'Join' message when an app server >> is started inside a container >> >> Also, it was suggested that we should test this with multiple domains >> (not only AS, but also ESB.. etc) >> >> Regarding the introductory presentation, I think its better to add Agent >> registration part and some of the controller's functionalities >> (persistence) so that the overall picture gets more clearer. >> >> >> On Fri, May 4, 2012 at 8:52 PM, Nirmal Fernando wrote: >> >>> Hi All, >>> >>> Today we had another demo. >>> >>> Participants were: Azeez, Srinath, Dimuthu, Damitha, Sameera, Pradeep, >>> Ranga, Lahiru, Sajith and myself. >>> >>> First we gave a brief overview of the autoscaling architecture. Then we >>> started the demo. >>> >>> We were able to demo end-end (LB -> Controller --> Agent) scenario for >>> spawning an instance (through LB sanity check) and termination of an >>> instance (through scaling down call) within a LXC container. >>> >>> Few suggestions came up: >>> >>> 1. Create separate carbon instances (rather than using Appservers) for >>> controller and agent. >>> 2. Create a simple UI for controller to show instances spawned in each >>> adapter, instances belong to a particular domain etc. >>> 3. Fixing the domain related issue in AutoscaleInMediator (This arose >>> with the changes in loadbalancer.conf to reflect tenant aware load >>> balancing). >>> 4. Fixing the routing issue using Azeez's fix to Axis2. >>> 5. Make scaling up demonstrable using a back-end service which has some >>> processing (or having a Thread.sleep(..) call). >>> >>> Please add anything I've missed! >>> >>> PS: We'll repeat the demo next week (hopefully with some more >>> improvements next week, for Sanjiva, Paul and anyone interested). >>> >>> >>> -- >>> >>> Thanks & regards, >>> Nirmal >>> >>> Software Engineer- Platform Technologies Team, WSO2 Inc. >>> Mobile: +94715779733 >>> Blog: http://nirmalfdo.blogspot.com/ >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Sajith Kariyawasam* >> *Senior Software Engineer; WSO2, Inc.; http://wso2.com* >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > __ > Damitha Kumarage > Technical Leader; WSO2 Inc. > Oxygenating the Web Service Platform > http://www.wso2.com/ > blog: > http://damithakumarage.wordpress.com/ > __ > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Possible solution for routing messages from the LB into the Carbon processes within the LXCs
Guys please keep this level of conversation on architecture@ .. moving. Sanjiva. On Wed, May 2, 2012 at 8:30 AM, Sanjiva Weerawarana wrote: > This is awesome Azeez - much better than adding routes to the LB node! > > I've been thinking about the network address problem .. what set of IPs to > use for the LXCs. Using 10.* or 192.168.* requires manual intervention > because anything we pick may be an already used network the organization .. > and those will then become inaccessible to any app running inside an LXC. > > I looked at 169.254 and it looks like that's an option. See [1][2][3] .. > its called a "link local" address and it seems like the right thing for us > to use. So we'd give say 169.254.99.* for the internal boxes and have > iptables forward the ports to those. Looks like we can simply bring up the > LXC, have it pick up whatever IP in the 169.254 range and then add a > default route to the host IP and register itself with the host (host IP > would have to be a boot param). > > [1] http://en.wikipedia.org/wiki/Private_network > [2] http://tools.ietf.org/html/rfc5735 > [3] http://tools.ietf.org/html/rfc3927 > > Sanjiva. > > On Tue, May 1, 2012 at 11:05 PM, Afkham Azeez wrote: > >> I have got this working for the well-known membership scheme. Let's test >> it with the LXC setup tomorrow. The route addition to the LB machine is not >> a scalable approach since we will need to do this in all worker node >> machines as well since the members in a cluster should be able to >> communicate with each other. >> >> >> On Tue, May 1, 2012 at 9:25 PM, Afkham Azeez wrote: >> >>> I just went through the Tribes code and figured out that the local >>> member host and bind address can be configured to be different values. It >>> is the localMemberHost that is advertised by Tribes while >>> the localMemberBindAddress is the IP address used for binding the server >>> socket. I will make the necessary changes to Axis2 and inform this list. My >>> plan is to add a new optional parameter called localMemberBindAddress to >>> the axis2.xml's clustering section, in addition to the already existing >>> localMemberHost. If localMemberBindAddress is not specified, we assume that >>> it is same as the localMemberHost. >>> >>> e.g. >>> 10.100.3.67 >>> >>> 192.168.1.121 >>> >>> >>> Then we have to setup iptables on the physical machine to do port >>> forwarding. In this model, we have to make sure that all Carbon processes >>> started within LXCs have unique ports. Otherwise the port forwarding will >>> not work. >>> >>> Thoughts welcome. >>> >>> -- >>> *Afkham Azeez* >>> Director of Architecture; WSO2, Inc.; http://wso2.com >>> Member; Apache Software Foundation; http://www.apache.org/ >>> * <http://www.apache.org/>** >>> email: **az...@wso2.com* * cell: +94 77 3320919 >>> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >>> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>> * >>> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >>> * >>> * >>> *Lean . Enterprise . Middleware* >>> >>> >> >> >> -- >> *Afkham Azeez* >> Director of Architecture; WSO2, Inc.; http://wso2.com >> Member; Apache Software Foundation; http://www.apache.org/ >> * <http://www.apache.org/>** >> email: **az...@wso2.com* * cell: +94 77 3320919 >> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >> twitter: **http://twitter.com/afkham_azeez*<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 >> >> > > > -- > Sanjiva Weerawarana, Ph.D. > Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ > email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 > 650 265 8311 > blog: http://sanjiva.weerawarana.org/ > > > Lean . Enterprise . Middleware > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Possible solution for routing messages from the LB into the Carbon processes within the LXCs
This is awesome Azeez - much better than adding routes to the LB node! I've been thinking about the network address problem .. what set of IPs to use for the LXCs. Using 10.* or 192.168.* requires manual intervention because anything we pick may be an already used network the organization .. and those will then become inaccessible to any app running inside an LXC. I looked at 169.254 and it looks like that's an option. See [1][2][3] .. its called a "link local" address and it seems like the right thing for us to use. So we'd give say 169.254.99.* for the internal boxes and have iptables forward the ports to those. Looks like we can simply bring up the LXC, have it pick up whatever IP in the 169.254 range and then add a default route to the host IP and register itself with the host (host IP would have to be a boot param). [1] http://en.wikipedia.org/wiki/Private_network [2] http://tools.ietf.org/html/rfc5735 [3] http://tools.ietf.org/html/rfc3927 Sanjiva. On Tue, May 1, 2012 at 11:05 PM, Afkham Azeez wrote: > I have got this working for the well-known membership scheme. Let's test > it with the LXC setup tomorrow. The route addition to the LB machine is not > a scalable approach since we will need to do this in all worker node > machines as well since the members in a cluster should be able to > communicate with each other. > > > On Tue, May 1, 2012 at 9:25 PM, Afkham Azeez wrote: > >> I just went through the Tribes code and figured out that the local member >> host and bind address can be configured to be different values. It is the >> localMemberHost that is advertised by Tribes while >> the localMemberBindAddress is the IP address used for binding the server >> socket. I will make the necessary changes to Axis2 and inform this list. My >> plan is to add a new optional parameter called localMemberBindAddress to >> the axis2.xml's clustering section, in addition to the already existing >> localMemberHost. If localMemberBindAddress is not specified, we assume that >> it is same as the localMemberHost. >> >> e.g. >> 10.100.3.67 >> >> 192.168.1.121 >> >> >> Then we have to setup iptables on the physical machine to do port >> forwarding. In this model, we have to make sure that all Carbon processes >> started within LXCs have unique ports. Otherwise the port forwarding will >> not work. >> >> Thoughts welcome. >> >> -- >> *Afkham Azeez* >> Director of Architecture; WSO2, Inc.; http://wso2.com >> Member; Apache Software Foundation; http://www.apache.org/ >> * <http://www.apache.org/>** >> email: **az...@wso2.com* * cell: +94 77 3320919 >> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >> * >> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >> * >> * >> *Lean . Enterprise . Middleware* >> >> > > > -- > *Afkham Azeez* > Director of Architecture; WSO2, Inc.; http://wso2.com > Member; Apache Software Foundation; http://www.apache.org/ > * <http://www.apache.org/>** > email: **az...@wso2.com* * cell: +94 77 3320919 > blog: **http://blog.afkham.org* <http://blog.afkham.org>* > twitter: **http://twitter.com/afkham_azeez*<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 > > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] Verification/ Health Check Code or Page for Carbon
+1. On Tue, Apr 3, 2012 at 9:24 PM, Afkham Azeez wrote: > Folks, > I'm reviving an almost 3 year old thread. The thing is, we still don't > have the following implemented, and we need it today as much as we needed > it 3 years ago. We are seeing that from time to time, the server hangs > without properly starting up during tests. There should be an underlying > root cause that is triggering this. If we had a health check module which > we fire up before starting Carbon core, we can perform some OSGi level > checks and print warning logs. > > Azeez > > On Fri, Aug 7, 2009 at 12:47 PM, Srinath Perera wrote: > >> Hi All; >> >> One of the main challenges dealing with carbon (at least for me) is >> that it does not (or very less) give error messages, and if I added a >> wrong bundle it saliently keep the bundle in a error state. Of course >> there is a way to enable carbon console and look in to it, but not >> many knows how to query and figure out the data presented by carbon. >> >> Can we write a code/ Web page that will be called either after start >> up or on user request, which inspect all the bundles/ dependencies, >> figure out problems, and provide potential human readable solutions to >> the problem. Basically I am proposing to capture the knowledge >> trapped in Carbon guys and translate to verification logic + human >> readable messages. It will be much like Happy Axis2 page Axis2 has. >> >> WDYT? >> >> Srinath >> >> -- >> >> Srinath Perera, Ph.D. >> WSO2 Inc. http://wso2.com >> Blog: http://srinathsview.blogspot.com/ >> >> ___ >> Architecture mailing list >> architect...@lists.wso2.com >> https://lists.wso2.com/cgi-bin/mailman/listinfo/architecture >> > > > > -- > *Afkham Azeez* > Director of Architecture; WSO2, Inc.; http://wso2.com > Member; Apache Software Foundation; http://www.apache.org/ > * <http://www.apache.org/>** > email: **az...@wso2.com* * cell: +94 77 3320919 > blog: **http://blog.afkham.org* <http://blog.afkham.org>* > twitter: **http://twitter.com/afkham_azeez*<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 > > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Autoscaling with LXCs - end to end demo
Excellent! I look forward to seeing the next iteration ... On Wed, Apr 25, 2012 at 9:16 PM, Afkham Azeez wrote: > Today we were able to see an end to end demo where the autoscaler talked > to the Tropos controller, and the controller spawned LXC instances! Tropos > is the name we've been using for this 'thing' we are doing with > LXC+autoscaler+LB+agents :) If there is a better name, please come up with > suggestions :) > > Some stuff were done manually to get the end to end flow working, but the > team got it working. Good job folks! > > Damitha et. al., please schedule another demo for all interested parties > next week. It would be ideal if the manual steps are fixed to be done > automatically with scripts etc. > > Thanks > Azeez > > -- > *Afkham Azeez* > Director of Architecture; WSO2, Inc.; http://wso2.com > Member; Apache Software Foundation; http://www.apache.org/ > * <http://www.apache.org/>** > email: **az...@wso2.com* * cell: +94 77 3320919 > blog: **http://blog.afkham.org* <http://blog.afkham.org>* > twitter: **http://twitter.com/afkham_azeez*<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 > > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How to configure a LB cluster?
You don't set them up that way. If you have 2 LBs, then there are two modes: 1. they'd be mapped to the same IP and one will take over for the other via Linux HA or some similar mechanism. So as far as the service nodes go there's only one LB. 2. they'd be running hot-hot and clients will manage routing via (probably) DNS round robin type scheme Alternatively, you can set up another LB (maybe hardware one) in front of our 2 LBs and then the service nodes would have that name/IP as the endpoint. If you want that to have HA then you have to go to (1) or (2). Sanjiva. On Tue, Apr 10, 2012 at 4:39 PM, Nirmal Fernando wrote: > Hi All, > > Say I have a primary and secondary LBs. How to configure them such that > LBs know each other's existence? > > PS: I know how to configure a single LB, and cluster of other instances. > There we map LB's public IP in axis2.xml of other instances. I tried same > way with 2 LBs, but it failed to build AxisConfig and I think it's not the > correct way. > > -- > > Thanks & regards, > Nirmal > > Software Engineer- Platform Technologies Team, WSO2 Inc. > Mobile: +94715779733 > Blog: http://nirmalfdo.blogspot.com/ > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API Manager - Pre alpha 1 available for download
Sumedha any reason to not call this M1? Not sure what semantic "pre alpha 1" means! On Mon, Apr 2, 2012 at 8:38 AM, Sumedha Rubasinghe wrote: > Pre alpha 1 pack of WSO2 API Manager can be downloaded from - > http://people.wso2.com/~sumedha/builds/am/02-04-2012/wso2am-1.0.0-SNAPSHOT.zip > > A README on how to test functionality is available inside > samples/TwitterSearch (also available @ > http://svn.wso2.org/repos/wso2/carbon/platform/trunk/products/apimgt/modules/samples/TwitterSearch/README.txt > ) > > We welcome feedback in the form of JIRA issues via > https://wso2.org/jira/browse/APISTORE > > -- > API Team > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API Manager Build - 27/03/2012
Guys I don't see version labels .. is this M1? On Tue, Mar 27, 2012 at 9:01 PM, Prabath Siriwardena wrote: > Hi Sandapa, > > Please find the latest build for testing at [1]... > > -- > Thanks & Regards, > Prabath > > [1]: http://people.wso2.com/~prabath/api-manager/ > > Mobile : +94 71 809 6732 > > http://blog.facilelogin.com > http://RampartFAQ.com > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Let's increase default value for session timeout
t;> Dev@wso2.org > >> >>> http://wso2.org/cgi-bin/mailman/listinfo/dev > >> >>> > >> >> > >> >> > >> >> > >> >> -- > >> >> Amila Suriarachchi > >> >> > >> >> Software Architect > >> >> WSO2 Inc. ; http://wso2.com > >> >> lean . enterprise . middleware > >> >> > >> >> phone : +94 71 3082805 > >> >> > >> >> > >> >> ___ > >> >> Dev mailing list > >> >> Dev@wso2.org > >> >> http://wso2.org/cgi-bin/mailman/listinfo/dev > >> >> > >> > > >> > > >> > > >> > -- > >> > Dimuthu Leelarathne > >> > Technical Lead > >> > > >> > WSO2, Inc. (http://wso2.com) > >> > email: dimut...@wso2.com > >> > > >> > Lean . Enterprise . Middleware > >> > > >> > > >> > ___ > >> > Dev mailing list > >> > Dev@wso2.org > >> > http://wso2.org/cgi-bin/mailman/listinfo/dev > >> > > >> > >> > >> > >> -- > >> Mobile : +94773330538 > >> ___ > >> Dev mailing list > >> Dev@wso2.org > >> http://wso2.org/cgi-bin/mailman/listinfo/dev > > > > > > > > > > -- > > Regards, > > > > Tharindu > > > > blog: http://mackiemathew.com/ > > M: +9459908 > > > > > > -- > Mobile : +94773330538 > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] API Manager pre-M1 pack
On Wed, Mar 21, 2012 at 8:40 AM, Prabath Siriwardena wrote: > API Manager : https://localhost:9443/carbon >>> >> >> Above context name is not consistent given the context names below. Why >> not call it https://localhost:9443/ <https://localhost:9443/carbon> >> apimanager >> > > There is no separate web app for API Manager - its the carbon admin > console... > Then lets not change the context for that. We will (eventually) have another role and UI for "API managers" .. plus calling the admin console something different is a bad idea because you can (and need to be able to) admin the normal server stuff. Sanjiva. -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Shall we include 'session.getId()' method in Jaggery?
On Sun, Mar 11, 2012 at 10:49 AM, Manjula Rathnayake wrote: > On Sun, Mar 11, 2012 at 10:35 AM, Sanjiva Weerawarana wrote: >> >>> Why does anyone want to get the actual cookie value on the server side?? >>> The session is represented by the session object .. what more do you want >>> the cookie for? >>> >> This is needed when we need to map some state in server side with current >> session, for example the user who is logged in, need to be stored. I came >> across this when developing sso relying party. Actually this is available >> in JSP. >> > > And initially I thought we can store logged in user value in a session > variable. But when Identity server redirect user to assertion consumer > service, the session is different from the jaggery app requested. That is > why I had to maintain the session id and user id in host object > implementation. > The IS redirection happens before Jaggery app code runs, isn't it?? I'm confused .. if the SESSION_ID is stored, where do you store it and how do you get it back? The session is where state can be stored and the session object (which is keyed off the session ID) is equally unique as the session ID itself. I think there's a deeper issue around separating login status from session status. This is the same problem we have in Carbon admin consoles .. we confuse loggedin-ness with the lifetime of the session. It should be different .. let me start a separate thread on that. Sanjiva. -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Carbon Source (Orbit/Kernel/Platform) is Frozen for Commits from 10.00am IST on 11 th Mar, 2012
Its not worth it if we are going to lose history .. but if there's a way to move it with sync then great. On Sun, Mar 11, 2012 at 4:40 PM, Pradeep Fernando wrote: > Hi, > > On Sun, Mar 11, 2012 at 4:21 PM, Selvaratnam Uthaiyashankar < > shan...@wso2.com> wrote: > >> But that means, svn.wso2.org/repos/carbon/ is going to be the svn >> repo. So, during the move, we will loose all previous histories. Will >> it worth? >> > > you are correct, it seems. we can't do svn mv/copy in that case. we have > to go with svn sync[1]. > > [1] http://svn.apache.org/repos/asf/subversion/trunk/notes/svnsync.txt > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Carbon Source (Orbit/Kernel/Platform) is Frozen for Commits from 10.00am IST on 11 th Mar, 2012
Great job :).
Now .. not to be painful :(, but ..
It seems to me "wso2" is redundant. Any chance we can lose it and get to:
svn.wso2.org/repos/carbon/{orbit,kernel,platform}/{trunk,branches,tags}
??
Sanjiva.
On Sun, Mar 11, 2012 at 2:22 PM, Pradeep Fernando wrote:
> Hi all,
>
> we are done with svn restructuring. New source locations.
>
> Orbit - https://svn.wso2.org/repos/wso2/carbon/orbit/trunk/
> Kernel - https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/
> Platform - https://svn.wso2.org/repos/wso2/carbon/platform/trunk/
>
>
> @Build-team: please update the source locations in the bamboo-builder
> machine.
>
>
> thanks,
> --Pradeep
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
--
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
650 265 8311
blog: http://sanjiva.weerawarana.org/
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Shall we include 'session.getId()' method in Jaggery?
In other words, where do you call request.getHeader("Cookie") now and what
do you do with it?
On Sun, Mar 11, 2012 at 10:35 AM, Sanjiva Weerawarana wrote:
> Why does anyone want to get the actual cookie value on the server side??
> The session is represented by the session object .. what more do you want
> the cookie for?
>
> Sanjiva.
>
> On Sun, Mar 11, 2012 at 10:29 AM, Manjula Rathnayake wrote:
>
>> Hi,
>>
>> We get JSESSIONID from request.getHeader("Cookie") for the moment.
>>
>> Thank you.
>>
>> --
>> Manjula Rathnayaka
>> Software Engineer
>> WSO2, Inc.
>> Mobile:+94 77 743 1987
>>
>> ___________
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Sanjiva Weerawarana, Ph.D.
> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
> email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
> 650 265 8311
> blog: http://sanjiva.weerawarana.org/
>
> Lean . Enterprise . Middleware
>
--
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
650 265 8311
blog: http://sanjiva.weerawarana.org/
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Shall we include 'session.getId()' method in Jaggery?
Why does anyone want to get the actual cookie value on the server side??
The session is represented by the session object .. what more do you want
the cookie for?
Sanjiva.
On Sun, Mar 11, 2012 at 10:29 AM, Manjula Rathnayake wrote:
> Hi,
>
> We get JSESSIONID from request.getHeader("Cookie") for the moment.
>
> Thank you.
>
> --
> Manjula Rathnayaka
> Software Engineer
> WSO2, Inc.
> Mobile:+94 77 743 1987
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
--
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
650 265 8311
blog: http://sanjiva.weerawarana.org/
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
