Hi Hemika,
Thanks ;)
This attribute can be used to declare indirect dependencies to a particular
component. I will put a detailed explanation to the blog soon.
Thanks,
Sameera.
On Wed, May 18, 2016 at 12:28 PM, Hemika Kodikara wrote:
> Hi Sameera,
>
> I saw this
Hi All,
As Indika mentioned, we are getting the following error on MB startup.
osgi> 16:55:36.567 [Timer-0] ERROR
org.wso2.carbon.datasource.core.internal.DataSourceListenerComponent -
Error occurred while initializing data sources
org.wso2.carbon.datasource.core.exception.DataSourceException:
Hi Sameera,
I saw this "dependentComponentName" in the carbon.component tag in [1]. May
I know the purpose of it ? Best if you could add it to the blog :) . The
blog is very understandable.
[1] -
https://github.com/wso2/msf4j/pull/169/files#diff-357e4854869b2e21c38b1b437f11095aR334
Regards,
Hi Niranjan,
Yes. I can access osgi console. Here is the output of carbon-jndi bundle.
It is in ACTIVE state.
*osgi> ss jndi*
"Framework is launched."
idState Bundle
71ACTIVE org.wso2.carbon.jndi_1.0.0.SNAPSHOT
*osgi> b 71*
org.wso2.carbon.jndi_1.0.0.SNAPSHOT [71]
Id=71,
Hi Indika,
Are you able to start the access the osgi console? If so, can you check if
carbon-jndi bundle is active?
Regards,
Nira
On Tue, May 17, 2016 at 5:17 PM, Indika Sampath wrote:
> I update kernel version to 5.1.0-alpha2 and made necessary changes in
> pom.xml. Also
I update kernel version to 5.1.0-alpha2 and made necessary changes in
pom.xml. Also clone carbon-datasources and carbon-jndi, locally build and
update pom.xml with 1.0.0-SNAPSHOT. I didn't get any issue at build time.
But below exception throws at the server start up. Appreciate your input.
Thanks for the information.
Datasources issue is solved.
Hemika Kodikara
Software Engineer
WSO2 Inc.
lean . enterprise . middleware
http://wso2.com
Mobile : +9477762
On Fri, May 13, 2016 at 4:56 PM, Sameera Jayasoma wrote:
> Refer the following article to get
Refer the following article to get information about the new syntax.
https://medium.com/@sameera.jayasoma/resolving-startup-order-of-carbon-components-in-wso2-carbon-5-0-0-497fe3287e67
On Fri, May 13, 2016 at 4:26 PM, Niranjan Karunanandham
wrote:
> Hi Hemika,
>
> The
Hi Hemika,
The startup resolver changes compatible to kernel 5.1.0-alpha2 is available
in the master branch (PR [1]) of carbon-datasources. The carbon-datasources
1.0.0-alpha depends on the older format.
[1] - https://github.com/wso2/carbon-datasources/pull/14
Regards,
Nira
On Fri, May 13,
Thanks for the response. I have changed the kernel version to 5.1.0-alpha2
as mentioned. The earlier error is not coming. But I am getting the
following error. Seems like its coming from carbon-datasources. I checked
this with m1 version and also alpha version for datasources.
Hi Hemika,
There has been some changes to the Startup Resolver in the 5.1.0-alpha2
release. Therefore IMO it would be better if you can use 5.1.0-alpha2 and
carbon-parent version 5.
Regards,
Nira
On Fri, May 13, 2016 at 2:51 PM, Hemika Kodikara wrote:
> Hi All,
>
> I am
Hi Hemika,
This is because of the changes in the startup order resolver component in
C5. We've improved the syntax a little bit. I will share the documentation
in few mins.
Thanks,
Sameera.
On Fri, May 13, 2016 at 2:51 PM, Hemika Kodikara wrote:
> Hi All,
>
> I am getting
Hi All,
I am getting this error when starting up the MB C5 pack. We are working on
the released 5.0.0 version of carbon-kernel. Any idea how this error occurs
and how to avoid it ?
[2016-05-13 14:43:28,491] ERROR
13 matches
Mail list logo