Hi,
There were some changes in the proposed architecture after the discussion
had with Srinath and Shammi today.
1. There are only queue number of slots. When a message comes A slot
will be created to the destination queue of the message if it is not
already created and save in the
Hi All,
I have implemented a component for ES to provide the following
functionality,
1. *Register custom Event Types*
Currently, Registry provides several events to which users can subscribe
to. i.e. Create LC, Delete LC, Update, Delete etc. By using custom Event
Type registration
Hi Sameera,
With regards to the two new event types that you introduced, I think this
is the best workaround possible right now, since the registry events are
not easily customizable. There is one possibility though, [1], but that is
not the most ideal. But, this is something you were aware of?
Hi Senaka,
Thank you for the feedback. :)
Yes, we came across that sample when we started doing this. But after a
discussion with Ruchira it was decided not to follow that method as it is
not ideal.
We also need to send html content in the email. We can set the html
formatted content through
Hi All
Problem : App Factory deployers should be able to add application types by
packaging everything in a file. For example to add foo apptype add
foo.apptype archive file and putting it in a location. [1]
Solution : Add a new deployer (Apptype Deployer), which will listen to the
location
Hi All,
We thought of come-up with an XSD for the apptype.xml and use it to
validate the xml file against the mandatory elements. If apptype.xml is
validated and the result is success then it can be unmarshelled with JAXB.
On Mon, Jul 28, 2014 at 5:33 PM, Danushka Fernando danush...@wso2.com
Hi,
Is it possible to run carbon server outside standalone mode, in other
application server?
As far as i have read, it is possible:
http://wso2.com/library/articles/stuff-works-wso2-carbon/
But we cant put it to work and we also found some questions on
stackoverflow
No, we stopped
I'm not really fond of having a predefined schema for application type xml.
reasons:
1) in my opinion is too early to figure out what should be in the schema
given that we don't have lot of apptypes (or identified what we will
support in future)
2) I like to draw an example from Apache Ant.
Hi Milinda,
we need to come up with a method for form generation to cater for input and
outout, response of human tasks. One option is to use the renderings
element to specify form information and use that to generate the ui.
Additionally, we could provide a way to specify input output and
Hi Milinda,
will the BPMN/activiti processes also supported by the jaggery UI for
WS-Human-Tasks?
best regards
Manfred
2014-07-28 19:38 GMT+02:00 Nandika Jayawardana nand...@wso2.com:
Hi Milinda,
we need to come up with a method for form generation to cater for input
and outout, response
Hi,
I have added the plotted graph in the doc [1].
[1]
https://docs.google.com/a/wso2.com/document/d/1aubN2MsPYb-biGIhyVs2KSDs9cQ0D_MdCo-75hFf10A/edit
Regards,
Firzhan
On Mon, Jul 28, 2014 at 10:00 AM, Firzhan Naqash firz...@wso2.com wrote:
Hi,
Sorry I was working on NDataSource
Hi all,
Thinking about the range of apps that we'll be supporting, I believe the
mandatory tags will be very minimal(one or two or else). So I am +1 not
doing the schema validation yet.
If we use any standard parser it will properly give out any unrecognised
tags.
thanks,
dimuthu
On Mon, Jul
Hi,
*Suggestion 01*
Currently we have a application home which shows some basic information
about an application like name, icon, app type, owner, description, repo
url and information associated with versions and their current status. In
1.0.0 we had more information like team composition and
Hi David,
The article you have linked at [1] is based on Carbon 1.5.1, which makes it
obsolete since the latest released Carbon version as of this moment is
4.2.0. Therefore it has undergone quite a lot of architectural changes when
you compare it with v1.5.1. And as all the stackoverflow answers
HI Dimuthu
There are several mandatory tags like app type name, description, and
application type processor. These are used in our code / jaggery apps. But
there could be other tags which are not mandatory and also specific to
certain app types which are used inside the application type processor.
Hi Danushka,
Does all the app types contain a certain set of mandatory tags? I think we
will have different mandatory tags according to different app types. So it
is not good to be base on a few mandatory tags for each app type. Hence
shouldn't we have a different validation mechanism for each
Hi Gayan
These mandatory tags I mentioned are used in the common code which should
be same to all app types. Check my previous mail.
Thanks Regards
Danushka Fernando
Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729
On Tue, Jul 29, 2014 at 10:40 AM, Gayan Dhanushka
Hi all,
HTTP Inbound Implementation using HTTP Core has been almost
completed and Integration Tests and Documentation has to be done.High Level
Implementation details as follows.
- DefaultListeningIOReactor is started when ESB starts with
InboundConfigurations.Same IOReactor
Following are the main decisions taken in the review meeting held on 28th
July.
Thread pool in Inbound Endpoint
--
Introduce two new parameters to inbound endpoint configuration.
1. Sequenial (default = false)
This is needed to be set to true when it
19 matches
Mail list logo
