Is this going to be part of the data bridge?
On Wed, Apr 3, 2013 at 10:58 AM, Sriskandarajah Suhothayan <[email protected]>wrote: > Thanks Kishanthan for the idea > We'll give a try to use the appropriate TransportServices to enable the > user to configure the Axis2 transport via UI at startup/runtime > > Suho > > > On Wed, Apr 3, 2013 at 9:49 AM, Mohanadarshan Vivekanandalingam < > [email protected]> wrote: > >> Hi Kishanthan, >> >> No, we are not changing the UI of a particular transport adaptor at >> run-time... It can be changed by the user if it is an external transport >> adaptor which is written by him (not in run time). We are still working on >> the UI component then we can consider your idea and look about that also... >> Appreciate your suggestion. >> >> Thanks & Regards, >> Mohan >> >> >> >> On Wed, Apr 3, 2013 at 9:17 AM, Kishanthan Thangarajah < >> [email protected]> wrote: >> >>> Hi Mohan, >>> >>> >>> On Sat, Mar 30, 2013 at 11:43 PM, Mohanadarshan Vivekanandalingam < >>> [email protected]> wrote: >>> >>>> Hi, >>>> >>>> We have started the work of modifying the CEP server. As the first step >>>> we have start re-writing the broker module of the CEP. In our next release >>>> we are going to have Transport Adaptor module instead of broker module. >>>> Transport Adaptor module going to do similar work as broker does. But >>>> through the Transport adaptor module we can provide more user friendliness. >>>> >>>> In the new architecture, same as broker module the core part will be >>>> handle by the Transport Adaptor. >>>> >>>> *Transport Adaptor Core* >>>> >>>> - Transport Adaptor core contains the base methods to create >>>> transportAdaptorDto and to handle transport adaptor configuration >>>> details. >>>> - It exposes two services, 1) to register a transport adaptor 2) to >>>> get the information about transport adaptors. >>>> - It allows to write external transport adaptor component and >>>> register it easily. >>>> - Each and every transport adaptor types (broker types - jms, agent >>>> & etc...) is written as individual module and registered with this >>>> transport adaptor core. >>>> >>>> >>>> Other important module which manages the transport adaptor is transport >>>> adaptor manager. This module contains 3 sub components. There are core, >>>> admin & UI, similar as old broker manager module. >>>> But in the new module we have changed some old implementations. >>>> >>>> *Transport Adaptor Manager Core* >>>> >>>> - We have remove the registry related configurations of a transport >>>> adaptor (broker). and all the transport adaptor information are stored >>>> as a >>>> xml file like we are handing the bucket. >>>> - We have also provided the hot deployment facility for transport >>>> adaptor creation. >>>> - All the transport adaptor information will store in the file >>>> system. >>>> - It access the transport adaptor service and get the information >>>> regarding the transport adaptors and their properties. >>>> - It exposes a service to get the transport >>>> adaptor configuration and to store the new transport adaptor >>>> configuration. >>>> >>>> >>>> *Transport Adaptor Manager Admin* >>>> >>>> - It act as an interface between the UI and core. >>>> - It exposes an admin service to UI to get the information that needed >>>> to create the UI and to store those information >>>> >>>> >>>> This architecture will also provide the flexibility to integrated the >>>> CEP with other products easily. >>>> We are now moving forward to create the UI component for transport >>>> adaptor. >>>> >>> >>> One question regarding the UI component, >>> >>> This means that the user is allowed to change the configuration of a >>> particular transport at run-time. So how are you planning to get those >>> changes and plug in to run-time information? >>> >>> Just a thought, you can give a try and use the TransportService for >>> this. Have a look at the JMSTransportService for more info. >>> >>> Thanks, >>> Kishanthan. >>> >>> Hope our new design will provide more flexibility to work with CEP... >>>> Any suggestions? >>>> >>>> >>>> >>>> Thanks & Regards >>>> Mohan >>>> >>>> >>>> >>>> >>>> -- >>>> *V. Mohanadarshan* >>>> *Software Engineer,* >>>> *Data Technologies Team,* >>>> *WSO2, Inc. http://wso2.com * >>>> *lean.enterprise.middleware.* >>>> * >>>> * >>>> email: [email protected] >>>> phone:(+94) 771117673 >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> [email protected] >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> *Kishanthan Thangarajah* >>> Software Engineer, >>> Development Technologies Team, >>> WSO2, Inc. >>> lean.enterprise.middleware >>> >>> Mobile - +94773426635 >>> Blog - *http://kishanthan.wordpress.com* >>> Twitter - *http://twitter.com/kishanthan* >>> >> >> >> >> -- >> *V. Mohanadarshan* >> *Software Engineer,* >> *Data Technologies Team,* >> *WSO2, Inc. http://wso2.com * >> *lean.enterprise.middleware.* >> * >> * >> email: [email protected] >> phone:(+94) 771117673 >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *S. Suhothayan > * > *Software Engineer, > Member, Management Committee - Data Technologies Team, > * > * * > *WSO2 Inc. **http://wso2.com > <http://wso2.com/>* > *lean . enterprise . middleware* > > *cell: (+94) 779 756 757 > blog: **http://suhothayan.blogspot.com/* <http://suhothayan.blogspot.com/> > * > twitter: **http://twitter.com/suhothayan* <http://twitter.com/suhothayan>* > linked-in: **http://lk.linkedin.com/in/suhothayan* > * > * > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Regards, Tharindu Mathew Associate Technical Lead, WSO2 BAM Member - Data Mgmt. Committee blog: http://tharindumathew.com/ M: +94777759908
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
