from:"Lakmali Baminiwatta"

Re: [Carbon-dev] Issue in implementing JPA support on ESB Smooks Mediator

2012-03-05 Thread Lakmali Baminiwatta

Hi all,

Thanks all for the suggestions. I tried out what Hiranya has mentioned but
it doesn't solve the problem. Will further look into the options suggested
by Pradeep to get this work.

Thanks,
Lakmali

On Mon, Mar 5, 2012 at 7:03 PM, Pradeep Fernando  wrote:

> Hi all,
>
> The JPA uses provider architecture. There it loads providers using java
> spi mechanism. The problem is with unique classLoaders, this does not work
> in OSGi. (earlier we used to load them all using
> application/carbon-bootstrap classLoader by placing them in outer lib)
>
> two viable options.
>
> 1. go for OSGi JPA implementation. (eclipse gemini, apache aries are two
> impls)
> 2. use fragmenting mechanism to laod bundles using the same classLoader.
>
>
> Any other suggestions ?
>
> --Pradeep
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Lakmali Baminiwatta*
*
Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware

*
*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Issue in implementing JPA support on ESB Smooks Mediator

2012-03-05 Thread Lakmali Baminiwatta

Hi all,

I am working on extending smooks functionality on WSO2 ESB Smooks Mediator.
When implementing JPA support with hibernate on smooks mediator, I am
facing an issue of not being able to find the persistence provider. I
placed the persistence.xml file inside a jar which contains the entity
classes (as META-INF/persistence.xml). I added that jar to ESB
repository/components/lib location. Also added all the other required jars
(hibernate-entitymanager, persistence-api, etc) to the same location. But
when executing a sample service I get this error as,

javax.persistence.PersistenceException: No Persistence provider for
EntityManager named db
at
javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:89)
at
javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:60)

It seems that although hibernate-entitymanager jar is added to the
repository/components/lib Smooks can not find the Persistence Provider.

This similar problem had been encountered sometime back and provided with a
solution on a support issue [1]. There an additional script had been added
to wso2server.sh in order to add all the jars inside  repository/components/lib
to the classpath. As the client has responded the solution has worked. But
it seems that solution doesn't work in trunk now. We exactly do not know
how that solution worked at that time and why isn't that working now.

So I appreciate any assistance, comments regarding this issue.

Also I came to know that WSO2 BPS has implemented JPA functionality and I
would like to know how you have been supported this ?


[1] 
https://support.wso2.com/jira/browse/THOMREUTDEVSPRT-9


Thank you!

regards,
Lakmali
*
*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Built is still broken

2012-02-27 Thread Lakmali Baminiwatta

Hi,

I was building bam2 in trunk. I had to explicitly build several
service-stubs, components, features which are not included in trunk build
in order to build bam2. So shouldn't those added with trunk build?

regards,
Lakmali

On Tue, Feb 28, 2012 at 10:12 AM, Asela Pathberiya  wrote:

>
>
> On Tue, Feb 28, 2012 at 8:20 AM, Sameera Jayasoma wrote:
>
>> Hi Samisa,
>>
>> Here is the current state of the build.
>>
>> Compilation Failures:
>> * Identity Entitlement component.
>>
>
> This is fixed in r121543
>
> Thanks,
> Asela.
>
>
>>
>> Build failures:
>> * ESB
>>
>> Integration Test Failures:
>> * GS
>> * BAM
>> * DSS
>> * CEP
>> * ESB
>> * BPS
>> * BRS
>> * MB
>> * AS
>>
>> We are working with the respective product teams to fix these issues.
>>
>> Thanks,
>> Sameera.
>>
>> On Mon, Feb 27, 2012 at 12:39 AM, Sameera Jayasoma wrote:
>>
>>>
>>>
>>> On Sun, Feb 26, 2012 at 5:10 PM, Samisa Abeysinghe wrote:
>>>
>>>> A week has gone by after the svn migration and still the platform and
>>>> product builds in Bamboo are badly breaking.
>>>>
>>>> We cannot really release Carbon kernel end of March with builds failing
>>>> at this rate, end of Feb.
>>>>
>>>> This got to be fixed. Now!
>>>>
>>>
>>> +1. The platform and product build was broken over the last week.  But I
>>> could build Carbon Kenel, Platform successfully last Friday. And also I
>>> could build all the product without the integration tests. Yes. That means
>>> build is still broken. We will update this list on the progress of the
>>> builds  by EOD Tomorrow.
>>>
>>> On a side note. Most ( I said most, because there were some failures due
>>> to developer mistakes) of these build brakes happens because of the
>>> following two changes.
>>>
>>> 1) SVN Restructuring.
>>> 2) Tomcat Ossification changes.
>>>
>>> I guess, build brakes due to former are all fixed by now. But latter is
>>> a platform-wide change. We basically changes carbon up side down IMHO. This
>>> change affected the following areas.
>>>
>>> * Carbon server initialization
>>>- Carbon is no longer a Webapp. I.e, Carbon does not run inside an
>>> embedded tomcat instance.
>>>- Carbon is pure OSGi runtime and Tomcat is a bundle in this runtime.
>>> * The way we create and start Tomcat Connectors.
>>>- Hence the port offset mechanism was broken.
>>> * Graceful restart.
>>> * There are lots of changes when it comes to class loading patterns.
>>> * Most of the jars in CARBON_HOME/lib have be moved to the plugins dir
>>> as bundles. We've added some new orbit bundles.
>>>
>>> We had a review of this last Thursday. All of the above tasks were
>>> completed, except the port offset issue. Pradeep was looking into it.
>>>
>>> Now most of the issues we are facing is at the integration test layer.
>>> Because of these changes, we had to update the components, products builds
>>> and integration tests.
>>>
>>> Anyway we should have completed this task last Friday.  As I
>>> said earlier, we will update this thread with the progress of the builds.
>>>
>>> Thanks,
>>> Sameera.
>>>
>>>> Thanks,
>>>> Samisa...
>>>>
>>>> Samisa Abeysinghe
>>>> VP Engineering
>>>> WSO2 Inc.
>>>> http://wso2.com
>>>> http://wso2.org
>>>>
>>>>
>>>> ___
>>>> Carbon-dev mailing list
>>>> Carbon-dev@wso2.org
>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Sameera Jayasoma
>>> Technical Lead and Product Manager, WSO2 Carbon
>>>
>>> WSO2, Inc. (http://wso2.com)
>>> email: same...@wso2.com
>>> blog: http://tech.jayasoma.org
>>>
>>> Lean . Enterprise . Middleware
>>>
>>
>>
>>
>> --
>> Sameera Jayasoma
>> Technical Lead and Product Manager, WSO2 Carbon
>>
>> WSO2, Inc. (http://wso2.com)
>> email: same...@wso2.com
>> blog: http://tech.jayasoma.org
>>
>> Lean . Enterprise . Middleware
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Lakmali Baminiwatta*
*
Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware
mobile:  +94 71 2335936
*
*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Unexpected subelement error in a data service client.

2012-02-23 Thread Lakmali Baminiwatta

>at cu.uci.informatizacion.servicios.personal.Cliente.main(*
> Cliente.java:197*)
>
> Caused by: *java.lang.Exception*: *
> org.apache.axis2.databinding.ADBException*: Unexpected subelement
> Municipio
>
>at
> cu.uci.informatizacion.servicios.personal.PersonalWS2Stub$Municipio$Factory.parse(
> *PersonalWS2Stub.java:25551*)
>
>at
> cu.uci.informatizacion.servicios.personal.PersonalWS2Stub$Persona25$Factory.parse(
> *PersonalWS2Stub.java:13460*)
>
>at
> cu.uci.informatizacion.servicios.personal.PersonalWS2Stub$Personas24$Factory.parse(
> *PersonalWS2Stub.java:28114*)
>
>at
> cu.uci.informatizacion.servicios.personal.PersonalWS2Stub$Personas26$Factory.parse(
> *PersonalWS2Stub.java:25868*)
>
>    at
> cu.uci.informatizacion.servicios.personal.PersonalWS2Stub.fromOM(*
> PersonalWS2Stub.java:39191*)
>
>... 3 more
>
> Caused by: *org.apache.axis2.databinding.ADBException*: Unexpected
> subelement Municipio
>
>at
> cu.uci.informatizacion.servicios.personal.PersonalWS2Stub$Municipio$Factory.parse(
> *PersonalWS2Stub.java:25493*)
>
>... 7 more
>
> ** **
>
> ** **
>
> ** **
>
> Any idea? The problem are in the Stub client class.
>
> ** **
>
> Saludos,
>
> Ing. Jorge Infante Osorio.
>
> J´Dpto Soluciones SOA.
>
> CDAE.
>
> Fac. 5.
>
> UCI.
>
> ** **
>
>   <http://www.antiterroristas.cu/>
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Lakmali Baminiwatta*
*
Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware
mobile:  +94 71 2335936
*
*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] [Bamboo-Build] Carbon-Kernel > Graphite-Build > #29 has FAILED. Change made by 6 authors.

2012-02-16 Thread Lakmali Baminiwatta

Hi,

Fixed the issue.

Thanks,
Lakmali

On Thu, Feb 16, 2012 at 8:37 PM, Shammi Jayasinghe  wrote:

> Hi Lakmali,
>
>  This build failure is due to a problem in stratos.deployment.feature.
> Please have a look.
>
> Thanks
> Shammi
>
>
> [ERROR] The build could not read 1 project -> [Help 1] 16-Feb-2012
> 06:36:15 [ERROR]   16-Feb-2012 06:36:15 [ERROR]   The project
> org.wso2.carbon:org.wso2.carbon.stratos.deployment.feature:1.1.0-SNAPSHOT
> (/home/bamboo/Bamboo-3.4/source-repository/build-dir/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1/features/stratos/deployment/pom.xml)
> has 1 error 16-Feb-2012 06:36:15 [ERROR] Non-resolvable parent POM:
> Could not find artifact org.wso2.carbon:common-feature:pom:1.1.0-SNAPSHOT
> and 'parent.relativePath' points at wrong local POM @ line 22, column 12 ->
> [Help 2] 16-Feb-2012 06:36:15 [ERROR] 16-Feb-2012 06:36:15 [ERROR] To see
> the full stack trace of the errors, re-run Maven with the -e 
> switch.16-Feb-2012 06:36:15[ERROR]
> Re-run Maven using the -X switch to enable full debug logging. 16-Feb-2012
> 06:36:15 [ERROR]
> On Thu, Feb 16, 2012 at 8:07 PM, Bamboo  wrote:
>
>>   [image: Failed]  
>> Carbon-Kernel<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL/>›
>> Graphite-Build<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD/>›
>> #29<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-29/>
>> failed
>>
>> Code has been updated by 
>> pradeeban<http://builder4.us1.wso2.org:/bamboo/browse/author/pradeeban>,
>> kasunw <http://builder4.us1.wso2.org:/bamboo/browse/author/kasunw>,
>> chamara <http://builder4.us1.wso2.org:/bamboo/browse/author/chamara>,
>> achala <http://builder4.us1.wso2.org:/bamboo/browse/author/achala>,
>> ajithn <http://builder4.us1.wso2.org:/bamboo/browse/author/ajithn>,
>> buddhikac<http://builder4.us1.wso2.org:/bamboo/browse/author/buddhikac>
>> .
>>
>> No failed tests found, a possible compilation error.
>>Failing 
>> Jobs<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-29/>
>> Job
>> Duration Tests[image: Failed]  Default 
>> Job<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-29/>
>>  (Default
>> Stage)  1 minute  No tests found  
>> Logs<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-29/log>|
>> Artifacts<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-29/artifact>
>>  Code
>> Changes<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-29/commit/>
>>   View
>> all 8 code 
>> changes<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-29/commit/>
>> chamara <http://builder4.us1.wso2.org:/bamboo/browse/author/chamara>
>> Synapse configuration command class used to ravana test  120894
>> ajithn<http://builder4.us1.wso2.org:/bamboo/browse/author/ajithn>
>> Adding -i interactive flag for check-in client  120893
>> ajithn<http://builder4.us1.wso2.org:/bamboo/browse/author/ajithn>
>> Adding -i interactive flag for check-in client  120891   5 more 
>> changes…<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-29/commit>
>>  View
>> Online<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-29>
>> | Add 
>> Comments<http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-29?commentMode=true>
>>
>> This message was sent by Atlassian 
>> Bamboo<http://builder4.us1.wso2.org:/bamboo>
>> .
>>
>> If you wish to stop receiving these emails edit your user 
>> profile<http://builder4.us1.wso2.org:/bamboo/profile/userNotifications.action>or
>>  notify
>> your 
>> administrator<http://builder4.us1.wso2.org:/bamboo/viewAdministrators.action>
>> .
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Best Regards,*
>
> Shammi Jayasinghe*
> Senior Software Engineer; WSO2, Inc.; http://wso2.com,
> mobile: +94 71 4493085
>
>
>


-- 
Lakmali Baminiwatta*
*
Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware
mobile:  +94 71 2335936
*
*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] WSO2 Committers += Lakmali

2012-02-06 Thread Lakmali Baminiwatta

Thanks! It is my great pleasure to become a WSO2 Committer and will give my
best contribution in future.

Thanks,
Lakmali

On Mon, Feb 6, 2012 at 4:57 PM, Anjana Fernando  wrote:

> Hi Lakmali,
>
> Congratulations and welcome aboard as a WSO2 Committer. Keep up the good
> work.
>
> Cheers,
> Anjana.
>
> --
> *Anjana Fernando*
> Senior Software Engineer
> WSO2 Inc. | http://wso2.com
> lean . enterprise . middleware
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Lakmali Baminiwatta*
*
Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware
mobile:  +94 71 2335936
*
*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Issue in ESB Smooks Mediator Streaming Improvements

2012-01-17 Thread Lakmali Baminiwatta

Hi,

I am working on enabling streaming xml events from OMElement inside ESB
Smooks Mediator. This is to process large messages through Smooks mediator.
Previously Smooks mediator used to build the message envelop as
*synCtx.getEnvelope().build()
*(synCtx is the MessageContext ) before processing the message. Since it
builds the element inside memory, I removed that step.

I used to test the new streaming implementation with two scenarios.

Scenario 1 :- Input message is read from the VFS transport, and streamed to
Smooks mediator. Inside that message is processed by smooks and child
elements from the MessageContext is detached & transformed element it added
to MessageContext. This worked successfully. The ESB configuration sequence
is,









Scenario 2 :- A proxy service to a DSS endpoint and its response is
processed by smooks mediator in outSequence.

   http://localhost:9765/services/OrderDetails"; />


   


   
   
  

After smooks processing the message, the child elements from the
MessageContext envelop is detached and new transformed message is added.
But when iterating through the MessageContext and calling next(),
OMException is thrown as follows.

*org.apache.axiom.om.OMException
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:212)
at
org.apache.axiom.soap.impl.llom.SOAPBodyImpl.buildNext(SOAPBodyImpl.java:171)
at
org.apache.axiom.om.impl.llom.OMNodeImpl.getNextOMSibling(OMNodeImpl.java:122)
at
org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementImpl.java:343)
at
org.apache.axiom.om.impl.traverse.OMChildElementIterator.next(OMChildElementIterator.java:104)
at
org.wso2.carbon.mediator.transform.Output.setXMLPayload(Output.java:208)
at org.wso2.carbon.mediator.transform.Output.process(Output.java:84)
at
org.wso2.carbon.mediator.transform.SmooksMediator.mediate(SmooksMediator.java:94)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:60)
at
org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:114)
at
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:219)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:370)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:160)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)
at
org.apache.synapse.transport.nhttp.ClientWorker.run(ClientWorker.java:275)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:173)
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)*

The issue is why only the second scenario can not access the MessageContext
after smooks has processed the message. Adding back the
*synCtx.getEnvelope().build()
*solves this issue, but large messages can not be processed that way. Can
anybody kindly look into this issue and explain why is it required to build
up the message?

Thanks,
Lakmali


-- 
Lakmali Baminiwatta*
*
Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware
mobile:  +94 71 2335936
*
*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] XA Transactions

2011-12-16 Thread Lakmali Baminiwatta

ork.eventmgr.EventManager$EventThread.run(EventManage
> r.java:330)
> [2011-12-15 16:44:27,225]  INFO - EventBrokerBuilderDS Successfully
> registered the event broker
>
> Saludos,
> Ing. Jorge Infante Osorio.
> J´Dpto Soluciones SOA.
> CDAE.
> Fac. 5.
> UCI.
>
> De: Anjana Fernando [mailto:anj...@wso2.com]
> Enviado el: lunes, 12 de diciembre de 2011 4:22
> Para: Jorge Infante Osorio
> CC: carbon-dev@wso2.org
> Asunto: Re: XA Transactions
>
> Hi Jorge,
>
> I'm a bit busy with some work now, I will check it out later, but I've done
> this in some way earlier, maybe we'd the server.xml in earlier Carbon
> versions, I'm not totally sure, you can google around a bit and find the
> possibilities of adding a data source in Tomcat. In case I find the
> solution
> first, I will give an update.
>
> Cheers,
> Anjana.
> On Mon, Dec 12, 2011 at 12:12 AM, Jorge Infante Osorio 
> wrote:
> Hi Anjana.
>
> To work with transactions in Tomcat, I need to work with the server.xml and
> context.xml files.
>
> I found context.xml under [CARBON_HOME]\lib\tomcat\conf\ but I don´t find
> server.xml. Following an Afkham  message, I see that carbon don't support
> server.xml config yet.
>
> What can I do in the case I cannot use server.xml?
>
>
> Another idea: deploy ESB inside Apache Tomcat?? For me it´s not so good
> because I want to use ESB standalone.
>
> Thanks
> Saludos,
> Ing. Jorge Infante Osorio.
> J´Dpto Soluciones SOA.
> CDAE.
> Fac. 5.
> UCI.
>
> De: Anjana Fernando [mailto:anj...@wso2.com]
> Enviado el: domingo, 11 de diciembre de 2011 2:38
> Para: Jorge Infante Osorio
> CC: carbon-dev@wso2.org
> Asunto: Re: XA Transactions
> Hi Jorge,
> On Sun, Dec 11, 2011 at 12:53 PM, Jorge Infante Osorio 
> wrote:
> My bad. I forgot to check that option  :-D  thanks, it work now.
>
> Can I do the same config with the DBReport in ESB? I´m try to figure out
> how
> to do a transaction between 3 DBReport mediators.
>
> Good to hear it works! .. as for DBReport, I'm afraid you can't use the
> same
> configuration, for this, you may have to dig into the Tomcat configurations
> and create an XA data source there. I haven't personally tested that
> scenario that much. But we are also planning to add the XA data source
> support to the data sources component we have, so we can create global XA
> data sources from there, which can be used by anywhere.
>
> Cheers,
> Anjana.
>
>
> Saludos,
> Ing. Jorge Infante Osorio.
> J´Dpto Soluciones SOA.
> CDAE.
> Fac. 5.
> UCI.
>
> De: Anjana Fernando [mailto:anj...@wso2.com]
> Enviado el: domingo, 11 de diciembre de 2011 1:36
> Para: Jorge Infante Osorio; carbon-dev
> Asunto: Re: XA Transactions
>
> Hi,
>
> For the error you just mentioned, as the error message mentions,
> distributed
> transactions must be enabled in the data service to allow usage of XA data
> sources. This settings is there in the first page of the wizard, where you
> can check "Enable Distributed Transactions" check box, or else in XML edit,
> in the initial "data" XML element, you can set the attribute, enableDTP to
> true, e.g.   ...
>
> Cheers,
> Anjana.
>
>
>
> Fin a la injusticia, LIBERTAD AHORA A NUESTROS CINCO COMPATRIOTAS QUE SE
> ENCUENTRAN INJUSTAMENTE EN PRISIONES DE LOS EEUU!
> http://www.antiterroristas.cu
> http://justiciaparaloscinco.wordpress.com
>
>
>
> --
> Anjana Fernando
> Senior Software Engineer
> WSO2 Inc. | http://wso2.com
> lean . enterprise . middleware
>
>
>
> Fin a la injusticia, LIBERTAD AHORA A NUESTROS CINCO COMPATRIOTAS QUE SE
> ENCUENTRAN INJUSTAMENTE EN PRISIONES DE LOS EEUU!
> http://www.antiterroristas.cu
> http://justiciaparaloscinco.wordpress.com
>
>
>
> --
> Anjana Fernando
> Senior Software Engineer
> WSO2 Inc. | http://wso2.com
> lean . enterprise . middleware
>
>
>
> Fin a la injusticia, LIBERTAD AHORA A NUESTROS CINCO COMPATRIOTAS QUE SE
> ENCUENTRAN INJUSTAMENTE EN PRISIONES DE LOS EEUU!
> http://www.antiterroristas.cu
> http://justiciaparaloscinco.wordpress.com
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>



-- 
*Lakmali Baminiwatta
*
*Software Engineer
*
*WSO2, Inc.: http://wso2.com*
*lean.enterprise.middleware*

*mobile:  +94 71 2335936*
*
*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] List down the product builds which are compatible with maven3

2011-12-09 Thread Lakmali Baminiwatta

t;>> I will work on fixing the load balancer profile, since that is
>>>>>>>>>> outdated in trunk.
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>> Pradeeban.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Thu, Dec 8, 2011 at 3:29 PM, Thilina Buddhika <
>>>>>>>>>> thili...@wso2.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> IS can be built with Maven3 without any issue.
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>> Thilina
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Thu, Dec 8, 2011 at 3:14 PM, Suhothayan Sriskandarajah <
>>>>>>>>>>> s...@wso2.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> CEP can be built with maven 3
>>>>>>>>>>>> I built revision 117070
>>>>>>>>>>>>
>>>>>>>>>>>> Regards
>>>>>>>>>>>> Suho
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Thu, Dec 8, 2011 at 3:09 PM, Waruna Ranasinghe <
>>>>>>>>>>>> war...@wso2.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> BPS can be built with Maven 3.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>> Waruna
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Thu, Dec 8, 2011 at 2:23 PM, Pradeep Fernando <
>>>>>>>>>>>>> prad...@wso2.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> correction: PMs or team member
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> thanks,
>>>>>>>>>>>>>> --Pradeep
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ___
>>>>>>>>>>>>>> Carbon-dev mailing list
>>>>>>>>>>>>>> Carbon-dev@wso2.org
>>>>>>>>>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>>
>>>>>>>>>>>>> -
>>>>>>>>>>>>> Waruna Ranasinghe
>>>>>>>>>>>>> Senior Software Engineer, WSO2
>>>>>>>>>>>>>
>>>>>>>>>>>>> Mobile: SL +94 724 318285
>>>>>>>>>>>>> BLOG: http://warunapw.blogspot.com
>>>>>>>>>>>>>
>>>>>>>>>>>>> www.wso2.com - "Lean . Enterprise . Middleware"
>>>>>>>>>>>>>
>>>>>>>>>>>>> ___
>>>>>>>>>>>>> Carbon-dev mailing list
>>>>>>>>>>>>> Carbon-dev@wso2.org
>>>>>>>>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> ___
>>>>>>>>>>>> Carbon-dev mailing list
>>>>>>>>>>>> Carbon-dev@wso2.org
>>>>>>>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Thilina Buddhika
>>>>>>>>>>> Associate Technical Lead
>>>>>>>>>>> WSO2 Inc. ; http://wso2.com
>>>>>>>>>>> lean . enterprise . middleware
>>>>>>>>>>>
>>>>>>>>>>> phone : +94 77 44 88 727
>>>>>>>>>>> blog : http://blog.thilinamb.com
>>>>>>>>>>>
>>>>>>>>>>> ___
>>>>>>>>>>> Carbon-dev mailing list
>>>>>>>>>>> Carbon-dev@wso2.org
>>>>>>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Kathiravelu Pradeeban.
>>>>>>>>>> Software Engineer.
>>>>>>>>>> WSO2 Inc.
>>>>>>>>>>
>>>>>>>>>> Blog: [Llovizna] http://kkpradeeban.blogspot.com/
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ___
>>>>>>>>>> Carbon-dev mailing list
>>>>>>>>>> Carbon-dev@wso2.org
>>>>>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Thanks,
>>>>>>>>> Shariq.
>>>>>>>>>
>>>>>>>>> ___
>>>>>>>>> Carbon-dev mailing list
>>>>>>>>> Carbon-dev@wso2.org
>>>>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ___
>>>>>>>>> Carbon-dev mailing list
>>>>>>>>> Carbon-dev@wso2.org
>>>>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Best Regards,*
>>>>>>>>
>>>>>>>> Shammi Jayasinghe*
>>>>>>>> Senior Software Engineer; WSO2, Inc.; http://wso2.com,
>>>>>>>> mobile: +94 71 4493085
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ___
>>>>>>>> Carbon-dev mailing list
>>>>>>>> Carbon-dev@wso2.org
>>>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Kathiravelu Pradeeban.
>>>>>>> Software Engineer.
>>>>>>> WSO2 Inc.
>>>>>>>
>>>>>>> Blog: [Llovizna] http://kkpradeeban.blogspot.com/
>>>>>>>
>>>>>>>
>>>>>>> ___
>>>>>>> Carbon-dev mailing list
>>>>>>> Carbon-dev@wso2.org
>>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Regards,
>>>>>>
>>>>>> Tharindu
>>>>>>
>>>>>> blog: http://mackiemathew.com/
>>>>>>
>>>>>>
>>>>>> ___
>>>>>> Carbon-dev mailing list
>>>>>> Carbon-dev@wso2.org
>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Thanks,
>>>>> Shariq.
>>>>>
>>>>>
>>>>> ___
>>>>> Carbon-dev mailing list
>>>>> Carbon-dev@wso2.org
>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Kathiravelu Pradeeban.
>>>> Software Engineer.
>>>> WSO2 Inc.
>>>>
>>>> Blog: [Llovizna] http://kkpradeeban.blogspot.com/
>>>>
>>>>
>>>
>>>
>>> --
>>> Kathiravelu Pradeeban.
>>> Software Engineer.
>>> WSO2 Inc.
>>>
>>> Blog: [Llovizna] http://kkpradeeban.blogspot.com/
>>>
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
*Lakmali Baminiwatta
*
*Software Engineer
*
*WSO2, Inc.: http://wso2.com*
*lean.enterprise.middleware*

*mobile:  +94 71 2335936*
*
*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Blocker issue in DSS 2.6.3

2011-12-06 Thread Lakmali Baminiwatta

Hi Nirodha,

In the "get City by ID" query you have given a result element (ID) which is
not returned by the specified query.  Query only returns Name and
CountryCode, but you have configured the result with ID as well. In that
case the mentioned exception has occurred. Removing ID result element,
makes this service work correctly.

  Select Name, CountryCode from City WHERE ID=:id

 15
 reverse
 true
 100
 50

Thanks

On Wed, Dec 7, 2011 at 12:02 PM, Nirodha Pramod  wrote:

> Hi DSS team,
>
> Services with input parameters does not work. Please have a look.
>
> https://wso2.org/jira/browse/CARBON-11753
>
> --
> *Nirodha Pramod*
> Software Engineer, QA.
> Tel : 0716429078
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>

-- 
*Lakmali Baminiwatta
*
*Software Engineer
*
*WSO2, Inc.: http://wso2.com*
*lean.enterprise.middleware*

*mobile:  +94 71 2335936*
*
*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] ESB Smooks Mediator Improvements

2011-11-18 Thread Lakmali Baminiwatta

Hi,

We have been able to process huge messages in CSV and EDI formats as well
after configuring Smooks with SAX filtering. So I tested ESB Smooks
mediator with huge input messages using the split and route approach. The
huge messages I used to test were XML file (9.6GB), CSV file (9.4GB) and
EDI file (10.5GB). They executed successfully.

Now I am hoping to try out all the other Smooks capabilities inside ESB
Smooks mediator. Also I am planing to check whether we can process a huge
message returned from a service call to a DSS endpoint ( DSS will query a
large database and generate the huge result set)

After that I will write some articles on these scenarios including some ESB
samples to perform these Smooks capabilities.

Thanks!


On Thu, Nov 17, 2011 at 10:18 PM, Paul Fremantle  wrote:

> Awesome!
>
> I think we need to look at all the mediators and whether they can support
> streaming and in which scenarios. We should write a document on this too
> (as well as publishing an article on this specific scenario).
>
> Paul
>
> On 17 November 2011 16:33, Lakmali Baminiwatta  wrote:
>
>> Hi,
>>
>> We have been looking into providing Huge Message Processing capability
>> from ESB Smooks mediatior. For processing Huge messages of GBs it is
>> required to stream the data from the ESB MessageContext to the Smooks
>> filter call. For that Jasintha did a modification to the existing Smooks
>> mediator component. Jasintha's modification was on processing the Smooks
>> input and he had introduced the method [1] to support streaming from the
>> MessageContext.
>>   *
>> *With this modification I tested the ESB Smooks mediator for huge XML
>> messages, but mediator could process maximum of 144MB input file. Then I
>> made a small change to the Jasintha's modification which was passing false
>> value to cache (boolean) argument of the method [1]. There after mediator
>> can process Huge XML Messages of GBs where I had tested a 9.6 GB file.
>> Smooks mediator was given a 9.6GB XML file and Smooks mediator was
>> configured to split and route the message to file destinations and this
>> worked successfully. Currently Smooks supports Huge Message Processing only
>> for XML inputs and for other data inputs like CSV and EDI it is not
>> supported as they get build up on the memory at the transformation. We had
>> been posted a question on this to the Smooks forum and waiting to hear from
>> them.
>>
>> I am using VFS transport to read the input file. When giving XML type
>> input to smooks mediator, I used application/xml as the content type. But
>> now with the modifications to the Smooks mediator component application/xml
>> content type for XML no longer works and gives
>> "org.xml.sax.SAXParseException: Premature end of file" exception. We
>> debugged the component sourcewhile processing an XML and checked the
>> content of the stream generated from the reader object returned by the
>> method [1]. It contained no data.
>>
>> When the content type is used as text/plain both the XML and TEXT input
>> types to Smooks mediator works without any issues.
>>
>> So now the issue is when providing an XML input to Smooks mediator, if
>> application/xml Content type is configured for VFS transport, no data is
>> returned from the stream generated from the method [1].  Any support to
>> resolve this issue is really appreciated.
>>
>> *[1] **ElementHelper.getTextAsStream(**Element element, boolean cache)*from 
>> the Axiom API (
>> *org.apache.axiom.om.util.ElementHelper*).
>>
>> Thanks!
>>
>>
>> --
>> *Lakmali Baminiwatta
>> *
>> *Software Engineer
>> *
>> *WSO2, Inc.: http://wso2.com*
>> *lean.enterprise.middleware*
>>
>> *
>> *
>> *
>> *
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Paul Fremantle
> CTO and Co-Founder, WSO2
> OASIS WS-RX TC Co-chair, VP, Apache Synapse
>
> UK: +44 207 096 0336
> US: +1 646 595 7614
>
> blog: http://pzf.fremantle.org
> twitter.com/pzfreo
> p...@wso2.com
>
> wso2.com Lean Enterprise Middleware
>
> Disclaimer: This communication may contain privileged or other
> confidential information and is intended exclusively for the addressee/s.
> If you are not the intended recipient/s, or believe that you may have
> received this communication in error, please reply to the sender indicating
> that fact and delete the copy you received and in a

[Carbon-dev] ESB Smooks Mediator Improvements

2011-11-17 Thread Lakmali Baminiwatta

Hi,

We have been looking into providing Huge Message Processing capability from
ESB Smooks mediatior. For processing Huge messages of GBs it is required to
stream the data from the ESB MessageContext to the Smooks filter call. For
that Jasintha did a modification to the existing Smooks mediator component.
Jasintha's modification was on processing the Smooks input and he had
introduced the method [1] to support streaming from the MessageContext.
  *
*With this modification I tested the ESB Smooks mediator for huge XML
messages, but mediator could process maximum of 144MB input file. Then I
made a small change to the Jasintha's modification which was passing false
value to cache (boolean) argument of the method [1]. There after mediator
can process Huge XML Messages of GBs where I had tested a 9.6 GB file.
Smooks mediator was given a 9.6GB XML file and Smooks mediator was
configured to split and route the message to file destinations and this
worked successfully. Currently Smooks supports Huge Message Processing only
for XML inputs and for other data inputs like CSV and EDI it is not
supported as they get build up on the memory at the transformation. We had
been posted a question on this to the Smooks forum and waiting to hear from
them.

I am using VFS transport to read the input file. When giving XML type input
to smooks mediator, I used application/xml as the content type. But now
with the modifications to the Smooks mediator component application/xml
content type for XML no longer works and gives
"org.xml.sax.SAXParseException: Premature end of file" exception. We
debugged the component sourcewhile processing an XML and checked the
content of the stream generated from the reader object returned by the
method [1]. It contained no data.

When the content type is used as text/plain both the XML and TEXT input
types to Smooks mediator works without any issues.

So now the issue is when providing an XML input to Smooks mediator, if
application/xml Content type is configured for VFS transport, no data is
returned from the stream generated from the method [1].  Any support to
resolve this issue is really appreciated.

*[1] **ElementHelper.getTextAsStream(**Element element, boolean
cache)*from the Axiom API (
*org.apache.axiom.om.util.ElementHelper*).

Thanks!


-- 
*Lakmali Baminiwatta
*
*Software Engineer
*
*WSO2, Inc.: http://wso2.com*
*lean.enterprise.middleware*

*
*
*
*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] ESB Smooks Support

2011-11-06 Thread Lakmali Baminiwatta

Hi all,

We have been looking into possibility of implementing Smooks as a
standalone feature to support all of Smooks capabilities. But as we have
experienced by trying out their samples and other mentioned features, we
have realized that Smooks has not straightforward mechanisms to address
some of the scenarios such as,

1. We can not define the data source of a Smooks filtering process within
the Smooks configuration. It need to be fed from outside the
configuration.
2. We can not define flow of message filters as to take the output from one
Smooks filter and set as the input of another Smooks filter.

We even communicated with Tom Fennelly, a core developer of Smooks about
those drawbacks, but there were no straightforward solutions to those.

If we are using ESB to execute Smooks capabilities those drawbacks will be
solved. Currently ESB only uses Smooks transformation feature. We have
tried out other Smooks features inside current ESB Smooks mediator and they
worked fine. Also defining a flow of Smooks filters can be done through
ESB. So finally we have identified two features which must be implemented
inside ESB in order to support all of Smooks capabilities from the ESB
Smooks mediator itself.

1. Supporting message streaming to the ESB Smooks mediator other than
keeping the whole message inside the memory. Currently Jasintha had been
looking into this and he has a solution for this.

2. Smooks filter can output a Java Result which is a Java bean and it will
be remain inside the Smooks ExecutionContext. So if we can set that Java
bean result of Smooks mediator to the ESB Message Context, we can use it in
other ESB mediators.

If the above mentioned features are supported from ESB, all of the Smooks
capabilities can be supported from the ESB itself.

Thanks,

Lakmali
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] my photo

2011-10-25 Thread Lakmali Baminiwatta

Please ignore! I have mistaken the sent address! Really sorry!


On Wed, Oct 26, 2011 at 9:53 AM, Lakmali Baminiwatta wrote:

>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Build failure in components/axis2-repo-mgt

2011-09-21 Thread Lakmali Baminiwatta

hi,

Thanks! The compilation error is fixed now..

Lakmali

On Wed, Sep 21, 2011 at 10:02 AM, Muhammed Shariq  wrote:

> Hi,
>
> I changed the modifier of terminateTenantConfigContext method to public
> in TenantAxisUtils.java after a clarifying with Azeez, can you please take
> an svn up at org.wso2.carbon.core and continue building.
>
>
> On Wed, Sep 21, 2011 at 1:04 PM, Muhammed Shariq  wrote:
>
>> Hi,
>>
>> This compilation error occurs due to a recent change done by DimuthuL,
>>
>> 112472   dimuthul private static void
>> terminateTenantConfigContext(ConfigurationContext tenantCfgCtx) {
>>
>> Is there any other method that could be used to terminate the tenants axis
>> config?
>>
>> On Wed, Sep 21, 2011 at 10:01 AM, Lakmali Baminiwatta 
>> wrote:
>>
>>> hi,
>>>
>>> I am getting a compilation error while building Components. Here is the
>>> full error.
>>>
>>> [INFO] BUILD FAILURE
>>> [INFO]
>>> 
>>> [INFO] Total time: 3.653s
>>> [INFO] Finished at: Wed Sep 21 04:29:35 GMT 2011
>>> [INFO] Final Memory: 21M/981M
>>> [INFO]
>>> 
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile
>>> (default-compile) on project org.wso2.carbon.repomanager.axis2: Compilation
>>> failure
>>>
>>> [ERROR]
>>> /home/lakmali/workspace/carbon/components/axis2-repo-mgt/org.wso2.carbon.repomanager.axis2/src/main/java/org/wso2/carbon/repomanager/axis2/Axis2RepoManager.java:[215,31]
>>> terminateTenantConfigContext(org.apache.axis2.context.ConfigurationContext)
>>> has private access in
>>> org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils
>>>
>>> [ERROR] -> [Help 1]
>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
>>> goal org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile
>>> (default-compile) on project org.wso2.carbon.repomanager.axis2: Compilation
>>> failure
>>> /home/lakmali/workspace/carbon/components/axis2-repo-mgt/org.wso2.carbon.repomanager.axis2/src/main/java/org/wso2/carbon/repomanager/axis2/Axis2RepoManager.java:[215,31]
>>> terminateTenantConfigContext(org.apache.axis2.context.ConfigurationContext)
>>> has private access in
>>> org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils
>>>
>>>
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>>> 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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
>>> Caused by: org.apache.maven.plugin.CompilationFailureException:
>>> Compilation failur

[Carbon-dev] Build failure in components/axis2-repo-mgt

2011-09-20 Thread Lakmali Baminiwatta

hi,

I am getting a compilation error while building Components. Here is the full
error.

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 3.653s
[INFO] Finished at: Wed Sep 21 04:29:35 GMT 2011
[INFO] Final Memory: 21M/981M
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile
(default-compile) on project org.wso2.carbon.repomanager.axis2: Compilation
failure

[ERROR]
/home/lakmali/workspace/carbon/components/axis2-repo-mgt/org.wso2.carbon.repomanager.axis2/src/main/java/org/wso2/carbon/repomanager/axis2/Axis2RepoManager.java:[215,31]
terminateTenantConfigContext(org.apache.axis2.context.ConfigurationContext)
has private access in
org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils

[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile
(default-compile) on project org.wso2.carbon.repomanager.axis2: Compilation
failure
/home/lakmali/workspace/carbon/components/axis2-repo-mgt/org.wso2.carbon.repomanager.axis2/src/main/java/org/wso2/carbon/repomanager/axis2/Axis2RepoManager.java:[215,31]
terminateTenantConfigContext(org.apache.axis2.context.ConfigurationContext)
has private access in
org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils


at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation
failure
/home/lakmali/workspace/carbon/components/axis2-repo-mgt/org.wso2.carbon.repomanager.axis2/src/main/java/org/wso2/carbon/repomanager/axis2/Axis2RepoManager.java:[215,31]
terminateTenantConfigContext(org.apache.axis2.context.ConfigurationContext)
has private access in
org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils


at
org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:656)
at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
[ERROR]


Thanks,
Lakmali
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Carbon-dev Digest, Vol 44, Issue 86

2011-09-20 Thread Lakmali Baminiwatta

hi,

Thanks.. ! The core build failure issue is fixed now..

Lakmali



> Date: Wed, 21 Sep 2011 02:49:02 +0530
> From: Pradeep Fernando 
> To: carbon-dev 
> Subject: Re: [Carbon-dev] Carbon build failure
> Message-ID:
> >
> Content-Type: text/plain; charset=UTF-8
>
> Hi,
>
> On Tue, Sep 20, 2011 at 8:49 PM, Lakmali Baminiwatta 
> wrote:
> > hi,
> >
> > Yes, I did a svn up for carbon-p2-plugin in dependecies, but there were
> no
> > updates. Also I did build it again after svn up.
>
> My fault. Partial commit. Can you try it out now.
>
> thanks,
> --Pradeep
>
> >
> > Thanks,
> > Lakmali
> >
>
>
>
> --
> Pradeep Fernando
> Software Engineer
> WSO2 Inc; http://wso2.com/
>
> blog:?http://pradeepfernando.blogspot.com/
> m: +94776603662
>
>
> --
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
> End of Carbon-dev Digest, Vol 44, Issue 86
> **
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Core module build failure

2011-09-19 Thread Lakmali Baminiwatta

hi,

I am building the carbon trunk(latest) and getting this build failure of
finding goal 'publish-product' in plugin org.wso2.maven:carbon-p2-
plugin:1.4-SNAPSHOT.

Here is the full error

 [INFO]

[INFO] Building WSO2 Carbon - Carbon P2 Profile 3.2.0-SNAPSHOT
[INFO]

[INFO]

[INFO] Reactor Summary:
[INFO]
[INFO] WSO2 Carbon Core - Parent Maven Project ... SUCCESS [0.354s]
[INFO] WSO2 Carbon - Thread .. SUCCESS [1.576s]
[INFO] WSO2 Carbon - Better Tomcat ... SUCCESS [4.081s]
[INFO] WSO2 Carbon - Registry API  SUCCESS [8.212s]
[INFO] WSO2 Carbon - User Manager API  SUCCESS [0.587s]
[INFO] WSO2 Carbon - Xbootclasspath libraries  SUCCESS [0.551s]
[INFO] WSO2 Carbon - Logging . SUCCESS [0.751s]
[INFO] WSO2 Carbon - Queuing . SUCCESS [0.407s]
[INFO] WSO2 Carbon - Secure Vault  SUCCESS [0.712s]
[INFO] WSO2 Carbon - Base  SUCCESS [0.711s]
[INFO] WSO2 Carbon - Caching . SUCCESS [0.864s]
[INFO] WSO2 Carbon - Utilities ... SUCCESS [2.221s]
[INFO] WSO2 Carbon - Bootstrap ... SUCCESS [0.614s]
[INFO] WSO2 Carbon - Servlet to OSGi Bridge .. SUCCESS [1.314s]
[INFO] WSO2 Carbon - OSGi Security ... SUCCESS [0.722s]
[INFO] WSO2 Carbon - Xbootclasspath library for Registry Kernel  SUCCESS
[0.381s]
[INFO] WSO2 Carbon - Logging Extension ... SUCCESS [1.419s]
[INFO] WSO2 Carbon - Windows NT Service Installer  SUCCESS [0.738s]
[INFO] WSO2 Carbon - User Manager Kernel . SUCCESS [3.393s]
[INFO] WSO2 Carbon - Registry Kernel . SUCCESS [32.151s]
[INFO] WSO2 Carbon - Context . SUCCESS [0.721s]
[INFO] WSO2 Carbon - Kernel .. SUCCESS [4.832s]
[INFO] WSO2 Carbon - Registry Server . SUCCESS [0.939s]
[INFO] WSO2 Carbon - Component Manager Aggregator Module . SUCCESS [0.005s]
[INFO] WSO2 Carbon - Component Manager Core .. SUCCESS [0.779s]
[INFO] WSO2 Carbon - Server Role Manager Aggregator Module  SUCCESS [0.006s]
[INFO] WSO2 Carbon - Server-Roles Manager  SUCCESS [0.744s]
[INFO] WSO2 Carbon - Application Deployer  SUCCESS [1.814s]
[INFO] WSO2 Carbon - Core Common . SUCCESS [0.589s]
[INFO] WSO2 Carbon - Default Authenticator Proxy . SUCCESS [1.346s]
[INFO] WSO2 Carbon - Services  SUCCESS [1.316s]
[INFO] WSO2 Carbon - HTTP Bridge . SUCCESS [0.630s]
[INFO] WSO2 Carbon - UI .. SUCCESS [3.976s]
[INFO] WSO2 Carbon - Atomikos  SUCCESS [0.858s]
[INFO] WSO2 Carbon - Standalone Server ... SUCCESS [6.133s]
[INFO] WSO2 Carbon - Servlet Bridge .. SUCCESS [0.405s]
[INFO] WSO2 Carbon - Internationalization  SUCCESS [0.035s]
[INFO] WSO2 Carbon - Default tree menu structure . SUCCESS [0.031s]
[INFO] WSO2 Carbon - Registry tree menu structure  SUCCESS [0.030s]
[INFO] WSO2 Carbon - Governance tree menu structure .. SUCCESS [0.042s]
[INFO] WSO2 Carbon - Tools tree menu structure ... SUCCESS [0.035s]
[INFO] WSO2 Carbon - Parent Menu . SUCCESS [0.006s]
[INFO] WSO2 Carbon - Server Administration Common  SUCCESS [0.628s]
[INFO] WSO2 Carbon - Server Administration ... SUCCESS [1.156s]
[INFO] WSO2 Carbon - Server Administration UI  SUCCESS [0.608s]
[INFO] WSO2 Carbon - User Management Common .. SUCCESS [0.527s]
[INFO] WSO2 Carbon - User Management . SUCCESS [1.369s]
[INFO] WSO2 Carbon - User Management UI .. SUCCESS [0.768s]
[INFO] WSO2 Carbon - Cluster Management Core . SUCCESS [0.648s]
[INFO] WSO2 Carbon - Addressing .. SUCCESS [0.077s]
[INFO] WSO2 Carbon - Directory Server  SUCCESS [1.669s]
[INFO] WSO2 Carbon - Component Manager Web Services .. SUCCESS [0.793s]
[INFO] WSO2 Carbon - Component Manager UI  SUCCESS [0.792s]
[INFO] WSO2 Carbon - Server-Roles Manager UI . SUCCESS [0.791s]
[INFO] WSO2 Carbon - Features  SUCCESS [0.324s]
[INFO] WSO2 Carbon - Carbon Common Feature ... SUCCESS [3.319s]
[INFO] WSO2 Carbon - Carbon Server Feature ... SUCCESS [0.621s]
[INFO] WSO2 Carbon - Carbon UI Feature ... SUCCESS [0.627s]
[INFO] WSO2 Carbon - Carbon Runtime Feature .

Re: [Carbon-dev] Issue in implementing JPA support on ESB Smooks Mediator

[Carbon-dev] Issue in implementing JPA support on ESB Smooks Mediator

Re: [Carbon-dev] Built is still broken

Re: [Carbon-dev] Unexpected subelement error in a data service client.

Re: [Carbon-dev] [Bamboo-Build] Carbon-Kernel > Graphite-Build > #29 has FAILED. Change made by 6 authors.

Re: [Carbon-dev] WSO2 Committers += Lakmali

[Carbon-dev] Issue in ESB Smooks Mediator Streaming Improvements

Re: [Carbon-dev] XA Transactions

Re: [Carbon-dev] List down the product builds which are compatible with maven3

Re: [Carbon-dev] Blocker issue in DSS 2.6.3

Re: [Carbon-dev] ESB Smooks Mediator Improvements

[Carbon-dev] ESB Smooks Mediator Improvements

[Carbon-dev] ESB Smooks Support

Re: [Carbon-dev] my photo

Re: [Carbon-dev] Build failure in components/axis2-repo-mgt

[Carbon-dev] Build failure in components/axis2-repo-mgt

Re: [Carbon-dev] Carbon-dev Digest, Vol 44, Issue 86

[Carbon-dev] Core module build failure

18 matches

Site Navigation

Mail list logo

Footer information