Hi Danushka, Lasitha,

Thanks for the information.

 I will check the exact error in osgi console.

Thanks.

On Thu, Feb 19, 2015 at 2:35 PM, Lasitha Wattaladeniya <[email protected]>
wrote:

> Hi jagath,
>
> check whether u have included the correct *registry* package imports in
> maven osgi bundle plugin config. May be that's why orderprocessorbackend is
> not resolving.
>
> eg:  <plugins> <plugin> <groupId>org.apache.felix</groupId> <artifactId
> >maven-bundle-plugin</artifactId> <version>1.4.0</version> <extensions
> >true</extensions> <configuration> <instructions> <Bundle-SymbolicName>
> ${project.artifactId}</Bundle-SymbolicName> <Bundle-Name>
> ${project.artifactId}</Bundle-Name> <Export-Package>
> </Export-Package> <Import-Package>
>
> org.wso2.carbon.registry.core.* </Import-Package> <Carbon-Component
> >UIBundle</Carbon-Component> </instructions> </configuration> </plugin> </
> plugins>
>
>
>
>
> On Thu, Feb 19, 2015 at 2:11 PM, Danushka Fernando <[email protected]>
> wrote:
>
>> This is because of some unreolved osgi dependency. Can you start the
>> server with -DosgiConsole option and check the issue in osgi console.
>>
>> Thanks & Regards
>> Danushka Fernando
>> Software Engineer
>> WSO2 inc. http://wso2.com/
>> Mobile : +94716332729
>>
>> On Thu, Feb 19, 2015 at 1:47 PM, Jagath Sisirakumara Ariyarathne <
>> [email protected]> wrote:
>>
>>> Adding more..
>>>
>>> This issue occurs only when the registry is used in the module.
>>> Otherwise it works fine.
>>>
>>> Thanks.
>>>
>>> On Thu, Feb 19, 2015 at 1:30 PM, Jagath Sisirakumara Ariyarathne <
>>> [email protected]> wrote:
>>>
>>>> Hi,
>>>>
>>>> I followed [1] to develop a carbon component and [2] to use registry in
>>>> it. After that, when the carbon starts, it gives the below message
>>>> continuously and does not start up. Here, "orderprocessingbackend" is the
>>>> module which uses the registry.
>>>>
>>>> [2015-02-19 12:52:14,851]  WARN
>>>> {org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is
>>>> delayed due to the following unsatisfied items:
>>>> [2015-02-19 12:52:14,852]  WARN
>>>> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
>>>> OSGiAxis2Service: orderprocessingbackend-1.0.8
>>>> [2015-02-19 12:53:14,850]  WARN
>>>> {org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is
>>>> delayed due to the following unsatisfied items:
>>>> [2015-02-19 12:53:14,851]  WARN
>>>> {org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
>>>> OSGiAxis2Service: orderprocessingbackend-1.0.8
>>>>
>>>>
>>>> I used WSO2 Carbon 4.3.0 and added below dependency to the pom file.
>>>>
>>>> <dependency>
>>>>     <groupId>org.wso2.carbon</groupId>
>>>>     <artifactId>org.wso2.carbon.registry.core</artifactId>
>>>>     <version>4.3.0</version>
>>>> </dependency>
>>>>
>>>> What would be the issue here?
>>>>
>>>>
>>>> [1] -
>>>> http://wso2.com/library/tutorials/2014/03/how-to-write-a-wso2-carbon-component/
>>>> [2] -
>>>> http://wso2.com/library/articles/2012/03/carbon-context-its-usages-wso2-products/
>>>>
>>>> --
>>>> Jagath Ariyarathne
>>>> Technical Lead
>>>> WSO2 Inc.  http://wso2.com/
>>>> Email: [email protected]
>>>> Mob  : +94 77 386 7048
>>>>
>>>>
>>>
>>>
>>> --
>>> Jagath Ariyarathne
>>> Technical Lead
>>> WSO2 Inc.  http://wso2.com/
>>> Email: [email protected]
>>> Mob  : +94 77 386 7048
>>>
>>>
>>> _______________________________________________
>>> Dev mailing list
>>> [email protected]
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>> _______________________________________________
>> Dev mailing list
>> [email protected]
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Lasitha Wattaladeniya
> Software Engineer
> WSO2, Inc. | http://wso2.com
> lean. enterprise. middleware
>
> Mobile : +94719397528
> Blog : techreadme.blogspot.com
>



-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: [email protected]
Mob  : +94 77 386 7048
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to