Re: [Dev] Compilation Failure when building Kernel - /carbon/kernel/branches/4.0.0/core/org.wso2.carbon.utils/4.0.0

2012-08-28 Thread Buddhima Wijeweera 
PS: local repo. is At revision 140283.


On Wed, Aug 29, 2012 at 11:13 AM, Buddhima Wijeweera wrote:

> Hi ,
>
> I'm getting following error when building kernel
>
> [INFO] -
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
> /home/buddhima/buddhima/repo/carbon/kernel/branches/4.0.0/core/org.wso2.carbon.utils/4.0.0/src/main/java/org/wso2/carbon/utils/multitenancy/CarbonContextHolder.java:[787,44]
> cannot find symbol
> symbol  : method
> getDistributedCacheWithMode(java.lang.String,java.lang.String,boolean,boolean)
> location: interface org.wso2.carbon.caching.core.CarbonCacheManager
> [INFO] 1 error
> [INFO] -
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 5.490s
> [INFO] Finished at: Wed Aug 29 11:08:30 IST 2012
> [INFO] Final Memory: 14M/143M
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
> (default-compile) on project org.wso2.carbon.utils: Compilation failure
> [ERROR]
> /home/buddhima/buddhima/repo/carbon/kernel/branches/4.0.0/core/org.wso2.carbon.utils/4.0.0/src/main/java/org/wso2/carbon/utils/multitenancy/CarbonContextHolder.java:[787,44]
> cannot find symbol
> [ERROR] symbol  : method
> getDistributedCacheWithMode(java.lang.String,java.lang.String,boolean,boolean)
> [ERROR] location: interface org.wso2.carbon.caching.core.CarbonCacheManager
> [ERROR] -> [Help 1]
> [ERROR]
>
>
> Thank you!!!
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Compilation Failure when building Kernel - /carbon/kernel/branches/4.0.0/core/org.wso2.carbon.utils/4.0.0

2012-08-28 Thread Buddhima Wijeweera 
Hi ,

I'm getting following error when building kernel

[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR]
/home/buddhima/buddhima/repo/carbon/kernel/branches/4.0.0/core/org.wso2.carbon.utils/4.0.0/src/main/java/org/wso2/carbon/utils/multitenancy/CarbonContextHolder.java:[787,44]
cannot find symbol
symbol  : method
getDistributedCacheWithMode(java.lang.String,java.lang.String,boolean,boolean)
location: interface org.wso2.carbon.caching.core.CarbonCacheManager
[INFO] 1 error
[INFO] -
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 5.490s
[INFO] Finished at: Wed Aug 29 11:08:30 IST 2012
[INFO] Final Memory: 14M/143M
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
(default-compile) on project org.wso2.carbon.utils: Compilation failure
[ERROR]
/home/buddhima/buddhima/repo/carbon/kernel/branches/4.0.0/core/org.wso2.carbon.utils/4.0.0/src/main/java/org/wso2/carbon/utils/multitenancy/CarbonContextHolder.java:[787,44]
cannot find symbol
[ERROR] symbol  : method
getDistributedCacheWithMode(java.lang.String,java.lang.String,boolean,boolean)
[ERROR] location: interface org.wso2.carbon.caching.core.CarbonCacheManager
[ERROR] -> [Help 1]
[ERROR]


Thank you!!!
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Usage] Improve ErrorHandling/Logging in RegistryUsageListener

2012-08-28 Thread Amila Maha Arachchi 
On Sun, Aug 26, 2012 at 11:51 AM, Amila Maha Arachchi wrote:

> Hi Rajika,
>
> I think this should be only bundled in the usage.agent feature. I'll
> remove it from other places.
>

Removed the usage agent from stratos.common feature and usage.server
feature. Now it is bundled with only the usage.agent feature.

>
> AmilaM.
>
> On Fri, Aug 24, 2012 at 4:25 PM, Rajika Kumarasiri wrote:
>
>> I also noticed that the usage agent feature bundle with many features,
>> stratos.common.feature and usage.agent.feature and it's not a good idea to
>> have duplicates.
>>
>> Rajika
>>
>> On Fri, Aug 24, 2012 at 3:16 PM, Senaka Fernando  wrote:
>>
>>>  Hi Amila,
>>>
>>> The usage listener is running for tenants and performs several internal
>>> registry operations and completes processing. We have no clue on the
>>> decisions or some of the errors that have been resulted in this handler due
>>> to poor ErrorHandling/Logging. Please fix.
>>>
>>> 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
>>>
>>>
>>
>
>
> --
> *Amila Maharachchi*
> Technical Lead
> Member, Management Committee - Cloud & Platform TG
> WSO2, Inc.; http://wso2.com
>
> Blog: http://maharachchi.blogspot.com
> Mobile: +94719371446
>
>
>


-- 
*Amila Maharachchi*
Technical Lead
Member, Management Committee - Cloud & Platform TG
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

Re: [Dev] Help - Invoking basic-auth secured WS

2012-08-28 Thread Thilini Ishaka 
On Wed, Aug 29, 2012 at 12:30 AM, Mohammad Benslimne <
mohammad.benslim...@gmail.com> wrote:

> Hello,
>
> Any good news ?:)
>

We will check this and get back to you ASAP.

Thanks
Thilini

>
>
> Regards,
> Mohammad
>
> On 20 August 2012 09:18, Mohammad Benslimne  > wrote:
>
>> Thanks for your response
>>
>> Here it is my archive ...
>>
>>
>> Regards,
>> Mohammad
>>
>> On 19 August 2012 09:49, Thilini Ishaka  wrote:
>>
>>> Hi,
>>>
>>> Could you please send us the BPEL archive?
>>>
>>> Thanks
>>> Thilini
>>>
>>>
>>> On Fri, Aug 17, 2012 at 11:32 PM, Mohammad Benslimne <
>>> mohammad.benslim...@gmail.com> wrote:
>>>
 Hi,

 I tried to deploy my BPEL project using the WSO2 BPS 3.0.0 
 Alpha,
 but I'm getting FileNotFoundException problem (with both WSO2 Carbin 3.2
 and 4 runtimes) :

 [2012-08-17 13:34:36,160] ERROR
 {org.wso2.carbon.bpel.deployer.BPELDeployer} -  Error deploying BPEL
 package: Nos_1.0.0.zip
 org.apache.ode.bpel.iapi.ContextException: Couldn't read WSDL document
 at NosArtifacts.wsdl
  at
 org.apache.ode.store.DeploymentUnitDir.getDocRegistry(DeploymentUnitDir.java:325)
  at
 org.apache.ode.store.DeploymentUnitDir.getDefinitionForService(DeploymentUnitDir.java:333)
  at
 org.wso2.carbon.bpel.core.ode.integration.store.ProcessConfigurationImpl.getDefinitionForService(ProcessConfigurationImpl.java:272)
  at
 org.wso2.carbon.bpel.core.ode.integration.store.ProcessConfigurationImpl.initPartnerLinks(ProcessConfigurationImpl.java:614)
  at
 org.wso2.carbon.bpel.core.ode.integration.store.ProcessConfigurationImpl.(ProcessConfigurationImpl.java:152)
  at
 org.wso2.carbon.bpel.core.ode.integration.store.TenantProcessStoreImpl.deployBPELPackageInODE(TenantProcessStoreImpl.java:589)
  at
 org.wso2.carbon.bpel.core.ode.integration.store.TenantProcessStoreImpl.deploy(TenantProcessStoreImpl.java:249)
  at
 org.wso2.carbon.bpel.deployer.BPELDeployer.deploy(BPELDeployer.java:97)
  at
 org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
  at
 org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:810)
  at
 org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
  at
 org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
  at
 org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
  at
 org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
  at
 org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59)
  at
 org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67)
  at
 org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:77)
  at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
  at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown
 Source)
  at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
  at
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Unknown
 Source)
  at
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Unknown
 Source)
  at
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown
 Source)
  at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
 Source)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
  at java.lang.Thread.run(Unknown Source)
 Caused by: javax.wsdl.WSDLException: WSDLException (at
 /definitions/types/schema/schema): faultCode=PARSER_ERROR: Problem parsing
 'saml-2.0-os/dependencies/xmldsig-core-schema.xsd'.:
 java.io.FileNotFoundException:
 C:\IN\wso2bps-3.0.0-SNAPSHOT\saml-2.0-os\dependencies\XMLSchema.dtd (Le
 chemin d’accès spécifié est introuvable)
  at
 com.ibm.wsdl.xml.WSDLReaderImpl.getDocument(WSDLReaderImpl.java:2166)
  at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(WSDLReaderImpl.java:845)
  at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(WSDLReaderImpl.java:879)
  at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(WSDLReaderImpl.java:669)
  at com.ibm.wsdl.xml.WSDLReaderImpl.parseTypes(WSDLReaderImpl.java:630)
  at
 com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(WSDLReaderImpl.java:342)
  at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2320)
  at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2284)
  at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2337)
  at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2358)
  at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2390)

[Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Kernel_4.0.0 > #148 has FAILED. Change made by Kishanthan Thangarajah, prabath and azeez.

2012-08-28 Thread Bamboo 

---
WSO2 Carbon BRANCH > Kernel_4.0.0 > #148 failed.
---
Code has been updated by Kishanthan Thangarajah, prabath, azeez.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-KER000-148/

-
Currently Responsible
-

Kishanthan Thangarajah (Automatically assigned)



--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.



--
Code Changes
--
Kishanthan Thangarajah (140236):

>fixing WSAS-1042, we need to set the correct configuration context in 
>LocalTranportReciever

azeez (140229):

>Added Axiom 1.2.11.wso2v3
>

azeez (140228):

>Updated versions
>



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Platform_4.0.0 > #219 was SUCCESSFUL (with 1788 tests). Change made by 6 authors.

2012-08-28 Thread Bamboo 

---
WSO2 Carbon BRANCH > Platform_4.0.0 > #219 was successful.
---
This build occurred because it is a dependant of WCB001-KER000-147.
1788 tests in total.

http://wso2.org/bamboo/browse/WCB001-PLA000-219/




--
Code Changes
--
tharindu (140242):

>go to dashboard goes to link in new tab

suresh (140227):

>adding 4.0.1 of oauth stub to oauth ui feature

isuruw (140237):

>Fixing the issue REGISTRY-1205



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Help - Invoking basic-auth secured WS

2012-08-28 Thread Mohammad Benslimne 
Hello,

Any good news ?:)


Regards,
Mohammad

On 20 August 2012 09:18, Mohammad Benslimne
wrote:

> Thanks for your response
>
> Here it is my archive ...
>
>
> Regards,
> Mohammad
>
> On 19 August 2012 09:49, Thilini Ishaka  wrote:
>
>> Hi,
>>
>> Could you please send us the BPEL archive?
>>
>> Thanks
>> Thilini
>>
>>
>> On Fri, Aug 17, 2012 at 11:32 PM, Mohammad Benslimne <
>> mohammad.benslim...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I tried to deploy my BPEL project using the WSO2 BPS 3.0.0 
>>> Alpha,
>>> but I'm getting FileNotFoundException problem (with both WSO2 Carbin 3.2
>>> and 4 runtimes) :
>>>
>>> [2012-08-17 13:34:36,160] ERROR
>>> {org.wso2.carbon.bpel.deployer.BPELDeployer} -  Error deploying BPEL
>>> package: Nos_1.0.0.zip
>>> org.apache.ode.bpel.iapi.ContextException: Couldn't read WSDL document
>>> at NosArtifacts.wsdl
>>>  at
>>> org.apache.ode.store.DeploymentUnitDir.getDocRegistry(DeploymentUnitDir.java:325)
>>>  at
>>> org.apache.ode.store.DeploymentUnitDir.getDefinitionForService(DeploymentUnitDir.java:333)
>>>  at
>>> org.wso2.carbon.bpel.core.ode.integration.store.ProcessConfigurationImpl.getDefinitionForService(ProcessConfigurationImpl.java:272)
>>>  at
>>> org.wso2.carbon.bpel.core.ode.integration.store.ProcessConfigurationImpl.initPartnerLinks(ProcessConfigurationImpl.java:614)
>>>  at
>>> org.wso2.carbon.bpel.core.ode.integration.store.ProcessConfigurationImpl.(ProcessConfigurationImpl.java:152)
>>>  at
>>> org.wso2.carbon.bpel.core.ode.integration.store.TenantProcessStoreImpl.deployBPELPackageInODE(TenantProcessStoreImpl.java:589)
>>>  at
>>> org.wso2.carbon.bpel.core.ode.integration.store.TenantProcessStoreImpl.deploy(TenantProcessStoreImpl.java:249)
>>>  at
>>> org.wso2.carbon.bpel.deployer.BPELDeployer.deploy(BPELDeployer.java:97)
>>>  at
>>> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
>>>  at
>>> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:810)
>>>  at
>>> org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
>>>  at
>>> org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
>>>  at
>>> org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
>>>  at
>>> org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
>>>  at
>>> org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59)
>>>  at
>>> org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67)
>>>  at
>>> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:77)
>>>  at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
>>>  at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source)
>>>  at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
>>>  at
>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Unknown
>>> Source)
>>>  at
>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Unknown
>>> Source)
>>>  at
>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown
>>> Source)
>>>  at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
>>> Source)
>>>  at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
>>>  at java.lang.Thread.run(Unknown Source)
>>> Caused by: javax.wsdl.WSDLException: WSDLException (at
>>> /definitions/types/schema/schema): faultCode=PARSER_ERROR: Problem parsing
>>> 'saml-2.0-os/dependencies/xmldsig-core-schema.xsd'.:
>>> java.io.FileNotFoundException:
>>> C:\IN\wso2bps-3.0.0-SNAPSHOT\saml-2.0-os\dependencies\XMLSchema.dtd (Le
>>> chemin d’accès spécifié est introuvable)
>>>  at com.ibm.wsdl.xml.WSDLReaderImpl.getDocument(WSDLReaderImpl.java:2166)
>>>  at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(WSDLReaderImpl.java:845)
>>>  at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(WSDLReaderImpl.java:879)
>>>  at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(WSDLReaderImpl.java:669)
>>>  at com.ibm.wsdl.xml.WSDLReaderImpl.parseTypes(WSDLReaderImpl.java:630)
>>>  at
>>> com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(WSDLReaderImpl.java:342)
>>>  at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2320)
>>>  at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2284)
>>>  at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2337)
>>>  at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2358)
>>>  at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2390)
>>>  at
>>> org.apache.ode.store.DeploymentUnitDir.getDocRegistry(DeploymentUnitDir.java:323)
>>>  ... 25 more
>>> Caused by: java.io.FileNotFoundException:
>>> C:\IN\wso2bps-3.0.0-SNAPSHOT\saml-2.0-os\dependencies\XMLSchema.dtd (Le
>>> chemin d’accès spécifié est introuvable)
>>>  at ja

[Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Platform_4.0.0 > #218 has FAILED. Change made by 22 authors.

2012-08-28 Thread Bamboo 

---
WSO2 Carbon BRANCH > Platform_4.0.0 > #218 failed.
---
This build occurred because it is a dependant of WCB001-KER000-146.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PLA000-218/

-
Currently Responsible
-

Kishanthan Thangarajah (Automatically assigned)



--
Failing Jobs
--
  - Default Job (Default Stage): 1788 tests passed.



--
Code Changes
--
krishantha (140139):

>Applying ishan's patch - TA-504

ajithn (140218):

>Fxied build issue due to version mismach with  thrift orbit 

hasini (140104):

>adding scim attribute to claim conversion



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Axiom upgraded to 1.2.11.wso2v3 in Carbon 4.0.0 branch

2012-08-28 Thread Afkham Azeez 
Please note $subject.

Samisa & I have been working on some Axiom performance improvements.

-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Invoking WSO2 Carbon admin services using BPEL.

2012-08-28 Thread Thilini Ishaka 
On Tue, Aug 28, 2012 at 8:39 PM, Sameera Jayasoma  wrote:

> Hi Thilini,
>
> Yeah this helps. Thanks for the reply. So now we have a way to invoke
> admin services. But does this mean that we have hard-code the
> username/passwords. Is there a way to dynamically set the username and the
> password?
>
No. At the moment you can not set the username/password dynamically.

>
> Sameera.
>
> On Tue, Aug 28, 2012 at 12:12 AM, Thilini Ishaka  wrote:
>
>> Hi,
>>
>> This can be done with BPS 3.0.0. Try out with alpha or beta released pack.
>>
>>  You have to add relevant http headers basically the username and
>> password via unified endpoints.
>> A sample configuration (.epr) is given below.
>>
>> 
>> SInvokeEPR
>> 
>>  *   adminx *
>> *adminy *
>> 
>> 
>>
>> FYI: [1] & [2]
>> [1]
>> https://svn.wso2.org/repos/wso2/carbon/platform/trunk/products/appfactory/modules/bpels/UserCreation/
>>
>> [2]
>> https://svn.wso2.org/repos/wso2/carbon/platform/trunk/products/appfactory/modules/distribution/product/resources/appfactory/endpoints/UserRegistrationService.epr
>>
>>
>> Hope this helps.
>>
>> Thanks
>> Thilini
>> On Tue, Aug 28, 2012 at 12:31 PM, Sameera Jayasoma wrote:
>>
>>> Hi Devs,
>>>
>>> If I put the requirement in another words, how can I add or read HTTP
>>> header  in a BPEL process. I don't think, BPEL language supports this as
>>> this is a transport dependent operation.
>>>
>>> I've implemented this in 3.2.* release using proxy services for each
>>> admin service.  These proxy services set the cookie value and invoke admin
>>> services. Once you logged in to the AuthenticationAdmin service you get a
>>> authenticated cookie and you can use this cookie value can be used for all
>>> subsequent invokations.
>>>
>>>1. BPEL process invoke the login method in the
>>>AuthenticationAdminProxy service which in turn invokes the back-end
>>>server's AuthenticationAdmin service. On the return path, this proxy
>>>service retrive the authenticated cookie and sent to BPEL as value in the
>>>SOAP message so the BPEL can save this value in a variable.
>>>2. For all the subsequent requests from the BPEL process, it send
>>>this cookie to the corresponding proxy services. These proxy services set
>>>the cookie as a HTTP header and invoke the back-end service.
>>>
>>> This is kinda hacky solution. But we couldn't find a proper solution at
>>> that time.  I would like to know whether we can do this properly in latest
>>> release. Please let me know.
>>>
>>> Thanks,
>>> Sameera.
>>>
>>> --
>>> Sameera Jayasoma
>>> Senior Technical Lead
>>>
>>> WSO2, Inc. (http://wso2.com)
>>> email: same...@wso2.com
>>> blog: http://tech.jayasoma.org
>>>
>>> Lean . Enterprise . Middleware
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Thilini Ishaka
>> WSO2 Inc. http://wso2.com*
>> *bolg: thiliniishaka.blogspot.com*
>> *linkedin: http://lk.linkedin.com/in/thiliniishaka*
>> *twitter: https://twitter.com/#!/ThiliniIsh*
>>
>>
>
>
> --
> Sameera Jayasoma
> Senior Technical Lead
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com
> blog: http://tech.jayasoma.org
>
> Lean . Enterprise . Middleware
>



-- 
*Thilini Ishaka
WSO2 Inc. http://wso2.com*
*bolg: thiliniishaka.blogspot.com*
*linkedin: http://lk.linkedin.com/in/thiliniishaka*
*twitter: https://twitter.com/#!/ThiliniIsh*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Invoking WSO2 Carbon admin services using BPEL.

2012-08-28 Thread Sameera Jayasoma 
Hi Thilini,

Yeah this helps. Thanks for the reply. So now we have a way to invoke admin
services. But does this mean that we have hard-code the username/passwords.
Is there a way to dynamically set the username and the password?

Sameera.

On Tue, Aug 28, 2012 at 12:12 AM, Thilini Ishaka  wrote:

> Hi,
>
> This can be done with BPS 3.0.0. Try out with alpha or beta released pack.
>
>  You have to add relevant http headers basically the username and
> password via unified endpoints.
> A sample configuration (.epr) is given below.
>
> 
> SInvokeEPR
> 
>  *   adminx *
> *adminy *
> 
> 
>
> FYI: [1] & [2]
> [1]
> https://svn.wso2.org/repos/wso2/carbon/platform/trunk/products/appfactory/modules/bpels/UserCreation/
>
> [2]
> https://svn.wso2.org/repos/wso2/carbon/platform/trunk/products/appfactory/modules/distribution/product/resources/appfactory/endpoints/UserRegistrationService.epr
>
>
> Hope this helps.
>
> Thanks
> Thilini
> On Tue, Aug 28, 2012 at 12:31 PM, Sameera Jayasoma wrote:
>
>> Hi Devs,
>>
>> If I put the requirement in another words, how can I add or read HTTP
>> header  in a BPEL process. I don't think, BPEL language supports this as
>> this is a transport dependent operation.
>>
>> I've implemented this in 3.2.* release using proxy services for each
>> admin service.  These proxy services set the cookie value and invoke admin
>> services. Once you logged in to the AuthenticationAdmin service you get a
>> authenticated cookie and you can use this cookie value can be used for all
>> subsequent invokations.
>>
>>1. BPEL process invoke the login method in the
>>AuthenticationAdminProxy service which in turn invokes the back-end
>>server's AuthenticationAdmin service. On the return path, this proxy
>>service retrive the authenticated cookie and sent to BPEL as value in the
>>SOAP message so the BPEL can save this value in a variable.
>>2. For all the subsequent requests from the BPEL process, it send
>>this cookie to the corresponding proxy services. These proxy services set
>>the cookie as a HTTP header and invoke the back-end service.
>>
>> This is kinda hacky solution. But we couldn't find a proper solution at
>> that time.  I would like to know whether we can do this properly in latest
>> release. Please let me know.
>>
>> Thanks,
>> Sameera.
>>
>> --
>> Sameera Jayasoma
>> Senior Technical Lead
>>
>> WSO2, Inc. (http://wso2.com)
>> email: same...@wso2.com
>> blog: http://tech.jayasoma.org
>>
>> Lean . Enterprise . Middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Thilini Ishaka
> WSO2 Inc. http://wso2.com*
> *bolg: thiliniishaka.blogspot.com*
> *linkedin: http://lk.linkedin.com/in/thiliniishaka*
> *twitter: https://twitter.com/#!/ThiliniIsh*
>
>


-- 
Sameera Jayasoma
Senior Technical Lead

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://tech.jayasoma.org

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Build failed due to cassandra version upgrade.

2012-08-28 Thread Supun Malinga 
Hi,

Please check r139120.

thanks,

On Tue, Aug 28, 2012 at 8:03 PM, Deependra Ariyadewa  wrote:

>
>
> On Tue, Aug 28, 2012 at 7:29 PM, Tharindu Mathew wrote:
>
>> I can't seem to reproduce this issue. Can you build the profile gen with
>> debug logs and check?
>
>
> There was a version issue related to thrift but SupunM fixed it.
>
>>
>>
>> On Tue, Aug 28, 2012 at 6:17 PM, Ajith Vitharana  wrote:
>>
>>> Hi all,
>>>
>>> This failure due to commit r140065, Please  fix this properly.
>>>
>>> Cannot complete the install because one or more required items could not
>>> be found.
>>>  Software being installed: WSO2 Carbon - Logging Management Feature
>>> 4.0.1 (org.wso2.carbon.logging.mgt.feature.group 4.0.1)
>>>  Missing requirement: apache-cassandra 1.1.3.wso2v1 (apache-cassandra
>>> 1.1.3.wso2v1) requires 'package org.apache.thrift
>>> [0.7.0.wso2v1,0.8.0.wso2v1)' but it could not be found
>>>  Cannot satisfy dependency:
>>>   From: WSO2 Carbon - Logging Management Feature 4.0.1
>>> (org.wso2.carbon.logging.mgt.feature.group 4.0.1)
>>>   To: org.wso2.carbon.logging.mgt.server.feature.group [4.0.1]
>>>  Cannot satisfy dependency:
>>>   From: WSO2 Carbon - Logging Management Core Feature 4.0.1
>>> (org.wso2.carbon.logging.mgt.server.feature.group 4.0.1)
>>>   To: apache-cassandra [1.1.3.wso2v1]
>>> Application failed, log file location:
>>> /home/ajithn/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1346157242629.log
>>>
>>> Thanks
>>> Ajith
>>>
>>> --
>>> Ajith Vitharana.
>>> WSO2 Inc. - http://wso2.org
>>> Email  :  aji...@wso2.com
>>> Mobile : +94714631794
>>>
>>>
>>>
>>
>>
>> --
>> Regards,
>>
>> Tharindu
>>
>> blog: http://mackiemathew.com/
>> M: +9459908
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Deependra Ariyadewa
> WSO2, Inc. http://wso2.com/ http://wso2.org
>
> email d...@wso2.com; cell +94 71 403 5996 ;
> Blog http://risenfall.wordpress.com/
> PGP info: KeyID: 'DC627E6F'
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Supun Malinga,

Software Engineer,
WSO2 Inc.
http://wso2.com
http://wso2.org
email - sup...@wso2.com 
mobile - 071 56 91 321
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Build failed due to cassandra version upgrade.

2012-08-28 Thread Ajith Vitharana 
On Tue, Aug 28, 2012 at 7:29 PM, Tharindu Mathew  wrote:

> I can't seem to reproduce this issue. Can you build the profile gen with
> debug logs and check?


The thrift dependency version is wrong in cassandra/1.1.3.wso2v1/pom.xml.
It should be correct as [*0.7.wso2v1,0.8.wso2v1*
)

[1]
https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0/dependencies/
*orbit/libthrift/0.7.wso2v1*
[2]
https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0/dependencies/orbit/cassandra/1.1.3.wso2v1/pom.xml

Thanks
Ajith


>
>
> On Tue, Aug 28, 2012 at 6:17 PM, Ajith Vitharana  wrote:
>
>> Hi all,
>>
>> This failure due to commit r140065, Please  fix this properly.
>>
>> Cannot complete the install because one or more required items could not
>> be found.
>>  Software being installed: WSO2 Carbon - Logging Management Feature 4.0.1
>> (org.wso2.carbon.logging.mgt.feature.group 4.0.1)
>>  Missing requirement: apache-cassandra 1.1.3.wso2v1 (apache-cassandra
>> 1.1.3.wso2v1) requires 'package org.apache.thrift
>> [0.7.0.wso2v1,0.8.0.wso2v1)' but it could not be found
>>  Cannot satisfy dependency:
>>   From: WSO2 Carbon - Logging Management Feature 4.0.1
>> (org.wso2.carbon.logging.mgt.feature.group 4.0.1)
>>   To: org.wso2.carbon.logging.mgt.server.feature.group [4.0.1]
>>  Cannot satisfy dependency:
>>   From: WSO2 Carbon - Logging Management Core Feature 4.0.1
>> (org.wso2.carbon.logging.mgt.server.feature.group 4.0.1)
>>   To: apache-cassandra [1.1.3.wso2v1]
>> Application failed, log file location:
>> /home/ajithn/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1346157242629.log
>>
>> Thanks
>> Ajith
>>
>> --
>> Ajith Vitharana.
>> WSO2 Inc. - http://wso2.org
>> Email  :  aji...@wso2.com
>> Mobile : +94714631794
>>
>>
>>
>
>
> --
> Regards,
>
> Tharindu
>
> blog: http://mackiemathew.com/
> M: +9459908
>
>


-- 
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

[Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Platform_4.0.0 > #217 was SUCCESSFUL (with 1788 tests). Change made by 16 authors.

2012-08-28 Thread Bamboo 

---
WSO2 Carbon BRANCH > Platform_4.0.0 > #217 was successful.
---
Code has been updated by hasini, krishantha, nuwanw, subash, ranga, chethiya, 
eranda, janaka, tharindu, amani, prabatha, ajanthan, supunm, reka, ajithn, 
lakmali.
1788 tests in total.

http://wso2.org/bamboo/browse/WCB001-PLA000-217/




--
Code Changes
--
tharindu (140060):

>fix cassandra version

ajithn (140088):

>fixed possible NPE

hasini (140067):

>adding a null check



--
Tests
--
Fixed Tests (15)
   - EndpointTest: Associating endpoints
   - EndpointTest: Attach endpoints to service
   - EndpointTest: Detach endpoints to service
   - EndpointTest: Add service with endpoints
   - EndpointTest: Non http endpoints to service
   - EndpointTest: Service adding endpoints with wsdl
   - EndpointTest: Add wsdl with endpoints
   - PolicyTest: Add policy
   - PolicyTest: Add policy from content
   - PolicyTest: Add policy from content no name
   - ServiceTest: Service delete
   - ServiceTest: Service attachments
   - ServiceTest: Add service
   - ServiceTest: Service search
   - WSDLTest: Add w s d l

--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Build error in features - org.wso2.carbon.identity.authenticator.iwa.ui.feature

2012-08-28 Thread Kishanthan Thangarajah 
This got resolved only after manually building
components/authenticators/iwa-authenticator, as it will install the
org.wso2.carbon:iwa-authenticator:pom:4.0.1. The issue is iwa-authenticator
doesn't have 4.0.0 release. So i thing to fix this, we have to include
the aggregator module (components/authenticators/iwa-authenticator) in the
patch release component pom.

   ../../../components/authenticators/iwa-authenticator

This should fix this.

On Tue, Aug 28, 2012 at 5:45 PM, Janaka Ranabahu  wrote:

> Hi Kishanthan,
>
> I did a svn update today and the issue got resolved. I did a full build
> including the kernel.
>
> Thanks,
> Janaka
>
>
> On Tue, Aug 28, 2012 at 5:36 PM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>> Is this fixed? I'm getting this a patch release features level.
>>
>> On Tue, Aug 28, 2012 at 10:02 AM, Janaka Ranabahu wrote:
>>
>>> Hi All,
>>>
>>> Im getting the following error when building features.
>>>
>>> [INFO] STS Feature ... SUCCESS
>>> [0.620s]
>>> [INFO] SAML2 based authenticator UI Feature .. SUCCESS
>>> [2.599s]
>>> [INFO] SAML2 based authenticator Server Feature .. SUCCESS
>>> [0.533s]
>>> [INFO] SAML2 based Single Sign-On authenticator Feature .. SUCCESS
>>> [3.211s]
>>> [INFO] IWA based authenticator UI Feature  FAILURE
>>> [0.820s]
>>> [INFO] IWA based authenticator Server Feature  SKIPPED
>>> [INFO] IWA based authenticator Feature ... SKIPPED
>>> [INFO] WSO2 Carbon - Api management Server Feature ... SKIPPED
>>> [INFO] WSO2 Carbon - API Publisher Feature ... SKIPPED
>>> [INFO] WSO2 Carbon - API Store Feature ... SKIPPED
>>> [INFO] WSO2 Carbon - Api management Feature .. SKIPPED
>>> [INFO] WSO2 Carbon - Patch releases - features - Aggregator Module
>>>  SKIPPED
>>> [INFO]
>>> 
>>> [INFO] BUILD FAILURE
>>> [INFO]
>>> 
>>> [INFO] Total time: 12:59.051s
>>> [INFO] Finished at: Tue Aug 28 09:55:47 IST 2012
>>> [INFO] Final Memory: 195M/414M
>>> [INFO]
>>> 
>>> [ERROR] Failed to execute goal on project
>>> org.wso2.carbon.identity.authenticator.iwa.ui.feature: Could not resolve
>>> dependencies for project
>>> org.wso2.carbon:org.wso2.carbon.identity.authenticator.iwa.ui.feature:pom:4.0.1:
>>> Failed to collect dependencies for
>>> [org.wso2.carbon:org.wso2.carbon.identity.authenticator.iwa.ui:jar:4.0.1
>>> (compile),
>>> org.wso2.carbon:org.wso2.carbon.identity.authenticator.iwa.stub:jar:4.0.1
>>> (compile)]: Failed to read artifact descriptor for
>>> org.wso2.carbon:org.wso2.carbon.identity.authenticator.iwa.ui:jar:4.0.1:
>>> Could not find artifact org.wso2.carbon:iwa-authenticator:pom:4.0.1 in
>>> wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/) ->
>>> [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/DependencyResolutionException
>>> [ERROR]
>>> [ERROR] After correcting the problems, you can resume the build with the
>>> command
>>> [ERROR]   mvn  -rf
>>> :org.wso2.carbon.identity.authenticator.iwa.ui.feature
>>>
>>>
>>> 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
>>>
>>>
>>
>>
>> --
>> *Kishanthan Thangarajah*
>> Software Engineer,
>> Development Technologies Team,
>> WSO2, Inc.
>> lean.enterprise.middleware
>>
>> Mobile - +94773426635
>> Blog - *http://kishanthan.wordpress.com*
>> Twitter - *http://twitter.com/kishanthan*
>>
>>
>
>
> --
> Janaka Ranabahu
> Software Engineer
> WSO2 Inc.
>
> Mobile +94 718370861
> Email : jan...@wso2.com
> Blog : janakaranabahu.blogspot.com
>
>


-- 
*Kishanthan Thangarajah*
Software Engineer,
Development Technologies Team,
WSO2, Inc.
lean.enterprise.middleware

Mobile - +94773426635
Blog - *http://kishanthan.wordpress.com*
Twitter - *http://twitter.com/kishanthan*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Build failed due to cassandra version upgrade.

2012-08-28 Thread Deependra Ariyadewa 
On Tue, Aug 28, 2012 at 7:29 PM, Tharindu Mathew  wrote:

> I can't seem to reproduce this issue. Can you build the profile gen with
> debug logs and check?


There was a version issue related to thrift but SupunM fixed it.

>
>
> On Tue, Aug 28, 2012 at 6:17 PM, Ajith Vitharana  wrote:
>
>> Hi all,
>>
>> This failure due to commit r140065, Please  fix this properly.
>>
>> Cannot complete the install because one or more required items could not
>> be found.
>>  Software being installed: WSO2 Carbon - Logging Management Feature 4.0.1
>> (org.wso2.carbon.logging.mgt.feature.group 4.0.1)
>>  Missing requirement: apache-cassandra 1.1.3.wso2v1 (apache-cassandra
>> 1.1.3.wso2v1) requires 'package org.apache.thrift
>> [0.7.0.wso2v1,0.8.0.wso2v1)' but it could not be found
>>  Cannot satisfy dependency:
>>   From: WSO2 Carbon - Logging Management Feature 4.0.1
>> (org.wso2.carbon.logging.mgt.feature.group 4.0.1)
>>   To: org.wso2.carbon.logging.mgt.server.feature.group [4.0.1]
>>  Cannot satisfy dependency:
>>   From: WSO2 Carbon - Logging Management Core Feature 4.0.1
>> (org.wso2.carbon.logging.mgt.server.feature.group 4.0.1)
>>   To: apache-cassandra [1.1.3.wso2v1]
>> Application failed, log file location:
>> /home/ajithn/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1346157242629.log
>>
>> Thanks
>> Ajith
>>
>> --
>> Ajith Vitharana.
>> WSO2 Inc. - http://wso2.org
>> Email  :  aji...@wso2.com
>> Mobile : +94714631794
>>
>>
>>
>
>
> --
> Regards,
>
> Tharindu
>
> blog: http://mackiemathew.com/
> M: +9459908
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Deependra Ariyadewa
WSO2, Inc. http://wso2.com/ http://wso2.org

email d...@wso2.com; cell +94 71 403 5996 ;
Blog http://risenfall.wordpress.com/
PGP info: KeyID: 'DC627E6F'
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error when loggin in to latest ESB build

2012-08-28 Thread Miyuru Wanninayaka 
this is just fixed


On Tue, Aug 28, 2012 at 6:58 PM, Miyuru Wanninayaka  wrote:

> [2012-08-28 18:48:24,147] ERROR - AbstractAuthenticator Unable to execute
> post authentication operations in a successful login. User - admin
> java.lang.NullPointerException
> at
> org.wso2.carbon.governance.registry.extensions.utils.CommonUtil.addRxtConfigs(CommonUtil.java:158)
> at
> org.wso2.carbon.governance.registry.extensions.listeners.RxtLoader.onLogin(RxtLoader.java:19)
> at
> org.wso2.carbon.core.services.callback.LoginSubscriptionManagerServiceImpl.triggerEvent(LoginSubscriptionManagerServiceImpl.java:41)
> at
> org.wso2.carbon.core.services.util.CarbonAuthenticationUtil.onSuccessAdminLogin(CarbonAuthenticationUtil.java:96)
> at
> org.wso2.carbon.core.services.authentication.AbstractAuthenticator.onSuccessLogin(AbstractAuthenticator.java:239)
> at
> org.wso2.carbon.core.services.authentication.AbstractAuthenticator.authenticate(AbstractAuthenticator.java:179)
> at
> org.wso2.carbon.server.admin.module.handler.AuthenticationHandler.isAuthenticated(AuthenticationHandler.java:161)
> at
> org.wso2.carbon.server.admin.module.handler.AuthenticationHandler.authenticate(AuthenticationHandler.java:86)
> at
> org.wso2.carbon.server.admin.module.handler.AuthenticationHandler.invoke(AuthenticationHandler.java:58)
> at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
> at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:262)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:168)
> at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
> at
> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
> at
> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:205)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
> at
> org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
> at
> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:58)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at
> org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:225)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> 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:179)
> 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:49)
> 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:1001)
> at
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579)
> at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
> 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:662)
>
>
> --
> Thanks,
> Miyuru
>



-- 
Thanks,
Miyuru
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Need dataservices feature for BAM2 beta

2012-08-28 Thread Vijayaratha Vijayasingam 
Hi all;
I could not find dataservices feature in BAM2 Beta p2 repo[1]...I need that
to install in BAM2beta pack
[1]http://people.wso2.com/~kasunw/BAM2-BETA-p2-repo/

Thanks
-Ratha
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Build failed due to cassandra version upgrade.

2012-08-28 Thread Tharindu Mathew 
I can't seem to reproduce this issue. Can you build the profile gen with
debug logs and check?

On Tue, Aug 28, 2012 at 6:17 PM, Ajith Vitharana  wrote:

> Hi all,
>
> This failure due to commit r140065, Please  fix this properly.
>
> Cannot complete the install because one or more required items could not
> be found.
>  Software being installed: WSO2 Carbon - Logging Management Feature 4.0.1
> (org.wso2.carbon.logging.mgt.feature.group 4.0.1)
>  Missing requirement: apache-cassandra 1.1.3.wso2v1 (apache-cassandra
> 1.1.3.wso2v1) requires 'package org.apache.thrift
> [0.7.0.wso2v1,0.8.0.wso2v1)' but it could not be found
>  Cannot satisfy dependency:
>   From: WSO2 Carbon - Logging Management Feature 4.0.1
> (org.wso2.carbon.logging.mgt.feature.group 4.0.1)
>   To: org.wso2.carbon.logging.mgt.server.feature.group [4.0.1]
>  Cannot satisfy dependency:
>   From: WSO2 Carbon - Logging Management Core Feature 4.0.1
> (org.wso2.carbon.logging.mgt.server.feature.group 4.0.1)
>   To: apache-cassandra [1.1.3.wso2v1]
> Application failed, log file location:
> /home/ajithn/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1346157242629.log
>
> Thanks
> Ajith
>
> --
> Ajith Vitharana.
> WSO2 Inc. - http://wso2.org
> Email  :  aji...@wso2.com
> Mobile : +94714631794
>
>
>


-- 
Regards,

Tharindu

blog: http://mackiemathew.com/
M: +9459908
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Error when loggin in to latest ESB build

2012-08-28 Thread Miyuru Wanninayaka 
[2012-08-28 18:48:24,147] ERROR - AbstractAuthenticator Unable to execute
post authentication operations in a successful login. User - admin
java.lang.NullPointerException
at
org.wso2.carbon.governance.registry.extensions.utils.CommonUtil.addRxtConfigs(CommonUtil.java:158)
at
org.wso2.carbon.governance.registry.extensions.listeners.RxtLoader.onLogin(RxtLoader.java:19)
at
org.wso2.carbon.core.services.callback.LoginSubscriptionManagerServiceImpl.triggerEvent(LoginSubscriptionManagerServiceImpl.java:41)
at
org.wso2.carbon.core.services.util.CarbonAuthenticationUtil.onSuccessAdminLogin(CarbonAuthenticationUtil.java:96)
at
org.wso2.carbon.core.services.authentication.AbstractAuthenticator.onSuccessLogin(AbstractAuthenticator.java:239)
at
org.wso2.carbon.core.services.authentication.AbstractAuthenticator.authenticate(AbstractAuthenticator.java:179)
at
org.wso2.carbon.server.admin.module.handler.AuthenticationHandler.isAuthenticated(AuthenticationHandler.java:161)
at
org.wso2.carbon.server.admin.module.handler.AuthenticationHandler.authenticate(AuthenticationHandler.java:86)
at
org.wso2.carbon.server.admin.module.handler.AuthenticationHandler.invoke(AuthenticationHandler.java:58)
at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:262)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:168)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
at
org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:205)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:58)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:225)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
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:179)
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:49)
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:1001)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
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:662)


-- 
Thanks,
Miyuru
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Build failed due to cassandra version upgrade.

2012-08-28 Thread Ajith Vitharana 
Hi all,

This failure due to commit r140065, Please  fix this properly.

Cannot complete the install because one or more required items could not be
found.
 Software being installed: WSO2 Carbon - Logging Management Feature 4.0.1
(org.wso2.carbon.logging.mgt.feature.group 4.0.1)
 Missing requirement: apache-cassandra 1.1.3.wso2v1 (apache-cassandra
1.1.3.wso2v1) requires 'package org.apache.thrift
[0.7.0.wso2v1,0.8.0.wso2v1)' but it could not be found
 Cannot satisfy dependency:
  From: WSO2 Carbon - Logging Management Feature 4.0.1
(org.wso2.carbon.logging.mgt.feature.group 4.0.1)
  To: org.wso2.carbon.logging.mgt.server.feature.group [4.0.1]
 Cannot satisfy dependency:
  From: WSO2 Carbon - Logging Management Core Feature 4.0.1
(org.wso2.carbon.logging.mgt.server.feature.group 4.0.1)
  To: apache-cassandra [1.1.3.wso2v1]
Application failed, log file location:
/home/ajithn/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1346157242629.log

Thanks
Ajith

-- 
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

Re: [Dev] Build error in features - org.wso2.carbon.identity.authenticator.iwa.ui.feature

2012-08-28 Thread Janaka Ranabahu 
Hi Kishanthan,

I did a svn update today and the issue got resolved. I did a full build
including the kernel.

Thanks,
Janaka

On Tue, Aug 28, 2012 at 5:36 PM, Kishanthan Thangarajah  wrote:

> Is this fixed? I'm getting this a patch release features level.
>
> On Tue, Aug 28, 2012 at 10:02 AM, Janaka Ranabahu  wrote:
>
>> Hi All,
>>
>> Im getting the following error when building features.
>>
>> [INFO] STS Feature ... SUCCESS
>> [0.620s]
>> [INFO] SAML2 based authenticator UI Feature .. SUCCESS
>> [2.599s]
>> [INFO] SAML2 based authenticator Server Feature .. SUCCESS
>> [0.533s]
>> [INFO] SAML2 based Single Sign-On authenticator Feature .. SUCCESS
>> [3.211s]
>> [INFO] IWA based authenticator UI Feature  FAILURE
>> [0.820s]
>> [INFO] IWA based authenticator Server Feature  SKIPPED
>> [INFO] IWA based authenticator Feature ... SKIPPED
>> [INFO] WSO2 Carbon - Api management Server Feature ... SKIPPED
>> [INFO] WSO2 Carbon - API Publisher Feature ... SKIPPED
>> [INFO] WSO2 Carbon - API Store Feature ... SKIPPED
>> [INFO] WSO2 Carbon - Api management Feature .. SKIPPED
>> [INFO] WSO2 Carbon - Patch releases - features - Aggregator Module
>>  SKIPPED
>> [INFO]
>> 
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time: 12:59.051s
>> [INFO] Finished at: Tue Aug 28 09:55:47 IST 2012
>> [INFO] Final Memory: 195M/414M
>> [INFO]
>> 
>> [ERROR] Failed to execute goal on project
>> org.wso2.carbon.identity.authenticator.iwa.ui.feature: Could not resolve
>> dependencies for project
>> org.wso2.carbon:org.wso2.carbon.identity.authenticator.iwa.ui.feature:pom:4.0.1:
>> Failed to collect dependencies for
>> [org.wso2.carbon:org.wso2.carbon.identity.authenticator.iwa.ui:jar:4.0.1
>> (compile),
>> org.wso2.carbon:org.wso2.carbon.identity.authenticator.iwa.stub:jar:4.0.1
>> (compile)]: Failed to read artifact descriptor for
>> org.wso2.carbon:org.wso2.carbon.identity.authenticator.iwa.ui:jar:4.0.1:
>> Could not find artifact org.wso2.carbon:iwa-authenticator:pom:4.0.1 in
>> wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/) ->
>> [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/DependencyResolutionException
>> [ERROR]
>> [ERROR] After correcting the problems, you can resume the build with the
>> command
>> [ERROR]   mvn  -rf
>> :org.wso2.carbon.identity.authenticator.iwa.ui.feature
>>
>>
>> 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
>>
>>
>
>
> --
> *Kishanthan Thangarajah*
> Software Engineer,
> Development Technologies Team,
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - +94773426635
> Blog - *http://kishanthan.wordpress.com*
> Twitter - *http://twitter.com/kishanthan*
>
>


-- 
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

Re: [Dev] Build error in features - org.wso2.carbon.identity.authenticator.iwa.ui.feature

2012-08-28 Thread Kishanthan Thangarajah 
Is this fixed? I'm getting this a patch release features level.

On Tue, Aug 28, 2012 at 10:02 AM, Janaka Ranabahu  wrote:

> Hi All,
>
> Im getting the following error when building features.
>
> [INFO] STS Feature ... SUCCESS [0.620s]
> [INFO] SAML2 based authenticator UI Feature .. SUCCESS [2.599s]
> [INFO] SAML2 based authenticator Server Feature .. SUCCESS [0.533s]
> [INFO] SAML2 based Single Sign-On authenticator Feature .. SUCCESS [3.211s]
> [INFO] IWA based authenticator UI Feature  FAILURE [0.820s]
> [INFO] IWA based authenticator Server Feature  SKIPPED
> [INFO] IWA based authenticator Feature ... SKIPPED
> [INFO] WSO2 Carbon - Api management Server Feature ... SKIPPED
> [INFO] WSO2 Carbon - API Publisher Feature ... SKIPPED
> [INFO] WSO2 Carbon - API Store Feature ... SKIPPED
> [INFO] WSO2 Carbon - Api management Feature .. SKIPPED
> [INFO] WSO2 Carbon - Patch releases - features - Aggregator Module  SKIPPED
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 12:59.051s
> [INFO] Finished at: Tue Aug 28 09:55:47 IST 2012
> [INFO] Final Memory: 195M/414M
> [INFO]
> 
> [ERROR] Failed to execute goal on project
> org.wso2.carbon.identity.authenticator.iwa.ui.feature: Could not resolve
> dependencies for project
> org.wso2.carbon:org.wso2.carbon.identity.authenticator.iwa.ui.feature:pom:4.0.1:
> Failed to collect dependencies for
> [org.wso2.carbon:org.wso2.carbon.identity.authenticator.iwa.ui:jar:4.0.1
> (compile),
> org.wso2.carbon:org.wso2.carbon.identity.authenticator.iwa.stub:jar:4.0.1
> (compile)]: Failed to read artifact descriptor for
> org.wso2.carbon:org.wso2.carbon.identity.authenticator.iwa.ui:jar:4.0.1:
> Could not find artifact org.wso2.carbon:iwa-authenticator:pom:4.0.1 in
> wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/) ->
> [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/DependencyResolutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn  -rf
> :org.wso2.carbon.identity.authenticator.iwa.ui.feature
>
>
> 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
>
>


-- 
*Kishanthan Thangarajah*
Software Engineer,
Development Technologies Team,
WSO2, Inc.
lean.enterprise.middleware

Mobile - +94773426635
Blog - *http://kishanthan.wordpress.com*
Twitter - *http://twitter.com/kishanthan*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Products_4.0.0 > #93 has FAILED. Change made by 16 authors.

2012-08-28 Thread Bamboo 

---
WSO2 Carbon BRANCH > Products_4.0.0 > #93 failed.
---
Code has been updated by hasini, krishantha, nuwanw, subash, ranga, chethiya, 
eranda, janaka, tharindu, amani, prabatha, ajanthan, supunm, ajithn, reka, 
lakmali.
No failed tests found, a possible compilation error.

http://wso2.org/bamboo/browse/WCB001-PRO000-93/

-
Currently Responsible
-

No one is responsible for fixing this build.



--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.



--
Code Changes
--
tharindu (140060):

>fix cassandra version

ajithn (140088):

>fixed possible NPE

supunm (140043):

>logic improvements



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Improve Carbon Studio features according to JAX-WS/JAX-RS changes.

2012-08-28 Thread Sagara Gunathunga 
On Tue, Aug 28, 2012 at 4:27 PM, Melan Nimesh  wrote:
> Hi Sagara,
>
> Please find my comments inline.
>
> On Fri, Aug 24, 2012 at 10:01 PM, Sagara Gunathunga  wrote:
>>
>> Hi Tooling team,
>>
>> Since AS 5.0.0 will provide 1st class support for CXF we need to
>> improve Carbon Studio features as well.
>>
>> Following 3 improvements are very important and does not require much
>> effort, better if we can include them into next few milestone
>> releases.
>>
>> 1. https://wso2.org/jira/browse/TOOLS-1255
>
> This feature is already available. it is available as separate class wizard.
> you can see it by right clicking on a project with  JAX-WS nature and go to
> New -> JAX-WS Service Class.  and it capable of adding multiple service
> class to a project.

I have noticed above separated wizard  but the idea here is we should
provide JAX-RS/JAX-WS wizards which are identical to current Axis2
service wizard. In current Axis2 wizard in a single wizard you can
create your web service class + valid service.xml file and end of the
wizard user have complete  Axis2 service. In same fashion we need to
improve JAX-WS/JAX-RS wizard so that it add service class and meta
data entries within the same wizard. If the user want to add more
service classes he may use above mentioned wizard.

>
>
>>
>>
>> 2. https://wso2.org/jira/browse/TOOLS-1256
>
> This feature is already available.  it is also available as separate class
> wizard and same as above.
>
>>
>>
>> 3. https://wso2.org/jira/browse/TOOLS-1257
>
> Is it good idea to ship a CXF runtime with DevStudio? it will increase size
> of devStudio distribution by 50 MB.

I can agree with you about the concern about the size CXF framework.
Since we ship CXF as the default JAX-WS/JAX-RS provider we need to
find a approach to integrate CXF tools with our DevStudio.


and is there any way to generation web
> service stub from CXF wsdl2java tool? Seems like it's only support client
> stub generation.

There are  -server and  -client options available, please refer
http://cxf.apache.org/docs/wsdl-to-java.html

Thanks !


>
>
>>
>>
>>
>>
>> Also following are not urgent as above but we need to add them into
>> tooling road map.
>>
>> 4. https://wso2.org/jira/browse/TOOLS-1259
>> 5. https://wso2.org/jira/browse/TOOLS-1260
>
> +1, I am looking into this
>
>>
>>
>>
>>
>>
>> Thanks !
>>
>> --
>> Sagara Gunathunga
>>
>> Technical Lead; WSO2, Inc.;  http://wso2.com
>> V.P Apache Web Services ;  http://ws.apache.org/
>> Blog ;  http://ssagara.blogspot.com
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
> Thanks,
> Melan
>



-- 
Sagara Gunathunga

Technical Lead; WSO2, Inc.;  http://wso2.com
V.P Apache Web Services ;  http://ws.apache.org/
Blog ;  http://ssagara.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Improve Carbon Studio features according to JAX-WS/JAX-RS changes.

2012-08-28 Thread Melan Nimesh 
Hi Sagara,

Please find my comments inline.

On Fri, Aug 24, 2012 at 10:01 PM, Sagara Gunathunga  wrote:

> Hi Tooling team,
>
> Since AS 5.0.0 will provide 1st class support for CXF we need to
> improve Carbon Studio features as well.
>
> Following 3 improvements are very important and does not require much
> effort, better if we can include them into next few milestone
> releases.
>
> 1. https://wso2.org/jira/browse/TOOLS-1255

This feature is already available. it
is available as separate class wizard. you can see it by right clicking on
a project with  JAX-WS nature and go to New -> JAX-WS Service Class.  and
it capable of adding multiple service class to a project.



>
> 2. https://wso2.org/jira/browse/TOOLS-1256

This feature is already available.  it is
also available as separate class wizard and same as above.


>
> 3. https://wso2.org/jira/browse/TOOLS-1257

Is it good idea to ship a CXF runtime with DevStudio? it will increase size
of devStudio distribution by 50 MB. and is there any way to generation web
service stub from CXF wsdl2java tool? Seems like it's only support client
stub generation.



>
>
>
> Also following are not urgent as above but we need to add them into
> tooling road map.
>
> 4. https://wso2.org/jira/browse/TOOLS-1259
> 5. https://wso2.org/jira/browse/TOOLS-1260

+1, I am looking into this


>
>
>
>
> Thanks !
>
> --
> Sagara Gunathunga
>
> Technical Lead; WSO2, Inc.;  http://wso2.com
> V.P Apache Web Services ;  http://ws.apache.org/
> Blog ;  http://ssagara.blogspot.com
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev


Thanks,
Melan
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Deploying Carbon bundles in Geronimo

2012-08-28 Thread Dileepa Jayakody 
Hi All,

After having problems with osgi httpservice in carbon bundle deployment in
Geronimo, I tried out the secondary option of running carbon in Geronimo in
web-app mode.

However when deploying carbon web app I came across the below JNDI issue
[2];
 Caused by: javax.naming.NoInitialContextException: Unable to determine
caller's BundleContext
at
org.apache.aries.jndi.OSGiInitialContextFactoryBuilder.getInitialContext(OSGiInitialContextFactoryBuilder.java:49)

I think this is related to the bug in aries.jndi 0.3.0 reported here [1].
Geronimo 3 uses aries v0.3.0 bundles. I will further look into this and get
this resolved.

Thanks,
Dileepa

[1] https://issues.apache.org/jira/browse/ARIES-554

[2]
 Loading crbn[2012-08-28
10:57:41,739] ERROR {org.wso2.carbon.ndatasource.core.DataSourceRepository}
-  Error in registering data source: WSO2_CARBON_DB - Error in creating
JNDI subcontext 'javax.naming.InitialContext@20828fe4/jdbc: Unable to
determine caller's BundleContext
org.wso2.carbon.ndatasource.common.DataSourceException: Error in creating
JNDI subcontext 'javax.naming.InitialContext@20828fe4/jdbc: Unable to
determine caller's BundleContext
at
org.wso2.carbon.ndatasource.core.DataSourceRepository.checkAndCreateJNDISubContexts(DataSourceRepository.java:243)
at
org.wso2.carbon.ndatasource.core.DataSourceRepository.registerJNDI(DataSourceRepository.java:268)
at
org.wso2.carbon.ndatasource.core.DataSourceRepository.registerDataSource(DataSourceRepository.java:389)
at
org.wso2.carbon.ndatasource.core.DataSourceRepository.addDataSource(DataSourceRepository.java:485)
at
org.wso2.carbon.ndatasource.core.DataSourceManager.initSystemDataSource(DataSourceManager.java:158)
at
org.wso2.carbon.ndatasource.core.DataSourceManager.initSystemDataSources(DataSourceManager.java:130)
at
org.wso2.carbon.ndatasource.core.internal.DataSourceServiceComponent.initSystemDataSources(DataSourceServiceComponent.java:168)
at
org.wso2.carbon.ndatasource.core.internal.DataSourceServiceComponent.setSecretCallbackHandlerService(DataSourceServiceComponent.java:154)
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.ComponentReference.bind(ComponentReference.java:367)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.bindReference(ServiceComponentProp.java:430)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.bind(ServiceComponentProp.java:218)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:344)
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.securevault.internal.SecretManagerInitializerComponent.activate(SecretManagerInitializerComponent.java:48)
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.m

[Dev] Build broken - Andes

2012-08-28 Thread Samisa Abeysinghe 
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 13.137s
[INFO] Finished at: Tue Aug 28 14:29:58 IST 2012
[INFO] Final Memory: 171M/1162M
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-antrun-plugin:1.6:run (compile) on project
andes: Execution compile of goal
org.apache.maven.plugins:maven-antrun-plugin:1.6:run
failed: A required class was missing while executing
org.apache.maven.plugins:maven-antrun-plugin:1.6:run:
org/apache/tools/ant/launch/Locator
[ERROR] -
[ERROR] realm =plugin>org.apache.maven.plugins:maven-antrun-plugin:1.6
[ERROR] strategy =
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] =
file:/C:/Users/Samisa%20Abeysinghe/.m2/repository/org/apache/maven/plugins/maven-antrun-plugin/1.6/maven-antrun-plugin-1.6.jar
[ERROR] urls[1] =
file:/C:/Users/Samisa%20Abeysinghe/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.1/plexus-interpolation-1.1.jar
[ERROR] urls[2] =
file:/C:/Users/Samisa%20Abeysinghe/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
[ERROR] urls[3] =
file:/C:/Users/Samisa%20Abeysinghe/.m2/repository/org/codehaus/plexus/plexus-utils/2.0.5/plexus-utils-2.0.5.jar
[ERROR] urls[4] =
file:/C:/Users/Samisa%20Abeysinghe/.m2/repository/org/apache/ant/ant-nodeps/1.8.1/ant-nodeps-1.8.1.jar
[ERROR] urls[5] =
file:/C:/Users/Samisa%20Abeysinghe/.m2/repository/org/apache/ant/ant/1.8.1/ant-1.8.1.jar
[ERROR] urls[6] =
file:/C:/Users/Samisa%20Abeysinghe/.m2/repository/org/apache/ant/ant-launcher/1.8.1/ant-launcher-1.8.1.jar
[ERROR] Number of foreign imports: 1
[ERROR] import: Entry[import  from realm
ClassRealm[project>org.wso2.carbon:platform-patch-releases:4.0.1, parent:
ClassRealm[maven.api, parent: null]]]
[ERROR]
[ERROR] -:
org.apache.tools.ant.launch.Locator
[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/PluginContainerException

Thanks,
Samisa...

Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Bamboo-Build] WSO2 Carbon BRANCH > Kernel_4.0.0 > #144 was SUCCESSFUL. Change made by azeez.

2012-08-28 Thread Bamboo 

---
WSO2 Carbon BRANCH > Kernel_4.0.0 > #144 was successful.
---
Code has been updated by azeez.

http://wso2.org/bamboo/browse/WCB001-KER000-144/




--
Code Changes
--
azeez (140057):

>Support for local transport
>



--
This message is automatically generated by Atlassian Bamboo___
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

2012-08-28 Thread Anjana Fernando 
Hi,

On Tue, Aug 28, 2012 at 11:33 AM, Sagara Gunathunga  wrote:

>
> I don't think shipping Greg with  jaxb version 2.1.7 is a acceptable
> solution we need to ship compatible set of libs for whole platform
> otherwise this make lot of unwanted issues when installing various
> features.  What I think is porting ndatasource in to  jaxb version
> (2.2.5 2.2.6) is the only solution here.
>
>
We have to understand the actual problem here, there is no such thing as
porting the ndatasource implementation to a new version. There is nothing
to port, it uses standard annotations and libs, and those hasn't changed.
It is a class loading issue we are having with the version upgrade, where
some classes, in the ndatasources error case, "JAXBContext", happens to be
that it's implementation is loaded from the JDK and it's API interface is
loaded from the OSGi bundle, so results in a classes not similar and a
"instance of" expressions fails in the JAXB code, which is the actual error
you get from ndatasources. So it is not only an issue for ndatasources, but
a generic error you will get in any place you use JAXB. So the bottom line
is, we have to find the actual root cause for these class loading issues
and fix those, then we should be able to just upgrade it to the latest
version and go from there.

Cheers,
Anjana.


> Thanks !
>
> >
> > 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
> >
>
>
>
> --
> Sagara Gunathunga
>
> Technical Lead; WSO2, Inc.;  http://wso2.com
> V.P Apache Web Services ;  http://ws.apache.org/
> Blog ;  http://ssagara.blogspot.com
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>



-- 
*Anjana Fernando*
Associate Technical Lead
WSO2 Inc. | http://wso2.com
lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Invoking WSO2 Carbon admin services using BPEL.

2012-08-28 Thread Thilini Ishaka 
Hi,

This can be done with BPS 3.0.0. Try out with alpha or beta released pack.

You have to add relevant http headers basically the username and password
via unified endpoints.
A sample configuration (.epr) is given below.


SInvokeEPR

 *   adminx *
*adminy *



FYI: [1] & [2]
[1]
https://svn.wso2.org/repos/wso2/carbon/platform/trunk/products/appfactory/modules/bpels/UserCreation/

[2]
https://svn.wso2.org/repos/wso2/carbon/platform/trunk/products/appfactory/modules/distribution/product/resources/appfactory/endpoints/UserRegistrationService.epr


Hope this helps.

Thanks
Thilini
On Tue, Aug 28, 2012 at 12:31 PM, Sameera Jayasoma  wrote:

> Hi Devs,
>
> If I put the requirement in another words, how can I add or read HTTP
> header  in a BPEL process. I don't think, BPEL language supports this as
> this is a transport dependent operation.
>
> I've implemented this in 3.2.* release using proxy services for each admin
> service.  These proxy services set the cookie value and invoke admin
> services. Once you logged in to the AuthenticationAdmin service you get a
> authenticated cookie and you can use this cookie value can be used for all
> subsequent invokations.
>
>1. BPEL process invoke the login method in the
>AuthenticationAdminProxy service which in turn invokes the back-end
>server's AuthenticationAdmin service. On the return path, this proxy
>service retrive the authenticated cookie and sent to BPEL as value in the
>SOAP message so the BPEL can save this value in a variable.
>2. For all the subsequent requests from the BPEL process, it send this
>cookie to the corresponding proxy services. These proxy services set the
>cookie as a HTTP header and invoke the back-end service.
>
> This is kinda hacky solution. But we couldn't find a proper solution at
> that time.  I would like to know whether we can do this properly in latest
> release. Please let me know.
>
> Thanks,
> Sameera.
>
> --
> Sameera Jayasoma
> Senior Technical Lead
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com
> blog: http://tech.jayasoma.org
>
> Lean . Enterprise . Middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Thilini Ishaka
WSO2 Inc. http://wso2.com*
*bolg: thiliniishaka.blogspot.com*
*linkedin: http://lk.linkedin.com/in/thiliniishaka*
*twitter: https://twitter.com/#!/ThiliniIsh*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Invoking WSO2 Carbon admin services using BPEL.

2012-08-28 Thread Sameera Jayasoma 
Hi Devs,

If I put the requirement in another words, how can I add or read HTTP
header  in a BPEL process. I don't think, BPEL language supports this as
this is a transport dependent operation.

I've implemented this in 3.2.* release using proxy services for each admin
service.  These proxy services set the cookie value and invoke admin
services. Once you logged in to the AuthenticationAdmin service you get a
authenticated cookie and you can use this cookie value can be used for all
subsequent invokations.

   1. BPEL process invoke the login method in the AuthenticationAdminProxy
   service which in turn invokes the back-end server's AuthenticationAdmin
   service. On the return path, this proxy service retrive the authenticated
   cookie and sent to BPEL as value in the SOAP message so the BPEL can save
   this value in a variable.
   2. For all the subsequent requests from the BPEL process, it send this
   cookie to the corresponding proxy services. These proxy services set the
   cookie as a HTTP header and invoke the back-end service.

This is kinda hacky solution. But we couldn't find a proper solution at
that time.  I would like to know whether we can do this properly in latest
release. Please let me know.

Thanks,
Sameera.

-- 
Sameera Jayasoma
Senior Technical Lead

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://tech.jayasoma.org

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev