After the discussion with Azeez, Kishanthan and myself, we decided to keep
mostly used configuration in the Carbon.xml under a new element called
. This element will includes the cluster domain information,
membership scheme information and local member properties. This will ensure
that users of th
Hi all,
$Subject happens in current released packs. We are addressing this issue in
M12(next milestone).
Current pom.xml as below. We have to make sure that below highlighted
entries are not changed by developers even by mistakes.
4.0.0
org.wso2.af
* bar*
* 1.0.0*
* war*
bar
bar
*Why A
@Azeez AFIK storage server is about provisioning of storage. It's doesn't
have the capability of persisting files via an HTTP API. After developing
the storage app we can bundle it with SS as well.
On Thu, Feb 20, 2014 at 8:08 PM, Afkham Azeez wrote:
> See http://wso2.com/products/storage-serve
Hi Manoj,
Just having a dependency in the pom.xml does not guarantee the ordering, it
is a build time dependency .. maybe you're using some other OSGi service
which in-turn transitively uses the ndatasource OSGi service somewhere, or
else, most probably, it is by chance, that your bundle is gettin
I didn't really face that issue, but thanks for pointing out. Since I used
the dependency config from the previous throttle component on my pom.xml,
the activation order would have worked correctly.
Regards,
Manoj
On Fri, Feb 21, 2014 at 8:45 AM, Amila Maha Arachchi wrote:
>
>
> On Friday, Febr
+1. Yep is what I meant.
Thanks,
Manoj
On Fri, Feb 21, 2014 at 1:19 AM, Anjana Fernando wrote:
> Hi guys,
>
> Yeah, the existing data source component does exactly that. When you
> mention a data source in a *-datasources.xml file, you can make it
> available as JNDI resource, that is what th
On Friday, February 21, 2014, Kasun Gajasinghe
>
wrote:
>
> I believe the issue here is that the JNDi context won't be available for a
> carbon component/bundle until the org.wso2.carbon.ndatasource.core bundle
> is activated during server startup. Any bundle that gets activated before
> this bund
I believe the issue here is that the JNDi context won't be available for a
carbon component/bundle until the org.wso2.carbon.ndatasource.core bundle
is activated during server startup. Any bundle that gets activated before
this bundle won't see the JNDi contexts. I think Manoj is facing that issue
Hi guys,
Yeah, the existing data source component does exactly that. When you
mention a data source in a *-datasources.xml file, you can make it
available as JNDI resource, that is what the following section of a data
source configuration does:
{RES_NAME}
{ICS}
{PRO
Hi Manoj,
Please find the responses inline.
On Thu, Feb 20, 2014 at 8:25 PM, Manoj Fernando wrote:
> Hi Senaka,
>
> What I meant was the scenario of me as an outside developer wanting to add
> a new datasource for my own carbon component. Right now, just adding the
> datasource into the xml do
Hi Senaka,
What I meant was the scenario of me as an outside developer wanting to add
a new datasource for my own carbon component. Right now, just adding the
datasource into the xml doesn't make it available as a JNDI resource. You
need to do that extra step of reading the XML and attaching tha
Hi Dulitha,
This is a useful use-case. If you have the time, can you use ES, SS and
G-Reg and get this to work? I can help too.
IMO, in thoery this should be doable, but practically there might be gaps.
We can surely write an article/case-study around some useful integration
scenarios like this.
Hi Manoj,
Datasources can be referenced by JNDI key even now. This is how it works in
Registry Kernel and UM. Is it done in some other way in carbon components?
And, for system properties, you can pass these through the wso2server.sh/bat.
I see no benefit of having a separate component to do just
My thoughts were basically on the scenario of which a developer (perhaps a
client) may want to develop a new carbon component (for example) and use a
separate datasource for persistence. If we can pre-load ALL datasources
into an initial context, we will not have to write the context
initializatio
See http://wso2.com/products/storage-server/
On Thu, Feb 20, 2014 at 7:49 PM, Chan wrote:
> Hi folks,
> In our platform - we don't yet have a solution for storing static files in
> the cloud. A solution that provides a simple service of persisting a file
> and getting back a URI. The Enterprise
Hi folks,
In our platform - we don't yet have a solution for storing static files in
the cloud. A solution that provides a simple service of persisting a file
and getting back a URI. The Enterprise Store team built a storage module in
the Publisher app that provides persisting of files to a databas
We allow defining data sources @ two levels targeting two different
audiences.
Type1:
Data sources defined in master-datasources.xml are used for server's
internal storage requirements. This includes data source definitions like
Registry database, User Store, etc. These data sources are modified b
Hi Manoj,
Are you discussing this WRT a mult-regional deployment of stores? Or is it
in the context of something else?
Thanks,
Senaka.
On Thu, Feb 20, 2014 at 12:50 PM, Manoj Fernando wrote:
> Was wondering if it makes sense to dynamically load ALL datasources
> defined in master-datasources.
*WSO2 Enterprise Mobility Manager (EMM) 1.0.0 Released!*
*February 2014*
*WSO2 Mobile team is pleased to announce the release of 1.0.0 Version of
the Open Source WSO2 EMM.*
WSO2 Enterprise Mobility Manager (EMM) is a unique solution designed to
specifically address the mobile enterprise needs. E
Was wondering if it makes sense to dynamically load ALL datasources defined
in master-datasources.xml during bootstrap (well... we could perhaps build
an enable/disable switch on the config).
Will be a useful feature when we may want to segregate various elements
that need to be persisted at diffe
20 matches
Mail list logo
