Hi Subash,
No that's not supposed to work like that. You'll ideally have one endpoint
for all tenants, because this is defined in a config file.
Thanks,
Senaka.
On Mon, Nov 19, 2012 at 10:31 AM, Subash Chaturanga wrote:
> Hi Senaka,
> Is $subject suppose to work ? If I change work list config
---
WSO2 Carbon 4.0.x > Products 4.0.5 > #25 failed.
---
Code has been updated by anjana, kasunw, sinthuja, nuwanw, supunm, dinusha,
shariq, lalaji, thilini.
No
---
WSO2 Carbon 4.0.x > Platform 4.0.4 > #49 failed.
---
Code has been updated by dharshanaw, nuwanw, subash, dinusha, sanjayav.
No failed tests found, a possible
---
WSO2 Carbon 4.0.x > Platform 4.0.5 > #25 failed.
---
Code has been updated by anjana, sinthuja.
No failed tests found, a possible compilation error.
http://w
---
WSO2 Carbon 4.0.x > Kernel 4.0.5 > #7 failed.
---
Code has been updated by asela.
No failed tests found, a possible compilation error.
http://wso2.org/bamboo
---
WSO2 Carbon 4.0.x - Nightly > Kernel_4.0.4 > #20 failed.
---
This build was triggered at the scheduled time of 1:00 PM
No failed tests found, a possible compi
---
WSO2 Carbon 4.0.x > Products 4.0.5 > #26 failed.
---
Code has been updated by shariq.
No failed tests found, a possible compilation error.
http://wso2.org/ba
Hi Guys,
I started Gadget Server 1.4.2 and uploaded a single gadget (embedded in a
car file created by dev studio).
and for some reason I could find the gadget in the registry. So I did a
content search ( Home> Registry>Search>Metadata) and it threw an error:
Can some one take a look?
Regards
Ra
---
WSO2 Carbon 4.0.x > Platform 4.0.5 > #26 failed.
---
Code has been updated by shariq.
No failed tests found, a possible compilation error.
http://wso2.org/ba
Hi Guys,
I created a Very simple Gadget (+ a Carbon application to go with that
using dev studio) and uploaded it to Gadget server 1.4.2
One thing I noticed is its not uploading gadget related xml file to
correct registry path.
for exmple : suppose my gadget is 'MyGadget' I suppose files related
---
WSO2 Carbon 4.0.x > Products 4.0.4 > #19 failed.
---
Code has been updated by krishantha, sinthuja, nuwanw, dushan, subash,
sanjayav, lalaji, anjana, kasunw,
---
WSO2 Carbon 4.0.x > Kernel 4.0.4 > #24 was successful.
---
Code has been updated by nuwand, supunm, amila, pradeep.
http://wso2.org/bamboo/browse/WCB001-KER0
Hi Ramith,
I checked with your attached .car file.The structure of .dar file inside
your car file may be the reason for your problem. I'm attaching a working
.car file with a gadget .dar included in it,which is created with dev
studio 2.0.1. Check the .dar structure in it.Once it deployed in GS
1.
---
WSO2 Carbon 4.0.x > Platform 4.0.4 > #50 was successful.
---
This build occurred because it is a dependant of WCB001-KER004-24.
973 tests in total.
http://ws
On Mon, Nov 19, 2012 at 6:45 PM, Selvaratnam Uthaiyashankar <
shan...@wso2.com> wrote:
> This problem is still there. Might be a windows specific issue. the source
> file contains some special characters in the comment.
Yes. Thanks for pointing this.. will fix in next version
Thanks,
Asela.
I fixed with the following windows system property;
variable name : JAVA_TOOL_OPTIONS
variable value : -Dfile.encoding=UTF8
thanks
On 20 November 2012 08:01, Asela Pathberiya wrote:
>
>
> On Mon, Nov 19, 2012 at 6:45 PM, Selvaratnam Uthaiyashankar <
> shan...@wso2.com> wrote:
>
>> This problem
Hi all,
I am using latest version of ESB 4.5.1, i did not add any jars or pulgins
to esb.
After login
1.While creating proxy Service --> Design In sequence
-->*Mediators*(property,log,clone,payload-factory)
1. i am successfully adding these *Mediators*.
2. But some times i am unab
---
WSO2 Carbon 4.0.x > Products 4.0.5 > #27 failed.
---
Code has been updated by lalaji.
No failed tests found, a possible compilation error.
http://wso2.org/ba
Added to BPS 3.0.1.
On Fri, Nov 16, 2012 at 5:09 PM, Anjana Fernando wrote:
> Hi guys,
>
> Reminder!, in case this wasn't already done.
>
> Cheers,
> Anjana.
>
> On Thu, Oct 4, 2012 at 9:24 AM, Anjana Fernando wrote:
>
>> Hi,
>>
>> I've added a new configuration called "tasks-config.xml", that
The test failures in kernel level seems to be intermittent. Possible
reasons for these failures are
1. Issue with test case itself.
2. Bamboo load causing test failures.
3. Failure introduced by carbon core.
The same set of tests have been executing successfully over last year. And
changes introd
---
WSO2 Carbon 4.0.x > Platform 4.0.5 > #27 failed.
---
Code has been updated by lalaji.
No failed tests found, a possible compilation error.
http://wso2.org/ba
---
WSO2 Carbon 4.0.x > Kernel 4.0.5 > #8 failed.
---
Code has been updated by nuwand.
No failed tests found, a possible compilation error.
http://wso2.org/bambo
---
WSO2 Carbon 4.0.x > Products 4.0.4 > #20 failed.
---
Code has been updated by shariq.
No failed tests found, a possible compilation error.
http://wso2.org/ba
Hi
This is regarding [1]. Seems we are specifically restricting this. Is there
particular reason why we do the following check and specifically
re-construct the service content with the old content.
if ("true".equals(resource.getProperty("registry.WSDLImport"))) {
resource.removePro
Hi
Found it through mail archives.
Thanks
On Tue, Nov 20, 2012 at 12:19 PM, Subash Chaturanga wrote:
> Hi
> This is regarding [1]. Seems we are specifically restricting this. Is
> there particular reason why we do the following check and specifically
> re-construct the service content with the o
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 14:00.787s
[INFO] Finished at: Mon Nov 19 23:18:03 PST 2012
[INFO] Final Memory: 268M/879M
[INFO]
-
Hi,
FYI, [2] is the corresponding jira.
[2] - https://wso2.org/jira/browse/CARBON-7227
On Tue, Nov 20, 2012 at 12:52 PM, Subash Chaturanga wrote:
> Hi
> Found it through mail archives.
> Thanks
>
>
> On Tue, Nov 20, 2012 at 12:19 PM, Subash Chaturanga wrote:
>
>> Hi
>> This is regarding [1]. S
Hi,
I was checking the issue [1], and by going through the code, I found that
when the deployment sync. message is coming to a server, it is running the
scheduled task manually by calling
"CarbonDeploymentSchedulerTask#runAxisDeployment" [2], which in turn calls
"ScheduleTask#run" method (the supe
---
WSO2 Carbon 4.0.x > Products 4.0.5 > #22 failed.
---
Code has been updated by sinthuja, amani, deep, dharshanaw, dushan, shariq,
sanjayav.
No failed tests fo
---
WSO2 Carbon 4.0.x > Kernel 4.0.5 > #4 failed.
---
Code has been updated by supunm.
No failed tests found, a possible compilation error.
http://wso2.org/bambo
+1.. why this came in hard coded when we are adding deployers dynamically?
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/b
---
Developer Studio > Eclipse-Tools > #557 failed.
---
Code has been updated by viraj.
No failed tests found, a possible compilation error.
http://wso2.org/bamb
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,
On Mon, Nov 19, 2012 at 1:30 PM, Anjana Fernando wrote:
> Hi,
>
> I was checking the issue [1], and by going through the code, I found that
> when the deployment sync. message is coming to a server, it is running the
> scheduled task manually by calling
> "CarbonDeploymentSchedulerTask#runAxisDep
Please replace the CarbonDeploymentSchedulerTask. runAxisDeployment method
with the following code:
public synchronized void runAxisDeployment() {
PrivilegedCarbonContext carbonContext =
PrivilegedCarbonContext.getThreadLocalCarbonContext();
carbonContext.setTenantId(tenantId);
[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
---
WSO2 Carbon 4.0.x > Platform 4.0.5 > #22 failed.
---
Code has been updated by sinthuja, amani, dharshanaw, deep, nuwand, dushan,
subash, supunm, dinusha, sha
On Mon, Nov 19, 2012 at 3:43 PM, Chethiya Abeysinghe wrote:
> [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 config
---
Developer Studio > Eclipse-Tools > #558 was successful.
---
Code has been updated by viraj.
http://wso2.org/bamboo/browse/DS0001-DSET01-558/
---
WSO2 Carbon 4.0.x - Nightly > Platform_4.0.5 > #3 failed.
---
Code has been updated by sinthuja, nuwanw, dushan, subash, sanjayav, johann,
amani, deep, dhars
---
WSO2 Carbon 4.0.x > Products 4.0.5 > #23 failed.
---
Code has been updated by krishantha, nuwanw, dharshanaw, nuwand, dushan,
subash, supunm, dinusha, shariq
---
WSO2 Carbon 4.0.x > Kernel 4.0.5 > #5 failed.
---
Code has been updated by nuwand.
No failed tests found, a possible compilation error.
http://wso2.org/bambo
---
WSO2 Carbon 4.0.x - Nightly > Kernel_4.0.5 > #4 failed.
---
This build was triggered at the scheduled time of 1:00 AM
No failed tests found, a possible compil
This problem is still there. Might be a windows specific issue. the source
file contains some special characters in the comment.
Shankar
On Thu, Oct 25, 2012 at 2:22 PM, Vijayaratha Vijayasingam
wrote:
> Hi all
> im getting this issue with commons/balana module
>
> [INFO]
> [INFO] --- maven-comp
---
Developer Studio > Eclipse-Tools > #559 failed.
---
Code has been updated by melan.
No failed tests found, a possible compilation error.
http://wso2.org/bamb
4.0.3 branch was built on a clean repo when doing the release and didn't
come across this issue. Probably Windows specific issue.
Rajika
On Mon, Nov 19, 2012 at 6:45 PM, Selvaratnam Uthaiyashankar <
shan...@wso2.com> wrote:
> This problem is still there. Might be a windows specific issue. the so
---
Developer Studio > Eclipse-Tools > #560 was successful.
---
Code has been updated by melan.
http://wso2.org/bamboo/browse/DS0001-DSET01-560/
---
WSO2 Carbon 4.0.x > Products 4.0.5 > #24 failed.
---
Code has been updated by sinthuja, nuwanw, dushan, reka, dinusha, chanaka.
No failed tests found, a possi
---
WSO2 Carbon 4.0.x > Platform 4.0.5 > #23 failed.
---
Code has been updated by krishantha, sinthuja, nuwanw, dharshanaw, dushan,
reka, dinusha, chanaka.
No fa
---
WSO2 Carbon 4.0.x > Kernel 4.0.5 > #6 failed.
---
Code has been updated by nuwand, pradeep, amila.
No failed tests found, a possible compilation error.
http:
Hi,
compilation failure in org.wso2.carbon.cassandra.cluster.mgt.ui/4.0.5. I
believe service-stub is not updated properly.
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR]
On Mon, Nov 19, 2012 at 9:43 PM, Sinthuja Ragendran wrote:
> Hi,
>
> compilation failure in org.wso2.carbon.cassandra.cluster.mgt.ui/4.0.5. I
> believe service-stub is not updated properly.
>
We will check the issue.
Thanks,
Deependra.
>
> [INFO] ---
---
WSO2 Carbon 4.0.x > Platform 4.0.5 > #24 failed.
---
Code has been updated by kasunw, nuwanw, supunm, dinusha, shariq, lalaji,
thilini.
No failed tests found
Pradeep committed this.
On Mon, Nov 19, 2012 at 3:41 PM, Afkham Azeez wrote:
> Please replace the CarbonDeploymentSchedulerTask. runAxisDeployment method
> with the following code:
>
> public synchronized void runAxisDeployment() {
> PrivilegedCarbonContext carbonContext =
> Privileg
---
WSO2 Carbon 4.0.x > Products 4.0.4 > #18 failed.
---
Code has been updated by dharshanaw, nuwanw, subash, dinusha.
No failed tests found, a possible compilati
---
WSO2 Carbon 4.0.x > Kernel 4.0.4 > #23 failed.
---
Code has been updated by pradeep.
No failed tests found, a possible compilation error.
http://wso2.org/bam
56 matches
Mail list logo
