[Dev] When features are generated using p2-feature-gen goal in carbon-p2-plugin, why not use a value equal to value
Hi, Is there any specific reason to do $subject? The value inside the is used to name the jar file of the particular feature. Besides, do we need to make changeable to the user of the plugin? This is regarding the issue https://wso2.org/jira/browse/CARBON-12876. This issue has been caused because of the generated .jar files for the features are not derivable from the artifactId. Therefore auto-generated category.xml file for CategoryPublisher can't point to the correct jar file URL. Thanks, -- Chethiya Abeysinghe Software Engineer; WSO2, Inc.; http://wso2.com/ email: cheth...@wso2.com blog: chethiya3000.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] When features are generated using p2-feature-gen goal in carbon-p2-plugin, why not use a value equal to value
Hi,
Since ID was required to generate the category.xml, I change the plugin to
read the FeatureId and the version from the pom.xml in repository. Now the
looks like follows in pom.xml:
org.wso2.carbon.broker.category
WSO2 Broker Category
broker category
org.wso2.carbon.broker
${carbon.version}
org.wso2.carbon.brokermanager
${carbon.version}
Thanks,
- Chethiya
On Wed, Apr 18, 2012 at 11:10 PM, Chethiya Abeysinghe wrote:
> Hi,
>
> Is there any specific reason to do $subject? The value inside the is
> used to name the jar file of the particular feature. Besides, do we need to
> make changeable to the user of the plugin?
>
> This is regarding the issue https://wso2.org/jira/browse/CARBON-12876.
> This issue has been caused because of the generated .jar files for the
> features are not derivable from the artifactId. Therefore auto-generated
> category.xml file for CategoryPublisher can't point to the correct jar file
> URL.
>
> Thanks,
>
> --
> Chethiya Abeysinghe
> Software Engineer; WSO2, Inc.; http://wso2.com/
> email: cheth...@wso2.com
> blog: chethiya3000.blogspot.com
>
>
>
--
Chethiya Abeysinghe
Software Engineer; WSO2, Inc.; http://wso2.com/
email: cheth...@wso2.com phone: +94 777444891
blog: chethiya3000.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] carbon-p2-repo 1.4-SNAPSHOT in trunk should 1.5-SNAPSHOT
There is already a version 1.4 in the nexus repo at [1]. [1] - http://sr5.us1.wso2.com/nexus/content/repositories/wso2-public/org/wso2/maven/carbon-p2-plugin/1.4/ Thanks -- Chethiya Abeysinghe Software Engineer; WSO2, Inc.; http://wso2.com/ email: cheth...@wso2.com phone: +94 777444891 blog: chethiya3000.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] carbon component plugin. Not working for custom group ID
Hi Pradeep, It seems generated pom.xml file of the service-stubs doesn't have a groupId. So it inherits groupId from its parent, org:wso2:carbon:service-stubs. I'll correct the archetype of the plugin to include groupId. Meanwhile you can add the gorupId to the service-stubs pom file manually to build it correctly. Thanks, - Chethiya On Wed, Apr 25, 2012 at 9:56 PM, Pradeep Fernando wrote: > Hi, > > If you give a different groupID during the interactive session, the > service stubs building fails. Can you confirm. Am i doing something wrong ? > > --Pradeep > -- Chethiya Abeysinghe Software Engineer; WSO2, Inc.; http://wso2.com/ email: cheth...@wso2.com phone: +94 777444891 blog: chethiya3000.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] carbon-p2-repo 1.4-SNAPSHOT in trunk should 1.5-SNAPSHOT
Ok. I'll work on that. - Chethiya On Fri, Apr 27, 2012 at 11:12 AM, Sameera Jayasoma wrote: > +1 for 1.5-SHAPHOST. We need to change this version before the release. > Chethiya, can you please work on this? > > Thanks, > Sameera. > > On Wed, Apr 25, 2012 at 1:15 PM, Chethiya Abeysinghe wrote: > >> There is already a version 1.4 in the nexus repo at [1]. >> >> >> [1] - >> http://sr5.us1.wso2.com/nexus/content/repositories/wso2-public/org/wso2/maven/carbon-p2-plugin/1.4/ >> >> Thanks >> -- >> Chethiya Abeysinghe >> Software Engineer; WSO2, Inc.; http://wso2.com/ >> email: cheth...@wso2.com phone: +94 777444891 >> blog: chethiya3000.blogspot.com >> >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Sameera Jayasoma > Technical Lead > > WSO2, Inc. (http://wso2.com) > email: same...@wso2.com > blog: http://tech.jayasoma.org > > Lean . Enterprise . Middleware > -- Chethiya Abeysinghe Software Engineer; WSO2, Inc.; http://wso2.com/ email: cheth...@wso2.com phone: +94 777444891 blog: chethiya3000.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] build failure: billing core
Hi, I got this error while building platform: [ERROR] Failed to execute goal on project org.wso2.carbon.billing.server.feature: Could not resolve dependencies for project org.wso2.carbon:org.wso2.carbon.billing.server.feature:pom:1.1.0-SNAPSHOT: Failure to find * org.wso2.carbon:org.wso2.carbon.billing.core:jar:4.0.0-SNAPSHOT* in http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in the local repository, resolution will not be reattempted until the update interval of wso2-nexus has elapsed or updates are forced -> [Help 1] And checking the trunk it seems the org.wos2.carbon:org.wso2.carbon.billing.core version in trunk ( https://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/stratos/billing/org.wso2.carbon.billing.core/pom.xml) is* 1.1.0-SNAPSHOT* Isn't there anything wrong? Thanks, - Chethiya On Thu, Mar 15, 2012 at 2:03 PM, Amila Maha Arachchi wrote: > I have enabled the old rule components temporarily. > > Thanks, > AmilaM. > > > On Wed, Mar 14, 2012 at 6:46 PM, Amila Maha Arachchi wrote: > >> Hi all, >> >> It needs some effort to change the billing.core and throttling.manager to >> get to work according to new rules implementations. I need AmilaS' help on >> this. Since this keeps the build on hold, I'll uncomment the old rules >> components to get the build done. Once the two components (billing and >> throttling) are modified we'll comment them again. >> >> Thanks, >> AmilaM. >> >> >> On Wed, Mar 14, 2012 at 5:19 PM, Amila Maha Arachchi wrote: >> >>> I'll have to build and check whether billing component is working after >>> making necessary changes. This should affect the throttling component too. >>> So I have to fix that also. >>> >>> AmilaM. >>> >>> >>> On Wed, Mar 14, 2012 at 4:53 PM, Pradeep Fernando wrote: >>> >>>> Hi All, >>>> >>>> this is a blocker for us. We were planning to get carbon-alpha packs >>>> today. please fix this asap. >>>> >>>> thanks, >>>> --Pradeep >>>> >>> >>> >>> >>> -- >>> *Amila Maharachchi* >>> Senior Software Engineer; WSO2, Inc.; http://wso2.com >>> >>> Blog: http://maharachchi.blogspot.com >>> Mobile: +94719371446 >>> >>> >>> >> >> >> -- >> *Amila Maharachchi* >> Senior Software Engineer; WSO2, Inc.; http://wso2.com >> >> Blog: http://maharachchi.blogspot.com >> Mobile: +94719371446 >> >> >> > > > -- > *Amila Maharachchi* > Senior Software Engineer; WSO2, Inc.; http://wso2.com > > Blog: http://maharachchi.blogspot.com > Mobile: +94719371446 > > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Chethiya Abeysinghe Software Engineer; WSO2, Inc.; http://wso2.com/ email: cheth...@wso2.com phone: +94 777444891 blog: chethiya3000.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Inserting Categories in p2 Repo
Hi,
We have changed the p2-repo-gen to generate the repository with category
information. So you can simply define categories and include appropriate
features into those categories. Once that repo with category information is
imported to the feature manger, you can see those defined categories in the
UI.
To feed in these information, you have to edit the
carbon/platform/trunk/features/repository/pom.xml file in svn by adding
element. An example of such a category is shown below. You can
include multiple elements.
org.wso2.carbon.broker.category
WSO2 Broker Category
broker category
org.wso2.carbon.broker
${carbon.version}
org.wso2.carbon.brokermanager
${carbon.version}
Please note that, and are required to include a feature to a
category. is the same ID used with p2-feature-gen goal of the
carbon-p2-plugin. You can find that if you look at the pom.xml of any
particular feature you want.
A sample pom.xml file to reside in repository folder is attached here.
Real pom file has a long list of features and hope people who are managing
individual features will insert their respective category information also
to this file.
Thanks,
--
Chethiya Abeysinghe
Software Engineer; WSO2, Inc.; http://wso2.com/
email: cheth...@wso2.com phone: +94 777444891
blog: chethiya3000.blogspot.com
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";>
org.wso2.carbon
carbon-features
4.0.0-SNAPSHOT
4.0.0
wso2carbon-feature-repository
pom
WSO2 Carbon - Feature Repository
http://wso2.org
org.wso2.maven
carbon-p2-plugin
1.4-SNAPSHOT
2-p2-repo-generation
package
p2-repo-gen
${basedir}/target/p2-agent
file:${basedir}/target/p2-repo
file:${basedir}/target/p2-repo
true
true
org.wso2.carbon:org.wso2.carbon.cep.feature:${carbon.version}
org.wso2.carbon:org.wso2.carbon.broker.feature:${carbon.version}
org.wso2.carbon:org.wso2.carbon.brokermanager.feature:${carbon.version}
org.wso2.carbon.broker.category
WSO2 Broker Category
broker category
org.wso2.carbon.broker
${carbon.version}
org.wso2.carbon.brokermanager
${carbon.version}
4.0.0-SNAPSHOT
1.1.0-SNAPSHOT
1.0.0-SNAPSHOT
2.1.0-wso2v6
4.1.0-SNAPSHOT
4.0.0-SNAPSHOT
4.0.0-SNAPSHOT
4.0.0-SNAPSHOT
1.3.1-SNAPSHOT
2.3.0-SNAPSHOT
0.11.wso2v1
1.3.0-SNAPSHOT
2.1.0-SNAPSHOT
0.13.0
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] build failure: billing core
Hi Amila, Working great now ! Thanks, - Chethiya On Wed, May 2, 2012 at 5:38 PM, Amila Maha Arachchi wrote: > Hi Chethiya, > > I recently changed the billing core version to stratos version. I have > missed this file when committing. Committed it now. Please take a svn up in > features/billing and see. > > Thanks, > AmilaM. > > > On Wed, May 2, 2012 at 3:49 PM, Chethiya Abeysinghe wrote: > >> Hi, >> >> I got this error while building platform: >> >> [ERROR] Failed to execute goal on project >> org.wso2.carbon.billing.server.feature: Could not resolve dependencies for >> project >> org.wso2.carbon:org.wso2.carbon.billing.server.feature:pom:1.1.0-SNAPSHOT: >> Failure to find * >> org.wso2.carbon:org.wso2.carbon.billing.core:jar:4.0.0-SNAPSHOT* in >> http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in >> the local repository, resolution will not be reattempted until the update >> interval of wso2-nexus has elapsed or updates are forced -> [Help 1] >> >> >> >> And checking the trunk it seems the >> org.wos2.carbon:org.wso2.carbon.billing.core version in trunk ( >> https://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/stratos/billing/org.wso2.carbon.billing.core/pom.xml) >> is* 1.1.0-SNAPSHOT* >> >> Isn't there anything wrong? >> >> Thanks, >> - Chethiya >> >> On Thu, Mar 15, 2012 at 2:03 PM, Amila Maha Arachchi wrote: >> >>> I have enabled the old rule components temporarily. >>> >>> Thanks, >>> AmilaM. >>> >>> >>> On Wed, Mar 14, 2012 at 6:46 PM, Amila Maha Arachchi wrote: >>> >>>> Hi all, >>>> >>>> It needs some effort to change the billing.core and throttling.manager >>>> to get to work according to new rules implementations. I need AmilaS' help >>>> on this. Since this keeps the build on hold, I'll uncomment the old rules >>>> components to get the build done. Once the two components (billing and >>>> throttling) are modified we'll comment them again. >>>> >>>> Thanks, >>>> AmilaM. >>>> >>>> >>>> On Wed, Mar 14, 2012 at 5:19 PM, Amila Maha Arachchi >>>> wrote: >>>> >>>>> I'll have to build and check whether billing component is working >>>>> after making necessary changes. This should affect the throttling >>>>> component >>>>> too. So I have to fix that also. >>>>> >>>>> AmilaM. >>>>> >>>>> >>>>> On Wed, Mar 14, 2012 at 4:53 PM, Pradeep Fernando wrote: >>>>> >>>>>> Hi All, >>>>>> >>>>>> this is a blocker for us. We were planning to get carbon-alpha packs >>>>>> today. please fix this asap. >>>>>> >>>>>> thanks, >>>>>> --Pradeep >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> *Amila Maharachchi* >>>>> Senior Software Engineer; WSO2, Inc.; http://wso2.com >>>>> >>>>> Blog: http://maharachchi.blogspot.com >>>>> Mobile: +94719371446 >>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Amila Maharachchi* >>>> Senior Software Engineer; WSO2, Inc.; http://wso2.com >>>> >>>> Blog: http://maharachchi.blogspot.com >>>> Mobile: +94719371446 >>>> >>>> >>>> >>> >>> >>> -- >>> *Amila Maharachchi* >>> Senior Software Engineer; WSO2, Inc.; http://wso2.com >>> >>> Blog: http://maharachchi.blogspot.com >>> Mobile: +94719371446 >>> >>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Chethiya Abeysinghe >> Software Engineer; WSO2, Inc.; http://wso2.com/ >> email: cheth...@wso2.com phone: +94 777444891 >> blog: chethiya3000.blogspot.com >> >> >> > > > -- > *Amila Maharachchi* > Senior Software Engineer; WSO2, Inc.; http://wso2.com > > Blog: http://maharachchi.blogspot.com > Mobile: +94719371446 > > > -- Chethiya Abeysinghe Software Engineer; WSO2, Inc.; http://wso2.com/ email: cheth...@wso2.com phone: +94 777444891 blog: chethiya3000.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] carbon-p2-repo 1.4-SNAPSHOT in trunk should 1.5-SNAPSHOT
carbon-p2-plugin in following pom files under platform/trunk/prodcuts have
been included as follows
carbon-p2-plugin
1.5-SNAPSHOT
I'm going to replace all those with ,
carbon-p2-plugin
${carbon.p2.plugin.version>}
So the version of the carbon-p2-plugin will inherit from the parent pom of
the product.
./as/modules/features/service/org.wso2.stratos.appserver.dashboard.ui.feature/pom.xml
./as/modules/features/service/org.wso2.stratos.appserver.deployment.feature/pom.xml
./as/modules/features/service/org.wso2.stratos.appserver.login.ui.feature/pom.xml
./as/modules/features/service/org.wso2.stratos.appserver.sample.installer.ui.feature/pom.xml
./as/modules/features/service/org.wso2.stratos.appserver.styles.feature/pom.xml
./as/modules/features/service/org.wso2.stratos.appserver.utils.feature/pom.xml
./as/modules/p2-profile-gen/service/pom.xml
./bam/modules/features/service/org.wso2.stratos.bam.styles.feature/pom.xml
./bam/modules/features/service/org.wso2.stratos.bam.ui.feature/pom.xml
./bam/modules/p2-profile-gen/service/pom.xml
./bps/modules/features/service/org.wso2.stratos.bps.dashboard.ui.feature/pom.xml
./bps/modules/features/service/org.wso2.stratos.bps.login.ui.feature/pom.xml
./bps/modules/features/service/org.wso2.stratos.bps.samples.utils.feature/pom.xml
./bps/modules/features/service/org.wso2.stratos.bps.styles.feature/pom.xml
./brs/modules/features/service/org.wso2.stratos.brs.dashboard.ui.feature/pom.xml
./brs/modules/features/service/org.wso2.stratos.brs.deployment.feature/pom.xml
./brs/modules/features/service/org.wso2.stratos.brs.login.ui.feature/pom.xml
./brs/modules/features/service/org.wso2.stratos.brs.styles.feature/pom.xml
./brs/modules/p2-profile/service/pom.xml
./csg/modules/features/service/org.wso2.stratos.csg.login.ui.feature/pom.xml
./csg/modules/features/service/org.wso2.stratos.csg.styles.feature/pom.xml
./csg/modules/p2-profile/service/pom.xml
./dss/modules/features/service/org.wso2.stratos.dss.dashboard.ui.feature/pom.xml
./dss/modules/features/service/org.wso2.stratos.dss.login.ui.feature/pom.xml
./dss/modules/features/service/org.wso2.stratos.dss.styles.feature/pom.xml
./dss/modules/p2-profile-gen/service/pom.xml
./esb/modules/features/service/org.wso2.stratos.esb.login.ui.feature/pom.xml
./esb/modules/features/service/org.wso2.stratos.esb.samples.feature/pom.xml
./esb/modules/features/service/org.wso2.stratos.esb.styles.feature/pom.xml
./esb/modules/p2-profile/service/pom.xml
./greg/modules/features/service/org.wso2.stratos.governance.ui.feature/pom.xml
./gs/modules/features/service/org.wso2.stratos.gadget.login.ui.feature/pom.xml
./gs/modules/features/service/org.wso2.stratos.gadget.menu.feature/pom.xml
./gs/modules/features/service/org.wso2.stratos.gadget.styles.feature/pom.xml
./gs/modules/p2-profile-gen/service/pom.xml
./gs2/modules/features/service/org.wso2.stratos.gadget.login.ui.feature/pom.xml
./gs2/modules/features/service/org.wso2.stratos.gadget.menu.feature/pom.xml
./gs2/modules/features/service/org.wso2.stratos.gadget.styles.feature/pom.xml
./gs2/modules/p2-profile-gen/service/pom.xml
./hosting/modules/features/service/org.wso2.stratos.hosting.dashboard.ui.feature/pom.xml
./hosting/modules/features/service/org.wso2.stratos.hosting.deployment.feature/pom.xml
./hosting/modules/features/service/org.wso2.stratos.hosting.login.ui.feature/pom.xml
./hosting/modules/features/service/org.wso2.stratos.hosting.sample.installer.ui.feature/pom.xml
./hosting/modules/features/service/org.wso2.stratos.hosting.styles.feature/pom.xml
./hosting/modules/features/service/org.wso2.stratos.hosting.utils.feature/pom.xml
./hosting/modules/p2-profile-gen/service/pom.xml
./manager/modules/features/service/org.wso2.stratos.manager.feature/pom.xml
./manager/modules/features/service/org.wso2.stratos.manager.server.feature/pom.xml
./manager/modules/features/service/org.wso2.stratos.manager.ui.feature/pom.xml
./manager/modules/p2-profile-gen/service/pom.xml
./ms/modules/features/service/org.wso2.ms.styles.feature/pom.xml
./ms/modules/features/service/org.wso2.stratos.ms.dashboard.ui.feature/pom.xml
./ms/modules/features/service/org.wso2.stratos.ms.deployment.feature/pom.xml
./ms/modules/features/service/org.wso2.stratos.ms.login.ui.feature/pom.xml
./ms/modules/features/service/org.wso2.stratos.ms.sample.installer.ui.feature/pom.xml
./ms/modules/features/service/org.wso2.stratos.ms.styles.feature/pom.xml
./ms/modules/p2-profile-gen/service/pom.xml
Thanks,
- Chethiya
On Fri, Apr 27, 2012 at 11:22 AM, Chethiya Abeysinghe wrote:
> Ok. I'll work on that.
> - Chethiya
>
>
> On Fri, Apr 27, 2012 at 11:12 AM, Sameera Jayasoma wrote:
>
>> +1 for 1.5-SHAPHOST. We need to change this version before the release.
>> Chethiya, can you please work on this?
>>
>> Thanks,
>> Sameera.
>>
>> On Wed, Apr 25, 2012 at 1:15 PM, Chethiya Abeysinghe
>> wrote:
Re: [Dev] WSO2 Committers += Chethiya
Hi, Thanks for making me a committer. Looking forward to contribute more. - Chethiya On Mon, May 7, 2012 at 3:01 PM, Dimuthu Leelarathne wrote: > Hi Chethiya, > > Congratulations! > > It is with great pleasure that we welcome you as a WSO2 committer. Thank > you for your contributions. > > thanks and best regards, > Dimuthu > > > -- > Dimuthu Leelarathne > Technical Lead > > WSO2, Inc. (http://wso2.com) > email: dimut...@wso2.com > > Lean . Enterprise . Middleware > > -- Chethiya Abeysinghe Software Engineer; WSO2, Inc.; http://wso2.com/ email: cheth...@wso2.com phone: +94 777444891 blog: chethiya3000.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Compilation failure at org.wso2.carbon.um.ws.service
it seems new org.wso2.carbon.um.ws.service.Util class is not imported. On Thu, May 24, 2012 at 7:15 AM, Janaka Ranabahu wrote: > Hi All, > > Im getting the following compilation failure. Any idea why? > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile > (default-compile) on project org.wso2.carbon.um.ws.service: Compilation > failure: Compilation failure: > [ERROR] > /media/NewVolume/carbon-branch/trunk/newTrunk/carbon/platform/trunk/components/remote-usermgt/org.wso2.carbon.um.ws.service/src/main/java/org/wso2/carbon/um/ws/service/UserStoreManagerService.java:[150,12] > cannot find symbol > [ERROR] symbol : variable Util > [ERROR] location: class > org.wso2.carbon.um.ws.service.UserStoreManagerService > [ERROR] > /media/NewVolume/carbon-branch/trunk/newTrunk/carbon/platform/trunk/components/remote-usermgt/org.wso2.carbon.um.ws.service/src/main/java/org/wso2/carbon/um/ws/service/UserStoreManagerService.java:[253,13] > cannot find symbol > [ERROR] symbol : variable Util > [ERROR] location: class > org.wso2.carbon.um.ws.service.UserStoreManagerService > [ERROR] > /media/NewVolume/carbon-branch/trunk/newTrunk/carbon/platform/trunk/components/remote-usermgt/org.wso2.carbon.um.ws.service/src/main/java/org/wso2/carbon/um/ws/service/AuthorizationManagerService.java:[50,8] > cannot find symbol > [ERROR] symbol : variable Util > [ERROR] location: class > org.wso2.carbon.um.ws.service.AuthorizationManagerService > [ERROR] > /media/NewVolume/carbon-branch/trunk/newTrunk/carbon/platform/trunk/components/remote-usermgt/org.wso2.carbon.um.ws.service/src/main/java/org/wso2/carbon/um/ws/service/AuthorizationManagerService.java:[57,8] > cannot find symbol > [ERROR] symbol : variable Util > [ERROR] location: class > org.wso2.carbon.um.ws.service.AuthorizationManagerService > [ERROR] -> [Help 1] > [ERROR] > > Thanks, > Janaka > > -- > Janaka Ranabahu > Software Engineer > WSO2 Inc. > > Mobile +94 718370861 > Email : jan...@wso2.com > Blog : janakaranabahu.blogspot.com > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Chethiya Abeysinghe Software Engineer; WSO2, Inc.; http://wso2.com/ email: cheth...@wso2.com phone: +94 777444891 blog: chethiya3000.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Getting rid of the doc generation from kernel
Hi,
It seem the conclusion at issue [1] is to do the $subject as we are moving
to a wiki based documentation. Doing so will reduce one another chance of
breaking the build.
Are we ready to do go ahead with this?
And if so, will removing [2] and editing [3] solve this problem.
It seems nothing else depends on directory at [2] except [3]. And no maven
project depends on artifact at [3] ("wso2carbon"
is nowhere mentioned in platform svn)
[1] - https://wso2.org/jira/browse/CARBON-13096
[2] -
https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/distribution/product/docs
[3] -
https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/distribution/product/modules/distribution/pom.xml
Thanks
--
Chethiya Abeysinghe
Software Engineer; WSO2, Inc.; http://wso2.com/
email: chethiya at wso2.com
blog: chethiya3000.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] org.wso2.carbon.registry.core.ghostregistry.GhostRegistry cannot be cast to org.wso2.carbon.registry.core.Registry
nvoke(StandardWrapperValve.java:225) >>> at >>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169) >>> at >>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) >>> at >>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168) >>> at >>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98) >>> at >>> org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:143) >>> at >>> org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156) >>> at >>> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927) >>> at >>> org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:48) >>> at >>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) >>> at >>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407) >>> at >>> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:999) >>> at >>> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:565) >>> at >>> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1620) >>> at >>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) >>> at >>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) >>> at java.lang.Thread.run(Thread.java:680) >>> >>> >>> -- >>> Regards, >>> >>> Tharindu >>> >>> blog: http://mackiemathew.com/ >>> M: +9459908 >>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Senaka Fernando* >> Product Manager - WSO2 Governance Registry; >> Associate Technical Lead; WSO2 Inc.; http://wso2.com* >> Member; Apache Software Foundation; http://apache.org >> >> E-mail: senaka AT wso2.com >> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >> Linked-In: http://linkedin.com/in/senakafernando >> >> *Lean . Enterprise . Middleware >> >> > > > -- > Regards, > > Tharindu > > blog: http://mackiemathew.com/ > M: +9459908 > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Chethiya Abeysinghe Software Engineer; WSO2, Inc.; http://wso2.com/ email: cheth...@wso2.com phone: +94 777444891 blog: chethiya3000.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Getting rid of the doc generation from kernel
Did the above mentioned change and it seems working fine. I'm going to
commit the change.
Thanks,
- Chethiya
On Fri, May 25, 2012 at 11:44 AM, Chethiya Abeysinghe wrote:
> Hi,
>
> It seem the conclusion at issue [1] is to do the $subject as we are moving
> to a wiki based documentation. Doing so will reduce one another chance of
> breaking the build.
> Are we ready to do go ahead with this?
>
> And if so, will removing [2] and editing [3] solve this problem.
>
> It seems nothing else depends on directory at [2] except [3]. And no maven
> project depends on artifact at [3] ("wso2carbon"
> is nowhere mentioned in platform svn)
>
>
> [1] - https://wso2.org/jira/browse/CARBON-13096
> [2] -
> https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/distribution/product/docs
> [3] -
> https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/distribution/product/modules/distribution/pom.xml
>
>
> Thanks
> --
> Chethiya Abeysinghe
> Software Engineer; WSO2, Inc.; http://wso2.com/
> email: chethiya at wso2.com
> blog: chethiya3000.blogspot.com
>
>
>
--
Chethiya Abeysinghe
Software Engineer; WSO2, Inc.; http://wso2.com/
email: cheth...@wso2.com phone: +94 777444891
blog: chethiya3000.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How to Check Whether you are Super Tenant?
This is
in
./org.wso2.carbon.registry.core/src/main/java/org/wso2/carbon/registry/app/RegistryResolver.java
and was a fix in recent hackathon. And this is the diff:
-if (tenantDomain == null) {
+if (tenantDomain == null ||
+
MultitenantConstants.SUPER_TENANT_DOMAIN_NAME.equals(tenantDomain))
{
It was a simple quick replace of the old logic using current mapping of *
tenantDomain* constants.
It's better to remove "||
MultitenantConstants.SUPER_TENANT_DOMAIN_NAME.equals(tenantDomain"
part I guess.
In fact do we need to proceed with the normal execution when there is no
tenantDomain in the servlet request? i.e. is it safe to try figure out the
domain name from username.
In case it's fine, there are two old bugs need to be fixed in
"getUserName()" and "getTenantId()".
- Chethiya
> Going through the code in Registry Kernel I discovered that you have made
> changes to determine whether you are super tenant as follows:
>
> tenantDomain == null ||
> MultitenantConstants.SUPER_TENANT_DOMAIN_NAME.equals(tenantDomain)
>
> Is this correct? Why are we checking for null or some constant?
>
> Thanks,
> Senaka.
>
> --
> *Senaka Fernando*
> Member - Integration Technologies Management Committee;
> Technical Lead; WSO2 Inc.; http://wso2.com*
> Member; Apache Software Foundation; http://apache.org
>
> E-mail: senaka AT wso2.com
> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
> Linked-In: http://linkedin.com/in/senakafernando
>
> *Lean . Enterprise . Middleware
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
--
Chethiya Abeysinghe
Software Engineer; WSO2, Inc.; http://wso2.com/
email: cheth...@wso2.com phone: +94 777444891
blog: chethiya3000.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] service-ui-config.xsd is taken effect rather than rxt.xsd when updating an RXT UI configuration
Hi,
I added new attribute called "" to repository/resources/rxt.xsd and added new RXT with
validate attribute in some fields.
Now when I'm going to update the rxt it gives the following error. That's
due to ManageGenericArtifactService using
org.wso2.carbon.governance.services.util.Util to validate updated content.
But that services.ui.Util class uses "service-ui-config.xsd" hardcoded in
it to validate.
Is it correct to put "" in
"service-ui-config.xsd" too? In fact what are the usages
of service-ui-config.xsd and rxt.xsd?
[2012-11-26 18:26:51,914] ERROR
{org.wso2.carbon.governance.services.util.Util} - Unable to validate the
given xml configuration
org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'validate'
is not allowed to appear in element 'field'.
at
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
Source)
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at
org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown
Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown
Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.processAttributes(Unknown
Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown
Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown
Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at
org.apache.xerces.jaxp.validation.StreamValidatorHelper.validate(Unknown
Source)
at org.apache.xerces.jaxp.validation.ValidatorImpl.validate(Unknown Source)
at javax.xml.validation.Validator.validate(Unknown Source)
* at
org.wso2.carbon.governance.services.util.Util.validateOMContent(Util.java:56)
*
* at
org.wso2.carbon.governance.services.util.Util.validateOMContent(Util.java:92)
*
* at
org.wso2.carbon.governance.generic.services.ManageGenericArtifactService.setArtifactUIConfiguration(ManageGenericArtifactService.java:317)
*
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.axis2.rpc.receivers.RPCUtil.invokeS
Thanks
--
Chethiya Abeysinghe
Software Engineer; WSO2, Inc.; http://wso2.com/
email: cheth...@wso2.com
blog: chethiya3000.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] A boolean attribute called "doValidation" to .rxt first element to optimise regex check
I'm planning to put $subject as an optimisation for API calls when adding
artifacts. When adding artifacts that belong to an RXT with this attribute
is "false" (or not present - for backward compatibility), will processed
faster bypassing the check. Otherwise there will be a recursive iterator
going through the RXT searching for fields with validation regex and doing
regex matching, for each addArtifact operation.
The only problem I have at the moment is the line 55:
OMElement head =
uigen.getUIConfiguration(client.getArtifactUIConfiguration(request.getParameter("key")),request,config,session);
in
platform/branches/4.0.0/components/governance/org.wso2.carbon.governance.generic.ui/4.0.5/src/main/resources/web/generic/add_edit.jsp
And similarly edit_ajaxprocessor.jsp too.
Here getArtifactUIConfiguration() only extracts the element of
the .rxt.
One solution is to put this optional "doValidation" attribute to
element as at BE OMElement for is anyway created. Is this viable?
I don't see any attribute in this element yet too.
Another solution for this is to add a new method
to ManageGenericArtifactService.java which is in
org.wso2.carbon.governance.generic. This will extract the content of the
actual .rxt resource.
Thanks
--
Chethiya Abeysinghe
Software Engineer; WSO2, Inc.; http://wso2.com/
email: cheth...@wso2.com
blog: chethiya3000.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] A boolean attribute called "doValidation" to .rxt first element to optimise regex check
Hi Senaka,
On Dec 1, 2012 7:29 AM, "Senaka Fernando" wrote:
>
> Hi Chethiya,
>
> Well my expectation was to do it in a way where each field will have an
attribute. If the attribute is present, we validate, if not we don't.
Therefore, this additional attribute sounds redundant to me. WDYT?
Ya we have those attributes in each field in need of validation. This
attribute I'm talking about should be in a root level element and yes it is
redundant. But I'm suggesting this redundancy for an optimization. I.e not
to iterate through the XML to find fields with validation when there is an
indication at the top saying not to do so.
Why we need to decide this now is if we don't put this attribute now, we
will be in trouble providing backward compatibility, in case we will need
to add this attribute later.
BTW currently add artifact method loads every rxt, parse all, matches the
one with required key, then load required data from it to a configuration
object by iterating. Possible optimization for these expensive operations
are using a bounded cache. In such a case we alternatively can generate
boolean called doValidation when loading the configuration to the cache.
In such a case this attribute is not really necessary to be in the rxt. But
if this is not a problem for the rxt writer, having this redundancy is the
optimal!
- Chethiya
>
> Thanks,
> Senaka.
>
>
> On Sat, Dec 1, 2012 at 1:22 AM, Chethiya Abeysinghe
wrote:
>>
>> I'm planning to put $subject as an optimisation for API calls when
adding artifacts. When adding artifacts that belong to an RXT with this
attribute is "false" (or not present - for backward compatibility), will
processed faster bypassing the check. Otherwise there will be a recursive
iterator going through the RXT searching for fields with validation regex
and doing regex matching, for each addArtifact operation.
>>
>> The only problem I have at the moment is the line 55:
>>
>> OMElement head =
uigen.getUIConfiguration(client.getArtifactUIConfiguration(request.getParameter("key")),request,config,session);
>>
>> in
>>
>>
platform/branches/4.0.0/components/governance/org.wso2.carbon.governance.generic.ui/4.0.5/src/main/resources/web/generic/add_edit.jsp
>>
>> And similarly edit_ajaxprocessor.jsp too.
>>
>> Here getArtifactUIConfiguration() only extracts the element of
the .rxt.
>>
>> One solution is to put this optional "doValidation" attribute to
element as at BE OMElement for is anyway created. Is
this viable? I don't see any attribute in this element yet too.
>>
>> Another solution for this is to add a new method
to ManageGenericArtifactService.java which is in
org.wso2.carbon.governance.generic. This will extract the content of the
actual .rxt resource.
>>
>> Thanks
>> --
>> Chethiya Abeysinghe
>> Software Engineer; WSO2, Inc.; http://wso2.com/
>> email: cheth...@wso2.com
>> blog: chethiya3000.blogspot.com
>>
>>
>
>
>
> --
>
>
> Senaka Fernando
> Member - Integration Technologies Management Committee;
> Technical Lead; WSO2 Inc.; http://wso2.com
> Member; Apache Software Foundation; http://apache.org
>
> E-mail: senaka AT wso2.com
> P: +1 408 754 7388; ext: 51736; M: +94 77 322 1818
> Linked-In: http://linkedin.com/in/senakafernando
>
> Lean . Enterprise . Middleware
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] A boolean attribute called "doValidation" to .rxt first element to optimise regex check
Ok. Will commit it without the proposed redundancy. There seems to be other
ways to do this as you mentioned. We'll figure that out once this is done.
Thanks.
- Chethiya
On Sat, Dec 1, 2012 at 1:49 PM, Senaka Fernando wrote:
> Hi Chethiya,
>
> What I'm most concerned is the inconvenience to the user in here. I know
> that this would bring about a performance gain, but I think usability does
> win. However, we should not simply rule this out.
>
> Isn't there any other way to do this? What's the hit in having a single
> XPath check to figure out whether at least one attribute is set? Or, right
> now, the artifact payload is parsed at least once when we build the
> content. Can't we have an in-place validation. This would mean that the
> existence check for the validation is IIRC a fairly inexpensive,
> getAttribute call on the OMElement. Or is there a possibility to introduce
> some form of caching and improve this later on, and leave what we have at
> the moment?
>
> Thanks,
> Senaka.
>
> On Sat, Dec 1, 2012 at 1:40 PM, Chethiya Abeysinghe wrote:
>
>> Hi Senaka,
>>
>> On Dec 1, 2012 7:29 AM, "Senaka Fernando" wrote:
>> >
>> > Hi Chethiya,
>> >
>> > Well my expectation was to do it in a way where each field will have an
>> attribute. If the attribute is present, we validate, if not we don't.
>> Therefore, this additional attribute sounds redundant to me. WDYT?
>>
>> Ya we have those attributes in each field in need of validation. This
>> attribute I'm talking about should be in a root level element and yes it is
>> redundant. But I'm suggesting this redundancy for an optimization. I.e not
>> to iterate through the XML to find fields with validation when there is an
>> indication at the top saying not to do so.
>>
>> Why we need to decide this now is if we don't put this attribute now, we
>> will be in trouble providing backward compatibility, in case we will need
>> to add this attribute later.
>>
>> BTW currently add artifact method loads every rxt, parse all, matches the
>> one with required key, then load required data from it to a configuration
>> object by iterating. Possible optimization for these expensive operations
>> are using a bounded cache. In such a case we alternatively can generate
>> boolean called doValidation when loading the configuration to the cache.
>>
>> In such a case this attribute is not really necessary to be in the rxt.
>> But if this is not a problem for the rxt writer, having this redundancy is
>> the optimal!
>>
>> - Chethiya
>>
>> >
>> > Thanks,
>> > Senaka.
>> >
>> >
>> > On Sat, Dec 1, 2012 at 1:22 AM, Chethiya Abeysinghe
>> wrote:
>> >>
>> >> I'm planning to put $subject as an optimisation for API calls when
>> adding artifacts. When adding artifacts that belong to an RXT with this
>> attribute is "false" (or not present - for backward compatibility), will
>> processed faster bypassing the check. Otherwise there will be a recursive
>> iterator going through the RXT searching for fields with validation regex
>> and doing regex matching, for each addArtifact operation.
>> >>
>> >> The only problem I have at the moment is the line 55:
>> >>
>> >> OMElement head =
>> uigen.getUIConfiguration(client.getArtifactUIConfiguration(request.getParameter("key")),request,config,session);
>> >>
>> >> in
>> >>
>> >>
>> platform/branches/4.0.0/components/governance/org.wso2.carbon.governance.generic.ui/4.0.5/src/main/resources/web/generic/add_edit.jsp
>> >>
>> >> And similarly edit_ajaxprocessor.jsp too.
>> >>
>> >> Here getArtifactUIConfiguration() only extracts the element
>> of the .rxt.
>> >>
>> >> One solution is to put this optional "doValidation" attribute to
>> element as at BE OMElement for is anyway created. Is
>> this viable? I don't see any attribute in this element yet too.
>> >>
>> >> Another solution for this is to add a new method
>> to ManageGenericArtifactService.java which is in
>> org.wso2.carbon.governance.generic. This will extract the content of the
>> actual .rxt resource.
>> >>
>> >> Thanks
>> >> --
>> >> Chethiya Abeysinghe
>> >> Software Engineer; WSO2, Inc.; http://wso2.com/
>> >> email: cheth...@wso2.com
>> >> blog: chethiya3000.blogspot.com
>> >>
>
Re: [Dev] wso2server.bat is updated to support UTF8 encoding on Windows by default
There are different Unix/Linux distros not having UTF8 by default. So we might have to consider doing this for .sh file too? - chethiya software engineer, WSO2 On Dec 6, 2012 3:09 PM, "Dileepa Jayakody" wrote: > Only changed the .bat file [1] because this is specific to Windows > > [1] > https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0/distribution/kernel/4.0.5/carbon-home/bin/wso2server.bat > > On Thu, Dec 6, 2012 at 2:59 PM, Dileepa Jayakody wrote: > >> Hi All, >> >> As a fix to [1], UTF8 characters not supported on Windows by default, I >> added the *-Dfile.encoding=UTF8 * parameter to wso2server.bat file in >> Kernel [2]. >> If anyone uses different/updated startup script please update the .bat >> script accordingly. >> >> Thanks, >> Dileepa >> >> [1] https://wso2.org/jira/browse/CARBON-14012 >> [2] >> https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0/distribution/kernel/4.0.5/carbon-home/bin >> >> -- >> Dileepa Jayakody, >> Software Engineer, WSO2 Inc. >> Lean . Enterprise . Middleware >> >> Mobile : +94777-857616 >> >> > > > -- > Dileepa Jayakody, > Software Engineer, WSO2 Inc. > Lean . Enterprise . Middleware > > Mobile : +94777-857616 > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] {branch 4.0.5}Registry metadata list menu is not working
> org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:101) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) > at > org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:36) > at > org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90) > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Chethiya Abeysinghe Software Engineer; WSO2, Inc.; http://wso2.com/ email: cheth...@wso2.com phone: +94 777444891 blog: chethiya3000.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Changing the nexus-repo URL of snmp4j-repo (https://server.oosnmp.net/dist/release/)
Still this error can occur while building particular maven projects of released brunches, trying to resolve old synapse versions as transitive dependencies. e.g. trying to run tests-new in greg 4.5.1. In such a case, adding following to the pom.xml of the errornous project might be a good solutions snmp4j-repo SNMP4J Repository https://dist.oosnmp.net/dist/release/ false never false Cheers, - Chethiya On Wed, Jan 23, 2013 at 11:22 AM, Chethiya Abeysinghe wrote: > > On Wed, Jan 23, 2013 at 9:31 AM, Dileepa Jayakody wrote: > >> If you are building 2.1.1-wso2v1, can you please comment out this invalid >> repo and try building? >> > > Thakns Dileepa. Ya, it's better getting rid of that repo. It solved me > getting this error. > > > > -- > Chethiya Abeysinghe > Software Engineer; WSO2, Inc.; http://wso2.com/ > email: cheth...@wso2.com phone: +94 777444891 > blog: chethiya3000.blogspot.com > > -- Chethiya Abeysinghe Software Engineer; WSO2, Inc.; http://wso2.com/ email: cheth...@wso2.com phone: +94 777444891 blog: chethiya3000.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] OSGi version range issue when deploying a bundle in dropins
y.core_4.0.0.SNAPSHOT [355] imports >>> >>> osgi> b 79 >>> jclouds-sshj_1.5.0.beta_2 [79] >>> Id=79, Status=ACTIVE Data >>> Root=/media/wso2/new-carbon/graphite/products/as/modules/distribution/target/wso2as-5.0.0-SNAPSHOT/repository/components/configuration/org.eclipse.osgi/bundles/79/data >>> No registered services. >>> No services in use. >>> Exported packages >>> org.jclouds.sshj.config; version="1.5.0.beta2"[exported] >>> org.jclouds.sshj; version="1.5.0.beta2"[exported] >>> Imported packages >>> com.google.common.base; version="12.0.0.wso2v1">> [55]> >>> com.google.common.collect; >>> version="12.0.0.wso2v1" >>> com.google.common.io; version="12.0.0.wso2v1">> [55]> >>> com.google.common.net; version="12.0.0.wso2v1">> [55]> >>> com.google.inject; version="1.3.0" >>> com.google.inject.binder; version="1.3.0">> [34]> >>> javax.annotation; version="0.0.0">> [0]> >>> javax.inject; version="3.0.0.wso2v1" >>> net.schmizz.sshj; version="0.8.0" >>> net.schmizz.sshj.common; version="0.8.0">> [101]> >>> net.schmizz.sshj.connection; version="0.8.0">> [101]> >>> net.schmizz.sshj.connection.channel.direct; >>> version="0.8.0" >>> net.schmizz.sshj.sftp; version="0.8.0" >>> net.schmizz.sshj.transport; version="0.8.0">> [101]> >>> net.schmizz.sshj.transport.verification; >>> version="0.8.0" >>> net.schmizz.sshj.userauth; version="0.8.0">> [101]> >>> net.schmizz.sshj.userauth.keyprovider; >>> version="0.8.0" >>> net.schmizz.sshj.xfer; version="0.8.0" >>> org.apache.commons.io.input; >>> version="2.0.0" >>> org.jclouds.compute.domain; >>> version="1.5.0.beta2" >>> org.jclouds.crypto; version="1.5.0.beta2">> [72]> >>> org.jclouds.domain; version="1.5.0.beta2">> [72]> >>> org.jclouds.http.handlers; >>> version="1.5.0.beta2" >>> org.jclouds.io; version="1.5.0.beta2">> [72]> >>> org.jclouds.io.payloads; >>> version="1.5.0.beta2" >>> org.jclouds.logging; version="1.5.0.beta2">> [72]> >>> org.jclouds.predicates; >>> version="1.5.0.beta2" >>> org.jclouds.rest; version="1.5.0.beta2">> [72]> >>> org.jclouds.ssh; version="1.5.0.beta2">> [71]> >>> org.jclouds.util; version="1.5.0.beta2">> [72]> >>> No fragment bundles >>> Named class space >>> jclouds-sshj; bundle-version="1.5.0.beta_2"[provided] >>> No required bundles >>> >>> >>> >>> -- >>> >>> Thanks & regards, >>> Nirmal >>> >>> Software Engineer- Platform Technologies Team, WSO2 Inc. >>> Mobile: +94715779733 >>> Blog: http://nirmalfdo.blogspot.com/ >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Amila Maharachchi* >> Technical Lead >> Member, Management Committee - Cloud & Platform TG >> WSO2, Inc.; http://wso2.com >> >> Blog: http://maharachchi.blogspot.com >> Mobile: +94719371446 >> >> >> > > > -- > > Thanks & regards, > Nirmal > > Software Engineer- Platform Technologies Team, WSO2 Inc. > Mobile: +94715779733 > Blog: http://nirmalfdo.blogspot.com/ > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Chethiya Abeysinghe Software Engineer; WSO2, Inc.; http://wso2.com/ email: cheth...@wso2.com phone: +94 777444891 blog: chethiya3000.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Removing duplicated orbits in 4.0.0 branch with 3.2.0 branch
Hi, We (I and Pradeep) have removed following orbits from 4.0.0 orbit branch at https://svn.wso2.org/repos/wso2/carbon/orbit/branches/4.0.0/ Idea behind that was to remove orbits with duplicated version in 3.2.0 branch at https://svn.wso2.org/repos/wso2/branches/carbon/3.2.0/orbit/ Please note that if you have done some changes to orbits and forgot to upgrade the version number of those orbits, those orbits should have been removed by this change. Anyway to make sure things are going fine with remaining set of orbits we will try do a build with a clean repo. Btw, we have notices there was one case with 'httpclient' orbit having version ""4.1.1-wso2v1" whereas in 3.2.0 orbits branch there was a bundle with version "4.1.1.wso2v1". We have removed this orbit too. Looking at the svn log of it, it looks like this version change is done by Nuwan on 2011-09-27 (r113161). @Nuwan Can you please let us know if this is NOT the same version of orbit exported in previous release. Deleting jakarta-taglibs Deleting janino Deleting jaxbri Deleting jaxws Deleting jena Deleting jettison Deleting jml Deleting joscar-client Deleting joscar-common Deleting joscar-protocol Deleting jruby Deleting js Deleting jsch Deleting json-simple Deleting jsr94 Deleting juddi Deleting jug Deleting ooxml-spreadsheet-schemas Deleting opencsv Deleting openid4java Deleting org.wso2.carbon.js.1.6R7 Deleting org.wso2.carbon.solr.client Deleting paypal Deleting perf4j Deleting quartz2 Deleting quickfixj Deleting rome Deleting savan-core Deleting saxon-bps Deleting smack Deleting smackx Deleting smooks Deleting solr Deleting step2 Deleting tranql-connector Deleting xalan-ode Deleting xerces Deleting xml-apis Deleting yaml Deleting derby Deleting drools Deleting geronimo-ejb_2.1_spec Deleting geronimo-jms_1.1_spec Deleting geronimo-kernel Deleting geronimo-spec-javamail Deleting geronimo-spec-jms Deleting hsqldb *Deleting httpclient* Deleting httpcore Deleting httpcore-nio Deleting *amber* Deleting avro Deleting axiom Deleting axion Deleting axis Deleting backport-util-concurrent Deleting commons-beanutils Deleting commons-cli Deleting commons-collections Deleting commons-configuration Deleting commons-dbcp Deleting commons-io Deleting commons-net Deleting commons-scxml Deleting compass Thanks, -- Chethiya Abeysinghe Software Engineer; WSO2, Inc.; http://wso2.com/ email: chethiya at wso2.com blog: chethiya3000.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Removing duplicated orbits in 4.0.0 branch with 3.2.0 branch
Hi, Further looking into the changes done to above orbits relative to their 3.2.0 orbit branch counterparts (by diff and svn log), we came with following list of orbits. We assume these changes need a version upgrade for these orbits. jaxbri - lot of changes jruby - bundle imports/exports changed juddi - deleted soem dependencies quickfixj - removed dependancy and changed the name saxon-bps - include DynamicImport xml-apis - bundle import/exports are changed amber - no amber in 3.2.0 axiom - dependancy delete, imports/export changed Owners of these orbits, please make sure to correct these orbits (probably you'll need to upgrade the version number) AND commit those changes to BOTH orbit/trunk and 4.0.0 orbit branch. Thanks, -Chethiya On Wed, Jul 11, 2012 at 11:16 AM, Anjana Fernando wrote: > Hi Pradeep, Chethiya, > > I did the required change in ndatasource.core, and I verified this by > debugging the "BundleCheckActivator" class to see if the ndatasource.core > bundle is picking up as having a DeployBefore header and matching with > UserCore requirement. For me though, the ndatasource bundle is always > activated (I put some sysouts and checked) before that point, but in some > situation the order can change as it may have happened to you. I've built > and run this with the maven repo I had with the trunk Orbit bundles, and it > works fine. And I just started on building the Orbit 4.0.0 branch with a > clean repo, so it will take some time to check it. In the meanwhile I've > committed the change, so it will great if one of you can test it since you > already have the new repo. > > Cheers, > Anjana. > > > On Wed, Jul 11, 2012 at 10:53 AM, Anjana Fernando wrote: > >> Hi Pradeep, >> >> This most probably because of another issue we got this, where the >> startup order of user-core and the ndatasource bundles got changed, and it >> can be that it is by pure chance that it worked earlier by ndatasource >> always activating first before user-core, I'm adding the bundle header >> "DeployBefore: User-Core" to ndatasource now, and will do some tests. >> >> Cheers, >> Anjana. >> >> >> On Wed, Jul 11, 2012 at 9:48 AM, Pradeep Fernando wrote: >> >>> Hi Chethiya, >>> >>> looks like we have to check the above orbits and see whether there are >>> significant modifications. Can you start on that please. I will join as >>> well. >>> >>> it will be a painful process :) >>> >>> --Pradeep >>> >> >> >> >> -- >> *Anjana Fernando* >> Associate Technical Lead >> WSO2 Inc. | http://wso2.com >> lean . enterprise . middleware >> > > > > -- > *Anjana Fernando* > Associate Technical Lead > WSO2 Inc. | http://wso2.com > lean . enterprise . middleware > -- Chethiya Abeysinghe Software Engineer; WSO2, Inc.; http://wso2.com/ email: cheth...@wso2.com phone: +94 777444891 blog: chethiya3000.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Removing duplicated orbits in 4.0.0 branch with 3.2.0 branch
Hi, SVN blame and log suggest most recent and significant changes for these bundles are done by following committers. Please attend to these ASAP to upgrade orbit versions. Please commit changes to the trunk and and 4.0.0 branch. jruby - bundle imports/exports changed -- 118810 | rathav juddi - deleted soem dependencies --- 130051 | waruna, r126920 | isuruw quickfixj - removed dependancy and changed the name -- r108637 | amilaj (old fix in 06-2011) saxon-bps - include DynamicImport r115971 | waruna xml-apis - bundle import/exports are changed r113161 | nuwan axiom - dependancy delete, imports/export changed --- r124825 | isuru Thanks, - Chethiya On Wed, Jul 11, 2012 at 3:07 PM, Chethiya Abeysinghe wrote: > Hi, > > Further looking into the changes done to above orbits relative to their > 3.2.0 orbit branch counterparts (by diff and svn log), we came with > following list of orbits. We assume these changes need a version upgrade > for these orbits. > > jaxbri - lot of changes > jruby - bundle imports/exports changed > juddi - deleted soem dependencies > quickfixj - removed dependancy and changed the name > saxon-bps - include DynamicImport > xml-apis - bundle import/exports are changed > amber - no amber in 3.2.0 > axiom - dependancy delete, imports/export changed > > Owners of these orbits, please make sure to correct these orbits (probably > you'll need to upgrade the version number) AND commit those changes to BOTH > orbit/trunk and 4.0.0 orbit branch. > > Thanks, > -Chethiya > > On Wed, Jul 11, 2012 at 11:16 AM, Anjana Fernando wrote: > >> Hi Pradeep, Chethiya, >> >> I did the required change in ndatasource.core, and I verified this by >> debugging the "BundleCheckActivator" class to see if the ndatasource.core >> bundle is picking up as having a DeployBefore header and matching with >> UserCore requirement. For me though, the ndatasource bundle is always >> activated (I put some sysouts and checked) before that point, but in some >> situation the order can change as it may have happened to you. I've built >> and run this with the maven repo I had with the trunk Orbit bundles, and it >> works fine. And I just started on building the Orbit 4.0.0 branch with a >> clean repo, so it will take some time to check it. In the meanwhile I've >> committed the change, so it will great if one of you can test it since you >> already have the new repo. >> >> Cheers, >> Anjana. >> >> >> On Wed, Jul 11, 2012 at 10:53 AM, Anjana Fernando wrote: >> >>> Hi Pradeep, >>> >>> This most probably because of another issue we got this, where the >>> startup order of user-core and the ndatasource bundles got changed, and it >>> can be that it is by pure chance that it worked earlier by ndatasource >>> always activating first before user-core, I'm adding the bundle header >>> "DeployBefore: User-Core" to ndatasource now, and will do some tests. >>> >>> Cheers, >>> Anjana. >>> >>> >>> On Wed, Jul 11, 2012 at 9:48 AM, Pradeep Fernando wrote: >>> >>>> Hi Chethiya, >>>> >>>> looks like we have to check the above orbits and see whether there are >>>> significant modifications. Can you start on that please. I will join as >>>> well. >>>> >>>> it will be a painful process :) >>>> >>>> --Pradeep >>>> >>> >>> >>> >>> -- >>> *Anjana Fernando* >>> Associate Technical Lead >>> WSO2 Inc. | http://wso2.com >>> lean . enterprise . middleware >>> >> >> >> >> -- >> *Anjana Fernando* >> Associate Technical Lead >> WSO2 Inc. | http://wso2.com >> lean . enterprise . middleware >> > > > > -- > Chethiya Abeysinghe > Software Engineer; WSO2, Inc.; http://wso2.com/ > email: cheth...@wso2.com phone: +94 777444891 > blog: chethiya3000.blogspot.com > > > -- Chethiya Abeysinghe Software Engineer; WSO2, Inc.; http://wso2.com/ email: cheth...@wso2.com phone: +94 777444891 blog: chethiya3000.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Removing duplicated orbits in 4.0.0 branch with 3.2.0 branch
I'm updating quickfixj orbit. On Wed, Jul 11, 2012 at 5:08 PM, Chethiya Abeysinghe wrote: > Hi, > > SVN blame and log suggest most recent and significant changes for these > bundles are done by following committers. Please attend to these ASAP to > upgrade orbit versions. Please commit changes to the trunk and and 4.0.0 > branch. > > jruby - bundle imports/exports changed -- 118810 | rathav > juddi - deleted soem dependencies --- 130051 | waruna, r126920 | isuruw > quickfixj - removed dependancy and changed the name -- r108637 | amilaj > (old fix in 06-2011) > saxon-bps - include DynamicImport r115971 | waruna > xml-apis - bundle import/exports are changed r113161 | nuwan > axiom - dependancy delete, imports/export changed --- r124825 | isuru > > Thanks, > - Chethiya > > > On Wed, Jul 11, 2012 at 3:07 PM, Chethiya Abeysinghe wrote: > >> Hi, >> >> Further looking into the changes done to above orbits relative to their >> 3.2.0 orbit branch counterparts (by diff and svn log), we came with >> following list of orbits. We assume these changes need a version upgrade >> for these orbits. >> >> jaxbri - lot of changes >> jruby - bundle imports/exports changed >> juddi - deleted soem dependencies >> quickfixj - removed dependancy and changed the name >> saxon-bps - include DynamicImport >> xml-apis - bundle import/exports are changed >> amber - no amber in 3.2.0 >> axiom - dependancy delete, imports/export changed >> >> Owners of these orbits, please make sure to correct these orbits >> (probably you'll need to upgrade the version number) AND commit those >> changes to BOTH orbit/trunk and 4.0.0 orbit branch. >> >> Thanks, >> -Chethiya >> >> On Wed, Jul 11, 2012 at 11:16 AM, Anjana Fernando wrote: >> >>> Hi Pradeep, Chethiya, >>> >>> I did the required change in ndatasource.core, and I verified this by >>> debugging the "BundleCheckActivator" class to see if the ndatasource.core >>> bundle is picking up as having a DeployBefore header and matching with >>> UserCore requirement. For me though, the ndatasource bundle is always >>> activated (I put some sysouts and checked) before that point, but in some >>> situation the order can change as it may have happened to you. I've built >>> and run this with the maven repo I had with the trunk Orbit bundles, and it >>> works fine. And I just started on building the Orbit 4.0.0 branch with a >>> clean repo, so it will take some time to check it. In the meanwhile I've >>> committed the change, so it will great if one of you can test it since you >>> already have the new repo. >>> >>> Cheers, >>> Anjana. >>> >>> >>> On Wed, Jul 11, 2012 at 10:53 AM, Anjana Fernando wrote: >>> >>>> Hi Pradeep, >>>> >>>> This most probably because of another issue we got this, where the >>>> startup order of user-core and the ndatasource bundles got changed, and it >>>> can be that it is by pure chance that it worked earlier by ndatasource >>>> always activating first before user-core, I'm adding the bundle header >>>> "DeployBefore: User-Core" to ndatasource now, and will do some tests. >>>> >>>> Cheers, >>>> Anjana. >>>> >>>> >>>> On Wed, Jul 11, 2012 at 9:48 AM, Pradeep Fernando wrote: >>>> >>>>> Hi Chethiya, >>>>> >>>>> looks like we have to check the above orbits and see whether there are >>>>> significant modifications. Can you start on that please. I will join as >>>>> well. >>>>> >>>>> it will be a painful process :) >>>>> >>>>> --Pradeep >>>>> >>>> >>>> >>>> >>>> -- >>>> *Anjana Fernando* >>>> Associate Technical Lead >>>> WSO2 Inc. | http://wso2.com >>>> lean . enterprise . middleware >>>> >>> >>> >>> >>> -- >>> *Anjana Fernando* >>> Associate Technical Lead >>> WSO2 Inc. | http://wso2.com >>> lean . enterprise . middleware >>> >> >> >> >> -- >> Chethiya Abeysinghe >> Software Engineer; WSO2, Inc.; http://wso2.com/ >> email: cheth...@wso2.com phone: +94 777444891 >> blog: chethiya3000.blogspot.com >> >> >> > > > -- > Chethiya Abeysinghe > Software Engineer; WSO2, Inc.; http://wso2.com/ > email: cheth...@wso2.com phone: +94 777444891 > blog: chethiya3000.blogspot.com > > > -- Chethiya Abeysinghe Software Engineer; WSO2, Inc.; http://wso2.com/ email: cheth...@wso2.com phone: +94 777444891 blog: chethiya3000.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Removing duplicated orbits in 4.0.0 branch with 3.2.0 branch
On Thu, Jul 12, 2012 at 11:55 AM, Vijayaratha Vijayasingam wrote: > Upgraded the jruby version > Only committed to trunk. I'm moving it to the 4.0.0 orbit branch. > > On 12 July 2012 11:51, Pradeep Fernando wrote: > >> shelan is working on axiom branching. hence we have one less orbit >> bundle to worry. >> >> --Pradeep >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Chethiya Abeysinghe Software Engineer; WSO2, Inc.; http://wso2.com/ email: cheth...@wso2.com phone: +94 777444891 blog: chethiya3000.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Bamboo-Build] Carbon Snapshot > Platform > #473 has FAILED (3 tests failed). Change made by 4 authors.
> View >> full test >> details<http://wso2.org/bamboo/browse/WSO2CARBON-PLATFORM-473/test> 3 >> New Test Failures Test Job TestSiddhiBackendRuntime >> testBAMEvent<http://wso2.org/bamboo/browse/WSO2CARBON-PLATFORM-JOB1-473/test/case/14551924> >> Default >> Job <http://wso2.org/bamboo/browse/WSO2CARBON-PLATFORM-JOB1-473/test> >> TestSiddhiBackendRuntime >> testStockTweet<http://wso2.org/bamboo/browse/WSO2CARBON-PLATFORM-JOB1-473/test/case/14551398> >> Default >> Job <http://wso2.org/bamboo/browse/WSO2CARBON-PLATFORM-JOB1-473/test> >> TestSiddhiBackendRuntime >> testQuery<http://wso2.org/bamboo/browse/WSO2CARBON-PLATFORM-JOB1-473/test/case/14551818> >> Default >> Job <http://wso2.org/bamboo/browse/WSO2CARBON-PLATFORM-JOB1-473/test> >> View >> Online <http://wso2.org/bamboo/browse/WSO2CARBON-PLATFORM-473> | Add >> Comments<http://wso2.org/bamboo/browse/WSO2CARBON-PLATFORM-473?commentMode=true> >> >> This message was sent by Atlassian Bamboo <http://wso2.org/bamboo>. >> >> If you wish to stop receiving these emails edit your user >> profile<http://wso2.org/bamboo/profile/userNotifications.action>or notify >> your administrator <http://wso2.org/bamboo/viewAdministrators.action>. >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Isuru Udana* > * > * > * > Software Engineer > * > Integration Technologies Team, WSO2 Inc.; http://wso2.com > email: isu...@wso2.com cell: +94 77 3791887 > blog: http://mytecheye.blogspot.com/ > twitter: http://twitter.com/isudana > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Chethiya Abeysinghe Software Engineer; WSO2, Inc.; http://wso2.com/ email: cheth...@wso2.com phone: +94 777444891 blog: chethiya3000.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Branching tool 2 used for applying branching strategy for Carbon 4.0.0 release work
Hi, Please find the changed version of branching tool at https://svn.wso2.org/repos/wso2/people/chethiya/branching-tool2. Please find the README file in it for usage instructions. Improvements: - extract the version of a pom form the leaf pom.xml(s) in the tree to be used for the branching strategy - modified pom-search.py to search recursively to alert incorrectly picked versions. Thanks -- Chethiya Abeysinghe Software Engineer; WSO2, Inc.; http://wso2.com/ email: cheth...@wso2.com blog: chethiya3000.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Important]C4 release: open L1 and L2 s
On Tue, Jul 24, 2012 at 12:48 PM, Pradeep Fernando wrote:
> Hi All,
>
> Here are the L1/L2 s that are in open state.
>
>
> **L1s**
> CARBON-13619 Clean up conf/README file and make catalina_server.xml
> as the default cofig file which can change the http/s ports statically.
> -Dileepa Jayakody
> CARBON-13534 CipherTool and Secure Vault are broken in trunk
> -Asela Pathberiya
>
> **L2s**
> CARBON-13635 NPE when running a load test with resource adding
> -Dimuthu Leelarathne
> CARBON-13608 Fix jgroups.bind_addr property -Dimuthu Leelarathne
> CARBON-13591 Login and logout user difference -Amila Maharachchi
> CARBON-13588 Modify Security Manager to allow tenants to read Rhino
> code generated folder -Chethiya Abeysinghe
>
I have been working on a solution for this. When tried to test it out with
a signed pack having security settings enabled, I noticed that this problem
is no longer in current AS build. I've also commented on the jira @
https://wso2.org/jira/browse/CARBON-13588, This is working probably due to
a change done by Ruchira.
> CARBON-13502 Ant task doesn't work to create war file [createWAR]
> -Pradeep
> CARBON-13386 Intermittent issue: ERROR
> {org.infinispan.interceptors.InvocationContextInterceptor} - ISPN000136:
> Execution error java.lang.InterruptedException when shutting down G-reg
> -Dimuthu
> CARBON-13208 TenantMgt AdminService invocation with wrong credentials
> returns too much of information to the user, but the information is also
> wrong -Kathiravelu Pradeeban
> CARBON-13167 supporting web-app mode deployment of carbon in Apache
> Tomcat -Pradeep Fernando
> CARBON-13140 wso2server.sh is not working with Solaris 10 in beta
> Packs-Reka Thirunavukkarasu
> CARBON-12895 Cannot enable JMS transport listener from UI -dushan
> abeyruwan
> CARBON-10230 Inconsistency of product clusters -Thilini Ishaka
>
>
> Carbon core *code freeze on tomorrow*, tentative release *date on 27 th*.
> I need a *progress update of each of the issues before EOD today.*(working on
> it/ not started/ not possible with this release/etc)
>
>
> regarding two issues assigned to me - will try to make them available in
> this release. Otherwise they will go out in a point release.
>
> thanks,
> --Pradeep
>
>
>
>
--
Chethiya Abeysinghe
Software Engineer; WSO2, Inc.; http://wso2.com/
email: cheth...@wso2.com phone: +94 777444891
blog: chethiya3000.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Important]C4 release: open L1 and L2 s
Chethiya Abeysinghe
Software Engineer at wso2
On Jul 24, 2012 11:11 PM, "Senaka Fernando" wrote:
>
> Hi Chethiya,
>
> Can you help with [1]? Pradeep seems to be having some blockers related
to WAR deployment.
Sure, will have a look.
>
> [1] https://wso2.org/jira/browse/CARBON-13677
>
> Thanks,
> Senaka.
>
> On Tue, Jul 24, 2012 at 11:04 AM, Chethiya Abeysinghe
wrote:
>>
>>
>>
>> On Tue, Jul 24, 2012 at 12:48 PM, Pradeep Fernando
wrote:
>>>
>>> Hi All,
>>>
>>> Here are the L1/L2 s that are in open state.
>>>
>>>
>>> **L1s**
>>> CARBON-13619 Clean up conf/README file and make
catalina_server.xml as the default cofig file which can change the http/s
ports statically. -Dileepa Jayakody
>>> CARBON-13534 CipherTool and Secure Vault are broken in trunk
-Asela Pathberiya
>>>
>>> **L2s**
>>> CARBON-13635 NPE when running a load test with resource adding
-Dimuthu Leelarathne
>>> CARBON-13608 Fix jgroups.bind_addr property -Dimuthu Leelarathne
>>> CARBON-13591 Login and logout user difference -Amila
Maharachchi
>>> CARBON-13588 Modify Security Manager to allow tenants to read Rhino
code generated folder -Chethiya Abeysinghe
>>
>>
>> I have been working on a solution for this. When tried to test it out
with a signed pack having security settings enabled, I noticed that this
problem is no longer in current AS build. I've also commented on the jira @
https://wso2.org/jira/browse/CARBON-13588, This is working probably due to
a change done by Ruchira.
>>
>>
>>>
>>> CARBON-13502 Ant task doesn't work to create war file [createWAR]
-Pradeep
>>> CARBON-13386 Intermittent issue: ERROR
{org.infinispan.interceptors.InvocationContextInterceptor} - ISPN000136:
Execution error java.lang.InterruptedException when shutting down G-reg
-Dimuthu
>>> CARBON-13208 TenantMgt AdminService invocation with wrong
credentials returns too much of information to the user, but the
information is also wrong -Kathiravelu Pradeeban
>>> CARBON-13167 supporting web-app mode deployment of carbon in Apache
Tomcat -Pradeep Fernando
>>> CARBON-13140 wso2server.sh is not working with Solaris 10 in beta
Packs-Reka Thirunavukkarasu
>>> CARBON-12895 Cannot enable JMS transport listener from UI -dushan
abeyruwan
>>> CARBON-10230 Inconsistency of product clusters -Thilini Ishaka
>>>
>>>
>>> Carbon core code freeze on tomorrow, tentative release date on 27 th. I
need a progress update of each of the issues before EOD today. (working on
it/ not started/ not possible with this release/etc)
>>>
>>>
>>> regarding two issues assigned to me - will try to make them available
in this release. Otherwise they will go out in a point release.
>>>
>>> thanks,
>>> --Pradeep
>>>
>>>
>>>
>>
>>
>>
>> --
>> Chethiya Abeysinghe
>> Software Engineer; WSO2, Inc.; http://wso2.com/
>> email: cheth...@wso2.com phone: +94 777444891
>> blog: chethiya3000.blogspot.com
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
>
>
> --
> Senaka Fernando
> Member - Integration Technologies Management Committee;
> Technical Lead; WSO2 Inc.; http://wso2.com
> Member; Apache Software Foundation; http://apache.org
>
> E-mail: senaka AT wso2.com
> P: +1 408 754 7388; ext: 51736; M: +94 77 322 1818
> Linked-In: http://linkedin.com/in/senakafernando
>
> Lean . Enterprise . Middleware
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] svn externals needed to be fixed in products in branch 4.0.0
/trunk/components/security/org.wso2.carbon.security.mgt/src/main/resources/scenarios products/dss/3.0.0/modules/samples/shopping_cart - dbs https://svn.wso2.org/repos/wso2/carbon/platform/trunk/samples/shopping-cart/data-service/dbs/ sql https://svn.wso2.org/repos/wso2/carbon/platform/trunk/samples/shopping-cart/data-service/sql/ products/esb/4.5.0/modules/samples/product/services/MTOMSwASampleService - conf https://svn.apache.org/repos/asf/synapse/trunk/java/modules/samples/services/MTOMSwASampleService/conf src https://svn.apache.org/repos/asf/synapse/trunk/java/modules/samples/services/MTOMSwASampleService/src products/as/5.0.0/modules/features/product - etc https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/features/etc products/esb/4.5.0/modules/samples/product/services/ReliableStockQuoteService - conf https://svn.apache.org/repos/asf/synapse/trunk/java/modules/samples/services/ReliableStockQuoteService/conf src https://svn.apache.org/repos/asf/synapse/trunk/java/modules/samples/services/ReliableStockQuoteService/src products/as/5.0.0/modules/samples/product/conf - rampart https://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/security/org.wso2.carbon.security.mgt/src/main/resources/scenarios products/esb/4.5.0/modules/samples/product/services/SecureStockQuoteService - conf https://svn.apache.org/repos/asf/synapse/trunk/java/modules/samples/services/SecureStockQuoteService/conf src https://svn.apache.org/repos/asf/synapse/trunk/java/modules/samples/services/SecureStockQuoteService/src products/wsf/modules/distribution - resources https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/distribution/kernel/carbon-home/repository/resources products/greg/4.5.0/config/rxts - api.rxt https://svn.wso2.org/repos/wso2/carbon/platform/trunk/products/apimgt/config/rxts/api.rxt products/dss/3.0.0/modules/features/product - etc https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/features/etc products/greg/4.5.0/modules/checkin-client/src/test/resources - carbon-home https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/distribution/kernel/carbon-home user-test https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/core/org.wso2.carbon.user.core/src/test/resources products/greg/4.5.0/modules/samples/filesampleutils - src https://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/registry/org.wso2.carbon.registry.samples.filesampleutils products/appfactory/modules/distribution/product/resources/bpel - conf https://svn.wso2.org/repos/wso2/carbon/platform/trunk/products/bps/modules/distribution/conf sql https://svn.wso2.org/repos/wso2/carbon/platform/trunk/products/bps/modules/distribution/sql products/bam2/2.0.0/modules/features/product - etc https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/features/etc products/esb/4.5.0/modules/samples/product/services/SimpleStockQuoteService - conf https://svn.apache.org/repos/asf/synapse/trunk/java/modules/samples/services/SimpleStockQuoteService/conf src https://svn.apache.org/repos/asf/synapse/trunk/java/modules/samples/services/SimpleStockQuoteService/src products/esb/4.5.0/modules/samples/product/services/LoadbalanceFailoverService - conf https://svn.apache.org/repos/asf/synapse/trunk/java/modules/samples/services/LoadbalanceFailoverService/conf src https://svn.apache.org/repos/asf/synapse/trunk/java/modules/samples/services/LoadbalanceFailoverService/src components/governance/org.wso2.carbon.governance.policy.ui/4.0.0/src/main/resources/web/policy - products/esb/4.5.0/modules/samples/product/services/FastStockQuoteService - conf https://svn.apache.org/repos/asf/synapse/trunk/java/modules/samples/services/FastStockQuoteService/conf src https://svn.apache.org/repos/asf/synapse/trunk/java/modules/samples/services/FastStockQuoteService/src products/greg/4.5.0/modules/samples/distributed-LCM - src/org.wso2.carbon.governance.samples.lcm https://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/governance/org.wso2.carbon.governance.samples.lcm src/org.wso2.carbon.governance.samples.lcm.notifications https://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/governance/org.wso2.carbon.governance.samples.lcm.notifications -- Chethiya Abeysinghe Software Engineer; WSO2, Inc.; http://wso2.com/ email: cheth...@wso2.com blog: chethiya3000.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Applying strategy to platform/platform-integration
Hi Krishantha, It seems $subject still needed to be done as it has been done in everywhere in 4.0.0 branch. Please let know whether you want us to do this. Thanks, - Chethiya -- Chethiya Abeysinghe Software Engineer; WSO2, Inc.; http://wso2.com/ email: cheth...@wso2.com phone: +94 777444891 blog: chethiya3000.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] svn externals needed to be fixed in products in branch 4.0.0
Fixed fro greg. Thanks - Chethiya On Thu, Aug 2, 2012 at 3:33 PM, Chethiya Abeysinghe wrote: > recursive svn proget on platform in 4.0.0 branch shows following externals > are still pointing to trunk. Going through the list, I found there are few > externals in ESB point to synapse trunk. > > > > > > products/gs/modules/features/product - etc > https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/features/etc > > products/apimgt/1.0.0/config/BAM - > bamClient/org.wso2.carbon.bam.client/src/main/resources/APIVersionServiceTimeSummaryScript.hiveql > > https://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/apimgt/org.wso2.carbon.apimgt.usage/org.wso2.carbon.apimgt.usage.analyzer/src/main/resources/APIVersionServiceTimeSummaryScript.hiveql > > bamClient/org.wso2.carbon.bam.client/src/main/resources/APIVersionKeyLastAccessSummaryScript.hiveql > > https://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/apimgt/org.wso2.carbon.apimgt.usage/org.wso2.carbon.apimgt.usage.analyzer/src/main/resources/APIVersionKeyLastAccessSummaryScript.hiveql > > bamClient/org.wso2.carbon.bam.client/src/main/resources/APIVersionUsageSummaryScript.hiveql > > https://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/apimgt/org.wso2.carbon.apimgt.usage/org.wso2.carbon.apimgt.usage.analyzer/src/main/resources/APIVersionUsageSummaryScript.hiveql > > bamClient/org.wso2.carbon.bam.client/src/main/resources/KeyUsageSummaryScript.hiveql > > https://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/apimgt/org.wso2.carbon.apimgt.usage/org.wso2.carbon.apimgt.usage.analyzer/src/main/resources/KeyUsageSummaryScript.hiveql > > bamClient/org.wso2.carbon.bam.client/src/main/resources/APIVersionKeyUsageSummaryScript.hiveql > > https://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/apimgt/org.wso2.carbon.apimgt.usage/org.wso2.carbon.apimgt.usage.analyzer/src/main/resources/APIVersionKeyUsageSummaryScript.hiveql > > products/esb/4.5.0/modules/features/product - etc > https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/features/etc > > products/as/5.0.0/modules/distribution/src/resources - db > https://svn.wso2.org/repos/wso2/carbon/platform/trunk/products/jaggery/server/distribution/src/resources/db > > products/manager/2.0.0/conf - identity.xml > https://svn.wso2.org/repos/wso2/carbon/platform/trunk/features/identity/identity-core/org.wso2.carbon.identity.core.server.feature/resources/identity.xml > > products/greg/4.5.0/modules/features/product - etc > https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/features/etc > > products/gs2/modules/features/product - etc > https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/features/etc > > products/esb/4.5.0/docs/xdoc - > > products/greg/4.5.0/modules/integration/registry/tests-new/src/test/resources > - artifacts/GREG > https://svn.wso2.org/repos/wso2/carbon/platform/trunk/platform-integration/clarity-tests/org.wso2.carbon.automation.test.repo/src/main/resources/artifacts/GREG > > axis2config > https://svn.wso2.org/repos/wso2/carbon/platform/trunk/platform-integration/clarity-tests/org.wso2.carbon.automation.test.repo/src/main/resources/axis2config > > client/modules > https://svn.wso2.org/repos/wso2/carbon/platform/trunk/platform-integration/clarity-tests/org.wso2.carbon.automation.test.repo/src/main/resources/client/modules > > keystores > https://svn.wso2.org/repos/wso2/carbon/platform/trunk/platform-integration/clarity-tests/org.wso2.carbon.automation.test.repo/src/main/resources/keystores > > products/apimgt/1.0.0/modules/distribution/resources - identity-sql > https://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/identity/org.wso2.carbon.identity.core/src/main/resources/dbscripts > > products/esb/4.5.0/modules/integration/tests/src/test/resources - > artifacts/ESB > https://svn.wso2.org/repos/wso2/carbon/platform/trunk/platform-integration/clarity-tests/org.wso2.carbon.automation.test.repo/src/main/resources/artifacts/ESB > > artifacts/AXIS2 > https://svn.wso2.org/repos/wso2/carbon/platform/trunk/platform-integration/clarity-tests/org.wso2.carbon.automation.test.repo/src/main/resources/artifacts/AXIS2 > > keystores > https://svn.wso2.org/repos/wso2/carbon/platform/trunk/platform-integration/clarity-tests/org.wso2.carbon.automation.test.repo/src/main/resources/keystores > > products/as/5.0.0/modules/samples/jaggerySamples - taskmaster > https://svn.wso2.org/repos/wso2/carbon/platform/trunk/products/jaggery/apps/taskmaster/ > > docs > https://svn.wso2.org/repos/wso2/carbon/platform/trunk/products/jaggery/apps/ROOT/
Re: [Dev] Applying strategy to platform/platform-integration
Hi guys, The version there is at the moment in platform-integration projects is 4.0.0. But as of Krishantha, the version need to be something like 1.0.0 as this product is more toward a stand alone project. Though this change might be not that messy, can this change wait till the today release? Or applying branching strategy to platform-integration a MUST before the release? P. S. Of course we can't apply branching strategy until we do this version change. Thanks, - Chethiya On Thu, Aug 2, 2012 at 6:59 PM, Krishantha Samaraweera wrote: > Yes we need to get $subject done. Will work with you to finish this off. > > Thanks, > Krishantha. > > > On Thu, Aug 2, 2012 at 6:03 PM, Chethiya Abeysinghe wrote: > >> Hi Krishantha, >> >> It seems $subject still needed to be done as it has been done in >> everywhere in 4.0.0 branch. Please let know whether you want us to do this. >> >> Thanks, >> - Chethiya >> >> >> -- >> Chethiya Abeysinghe >> Software Engineer; WSO2, Inc.; http://wso2.com/ >> email: cheth...@wso2.com phone: +94 777444891 >> blog: chethiya3000.blogspot.com >> >> >> > -- Chethiya Abeysinghe Software Engineer; WSO2, Inc.; http://wso2.com/ email: cheth...@wso2.com phone: +94 777444891 blog: chethiya3000.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Can not build kernel from the patch release pom in a clean repo
ses, but to axis2 parent pom. >> >> @janaka : please try out the suggested approach and commit if it is >> working. >> >> --pradeep >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Janaka Ranabahu > Software Engineer > WSO2 Inc. > > Mobile +94 718370861 > Email : jan...@wso2.com > Blog : janakaranabahu.blogspot.com > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Chethiya Abeysinghe Software Engineer; WSO2, Inc.; http://wso2.com/ email: cheth...@wso2.com phone: +94 777444891 blog: chethiya3000.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Products_4.0.0 > #68 has FAILED. Change made by 25 authors.
witch to enable full debug logging. >> build16-Aug-2012 19:51:25[ERROR] >> build16-Aug-2012 19:51:25[ERROR] For more information about the >> errors and possible solutions, please read the following articles: >> build16-Aug-2012 19:51:25[ERROR] [Help 1] >> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException >> build16-Aug-2012 19:51:25[ERROR] >> build16-Aug-2012 19:51:25[ERROR] After correcting the problems, >> you can resume the build with the command >> build16-Aug-2012 19:51:25[ERROR] mvn -rf >> :wso2bam-p2-profile-gen >> >> >> On Fri, Aug 17, 2012 at 8:22 AM, Bamboo wrote: >> >>> [image: Failed] WSO2 Carbon >>> BRANCH<http://wso2.org/bamboo/browse/WCB001/>› >>> Products_4.0.0 <http://wso2.org/bamboo/browse/WCB001-PRO000/> › >>> #68<http://wso2.org/bamboo/browse/WCB001-PRO000-68/> >>> failed >>> >>> Code has been updated by >>> krishantha<http://wso2.org/bamboo/browse/author/krishantha>, >>> nandika <http://wso2.org/bamboo/browse/author/nandika>, >>> nuwanw<http://wso2.org/bamboo/browse/author/nuwanw>, >>> Kishanthan >>> Thangarajah<http://wso2.org/bamboo/browse/user/kishant...@wso2.com>, >>> asela <http://wso2.org/bamboo/browse/author/asela>, >>> eranda<http://wso2.org/bamboo/browse/author/eranda>, >>> kasunw <http://wso2.org/bamboo/browse/author/kasunw>, >>> shammi<http://wso2.org/bamboo/browse/author/shammi>, >>> charitham <http://wso2.org/bamboo/browse/author/charitham>, >>> lakmali<http://wso2.org/bamboo/browse/author/lakmali>, >>> miyuru <http://wso2.org/bamboo/browse/author/miyuru>, >>> chamath<http://wso2.org/bamboo/browse/author/chamath>, >>> sinthuja <http://wso2.org/bamboo/browse/author/sinthuja>, >>> ishan<http://wso2.org/bamboo/browse/author/ishan>, >>> viraj <http://wso2.org/bamboo/browse/author/viraj>, >>> senaka<http://wso2.org/bamboo/browse/author/senaka>, >>> maninda <http://wso2.org/bamboo/browse/author/maninda>, >>> suho<http://wso2.org/bamboo/browse/author/suho>, >>> prabatha <http://wso2.org/bamboo/browse/author/prabatha>, >>> deep<http://wso2.org/bamboo/browse/author/deep>, >>> supunm <http://wso2.org/bamboo/browse/author/supunm>, >>> reka<http://wso2.org/bamboo/browse/author/reka>, >>> ajithn <http://wso2.org/bamboo/browse/author/ajithn>, >>> amila<http://wso2.org/bamboo/browse/author/amila>, >>> Isuru Udana Loku >>> Narangoda<http://wso2.org/bamboo/browse/user/isu...@wso2.com> >>> . >>> >>> No failed tests found, a possible compilation error. >>>Failing Jobs <http://wso2.org/bamboo/browse/WCB001-PRO000-68/>Job >>> Duration Tests[image: Failed] Default >>> Job<http://wso2.org/bamboo/browse/WCB001-PRO000-JOB1-68/> (Default >>> Stage) 88 minutes No tests found >>> Logs<http://wso2.org/bamboo/browse/WCB001-PRO000-JOB1-68/log>| >>> Artifacts <http://wso2.org/bamboo/browse/WCB001-PRO000-JOB1-68/artifact> >>> Code >>> Changes <http://wso2.org/bamboo/browse/WCB001-PRO000-68/commit/> View >>> all 164 code changes<http://wso2.org/bamboo/browse/WCB001-PRO000-68/commit/> >>> asela <http://wso2.org/bamboo/browse/author/asela> >>> adding identity 4.0.1 feature to patch pom 138587 >>> asela<http://wso2.org/bamboo/browse/author/asela> >>> adding 4.0.1 feature versions 138586 >>> asela<http://wso2.org/bamboo/browse/author/asela> >>> addming 4.0.1 versions 138585 161 more >>> changes…<http://wso2.org/bamboo/browse/WCB001-PRO000-68/commit> View >>> Online <http://wso2.org/bamboo/browse/WCB001-PRO000-68> | Add >>> Comments<http://wso2.org/bamboo/browse/WCB001-PRO000-68?commentMode=true> >>> >>> This message was sent by Atlassian Bamboo <http://wso2.org/bamboo>. >>> >>> If you wish to stop receiving these emails edit your user >>> profile<http://wso2.org/bamboo/profile/userNotifications.action>or notify >>> your administrator <http://wso2.org/bamboo/viewAdministrators.action>. >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Ajith Vitharana. >> WSO2 Inc. - http://wso2.org >> Email : aji...@wso2.com >> Mobile : +94714631794 >> >> >> > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Chethiya Abeysinghe Software Engineer; WSO2, Inc.; http://wso2.com/ email: cheth...@wso2.com phone: +94 777444891 blog: chethiya3000.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] reverting jaxb version in carbon back to 2.1.7
Hi all, As of some of the observations I had with Anjana while trying to resolve issue causing Linkage errors with jaxb, we figured out follows regarding the $subject. *Observations:* 1. If we remove jaxb form bundles.info file, still the server starts without any difference. 2. Current jaxb orbit bundle has following pom.xml file. com.sun.xml.bind jaxb-impl 2.2.5 com.sun.xml.bind jaxb-xjc 2.2.5 com.sun.*, org.relaxng.*, org.kohsuke.*, In here since the jaxb-api is commented out those packages are retrieved from jdk (added to launch.ini) . So the effective version of jaxb-api for java 1.6.0_33 is 2.1.10 as of one of my previous mails. But jaxb-impl is still there and those packages are exported from jaxb orbit bundle. 3. Carbon has been running for more than 1 month without any complains since the jaxb version upgrade except for this linkage error problem. i.e. since jaxb-api is loaded from JVM, it gives linkage error when unmarshaller is called with a bundle loaded javax.xml.stream.XMLStreamReader class object *Conclusions: * Catch in here is that jaxb-api is loaded form JVM. Therefore all what it consumes are also should be loaded from JVM as of the Java class loading mechanism, unless equinox does some tweaks on this. If that's the case jaxb-impl should also be loaded from JVM. @Pradeep can you please verify this? *If we assume that's the case,* it implies exported packages in jaxb-impl under jaxb bundle are not used by JVM loaded jaxb-api. That's why carbon starts even without jaxb orbit bundle. In that case, effective jaxb version running at current carbon builds is JVM dependant and for java 1.6.0_33 it's jaxb 2.1.10. *Actions we can take:* If that's the case we can safely revert back to previous jaxb orbit bundle (2.1.7.wso2v1) given that current jaxb bundle has been not effectively used and the used jaxb version for last month was JVM shipped jaxb (2.1.10 for java 1.6.0_33) Shall we revert back to jaxb 2.1.7.wso2v1 orbit bundle from current jaxb bundle (2.2.5.wso2v1) ? -- Chethiya Abeysinghe Software Engineer; WSO2, Inc.; http://wso2.com/ email: chethiya at wso2.com blog: chethiya3000.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] reverting jaxb version in carbon back to 2.1.7
Hi all,
We have tried replacing jaxb_2.1.7.wso2v1.jar in Aug-22 AS build.
jaxrs_basic sample has failed with following message in the server.
[2012-08-27 10:18:52,302] WARN
{org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor} - No message body
writer has been found for response class Customer.
And following message on client
[INFO]
[INFO] >>> exec-maven-plugin:1.2.1:java (default) @ jaxrs_basic >>>
[INFO]
[INFO] <<< exec-maven-plugin:1.2.1:java (default) @ jaxrs_basic <<<
[INFO]
[INFO] --- exec-maven-plugin:1.2.1:java (default) @ jaxrs_basic ---
Sent HTTP GET request to query customer info
[WARNING]
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
at java.lang.Thread.run(Thread.java:680)
Caused by: java.io.IOException: Server returned HTTP response code: 500 for
URL:
http://localhost:9763/jaxrs_basic/services/customers/customerservice/customers/123
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1436)
at java.net.URL.openStream(URL.java:1010)
at demo.jaxrs.client.Client.main(Client.java:51)
... 6 more
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 5.900s
[INFO] Finished at: Mon Aug 27 10:18:52 IST 2012
[INFO] Final Memory: 6M/528M
[INFO]
[ERROR] Failed to execute goal
org.codehaus.mojo:exec-maven-plugin:1.2.1:java (default) on project
jaxrs_basic: An exception occured while executing the Java class. null:
InvocationTargetException: Server returned HTTP response code: 500 for URL:
http://localhost:9763/jaxrs_basic/services/customers/customerservice/customers/123->
[Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
Anjana and I tried to overcome this by creating a jaxb orbit using version
2.1.0 (which is the version used in jdk). That's also produced a similar
result.
At the moment we don't have a clue about what's going on here. If you have
an idea please let us know.
Anyway reverting the jaxb version back to 2.1.7 is not the correct
solution. What we should try to get done is to get the new jaxb version
(2.2.5 2.2.6) work with ndatasource. I'll start another thread stating
problems we are facing with ndatasource when it uses the latest jaxb-api
loaded form orbit bundle.
Since reverting jaxb version back to 2.1.7 resolved the problem we are
having with UDDI on greg, I've change only the greg distribution to ship it
with jaxb version 2.1.7.
Thanks,
- Chethiya
On Thu, Aug 23, 2012 at 3:13 PM, Pradeep Fernando wrote:
> Hi chethiya,
>
> can you test this modification with a hosted JAXRS and JAXWS web-app
>
> ---PRadeep
>
--
Chethiya Abeysinghe
Software Engineer; WSO2, Inc.; http://wso2.com/
email: cheth...@wso2.com phone: +94 777444891
blog: chethiya3000.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Startup Error when restarting carbon 4.0.1 after installing greg feature category
at >>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819) >>> at >>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771) >>> at >>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130) >>> at >>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214) >>> at >>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433) >>> at >>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451) >>> at >>> org.wso2.carbon.registry.core.internal.RegistryCoreServiceComponent.activate(RegistryCoreServiceComponent.java:125) >>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>> at >>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >>> at >>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >>> at java.lang.reflect.Method.invoke(Method.java:597) >>> at >>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252) >>> at >>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146) >>> at >>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346) >>> at >>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588) >>> at >>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196) >>> at >>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:328) >>> at >>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:221) >>> at >>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104) >>> at >>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861) >>> at >>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) >>> at >>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148) >>> at >>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819) >>> at >>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771) >>> at >>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130) >>> at >>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214) >>> at >>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433) >>> at >>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451) >>> at >>> org.wso2.carbon.user.core.internal.Activator.startDeploy(Activator.java:67) >>> at >>> org.wso2.carbon.user.core.internal.BundleCheckActivator.start(BundleCheckActivator.java:61) >>> at >>> org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711) >>> at java.security.AccessController.doPrivileged(Native Method) >>> at >>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702) >>> at >>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683) >>> at >>> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381) >>> at >>> org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:389) >>> at >>> org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1130) >>> at >>> org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559) >>> at >>> org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544) >>> at >>> org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457) >>> at >>> org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243) >>> at >>> org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438) >>> at >>> org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1) >>> at >>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) >>> at >>> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) >>> Caused by: java.rmi.ConnectException: Connection refused to host: >>> localhost; nested exception is: >>> java.net.ConnectException: Connection refused >>> at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601) >>> at >>> sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198) >>> at >>> sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184) >>> at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:322) >>> at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source) >>> at >>> com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:97) >>> ... 117 more >>> >>> >>> -- >>> Dileepa Jayakody, >>> Software Engineer, WSO2 Inc. >>> Lean . Enterprise . Middleware >>> >>> Mobile : +94777-857616 >>> >>> >> >> >> -- >> Dileepa Jayakody, >> Software Engineer, WSO2 Inc. >> Lean . Enterprise . Middleware >> >> Mobile : +94777-857616 >> >> > > > -- > Dileepa Jayakody, > Software Engineer, WSO2 Inc. > Lean . Enterprise . Middleware > > Mobile : +94777-857616 > > -- Chethiya Abeysinghe Software Engineer; WSO2, Inc.; http://wso2.com/ email: cheth...@wso2.com phone: +94 777444891 blog: chethiya3000.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Startup Error when restarting carbon 4.0.1 after installing greg feature category
undleContextImpl.java:451) >> at >> org.wso2.carbon.user.core.internal.Activator.startDeploy(Activator.java:67) >> at >> org.wso2.carbon.user.core.internal.BundleCheckActivator.start(BundleCheckActivator.java:61) >> at >> org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711) >> at java.security.AccessController.doPrivileged(Native Method) >> at >> org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702) >> at >> org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683) >> at >> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381) >> at >> org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:389) >> at >> org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1130) >> at >> org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559) >> at >> org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544) >> at >> org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457) >> at >> org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243) >> at >> org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438) >> at >> org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1) >> at >> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) >> at >> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) >> Caused by: java.rmi.ConnectException: Connection refused to host: >> localhost; nested exception is: >> java.net.ConnectException: Connection refused >> at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601) >> at >> sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198) >> at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184) >> at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:322) >> at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source) >> at >> com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:97) >> ... 117 more >> >> >> -- >> Dileepa Jayakody, >> Software Engineer, WSO2 Inc. >> Lean . Enterprise . Middleware >> >> Mobile : +94777-857616 >> >> > > > -- > Dileepa Jayakody, > Software Engineer, WSO2 Inc. > Lean . Enterprise . Middleware > > Mobile : +94777-857616 > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Chethiya Abeysinghe Software Engineer; WSO2, Inc.; http://wso2.com/ email: cheth...@wso2.com phone: +94 777444891 blog: chethiya3000.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Feature manager is slow
AFAIK, installing a p2 feature means not just copying set of files. It computes required dependency trees too. Looking at the content.xml I think it can take sometime for computation. But always better to check with p2-dev as there can be cases which can be configured to avoid unnecessary dependency checks. - Chethiya On Mon, Sep 10, 2012 at 4:37 PM, Dileepa Jayakody wrote: > Hi Rajika, > > Thanks for the pointers. > In the feature-manager we are using p2 sdk, calling the p2-api under the > hood. > > For eg: to add and load a repository following code is used by us. > > IMetadataRepositoryManager metadataRepositoryManager = > ServiceHolder.getMetadataRepositoryManager(); > IArtifactRepositoryManager artifactRepositoryManager = > ServiceHolder.getArtifactRepositoryManager(); > > //adding metadata and artifact repositories > metadataRepositoryManager.addRepository(location); > artifactRepositoryManager.addRepository(location); > //Loading the metadata repository > metadataRepositoryManager.loadRepository(location, new > NullProgressMonitor()); > metadataRepositoryManager.setRepositoryProperty(location, > IRepository.PROP_NICKNAME, nickName); > > //Loading the artifact repository > artifactRepositoryManager.loadRepository(location, new > NullProgressMonitor()); > artifactRepositoryManager.setRepositoryProperty(location, > IRepository.PROP_NICKNAME, nickName); > > First we need to clarify how p2-works under the hood when loading a > repository from a given location. > Ideally it should just index the feature list by reading the the > repository's content.xml and artifacts.xml at this point without loading > all the features to the memory ( I believe this is what you are also > suggesting). > I will discuss this with p2-dev also and see how we can improve our > feature manager based on that. > > Thanks, > Dileepa > > > On Mon, Sep 10, 2012 at 4:12 PM, Rajika Kumarasiri wrote: > >> I meant the consumer task should do the feature installation >> asynchronously. >> >> Rajika >> >> >> On Mon, Sep 10, 2012 at 3:54 PM, Rajika Kumarasiri wrote: >> >>> If you have not done already, here how it should be done. >>> >>> There should be an instance of blocking queue instance which keeps track >>> of requested features to install. There should be a producer task which >>> drop next requested feature list to install into the blocking queue. There >>> should be a consumer task will remove items from the blocking queue. For >>> producing and consuming use >>> http://docs.oracle.com/javase/6/docs/api/java/util/concurrent/BlockingQueue.html#put<http://docs.oracle.com/javase/6/docs/api/java/util/concurrent/BlockingQueue.html#put%28E%29> >>> and >>> http://docs.oracle.com/javase/6/docs/api/java/util/concurrent/BlockingQueue.html#take() >>> so >>> that your consumer and producer task will not kill the CPU. >>> >>> Since Feature manager will not use frequently this model may not make >>> sense much, but I think it will be useful when our p2 feature repository >>> starts to grow. >>> >>> Hope this helps. >>> >>> Rajika >>> >>> On Mon, Sep 10, 2012 at 2:47 PM, Dileepa Jayakody wrote: >>> >>>> Hi Rajika, >>>> >>>> Is the repository you are adding a local-repository or a remote >>>> repository? >>>> >>>> Thanks, >>>> Dileepa >>>> >>>> On Mon, Sep 10, 2012 at 2:44 PM, Rajika Kumarasiri wrote: >>>> >>>>> I just tried to add the feature repository of 4.0.1 into a AS (built >>>>> from 4.0.1 branch) and it seems it just take too much time. >>>>> >>>>> I still can see the message "Adding repository.." and it just there. >>>>> >>>>> This need to improve. We just need to load the list features (just >>>>> names) and install any selected features asynchronously. >>>>> >>>>> It seems this loads the whole features into memory. >>>>> >>>>> Rajika >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Dileepa Jayakody, >>>> Software Engineer, WSO2 Inc. >>>> Lean . Enterprise . Middleware >>>> >>>> Mobile : +94777-857616 >>>> >>>> >>> >> > > > -- > Dileepa Jayakody, > Software Engineer, WSO2 Inc. > Lean . Enterprise . Middleware > > Mobile : +94777-857616 > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Chethiya Abeysinghe Software Engineer; WSO2, Inc.; http://wso2.com/ email: cheth...@wso2.com phone: +94 777444891 blog: chethiya3000.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Feature manager is slow
OK. Got it. We can reason out loading meta data of all the features to the memory for computing the dependency tree. But I don't think that needs feature artifacts to be loaded into memory too. I guess how it works is, first it hash all features in memory and then create dependency tree for the user selected features efficiently f > > Yes Chethiya p2 computes the dependencies before installing features. It > is called a provisioning plan. > > But Rajika's concern is that it's taking a long time at repository adding > stage, which should not be performing any dependency computations. But I > suspect p2 might be loading all the features in the repo to memory at this > stage. Have to clarify with p2-dev. > > Thanks, > Dileepa > > On Mon, Sep 10, 2012 at 5:47 PM, Chethiya Abeysinghe wrote: > >> AFAIK, installing a p2 feature means not just copying set of files. It >> computes required dependency trees too. Looking at the content.xml I think >> it can take sometime for computation. But always better to check with >> p2-dev as there can be cases which can be configured to >> avoid unnecessary dependency checks. >> >> - Chethiya >> >> On Mon, Sep 10, 2012 at 4:37 PM, Dileepa Jayakody wrote: >> >>> Hi Rajika, >>> >>> Thanks for the pointers. >>> In the feature-manager we are using p2 sdk, calling the p2-api under the >>> hood. >>> >>> For eg: to add and load a repository following code is used by us. >>> >>> IMetadataRepositoryManager metadataRepositoryManager = >>> ServiceHolder.getMetadataRepositoryManager(); >>> IArtifactRepositoryManager artifactRepositoryManager = >>> ServiceHolder.getArtifactRepositoryManager(); >>> >>> //adding metadata and artifact repositories >>> metadataRepositoryManager.addRepository(location); >>> artifactRepositoryManager.addRepository(location); >>> //Loading the metadata repository >>> metadataRepositoryManager.loadRepository(location, new >>> NullProgressMonitor()); >>> metadataRepositoryManager.setRepositoryProperty(location, >>> IRepository.PROP_NICKNAME, nickName); >>> >>> //Loading the artifact repository >>> artifactRepositoryManager.loadRepository(location, new >>> NullProgressMonitor()); >>> artifactRepositoryManager.setRepositoryProperty(location, >>> IRepository.PROP_NICKNAME, nickName); >>> >>> First we need to clarify how p2-works under the hood when loading a >>> repository from a given location. >>> Ideally it should just index the feature list by reading the the >>> repository's content.xml and artifacts.xml at this point without loading >>> all the features to the memory ( I believe this is what you are also >>> suggesting). >>> I will discuss this with p2-dev also and see how we can improve our >>> feature manager based on that. >>> >>> Thanks, >>> Dileepa >>> >>> >>> On Mon, Sep 10, 2012 at 4:12 PM, Rajika Kumarasiri wrote: >>> >>>> I meant the consumer task should do the feature installation >>>> asynchronously. >>>> >>>> Rajika >>>> >>>> >>>> On Mon, Sep 10, 2012 at 3:54 PM, Rajika Kumarasiri wrote: >>>> >>>>> If you have not done already, here how it should be done. >>>>> >>>>> There should be an instance of blocking queue instance which keeps >>>>> track of requested features to install. There should be a producer task >>>>> which drop next requested feature list to install into the blocking queue. >>>>> There should be a consumer task will remove items from the blocking queue. >>>>> For producing and consuming use >>>>> http://docs.oracle.com/javase/6/docs/api/java/util/concurrent/BlockingQueue.html#put<http://docs.oracle.com/javase/6/docs/api/java/util/concurrent/BlockingQueue.html#put%28E%29> >>>>> and >>>>> http://docs.oracle.com/javase/6/docs/api/java/util/concurrent/BlockingQueue.html#take() >>>>> so >>>>> that your consumer and producer task will not kill the CPU. >>>>> >>>>> Since Feature manager will not use frequently this model may not make >>>>> sense much, but I think it will be useful when our p2 feature repository >>>>> starts to grow. >>>>> >>>>> Hope this helps. >
Re: [Dev] Build failure in 4.0.2
Did you try svn up? I think I fixed this - chethiya software engineer, WSO2 On Sep 12, 2012 10:01 PM, "Rajika Kumarasiri" wrote: > Anybody else is getting this ? Is anybody working on this ? > > Rajika > > On Wed, Sep 12, 2012 at 12:19 PM, Rajika Kumarasiri wrote: > >> [INFO] BUILD FAILURE >> [INFO] >> >> [INFO] Total time: 43.400s >> [INFO] Finished at: Wed Sep 12 11:51:21 IST 2012 >> [INFO] Final Memory: 100M/558M >> [INFO] >> >> [ERROR] Failed to execute goal >> org.wso2.maven:carbon-p2-plugin:1.5:p2-feature-gen >> (4-p2-feature-generation) on project org.wso2.carbon.core.common.feature: >> ERROR: Failure to find >> org.wso2.carbon:org.wso2.carbon.registry.core:jar:4.0.2 in >> http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in >> the local repository, resolution will not be reattempted until the update >> interval of wso2-nexus has elapsed or updates are forced >> [ERROR] >> [ERROR] Try downloading the file manually from the project website. >> [ERROR] >> [ERROR] Then, install it using the command: >> [ERROR] mvn install:install-file -DgroupId=org.wso2.carbon >> -DartifactId=org.wso2.carbon.registry.core -Dversion=4.0.2 -Dpackaging=jar >> -Dfile=/path/to/file >> [ERROR] >> [ERROR] Alternatively, if you host your own repository you can deploy the >> file there: >> [ERROR] mvn deploy:deploy-file -DgroupId=org.wso2.carbon >> -DartifactId=org.wso2.carbon.registry.core -Dversion=4.0.2 -Dpackaging=jar >> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] >> [ERROR] >> [ERROR] >> [ERROR] org.wso2.carbon:org.wso2.carbon.registry.core:jar:4.0.2 >> [ERROR] >> [ERROR] from the specified remote repositories: >> [ERROR] wso2-nexus ( >> http://maven.wso2.org/nexus/content/groups/wso2-public/, releases=true, >> snapshots=true), >> [ERROR] central (http://repo1.maven.org/maven2, releases=true, >> snapshots=false) >> [ERROR] -> [Help 1] >> [ERROR] >> [ERROR] To see the full stack trace of the errors, re-run Maven with the >> -e switch. >> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >> [ERROR] >> [ERROR] For more information about the errors and possible solutions, >> please read the following articles: >> [ERROR] [Help 1] >> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException >> [ERROR] >> [ERROR] After correcting the problems, you can resume the build with the >> command >> [ERROR] mvn -rf :org.wso2.carbon.core.common.feature >> >> > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Error while trying to get box carrying working with a Java client
ol : method _getServiceClient() location: interface org.wso2.carbon.dataservices.samples.rdbms_sample.RDBMSSample [INFO] 1 error [INFO] - [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 50.653s [INFO] Finished at: Mon Oct 22 13:55:09 CDT 2012 [INFO] Final Memory: 19M/528M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project dataservice-client-samples: Compilation failure [ERROR] /Users/chethiya/wso2/carbon/branch/4.0.0/platform/products/dss/3.0.0/modules/samples/clients/src/org/wso2/carbon/dataservices/samples/RDBMSSample.java:[60,6] cannot find symbol [ERROR] symbol : method _getServiceClient() [ERROR] location: interface org.wso2.carbon.dataservices.samples.rdbms_sample.RDBMSSample [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException Chethiyas-MacBook-Pro:clients chethiya$ -- Chethiya Abeysinghe Software Engineer; WSO2, Inc.; http://wso2.com/ email: cheth...@wso2.com phone: +94 777444891 blog: chethiya3000.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] What's the Jaggery-convention of adding comments inside JSON files?
Hi Senaka,
AFAICU, how this is handled at API consumers' end is through separate
documentation. E.g.
http://developer.chrome.com/extensions/tabs.html#type-InjectDetails
I'm also keen to know if there are advanced technologies on this.
- chethiya
software engineer, WSO2
On Oct 29, 2012 12:29 AM, "Senaka Fernando" wrote:
> Hi Nuwan,
>
> Yes, correct. Say I have an element that can have 3 values, ex:- "type" :
> "SOME_VALUE", where SOME_VALUE can be "foo", "bar", "foobar". I want to
> explain to a user what these three different values would mean. Is this a
> result of some bad practice?
>
> Thanks,
> Senaka.
>
> On Mon, Oct 29, 2012 at 12:11 AM, Nuwan Bandara wrote:
>
>> Hi Senaka,
>>
>> Well so far, we didn't have a requirement for comments in json, for me I
>> feel its a self descriptive data structure. You cannot compare json with
>> XML and try to replace everything we have in XML. If commenting is a must.
>> yes of-cause you can have a comment element in a json object.
>>
>> Regards,
>> /Nuwan
>>
>> On Sun, Oct 28, 2012 at 11:34 AM, Senaka Fernando wrote:
>>
>>> Hi all,
>>>
>>> Yes, not being able to have comments is a serious miss in JSON AFAIU,
>>> because there is no way to document alternative options as in the case of
>>> XML. That's the reason why I asked what's our convention of adding
>>> comments/documentation. Some people have used the "_comment" element. If
>>> what Madhuka explains is the convention in Jaggery, we can follow that in
>>> AM/GS/G-Reg etc.
>>>
>>> Thanks,
>>> Senaka.
>>>
>>>
>>> On Sun, Oct 28, 2012 at 11:24 PM, Nuwan Bandara wrote:
>>>
Hi Senaka,
there is no such thing called comments in JSON. :)
Regards,
/Nuwan
On Sun, Oct 28, 2012 at 8:31 AM, Madhuka Udantha wrote:
> Hi,
>
> I don't believe we can have an actual comment in json[1]. The JSON
> should all be data, and if you include a comment, then it will be data
> too.
> In jaggery still it is same. We can have a designated data element called
> "_comment".
>
> Here sample that you can try out.
> eg:
>
> {
> *"displayName_comment":"give the jaggery app name", *
> "displayName":"Coffee Shop",
> "urlMappings":[
> {
> "url":"/orders/*",
>* "url_comment":"Comments for url mapping on URL",*
> "path":"/controller/order.jag"
> }
>
> ]
> }
>
> It is drawback of json.
>
> References
> [1] http://www.json.org/
>
> On Sun, Oct 28, 2012 at 1:30 PM, Senaka Fernando wrote:
>
>> Hi all,
>>
>> $subject?
>>
>> Thanks,
>> Senaka.
>>
>> --
>> *Senaka Fernando*
>> Member - Integration Technologies Management Committee;
>> Technical Lead; WSO2 Inc.; http://wso2.com*
>> Member; Apache Software Foundation; http://apache.org
>>
>> E-mail: senaka AT wso2.com
>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
>> Linked-In: http://linkedin.com/in/senakafernando
>>
>> *Lean . Enterprise . Middleware
>>
>>
>
>
> --
> *Madhuka* Udantha
> http://madhukaudantha.blogspot.com/
>
>
--
*Thanks & Regards,
Nuwan Bandara
Associate Technical Lead & Member, MC, Development Technologies
WSO2 Inc. - lean . enterprise . middleware | http://wso2.com
blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763
9629
*
[Dev] Amount of coupling needed between Endpoints and WSDLs in GReg - https://wso2.org/jira/browse/REGISTRY-1350
Hi all, Trying to find a resolution for the jira [1]. There are two options we see in here. Please comment to figure out what's the expected behaviour. 1. Delete endpoints when deleting the respective WSDL of it. If the user wants to delete a WSDL file, that implies no point of keeping endpoints. i.e. If user wants to keep an Endpoint, user will not delete respective WSDL file. We assume an endpoint can't be shared between multiple WSDLs. 2. Keep it the way it is now. That is, if a WSDL is deleted, respective Endpoints are persisted with their environments status too (Dev, Test, Stag, Prod, etc) [1] - https://wso2.org/jira/browse/REGISTRY-1350 Thanks -- Chethiya Abeysinghe Software Engineer; WSO2, Inc.; http://wso2.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Having DBDeployer in conf/axis2/tenant-axis2.xml
This cause one warning in [1] as we don't ship dataservice.core with GReg. Shall we get rid of DBDeployer in config file? [1] - https://wso2.org/jira/browse/REGISTRY-1426? Thanks -- Chethiya Abeysinghe Software Engineer; WSO2, Inc.; http://wso2.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Having DBDeployer in conf/axis2/tenant-axis2.xml
[2012-11-19 15:33:20,024] WARN - AxisConfigBuilder Unable to instantiate deployer org.wso2.carbon.dataservices.core.DBDeployer; see debug logs for more details This seems to be in other products too. e.g. ESB... And this configuration comes from carbon-home/repository/conf/axis2/tenant-axis2.xml in kernel. I'm removing the line : Thanks, - Chethiya On Mon, Nov 19, 2012 at 2:26 PM, Anjana Fernando wrote: > Hi, > > On Mon, Nov 19, 2012 at 2:15 PM, Sumedha Rubasinghe wrote: > >> +1.. why this came in hard coded when we are adding deployers dynamically? > > > That is something we have done a long time back, we now put these in the > component.xml. No idea why GREG have added this to their axis2.xml. > Anyways, yeah, we can just simply remove it. > > Cheers, > Anjana. > > >> >> >> On Mon, Nov 19, 2012 at 1:18 PM, Chethiya Abeysinghe >> wrote: >> >>> This cause one warning in [1] as we don't ship dataservice.core with >>> GReg. >>> >>> Shall we get rid of DBDeployer in config file? >>> >>> [1] - https://wso2.org/jira/browse/REGISTRY-1426? >>> >>> Thanks >>> -- >>> Chethiya Abeysinghe >>> Software Engineer; WSO2, Inc.; http://wso2.com/ >>> >>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> /sumedha >> m: +94 773017743 >> b : bit.ly/sumedha >> >> > > > -- > *Anjana Fernando* > Associate Technical Lead > WSO2 Inc. | http://wso2.com > lean . enterprise . middleware > -- Chethiya Abeysinghe Software Engineer; WSO2, Inc.; http://wso2.com/ email: cheth...@wso2.com phone: +94 777444891 blog: chethiya3000.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
