Re: [Carbon-dev] CEP integration test failures
On Wed, Feb 29, 2012 at 7:58 AM, Pradeep Fernando prad...@wso2.com wrote:
Hi,
i'm getting this error log.
[2012-02-29 00:54:10,639] INFO
{org.wso2.carbon.integration.framework.LoginLogoutUtil} - Successfully
logged in : JSESSIONID=7D09316AC27A87DF6EA115EC8F54C6F3; Path=/;
Secure=null; HttpOnly=null
[2012-02-29 00:54:10,639] INFO
{org.wso2.carbon.integration.framework.utils.ServerUtils} - Server started
successfully.
[2012-02-29 00:54:10,640] INFO
{org.wso2.carbon.integration.framework.ClientConnectionUtil} - Waiting
until server starts on port 7611
[2012-02-29 00:54:11,641] INFO
{org.wso2.carbon.integration.framework.ClientConnectionUtil} - Waiting
until server starts on port 7611
can somebody please give me some context. what is this port. FYI, server
starts on 9443.
This is because org.wso2.carbon.base.ServerConfiguration has renamed to
org.wso2.carbon.base.api.ServerConfigurationService.
So that both Qpid and Agent components does not start up.
Now fixed in the trunk.
thanks,
Amila.
--Pradeep
--
*Amila Suriarachchi*
Software Architect
WSO2 Inc. ; http://wso2.com
lean . enterprise . middleware
phone : +94 71 3082805
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Can't deploy Drools Guvnor in carbon
This web application works fine in tomcat and it has some security so that the users have to log into web app. thanks, Amila. On Wed, Feb 29, 2012 at 5:41 PM, Ishara Karunarathna isha...@wso2.comwrote: Hi, I tried to deploy Drools guvnor[1] in carbon. But it doesn't work. I went though [2] to fix it, but it didn't work Is there a way to do this. Thanks Ishara [1] http://www.jboss.org/drools/downloads [2] https://community.jboss.org/wiki/InstallingDroolsGuvnor50InTomcat6xAndJBossAS5 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Integration test failures in MB
On Wed, Feb 29, 2012 at 9:12 AM, Charith Wickramarachchi
char...@wso2.comwrote:
Here the test complains about the tcp port MB opens up for AMQP
communication.
Shammi was working on creating a MB product out of new broker dependency.
So looks like a broker 2 start-up issue.
Since we are in the process of merging new broker 2 features to the trunk.
You can expect this kind of a failures in the MB product for a while.
Will have a look.
this error is because of changing and internal OSGI service interface.
Fixed in the trunk.
thanks,
Amila.
thanks,
Charith
On Wed, Feb 29, 2012 at 8:56 AM, Pradeep Fernando prad...@wso2.comwrote:
Hi,
I get this error logs,
[2012-02-29 08:54:08,532] INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} -
[2012-02-29 08:54:08,529] INFO
{org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} - 'admin'
logged in at [2012-02-29 08:54:08,0529] from IP address 192.168.1.2
[2012-02-29 08:54:08,609] INFO
{org.wso2.carbon.integration.framework.LoginLogoutUtil} - Successfully
logged in : JSESSIONID=74B141B181978C2B969957A8AFC7C94A; Path=/;
Secure=null; HttpOnly=null
[2012-02-29 08:54:08,609] INFO
{org.wso2.carbon.integration.framework.utils.ServerUtils} - Server started
successfully.
[2012-02-29 08:54:08,625] INFO
{org.wso2.carbon.integration.framework.ClientConnectionUtil} - Waiting
until server starts on port 5672
[2012-02-29 08:54:09,626] INFO
{org.wso2.carbon.integration.framework.ClientConnectionUtil} - Waiting
until server starts on port 5672
[2012-02-29 08:54:10,627] INFO
{org.wso2.carbon.integration.framework.ClientConnectionUtil} - Waiting
until server starts on port 5672
[2012-02-29 08:54:11,627] INFO
{org.wso2.carbon.integration.framework.ClientConnectionUtil} - Waiting
until server starts on port 5672
[2012-02-29 08:54:12,628] INFO
{org.wso2.carbon.integration.framework.ClientConnectionUtil} - Waiting
until server starts on port 5672
[2012-02-29 08:54:13,629] INFO
{org.wso2.carbon.integration.framework.ClientConnectionUtil} - Waiting
until server starts on port 5672
server started on 9443. please have a look and if it is a problem with
carbon-core, please give me some context.
--Pradeep
--
Charith Dhanushka Wickramarachchi
Software Engineer
WSO2 Inc
http://wso2.com/
http://wso2.org/
blog
http://charithwiki.blogspot.com/
twitter
http://twitter.com/charithwiki
Mobile : 0776706568
--
*Amila Suriarachchi*
Software Architect
WSO2 Inc. ; http://wso2.com
lean . enterprise . middleware
phone : +94 71 3082805
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Carbon Integration Test Framework : Excluding axis2 jar from SecVerifier.aar
On Wed, Feb 29, 2012 at 10:55 PM, Subash Chaturanga sub...@wso2.com wrote: Hi Azeez, For some reason GReg has enabled child first class loading and having problems in deploying axis2 web services. Though any carbon server is expected to be able to deploy axis2 web services, greg is not capable of deploying SecVerifier.aar due to above reason. To get rid from problems due to unnecessary class loading from SecVerifier/lib, I have changed the integration/security-verifier/pom to exclude axis2 jar from packaging inside the aar, but to use that only in compile time. Not only axis2 jar remove all unnecessary jars. .aar service requires the classes written only for that service. thanks, Amila. And I tested it to BRS as well. Shall I commit it to trunk ? Thanks -- Subash Chaturanga Software Engineer WSO2 Inc. http://wso2.com email - sub...@wso2.com phone - 077 2225922 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Can't deploy Drools Guvnor in carbon
.carbon.webapp.mgt.TomcatGenericWebappsDeployer.handleHotDeployment(TomcatGenericWebappsDeployer.java:123)
at
org.wso2.carbon.webapp.mgt.TomcatGenericWebappsDeployer.deploy(TomcatGenericWebappsDeployer.java:95)
at
org.wso2.carbon.webapp.mgt.WebappDeployer.deploy(WebappDeployer.java:73)
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:371)
at
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
at
org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:139)
at
org.wso2.carbon.core.CarbonAxisConfigurator.loadServices(CarbonAxisConfigurator.java:448)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:95)
at
org.wso2.carbon.core.CarbonConfigurationContextFactory.createNewConfigurationContext(CarbonConfigurationContextFactory.java:65)
at
org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:367)
at
org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:262)
at
org.wso2.carbon.core.init.PreAxis2ConfigItemListener.bundleChanged(PreAxis2ConfigItemListener.java:117)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:847)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
[2012-03-01 12:32:09,435] ERROR
{org.wso2.carbon.tomcat.internal.ServerManager} -
webAppStandardEngine[Catalina].StandardHost[localhost].StandardContext[/guvnor-5.3.0.Final-tomcat-6.0]failed
to deploy
Can you please have a look?
I think this is a problem with new Tomcat OSGIfication.
thanks,
Amila.
thanks,
On Wed, Feb 29, 2012 at 4:56 AM, Amila Suriarachchi am...@wso2.comwrote:
This web application works fine in tomcat and it has some security so
that the users have to log into web app.
thanks,
Amila.
On Wed, Feb 29, 2012 at 5:41 PM, Ishara Karunarathna isha...@wso2.comwrote:
Hi,
I tried to deploy Drools guvnor[1] in carbon. But it doesn't work.
I went though [2] to fix it, but it didn't work
Is there a way to do this.
Thanks
Ishara
[1] http://www.jboss.org/drools/downloads
[2]
https://community.jboss.org/wiki/InstallingDroolsGuvnor50InTomcat6xAndJBossAS5
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
--
*Amila Suriarachchi*
Software Architect
WSO2 Inc. ; http://wso2.com
lean . enterprise . middleware
phone : +94 71 3082805
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
--
Supun Malinga,
Software Engineer,
WSO2 Inc.
http://wso2.com
http://wso2.org
email - sup...@wso2.com sup...@wso2.com
mobile - 071 56 91 321
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
--
*Amila Suriarachchi*
Software Architect
WSO2 Inc. ; http://wso2.com
lean . enterprise . middleware
phone : +94 71 3082805
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Different behaviours in ESB 3.2.2 and ESB trunk, when retrieving HttpServletRequest
-- 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 -- Mobile : +94773330538 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] JSON to SOAP conversion in WSO2 ESB
On Thu, Feb 23, 2012 at 11:19 AM, Prabath Siriwardena prab...@wso2.comwrote: On Thu, Feb 23, 2012 at 11:13 AM, Amila Suriarachchi am...@wso2.comwrote: Any thoughts.. on the behavior of the first scenario ? Within Soap Body you can have only one element. So that may be picking the first element as the soap body element. Thought about that..But looking at the spec - at http://www.w3.org/TR/soap12-part0/#Example - it looks like its not the case.. Is this something enforced by axis2..? Axis2 does not generate soap messages with may soap body elements. I thought this is a constraint put by basic profile. But I could not find a place saying so. thanks, Amila. Thanks regards, -Prabath thanks, Amila. -- Thanks Regards, Prabath Mobile : +94 71 809 6732 http://blog.facilelogin.com http://RampartFAQ.com ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Thanks Regards, Prabath Mobile : +94 71 809 6732 http://blog.facilelogin.com http://RampartFAQ.com ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ 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.
(* 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 -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] JSON to SOAP conversion in WSO2 ESB
On Thu, Feb 23, 2012 at 2:29 AM, Prabath Siriwardena prab...@wso2.comwrote:
Tried out some json stuff with the ESB latest release.. and following
what I observed...
The original json message which I want to send is following..
{name : Understanding JAVA , pages : 100}
When I sent this - this is the SOAP body I observed inside the ESB..
soapenv:Body xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/
nameUnderstanding
JAVA/name/soapenv:Body
You will notice that - pages element is missing there..
When I reformat my json message to the following - with a top, parent
element it worked fine..
{ request :{name : Understanding JAVA , pages : 100}}
and the SOAP body produced was...
soapenv:Body xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/
requestnameUnderstanding
JAVA/namepages100/pages/request/soapenv:Body
Any thoughts.. on the behavior of the first scenario ?
Within Soap Body you can have only one element. So that may be picking the
first element as the soap body element.
thanks,
Amila.
--
Thanks Regards,
Prabath
Mobile : +94 71 809 6732
http://blog.facilelogin.com
http://RampartFAQ.com
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
--
*Amila Suriarachchi*
Software Architect
WSO2 Inc. ; http://wso2.com
lean . enterprise . middleware
phone : +94 71 3082805
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Updating mvel2 orbit version to 2.0.19
is there any product other than CEP and BRS use this library?
thanks,
Amila.
On Mon, Feb 20, 2012 at 5:45 PM, Suhothayan Sriskandarajah s...@wso2.comwrote:
Drools and Siddhi have dependency on mvel2. Currently WSO2 platform uses
mvel 2.0.10 but
this version of mvel2 has some critical bugs where it couldn't process
expressions like
((7+(8*2)CSEStream.price) (CSEStream.symbol=='IBM')
and it is producing an error [1]
Hence this has been fixed in the latest stable version 2.0.19 released on
Nov 19 2010 [2].
I'm upgrading the mvel2 orbit to 2.0.19
Thanks
Suho
[1] [Error: was expecting type: java.lang.Boolean; but found type:
java.lang.Integer]
[Near : {... )price) (symbol=='IBM') }]
^
[Line: 1, Column: 40]
[2] http://mvel.codehaus.org/Downloading+MVEL
--
*S. Suhothayan
*
Software Engineer,
Data Technologies Team,
*WSO2, Inc. **http://wso2.com
http://wso2.com/*
*lean.enterprise.middleware.*
*email: **s...@wso2.com* s...@wso2.com* cell: (+94) 779 756 757
blog: **http://suhothayan.blogspot.com/* http://suhothayan.blogspot.com/
*
twitter: **http://twitter.com/suhothayan* http://twitter.com/suhothayan*
linked-in: **http://lk.linkedin.com/in/suhothayan*
*
*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
--
*Amila Suriarachchi*
Software Architect
WSO2 Inc. ; http://wso2.com
lean . enterprise . middleware
phone : +94 71 3082805
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] mediators develop error.
(ServiceRegistry.java:712) at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:129) at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:206) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:506) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:524) at org.wso2.carbon.core.services.internal.CarbonServicesServiceComponent.activate(CarbonServicesServiceComponent.java:72) 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:230) at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:140) at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:330) at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:560) at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:182) at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:292)*** * at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:226) at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:124) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:930) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220) at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:149) at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:757) at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:712) at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:129) at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:206) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:506) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:524) at org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:471) at org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:273) at org.wso2.carbon.core.init.PreAxis2ConfigItemListener.bundleChanged(PreAxis2ConfigItemListener.java:117) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:916) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:330) ** ** 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 -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Source code links broken on OT
it should be https://svn.wso2.org/repos/wso2/trunk/graphite/products/as thanks, Amila. On Sat, Feb 18, 2012 at 4:45 PM, Danushka Menikkumbura danushka.menikkumb...@gmail.com wrote: Hi, Just wanted to find out the link for app server source code. I do not see a link for source code on product home page (i.e. http://wso2.com/products/application-server/) I get a 404 for the link ( https://svn.wso2.org/repos/wso2/trunk/carbon/products/appserver) on http://wso2.org/library/application-server The link on the Projects tab directs me to some other page. Please take a look. Danushka ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Can not build the new carbon trunk.
is this still under construct?
I am getting an exception here.
[INFO] Building Maven P2 Profile Generation Plugin
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting directory
/home/amila/projects/trunk/carbon/dependencies/carbon-p2-plugin/target
[INFO] [incremental-build:incremental-build {execution: default}]
[INFO] Verifying module descriptor ...
[INFO] Pom descriptor modification detected.
[INFO] Deleting
/home/amila/projects/trunk/carbon/dependencies/carbon-p2-plugin/target
[INFO] [plugin:descriptor {execution: default-descriptor}]
[INFO] Using 2 extractors.
[INFO] Applying extractor for language: java
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] syntax error @[27,30] in
file:/home/amila/projects/trunk/carbon/dependencies/carbon-p2-plugin/src/main/java/org/wso2/maven/p2/generate/utils/PropertyReplacer.java
[INFO]
[INFO] Trace
com.thoughtworks.qdox.parser.ParseException: syntax error @[27,30] in
file:/home/amila/projects/trunk/carbon/dependencies/carbon-p2-plugin/src/main/java/org/wso2/maven/p2/generate/utils/PropertyReplacer.java
at com.thoughtworks.qdox.parser.impl.Parser.yyerror(Parser.java:716)
at com.thoughtworks.qdox.parser.impl.Parser.yyparse(Parser.java:826)
at com.thoughtworks.qdox.parser.impl.Parser.parse(Parser.java:697)
at
com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:300)
at
com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:316)
at
com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:312)
at
com.thoughtworks.qdox.JavaDocBuilder$1.visitFile(JavaDocBuilder.java:369)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:43)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.scan(DirectoryScanner.java:52)
at
com.thoughtworks.qdox.JavaDocBuilder.addSourceTree(JavaDocBuilder.java:366)
at
org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.discoverClasses(JavaMojoDescriptorExtractor.java:605)
at
org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.execute(JavaMojoDescriptorExtractor.java:572)
at
org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(DefaultMojoScanner.java:96)
at
org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute(AbstractGeneratorMojo.java:146)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
thanks,
Amila.
--
*Amila
Re: [Carbon-dev] Can not build the new carbon trunk.
Sorry this is because I have change the maven version to compile the branch.
thanks,
Amila.
On Sat, Feb 18, 2012 at 4:54 PM, Amila Suriarachchi am...@wso2.com wrote:
is this still under construct?
I am getting an exception here.
[INFO] Building Maven P2 Profile Generation Plugin
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting directory
/home/amila/projects/trunk/carbon/dependencies/carbon-p2-plugin/target
[INFO] [incremental-build:incremental-build {execution: default}]
[INFO] Verifying module descriptor ...
[INFO] Pom descriptor modification detected.
[INFO] Deleting
/home/amila/projects/trunk/carbon/dependencies/carbon-p2-plugin/target
[INFO] [plugin:descriptor {execution: default-descriptor}]
[INFO] Using 2 extractors.
[INFO] Applying extractor for language: java
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] syntax error @[27,30] in
file:/home/amila/projects/trunk/carbon/dependencies/carbon-p2-plugin/src/main/java/org/wso2/maven/p2/generate/utils/PropertyReplacer.java
[INFO]
[INFO] Trace
com.thoughtworks.qdox.parser.ParseException: syntax error @[27,30] in
file:/home/amila/projects/trunk/carbon/dependencies/carbon-p2-plugin/src/main/java/org/wso2/maven/p2/generate/utils/PropertyReplacer.java
at com.thoughtworks.qdox.parser.impl.Parser.yyerror(Parser.java:716)
at com.thoughtworks.qdox.parser.impl.Parser.yyparse(Parser.java:826)
at com.thoughtworks.qdox.parser.impl.Parser.parse(Parser.java:697)
at
com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:300)
at
com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:316)
at
com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:312)
at
com.thoughtworks.qdox.JavaDocBuilder$1.visitFile(JavaDocBuilder.java:369)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:43)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.scan(DirectoryScanner.java:52)
at
com.thoughtworks.qdox.JavaDocBuilder.addSourceTree(JavaDocBuilder.java:366)
at
org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.discoverClasses(JavaMojoDescriptorExtractor.java:605)
at
org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.execute(JavaMojoDescriptorExtractor.java:572)
at
org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(DefaultMojoScanner.java:96)
at
org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute(AbstractGeneratorMojo.java:146)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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.classworlds.Launcher.launchEnhanced
Re: [Carbon-dev] Can not build the new carbon trunk.
now getting this exception.
[ERROR] Failed to execute goal on project org.wso2.carbon.tomcat: Could not
resolve dependencies for project
org.wso2.carbon:org.wso2.carbon.tomcat:bundle:4.0.0-SNAPSHOT: The following
artifacts could not be resolved:
org.wso2.carbon:javax.servlet:jar:3.0.0.wso2v1,
org.wso2.carbon:org.apache.tomcat:jar:1.7.0.wso2v1: Could not find artifact
org.wso2.carbon:javax.servlet:jar:3.0.0.wso2v1 in wso2-nexus (
http://maven.wso2.org/nexus/content/groups/wso2-public/) - [Help 1]
thanks,
Amila.
On Sat, Feb 18, 2012 at 5:09 PM, Amila Suriarachchi am...@wso2.com wrote:
Sorry this is because I have change the maven version to compile the
branch.
thanks,
Amila.
On Sat, Feb 18, 2012 at 4:54 PM, Amila Suriarachchi am...@wso2.comwrote:
is this still under construct?
I am getting an exception here.
[INFO] Building Maven P2 Profile Generation Plugin
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting directory
/home/amila/projects/trunk/carbon/dependencies/carbon-p2-plugin/target
[INFO] [incremental-build:incremental-build {execution: default}]
[INFO] Verifying module descriptor ...
[INFO] Pom descriptor modification detected.
[INFO] Deleting
/home/amila/projects/trunk/carbon/dependencies/carbon-p2-plugin/target
[INFO] [plugin:descriptor {execution: default-descriptor}]
[INFO] Using 2 extractors.
[INFO] Applying extractor for language: java
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] syntax error @[27,30] in
file:/home/amila/projects/trunk/carbon/dependencies/carbon-p2-plugin/src/main/java/org/wso2/maven/p2/generate/utils/PropertyReplacer.java
[INFO]
[INFO] Trace
com.thoughtworks.qdox.parser.ParseException: syntax error @[27,30] in
file:/home/amila/projects/trunk/carbon/dependencies/carbon-p2-plugin/src/main/java/org/wso2/maven/p2/generate/utils/PropertyReplacer.java
at com.thoughtworks.qdox.parser.impl.Parser.yyerror(Parser.java:716)
at com.thoughtworks.qdox.parser.impl.Parser.yyparse(Parser.java:826)
at com.thoughtworks.qdox.parser.impl.Parser.parse(Parser.java:697)
at
com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:300)
at
com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:316)
at
com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:312)
at
com.thoughtworks.qdox.JavaDocBuilder$1.visitFile(JavaDocBuilder.java:369)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:43)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.scan(DirectoryScanner.java:52)
at
com.thoughtworks.qdox.JavaDocBuilder.addSourceTree(JavaDocBuilder.java:366)
at
org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.discoverClasses(JavaMojoDescriptorExtractor.java:605)
at
org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.execute(JavaMojoDescriptorExtractor.java:572)
at
org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(DefaultMojoScanner.java:96)
at
org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute(AbstractGeneratorMojo.java:146)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute
Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.
___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - sup...@wso2.com sup...@wso2.com mobile - 071 56 91 321 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev 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 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Orbit, Carbon and Graphite - New Face of Carbon SVN Repository.
meeting. Thanks, Sameera. On Mon, Feb 13, 2012 at 7:35 AM, Samisa Abeysinghe sam...@wso2.com wrote: On Mon, Feb 13, 2012 at 6:54 AM, Pradeep Fernando prad...@wso2.com wrote: On Mon, Feb 13, 2012 at 6:51 AM, Samisa Abeysinghe sam...@wso2.com wrote: And do we have Tomcat OSGi stuff in there now? No, not yet. Plan is to add them within next two days. Note that both AS and Jaggery are blocked on this. We have arrange a meeting too to discuss these today. 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 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ 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 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - sup...@wso2.com sup...@wso2.com mobile - 071 56 91 321 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev 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 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- /sumedha +94 773017743 ___ 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 -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando * Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Can not build the new carbon trunk.
this is because you have not build the orbit.
thanks,
Amila.
On Sat, Feb 18, 2012 at 10:21 PM, Senaka Fernando sen...@wso2.com wrote:
Hi Amila,
I am stuck at the same place, see e-mail on Jarvana repository.
Thanks,
Senaka.
On Sat, Feb 18, 2012 at 5:20 PM, Amila Suriarachchi am...@wso2.comwrote:
now getting this exception.
[ERROR] Failed to execute goal on project org.wso2.carbon.tomcat: Could
not resolve dependencies for project
org.wso2.carbon:org.wso2.carbon.tomcat:bundle:4.0.0-SNAPSHOT: The following
artifacts could not be resolved:
org.wso2.carbon:javax.servlet:jar:3.0.0.wso2v1,
org.wso2.carbon:org.apache.tomcat:jar:1.7.0.wso2v1: Could not find artifact
org.wso2.carbon:javax.servlet:jar:3.0.0.wso2v1 in wso2-nexus (
http://maven.wso2.org/nexus/content/groups/wso2-public/) - [Help 1]
thanks,
Amila.
On Sat, Feb 18, 2012 at 5:09 PM, Amila Suriarachchi am...@wso2.comwrote:
Sorry this is because I have change the maven version to compile the
branch.
thanks,
Amila.
On Sat, Feb 18, 2012 at 4:54 PM, Amila Suriarachchi am...@wso2.comwrote:
is this still under construct?
I am getting an exception here.
[INFO] Building Maven P2 Profile Generation Plugin
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting directory
/home/amila/projects/trunk/carbon/dependencies/carbon-p2-plugin/target
[INFO] [incremental-build:incremental-build {execution: default}]
[INFO] Verifying module descriptor ...
[INFO] Pom descriptor modification detected.
[INFO] Deleting
/home/amila/projects/trunk/carbon/dependencies/carbon-p2-plugin/target
[INFO] [plugin:descriptor {execution: default-descriptor}]
[INFO] Using 2 extractors.
[INFO] Applying extractor for language: java
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] syntax error @[27,30] in
file:/home/amila/projects/trunk/carbon/dependencies/carbon-p2-plugin/src/main/java/org/wso2/maven/p2/generate/utils/PropertyReplacer.java
[INFO]
[INFO] Trace
com.thoughtworks.qdox.parser.ParseException: syntax error @[27,30] in
file:/home/amila/projects/trunk/carbon/dependencies/carbon-p2-plugin/src/main/java/org/wso2/maven/p2/generate/utils/PropertyReplacer.java
at com.thoughtworks.qdox.parser.impl.Parser.yyerror(Parser.java:716)
at com.thoughtworks.qdox.parser.impl.Parser.yyparse(Parser.java:826)
at com.thoughtworks.qdox.parser.impl.Parser.parse(Parser.java:697)
at
com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:300)
at
com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:316)
at
com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:312)
at
com.thoughtworks.qdox.JavaDocBuilder$1.visitFile(JavaDocBuilder.java:369)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:43)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
at
com.thoughtworks.qdox.directorywalker.DirectoryScanner.scan(DirectoryScanner.java:52)
at
com.thoughtworks.qdox.JavaDocBuilder.addSourceTree(JavaDocBuilder.java:366)
at
org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.discoverClasses(JavaMojoDescriptorExtractor.java:605)
at
org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.execute(JavaMojoDescriptorExtractor.java:572)
at
org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(DefaultMojoScanner.java:96)
at
org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute(AbstractGeneratorMojo.java:146)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535
Re: [Carbon-dev] combining two query result
On Sat, Feb 18, 2012 at 2:10 AM, Jorge Infante Osorio jorg...@uci.cuwrote: You don´t have a similar configuration but for queries? My idea is to use 1 query that expose the results of two queries. ** ** My scenario: ** ** I have a query that return a set of Persons person id/id name/name Area id/id nameArea/nameArea /Area /person /Persons ** ** I extract the area from another query, a subquery, passing the user ID, but the areas are in two differents queries so I need first to combine the results of this queries in another query. ** ** ** ** With this configuration, it´ss possible to do that? I did this trick some similar case. for this you can define a dummy combine query. eg. query id=combineQuery useConfig=mysqldatasource sqlselect 1/sql result element=CombinedElements rowName=CombinedElement call-query href=areaQuery1 / call-query href=areaQuery2 / /result /query within your Persons query you can refer to this query. thanks, Amila. ** ** ** ** Saludos, Ing. Jorge Infante Osorio. J´Dpto Soluciones SOA. CDAE. Fac. 5. UCI. ** ** *De:* carbon-dev-boun...@wso2.org [mailto:carbon-dev-boun...@wso2.org] *En nombre de *Anjana Fernando *Enviado el:* miércoles, 15 de febrero de 2012 22:23 *Para:* carbon-dev@wso2.org *Asunto:* Re: [Carbon-dev] combining two query result ** ** Hi Jorge, We do have an unofficial functionality to do this, it is not in the UI wizard, basically in the data service configuration, in the operation, use the syntax in the following way: operation name=... call-query-group call-query href=q1/ call-query href=q2/ /call-query-group /operation Cheers, Anjana. On Thu, Feb 16, 2012 at 7:37 AM, Jorge Infante Osorio jorg...@uci.cu wrote: Hi folks. In DSS, it´s possible to combine two query result into the result of another query? In query X I have the result of a SELECT in one DB/table in server X, and in query Y I have the result of another SELECT in another DB/table in server Y. Both DB have a table with the same fields. I think in something similar to UNION in SQL. :-D It could be possible?? Saludos, Ing. Jorge Infante Osorio. J´Dpto Soluciones SOA. CDAE. Fac. 5. UCI. ** ** http://www.antiterroristas.cu/ ** ** http://www.antiterroristas.cu/ ___ Carbon-dev mailing list *Carbon-dev@wso2.org* *http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev* http://www.antiterroristas.cu/ -- *Anjana Fernando* Senior Software Engineer http://www.antiterroristas.cu/ WSO2 Inc. | *http://wso2.com* http://www.antiterroristas.cu/ lean . enterprise . middleware http://www.antiterroristas.cu/ http://www.antiterroristas.cu/ ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Performance numbers of Agent Component
On Thu, Feb 9, 2012 at 12:36 PM, Srinath Perera srin...@wso2.com wrote: Hi Suho, IMHO this covers about 90% of our usecases .. I think we should move on we do not required to do an performance study. Since anyway we don't have proper CEP or BAM service to consume events. But need to test for once client many server scenario to test for stability. thanks, Amila. I do not mind doing a larger perf study later .. .. but getting the server finished from siddhi side and releasing it, CEP perrf numbers, and integrating this with BAM are more urget IMHO --Srinath On Thu, Feb 9, 2012 at 12:29 PM, Suhothayan Sriskandarajah s...@wso2.com wrote: On Thu, Feb 9, 2012 at 12:00 PM, Amila Suriarachchi am...@wso2.com wrote: On Thu, Feb 9, 2012 at 11:47 AM, Tharindu Mathew thari...@wso2.com wrote: Suho, This does not measure the ability to handle load. Basically, what we did for load testing earlier was send around 2M messages, with concurrency as high increasing from 100 - 1500 clients. How many back end servers and client programs used for that? Your test is a measure of being able to consistently handle a stream of messages, which IMO, maybe important but is less interesting when handling load. This test has measured the one client one server. yes it can be improved to one client to many servers and many clients to many servers. This test also covers sending messages from many clients (2,5,10 20) to one server. Yes it could be improved to many clients to many server. If there are any specific requirements please suggest me a scenario, then I can do the testing and present the findings. Thanks Suho But this test gives the through put this can handle one client to server. For one client scenario whether you add messages with one thread or many threads does not effect the performance if there are enough messages to send. thanks, Amila. To truly test the ability to handle loads we need to do a distributed load test with an extremely high number of clients and see the breaking point. Earlier, we could not find such a point with a single machine. On Thu, Feb 9, 2012 at 11:31 AM, Suhothayan Sriskandarajah s...@wso2.com wrote: On Thu, Feb 9, 2012 at 11:24 AM, Amila Suriarachchi am...@wso2.com wrote: through put should not depend on the number of messages send. You need to send sufficient number of messages after server warmed up. Can you please first send around 2M messages and take the numbers for next 10M messages. And also try to test with number of back end servers. Yes, I'll work on this Thanks Suho thanks, Amila. On Wed, Feb 8, 2012 at 9:25 PM, Suhothayan Sriskandarajah s...@wso2.com wrote: According to the decisions made at the architecture mailing list on the subject Serializing generic Siddhi events using Thrift, I did some improvements to the code base of Agent component and did a performance testing. Here I did the tests by sending total of 1 million and 10 million events using for loop, in both cases I have sent events using 1,2,5,10 20 Clients. The results are as follows 1M 10M 1 245118.1269328.8 2 517509.1739699.7 5 585823.1923986.7 10345582.3418865.7 20285008.6368881.2 I have also attached the performance graph Regards Suho -- S. Suhothayan Software Engineer, Data Technologies Team, WSO2, Inc. http://wso2.com lean.enterprise.middleware. email: s...@wso2.com cell: (+94) 779 756 757 blog: http://suhothayan.blogspot.com/ twitter: http://twitter.com/suhothayan linked-in: http://lk.linkedin.com/in/suhothayan -- Amila Suriarachchi Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 -- S. Suhothayan Software Engineer, Data Technologies Team, WSO2, Inc. http://wso2.com lean.enterprise.middleware. email: s...@wso2.com cell: (+94) 779 756 757 blog: http://suhothayan.blogspot.com/ twitter: http://twitter.com/suhothayan linked-in: http://lk.linkedin.com/in/suhothayan -- Regards, Tharindu blog: http://mackiemathew.com/ M: +9459908 -- Amila Suriarachchi Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 -- S. Suhothayan Software Engineer, Data Technologies Team, WSO2, Inc. http://wso2.com lean.enterprise.middleware. email: s...@wso2.com cell: (+94) 779 756 757 blog: http://suhothayan.blogspot.com/ twitter: http://twitter.com/suhothayan linked-in: http://lk.linkedin.com/in/suhothayan -- Srinath Perera, Ph.D. Senior Software Architect, WSO2 Inc. Visiting Faculty, University of Moratuwa Member, Apache Software Foundation
[Carbon-dev] Suho += WSO2 committers
hi Suho, Congratulations and welcome aboard as a WSO2 Committer. Thank you for your contributions!. thanks, Amila. -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Performance numbers of Agent Component
through put should not depend on the number of messages send. You need to send sufficient number of messages after server warmed up. Can you please first send around 2M messages and take the numbers for next 10M messages. And also try to test with number of back end servers. thanks, Amila. On Wed, Feb 8, 2012 at 9:25 PM, Suhothayan Sriskandarajah s...@wso2.comwrote: According to the decisions made at the architecture mailing list on the subject Serializing generic Siddhi events using Thrift, I did some improvements to the code base of Agent component and did a performance testing. Here I did the tests by sending total of 1 million and 10 million events using for loop, in both cases I have sent events using 1,2,5,10 20 Clients. The results are as follows *1M 10M* *1* 245118.1269328.8 *2* 517509.1739699.7 *5* 585823.1923986.7 *10*345582.3418865.7 *20*285008.6368881.2 I have also attached the performance graph Regards Suho -- *S. Suhothayan * Software Engineer, Data Technologies Team, *WSO2, Inc. **http://wso2.com http://wso2.com/* *lean.enterprise.middleware.* *email: **s...@wso2.com* s...@wso2.com* cell: (+94) 779 756 757 blog: **http://suhothayan.blogspot.com/* http://suhothayan.blogspot.com/ * twitter: **http://twitter.com/suhothayan* http://twitter.com/suhothayan* linked-in: **http://lk.linkedin.com/in/suhothayan* * * -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] error with password in a data service. ERROR: Unexpected character '3' (code 51) (expected a name start character)
On Thu, Feb 9, 2012 at 8:44 AM, Anjana Fernando anj...@wso2.com wrote:
Hi Jorge,
Is the password value properly XML escaped in the dbs file? .. basically
you should enter that value from the wizard, which will automatically
escape it when writing the XML out, or the value if you're hand editing
should be amp;3dfA23aaaBBCm7dNCd#sdZ43.
or you need to use the ![CDATA[ tag to escape them.
thanks,
Amila.
Cheers,
Anjana.
On Wed, Feb 8, 2012 at 7:23 PM, Jorge Infante Osorio jorg...@uci.cuwrote:
Hi folk.
** **
I use AS 4.1.2.
** **
I need to use a password to access to a database and receive that error.
The pass that I use: 3dfA23aaaBBCm7dNCd#sdZ43
** **
ERROR:
** **
DS Code: UNKNOWN_ERROR
Nested Exception:-
org.apache.axiom.om.OMException:
com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '3'
(code 51) (expected a name start character)
at [row,col {unknown-source}]: [6,58]
** **
at
org.wso2.carbon.dataservices.core.DBDeployer.convertConfigToMultipleDSFormat(DBDeployer.java:464)
at
org.wso2.carbon.dataservices.core.DBDeployer.createDBService(DBDeployer.java:710)
at
org.wso2.carbon.dataservices.core.DBDeployer.processService(DBDeployer.java:1068)
at
org.wso2.carbon.dataservices.core.DBDeployer.deploy(DBDeployer.java:175)*
***
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:813)
at
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
at
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:371)
at
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
at
org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:365)
at
org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:73)
at
org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:94)
at
org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask.run(Scheduler.java:93)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)
Caused by: org.apache.axiom.om.OMException:
com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '3'
(code 51) (expected a name start character)
at [row,col {unknown-source}]: [6,58]
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:296)
at
org.apache.axiom.om.impl.llom.OMSerializableImpl.build(OMSerializableImpl.java:78)
at
org.apache.axiom.om.impl.llom.OMElementImpl.build(OMElementImpl.java:722)
at
org.wso2.carbon.dataservices.core.DBDeployer.convertConfigToMultipleDSFormat(DBDeployer.java:425)
... 14 more
Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected
character '3' (code 51) (expected a name start character)
at [row,col {unknown-source}]: [6,58]
at
com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:648)
at
com.ctc.wstx.sr.StreamScanner.parseFullName(StreamScanner.java:1861)
at
com.ctc.wstx.sr.StreamScanner.parseEntityName(StreamScanner.java:1985)***
*
at
com.ctc.wstx.sr.StreamScanner.fullyResolveEntity(StreamScanner.java:1496)
at
com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamReader.java:2757)
at
com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1019)
at
org.apache.axiom.util.stax.wrapper.XMLStreamReaderWrapper.next(XMLStreamReaderWrapper.java:225)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:681)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:214)
... 17 more
** **
Thanks,
** **
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
--
*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
--
*Amila Suriarachchi*
Software Architect
WSO2 Inc. ; http://wso2.com
lean . enterprise . middleware
phone : +94 71 3082805
___
Carbon-dev
Re: [Carbon-dev] Performance numbers of Agent Component
On Thu, Feb 9, 2012 at 11:47 AM, Tharindu Mathew thari...@wso2.com wrote: Suho, This does not measure the ability to handle load. Basically, what we did for load testing earlier was send around 2M messages, with concurrency as high increasing from 100 - 1500 clients. How many back end servers and client programs used for that? Your test is a measure of being able to consistently handle a stream of messages, which IMO, maybe important but is less interesting when handling load. This test has measured the one client one server. yes it can be improved to one client to many servers and many clients to many servers. But this test gives the through put this can handle one client to server. For one client scenario whether you add messages with one thread or many threads does not effect the performance if there are enough messages to send. thanks, Amila. To truly test the ability to handle loads we need to do a distributed load test with an extremely high number of clients and see the breaking point. Earlier, we could not find such a point with a single machine. On Thu, Feb 9, 2012 at 11:31 AM, Suhothayan Sriskandarajah s...@wso2.comwrote: On Thu, Feb 9, 2012 at 11:24 AM, Amila Suriarachchi am...@wso2.comwrote: through put should not depend on the number of messages send. You need to send sufficient number of messages after server warmed up. Can you please first send around 2M messages and take the numbers for next 10M messages. And also try to test with number of back end servers. Yes, I'll work on this Thanks Suho thanks, Amila. On Wed, Feb 8, 2012 at 9:25 PM, Suhothayan Sriskandarajah s...@wso2.com wrote: According to the decisions made at the architecture mailing list on the subject Serializing generic Siddhi events using Thrift, I did some improvements to the code base of Agent component and did a performance testing. Here I did the tests by sending total of 1 million and 10 million events using for loop, in both cases I have sent events using 1,2,5,10 20 Clients. The results are as follows *1M 10M* *1* 245118.1269328.8 *2* 517509.1739699.7 *5* 585823.1923986.7 *10*345582.3418865.7 *20*285008.6368881.2 I have also attached the performance graph Regards Suho -- *S. Suhothayan * Software Engineer, Data Technologies Team, *WSO2, Inc. **http://wso2.com http://wso2.com/* *lean.enterprise.middleware.* *email: **s...@wso2.com* s...@wso2.com* cell: (+94) 779 756 757 blog: **http://suhothayan.blogspot.com/*http://suhothayan.blogspot.com/ * twitter: **http://twitter.com/suhothayan*http://twitter.com/suhothayan * linked-in: **http://lk.linkedin.com/in/suhothayan* * * -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 -- *S. Suhothayan * Software Engineer, Data Technologies Team, *WSO2, Inc. **http://wso2.com http://wso2.com/* *lean.enterprise.middleware.* *email: **s...@wso2.com* s...@wso2.com* cell: (+94) 779 756 757 blog: **http://suhothayan.blogspot.com/*http://suhothayan.blogspot.com/ * twitter: **http://twitter.com/suhothayan* http://twitter.com/suhothayan * linked-in: **http://lk.linkedin.com/in/suhothayan* * * -- Regards, Tharindu blog: http://mackiemathew.com/ M: +9459908 -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] [Architecture] [Proposal] Restructuring the SVN repository of Carbon
On Mon, Feb 6, 2012 at 12:57 PM, Sameera Jayasoma same...@wso2.com wrote: I agree that the orbits project should not be a part of the Carbon or Carbon based products. Therefore we can make it a top level project, say carbon-orbits. But I am not sure whether we need to remove dependencies from the carbon svn project. It will complicate things. When we release Carbon core, we need to release only the dependencies of Carbon. Therefore we need to have a separation of dependencies. What I thought was not the dependencies as a whole. we don't need a new dependency version for each carbon core release. Lets say we did carbon 3.0.0 on axis2 1.6.1.wso2v1. Then we can either do the carbon 4.0.0 on axis2 1.6.1.wsov1 or v2. in the former case we don't need to do any axis2 release. But for latter case we can only release axis2 1.6.1.wso2v2. Same way for the components. if the dependency is not part of carbon core, then new release version can be done and release the component. if the dependencies you have mentioned only pointing to the such newer versions both do the same. thanks, Amila. IMV, service-stubs are part of the project. And aslo they are still undergoing changes. Therefore I would consider keeping the service-stubs separately in each of the projects. Please comment, if you have different views. Here is revised svn structure based on the received comments. carbon-orbits carbon |--dependencies |--orbits (To wrap dependencies as orbit bundles. These cannot be added to the top level carbon-orbits project. ) |--service-stubs |--core (core set of bundles.) |--features (Carbon core features) |--product (Carbon product) X (TODO we need to come up with a name. How about silicon. Dr. Sanjiva once mentioned this name. :) ) |--dependencies |--orbits (To wrap dependencies as orbit bundles. These cannot be added to the top level carbon-orbits project. ) |--service-stubs |--components |--features |--products Thanks, Sameera On Sun, Feb 5, 2012 at 11:50 AM, Amila Suriarachchi am...@wso2.comwrote: I think first we need to remove the dependencies and orbit from the carbon structure since they have nothing to do with carbon. Simply they produce a set of third party osgi bundles to be used with carbon. Same thing may be applied to service stubs since they only depend on the wsdl version. we can increment the service stubs version when the wsdl version or axis2 version changes (if required). for carbon we can have the structure you have suggested. If we think carbon components and features as independent entities, then they can have an independent truck branches etc .. Same thing can be done with products. Products can have its own trunk and branches and branch can always refer to released feature versions. But this model can lead to complications when installing other features to different products. thanks, Amila. On Sat, Feb 4, 2012 at 8:15 PM, Tharindu Mathew thari...@wso2.comwrote: ++1, for the execution On Sat, Feb 4, 2012 at 5:57 PM, Senaka Fernando sen...@wso2.com wrote: Hi Sameera, Pradeep, +1, but X should probably be a name of a derivative/allotrope of Carbon (like Diamond or Graphite) which makes our code names more meaningful. I really like the idea of having two-levels of dependencies and orbits very much, which simplifies the effort of doing a carbon release and sticking to that. Carbon must be just like the Linux kernel, and it can have its own release schedule. Please also note that carbon should continue to have a concept of service-stubs which can be reused by other components, and should also have an integration area. Thanks, Senaka. On Sat, Feb 4, 2012 at 5:16 PM, Pradeep Fernando prad...@wso2.comwrote: +1 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando * Lean . Enterprise . Middleware ___ Architecture mailing list architect...@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Regards, Tharindu blog: http://mackiemathew.com/ M: +9459908 ___ Architecture mailing list architect...@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Architecture mailing list architect...@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Carbon-dev] Enabling Broker component to support all JMS brokers
On Mon, Feb 6, 2012 at 6:24 PM, Paul Fremantle p...@wso2.com wrote: Suho What is the use case for this? Users can already use ActiveMQ with the ESB and other products via the JMS transport. There was (I think) a lot more work involved in adding QPid as a broker including tying into the Identity / User Manager as well as support for Multi-tenancy. Here we don't add ActiveMQ as a broker to carbon platform. This use case comes from the CEP side. This broker refers to the brokers CEP used to receive events from different real brokers. Idea is to be able to consume messages publish to a jms topic in an ActiveMQ broker in an CEP Bucket. thanks, Amila. Paul On 6 February 2012 07:04, Suhothayan Sriskandarajah s...@wso2.com wrote: Currently Broker component only supports Qpid broker and it doesn't have the ability to send messages to other JMS brokers. This is because the provider url used to create the connection is programmatically build using the username, password, ip address, port and virtual machine name. Now I'm is the process of extending Broker's functionality to support ActiveMQ. In this process I can either programmatically build the provider url of the ActiveMQ or I can generalize the process by asking the user to add the provider url itself. In both cases users need to add the relevant broker jars (activemq or other ) to the libs. Here since we are shipping Qpid I thought it will be appropriate for the user to have two UIs, one Qpid specific and the other a general JMS UI which will ask for prover url and JNDI class name. Please give your ideas on this approach Thanks Suho -- *S. Suhothayan * Software Engineer *WSO2, Inc. *http://wso2.com lean.enterprise.middleware. *email: **s...@wso2.com* s...@wso2.com* cell: (+94) 779 756 757 blog: **http://suhothayan.blogspot.com/*http://suhothayan.blogspot.com/ * twitter: **http://twitter.com/suhothayan* http://twitter.com/suhothayan * linked-in: **http://lk.linkedin.com/in/suhothayan* * * ___ 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 addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Enabling Broker component to support all JMS brokers
On Mon, Feb 6, 2012 at 7:48 PM, Paul Fremantle p...@wso2.com wrote: Aha ok that is much clearer :-) So basically this is a JMS transport for CEP? yes. thanks, Amila. Paul On 6 February 2012 13:25, Amila Suriarachchi am...@wso2.com wrote: On Mon, Feb 6, 2012 at 6:24 PM, Paul Fremantle p...@wso2.com wrote: Suho What is the use case for this? Users can already use ActiveMQ with the ESB and other products via the JMS transport. There was (I think) a lot more work involved in adding QPid as a broker including tying into the Identity / User Manager as well as support for Multi-tenancy. Here we don't add ActiveMQ as a broker to carbon platform. This use case comes from the CEP side. This broker refers to the brokers CEP used to receive events from different real brokers. Idea is to be able to consume messages publish to a jms topic in an ActiveMQ broker in an CEP Bucket. thanks, Amila. Paul On 6 February 2012 07:04, Suhothayan Sriskandarajah s...@wso2.comwrote: Currently Broker component only supports Qpid broker and it doesn't have the ability to send messages to other JMS brokers. This is because the provider url used to create the connection is programmatically build using the username, password, ip address, port and virtual machine name. Now I'm is the process of extending Broker's functionality to support ActiveMQ. In this process I can either programmatically build the provider url of the ActiveMQ or I can generalize the process by asking the user to add the provider url itself. In both cases users need to add the relevant broker jars (activemq or other ) to the libs. Here since we are shipping Qpid I thought it will be appropriate for the user to have two UIs, one Qpid specific and the other a general JMS UI which will ask for prover url and JNDI class name. Please give your ideas on this approach Thanks Suho -- *S. Suhothayan * Software Engineer *WSO2, Inc. *http://wso2.com lean.enterprise.middleware. *email: **s...@wso2.com* s...@wso2.com* cell: (+94) 779 756 757 blog: **http://suhothayan.blogspot.com/*http://suhothayan.blogspot.com/ * twitter: **http://twitter.com/suhothayan*http://twitter.com/suhothayan * linked-in: **http://lk.linkedin.com/in/suhothayan* * * ___ 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 addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ 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 addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Carbon-dev mailing list
Re: [Carbon-dev] [Architecture] [Proposal] Restructuring the SVN repository of Carbon
On Sat, Feb 4, 2012 at 5:14 PM, Sameera Jayasoma same...@wso2.com wrote: *Objective*: Make Carbon core a top level project in WSO2 trunk. At the moment complete Carbon platform code lies under https://svn.wso2.org/repos/wso2/trunk/carbon/. This structure has its own problems. *Motivations*: 1) Carbon core can be treated as a separate product which has its own dependencies, orbit and Carbon core can be released independently of other Carbon components, products. 2) To ensure that the Carbon based products can depend on a stable, well tested and released version of Carbon instead of the Carbon trunk. 3) This will also ensure the stability of the Carbon based products, because they are no longer depend on the Carbon trunk which might undergo drastic changes time to time. *Execution*: Here is my proposal. 1) We need to create two top level directories for Carbon and for components, features and Carbon based products. Sample structure is shown below. carbon |--dependencies |--orbits |--core (core set of bundles.) |--features (Carbon core features) |--product (Carbon product) X (TODO we need to come up with a name. How about silicon. Dr. Sanjiva once mentioned this name. :) ) |--dependencies |--orbits |--components |--features |--products 2) In order to change the existing svn structure to a structure like above, we need to hold all the commits, say for two to three days and restructure the SVN, test properly and release for commits. Please feel free to comment. Are we going to keep the same carbon version to the features? if not how we going to handle the feature repose? currently feature repos are named with carbon versions. thanks, Amila. Thanks, Sameera. -- 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 ___ Architecture mailing list architect...@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] [Architecture] [Proposal] Restructuring the SVN repository of Carbon
On Mon, Feb 6, 2012 at 8:24 AM, Sumedha Rubasinghe sume...@wso2.com wrote: +1 for the idea. B4 doing the actual change, how about running through different scenarios (like Amila mentioned) - like how we did for branching approach. Figuring out problems later would be costly in terms of time. +1. That is what I try to say as well. We need to think all the uses which are working with current model and see how they work with new system. thanks, Amila. /sumedha On Sat, Feb 4, 2012 at 5:14 PM, Sameera Jayasoma same...@wso2.com wrote: *Objective*: Make Carbon core a top level project in WSO2 trunk. At the moment complete Carbon platform code lies under https://svn.wso2.org/repos/wso2/trunk/carbon/. This structure has its own problems. *Motivations*: 1) Carbon core can be treated as a separate product which has its own dependencies, orbit and Carbon core can be released independently of other Carbon components, products. 2) To ensure that the Carbon based products can depend on a stable, well tested and released version of Carbon instead of the Carbon trunk. 3) This will also ensure the stability of the Carbon based products, because they are no longer depend on the Carbon trunk which might undergo drastic changes time to time. *Execution*: Here is my proposal. 1) We need to create two top level directories for Carbon and for components, features and Carbon based products. Sample structure is shown below. carbon |--dependencies |--orbits |--core (core set of bundles.) |--features (Carbon core features) |--product (Carbon product) X (TODO we need to come up with a name. How about silicon. Dr. Sanjiva once mentioned this name. :) ) |--dependencies |--orbits |--components |--features |--products 2) In order to change the existing svn structure to a structure like above, we need to hold all the commits, say for two to three days and restructure the SVN, test properly and release for commits. Please feel free to comment. Thanks, Sameera. -- 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 ___ Architecture mailing list architect...@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- /sumedha +94 773017743 ___ Architecture mailing list architect...@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Fix for Registry Deadlocking
have an auto_increment id, which will do a table wide lock, and will affect the above delete statements. So in the current way, we just reverse the DELETE statements, because there is a foreign key constraint on it, it has to be deleted in that order. So we can do one of the following, 1. Remove the foreign key constraint from REG_RESOURCE for REG_CONTENT_ID. 2. Put a cascading delete when defining the REG_RESOURCE, the two deletes then should happen atomically (hopefully). 3. Swap the INSERTs and in the first INSERT to insert the REG_RESOURCE, leave REG_CONTENT_ID empty, then insert the REG_CONTENT, then do an UPDATE on the earlier inserted REG_RESOURCE to set the REG_CONTENT_ID. From the above, I guess 3'rd option would be the easiest to implement with less changes. 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 -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Fix for Registry Deadlocking
On Mon, Feb 6, 2012 at 11:35 AM, Anjana Fernando anj...@wso2.com wrote: Hi Amila, On Mon, Feb 6, 2012 at 10:30 AM, Amila Suriarachchi am...@wso2.comwrote: On Mon, Feb 6, 2012 at 12:50 AM, Senaka Fernando sen...@wso2.com wrote: Hi all, We discussed this offline, and the issue here is valid, Anjana can explain further if someone wants to understand it. Can you please do that? I also thought (as Senaka mentioned) update sequence should be consistent across different transaction scenarios. In that case we need to study all the sql update patterns of the registry and put them to same lock acquiring sequence. I guess, that's what we just did. Updating scenarios are basically registry put and delete. The put operations actually does delete ones internally (when updating), so we aligned the actual inserts/delete sequences. So now, the separate delete operation also will also run in the same lock acquiring sequence. In that case you need to check all the transaction scenarios of the registry and see whether they acquire the locks in same order. Otherwise you will get deadlocks when the incompatible two transactions executed in parallel. It does not matter whether one registry transaction calls or not but finally all the database level transactions should acquire the locks in same order. thanks, Amila. Cheers, Anjana. thanks, Amila. But out of the three options, right now, only #3 seems to be possible without breaking consistency. But even this needs to be tested against all DBs, because we are momentarily fooling the DB, by inserting a NULL value as the content id. Anjana will work with someone (perhaps Ajith), who knows the registry kernel and get this fix checked in. We can easily test this with a bulk WSDL upload operation, that produces deadlocks. Thanks, Senaka. On Mon, Feb 6, 2012 at 12:08 AM, Senaka Fernando sen...@wso2.comwrote: Hi again, And with regard to #3, if that's a safe option go for it. That's probably due to somebody not realizing the possibility. Anyway, I'm not the expert when it comes to SQL stuff, may be Sumedha can provide some insight? Thanks, Senaka. On Mon, Feb 6, 2012 at 12:06 AM, Senaka Fernando sen...@wso2.comwrote: Hi Anjana, So is this a complete sequence of operations? If so, once a write lock is acquired, IIRC it will be held until the transaction completes - am I missing something? Also, there are some INSERT statements above the deletes. What about those? Thanks, Senaka. On Mon, Feb 6, 2012 at 12:00 AM, Anjana Fernando anj...@wso2.comwrote: Hi, I may have possibly found a solution for the registry deadlocking for concurrent puts/deletes. I was checking the SQL statements executed for a put, and the list is as follows. SELECT REG_PATH_ID FROM REG_PATH WHERE REG_PATH_VALUE='/_system/config/abc1' AND REG_TENANT_ID=0 SELECT REG_VERSION FROM REG_RESOURCE WHERE REG_PATH_ID=4 AND REG_NAME='abc1' AND REG_TENANT_ID=0 SELECT REG_PATH_ID FROM REG_PATH WHERE REG_PATH_VALUE='/_system/config/abc1' AND REG_TENANT_ID=0 SELECT REG_MEDIA_TYPE, REG_CREATOR, REG_CREATED_TIME, REG_LAST_UPDATOR, REG_LAST_UPDATED_TIME, REG_VERSION, REG_DESCRIPTION, REG_CONTENT_ID FROM REG_RESOURCE WHERE REG_PATH_ID=4 AND REG_NAME = 'abc1' AND REG_TENANT_ID=0 SELECT REG_CONTENT_DATA FROM REG_CONTENT WHERE REG_CONTENT_ID = 105 AND REG_TENANT_ID=0 SELECT REG_NAME, REG_VALUE FROM REG_PROPERTY P, REG_RESOURCE_PROPERTY RP WHERE P.REG_ID=RP.REG_PROPERTY_ID AND RP.REG_VERSION=2492 AND P.REG_TENANT_ID=0 AND RP.REG_TENANT_ID=0 SELECT R.REG_PATH_ID, R.REG_NAME, R.REG_VERSION, R.REG_MEDIA_TYPE, R.REG_CREATOR, R.REG_CREATED_TIME, R.REG_LAST_UPDATOR, R.REG_LAST_UPDATED_TIME, R.REG_DESCRIPTION, R.REG_CONTENT_ID FROM REG_RESOURCE R WHERE R.REG_PATH_ID=4 AND R.REG_NAME='abc1' AND R.REG_TENANT_ID=0 SELECT REG_CONTENT_DATA FROM REG_CONTENT_HISTORY WHERE REG_CONTENT_ID = 105 AND REG_TENANT_ID=0 SELECT REG_CONTENT_DATA FROM REG_CONTENT WHERE REG_CONTENT_ID = 105 AND REG_TENANT_ID=0 INSERT INTO REG_CONTENT_HISTORY (REG_CONTENT_ID, REG_CONTENT_DATA, REG_TENANT_ID) VALUES (105, 'Binary InputStream of length 9', 0) SELECT REG_PATH_ID FROM REG_RESOURCE_HISTORY WHERE REG_VERSION=2492 AND REG_TENANT_ID=0 INSERT INTO REG_RESOURCE_HISTORY (REG_PATH_ID, REG_NAME, REG_VERSION, REG_MEDIA_TYPE, REG_CREATOR, REG_CREATED_TIME, REG_LAST_UPDATOR, REG_LAST_UPDATED_TIME, REG_DESCRIPTION, REG_CONTENT_ID, REG_TENANT_ID) VALUES (4, 'abc1', 2492, 'text/plain', 'admin', '02/05/2012 22:05:18.685', 'admin', '02/05/2012 22:05:55.959', '', 105, 0) DELETE FROM REG_RESOURCE WHERE REG_PATH_ID=4 AND REG_NAME='abc1' AND REG_TENANT_ID=0 DELETE FROM REG_CONTENT WHERE REG_CONTENT_ID = 105 AND REG_TENANT_ID=0 INSERT INTO REG_SNAPSHOT (REG_PATH_ID, REG_RESOURCE_NAME, REG_RESOURCE_VIDS, REG_TENANT_ID) VALUES (4, 'abc1', 'Binary InputStream of length 8', 0) SELECT REG_TARGETPATH, REG_ASSOCIATION_TYPE FROM REG_ASSOCIATION WHERE
Re: [Carbon-dev] [Architecture] [Proposal] Restructuring the SVN repository of Carbon
I think first we need to remove the dependencies and orbit from the carbon structure since they have nothing to do with carbon. Simply they produce a set of third party osgi bundles to be used with carbon. Same thing may be applied to service stubs since they only depend on the wsdl version. we can increment the service stubs version when the wsdl version or axis2 version changes (if required). for carbon we can have the structure you have suggested. If we think carbon components and features as independent entities, then they can have an independent truck branches etc .. Same thing can be done with products. Products can have its own trunk and branches and branch can always refer to released feature versions. But this model can lead to complications when installing other features to different products. thanks, Amila. On Sat, Feb 4, 2012 at 8:15 PM, Tharindu Mathew thari...@wso2.com wrote: ++1, for the execution On Sat, Feb 4, 2012 at 5:57 PM, Senaka Fernando sen...@wso2.com wrote: Hi Sameera, Pradeep, +1, but X should probably be a name of a derivative/allotrope of Carbon (like Diamond or Graphite) which makes our code names more meaningful. I really like the idea of having two-levels of dependencies and orbits very much, which simplifies the effort of doing a carbon release and sticking to that. Carbon must be just like the Linux kernel, and it can have its own release schedule. Please also note that carbon should continue to have a concept of service-stubs which can be reused by other components, and should also have an integration area. Thanks, Senaka. On Sat, Feb 4, 2012 at 5:16 PM, Pradeep Fernando prad...@wso2.comwrote: +1 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando * Lean . Enterprise . Middleware ___ Architecture mailing list architect...@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Regards, Tharindu blog: http://mackiemathew.com/ M: +9459908 ___ Architecture mailing list architect...@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Cannot invoke a service when it manually deployed as an aar in GReg.
Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Carbon build failure
org.wso2.carbon.rule.ws.stub has not been added to service stubs pom.xml will add that. thanks, Amila. On Tue, Jan 24, 2012 at 4:55 PM, Afkham Azeez az...@wso2.com wrote: I got the following failure with a full update this morning; [INFO] WSO2 WSF/Java - Distribution .. SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 2:39:44.779s [INFO] Finished at: Tue Jan 24 15:27:51 IST 2012 [INFO] Final Memory: 882M/1713M [INFO] [ERROR] Failed to execute goal on project org.wso2.carbon.rule.ws.ui: Could not resolve dependencies for project org.wso2.carbon:org.wso2.carbon.rule.ws.ui:bundle:4.0.0-SNAPSHOT: Could not find artifact org.wso2.carbon:org.wso2.carbon.rule.ws.stub:jar:4.0.0-SNAPSHOT in wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/) - [Help 1] [ERROR] -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Data Services Mediator for ESB
On Sun, Jan 22, 2012 at 1:52 PM, Anjana Fernando anj...@wso2.com wrote: Hi Amila, On Sun, Jan 22, 2012 at 8:59 AM, Amila Suriarachchi am...@wso2.comwrote: I think this is not a problem of data related operations. But for a mediator there is non concept of service and operations. It just take an xml and output an xml. So it is like invoking an operation directly. If you look at the rules service and mediator configuration this service and operations are there only with web service part. Rule mediator does not have them (Event architecturly there is no relationship with web service and mediator). I see the confusion there. The idea on using operations in the mediator was to keep the original data service format intact. As in, to re-use the same data service configuration format, so we won't have to create a new separate configuration for that part. And in our current data service configuration, what we have are operations/resources. So we can look it at as an API, rather than a set of operations in a service. And what the mediator does is, pick a certain operations from a set of operations in an API, and call it. yes I do understand that. That is why in real case users have to write a .dbs file which is not shown here. What I am saying is that that may not be the best way to do that when thinking in a mediator perspective. thanks, Amila. Cheers, Anjana. But I also see some use case here as you have mentioned. Where users do need to enrich some xml messages with additional data. (for an example if ESB receives a customer Id this can be used to add all the customer formation with his last orders etc.. which will be send to another service). In this example[1] instead of using a data service we should have used the data service mediator to do that. thanks, Amila. [1] http://wso2.org/library/articles/2012/01/integrating-different-systems-with-wso2-esb So the proposal was actually, not to necessarily ship this mediator by default with the ESB, but to make it a separate feature and to install it on-demand for anyone interested. Cheers, Anjana. Thanks, Hiranya On Sat, Jan 21, 2012 at 11:52 AM, Amila Suriarachchi am...@wso2.comwrote: On Fri, Jan 20, 2012 at 3:00 PM, Dinusha Senanayaka dinu...@wso2.comwrote: Hi Amila, Thanks for the clarifications and feedbacks. On Fri, Jan 20, 2012 at 5:16 PM, Amila Suriarachchi am...@wso2.comwrote: I had a chat with Dinush and suggested to have some thing like this as in rule service. This is also similar to callout mediator calling a data service. Difference is not using the soap/Axis2/tcp layers. dsMediator serviceName= operation= source xpath=// soapBody|soapHeader|$foo|$bar/source target xpath=// resultXpath=soapBody|soapHeader|$foo|$bar/target dbConfig type=inline|registry /dbConfig /dsMediator In this model data service is looked as some thing take an xml and outputs an xml. source is the way mediator finds the xml to invoke DS and target is the place it stores the result xml. Earlier what we have suggested is to map the input parameters one by one using xpath or provide them as inline or map the whole set of parameters @ once using xpath. In new suggested way, we have only above last option and need to have the xml that can be directly used to call operation or do some xslt transformation and make the incoming soap body to have that xml. When you say using xpath then we need to think against which OMElement? that can be soapBody, soapHeader or an xml stored in a property. yes it is better to have parameter xpath support. I thought Data Serivice support that at the .dbs level. If not it may be more meaning full to add that the data service level. Can you please send a sample mediator configuration with the .dbs file for paramter xpath case? thanks, Amila. The source can be soapBody, soapHeader or a property and we can get a portion of that using xpath. Then again when the result came back it can be saved in any place and a part of the result can be selected using resultXpath and can be stored in a location given by xpath. Regards, Dinusha. thanks, Amila. On Thu, Jan 19, 2012 at 7:25 PM, Amila Suriarachchi am...@wso2.comwrote: On Wed, Jan 18, 2012 at 5:03 PM, Dinusha Senanayaka dinu...@wso2.com wrote: Hi All, We are going to develop a ESB mediator which can be shipped as a feature and once this feature is installed within ESB, the DS mediator can be used to make data services calls in-line, without making actual SOAP requests, but it will use in-memory calls to invoke data service operations. I think first you need to think the features this mediator going provide for an ESB user and hence what type of interface expect from the mediator configuration. For an example I am not seeing much relevance of service/operation resource here. Then think about the mediator configuration according
Re: [Carbon-dev] Data Services Mediator for ESB
On Sun, Jan 22, 2012 at 11:18 AM, Hiranya Jayathilaka hira...@wso2.comwrote: Hi, On Sat, Jan 21, 2012 at 11:54 PM, Anjana Fernando anj...@wso2.com wrote: Hi Hiranya, On Sat, Jan 21, 2012 at 6:37 PM, Hiranya Jayathilaka hira...@wso2.comwrote: I'm not entirely on board with the idea of running ESB functionality and DSS functionality on the same box/JVM. From SOA perspective it is best to keep these components separate as there could be several consumers who are interested in accessing the data exposed by the data service. Also performance wise the existing model is better because we can take advantage of the non-blocking model of the ESB to invoke data services without much overhead on the ESB. What is the exact problem you're trying to solve here? I guess, maybe we didn't describe this properly :) .. The idea is not to deploy a data service as a web service in the ESB. But it's just a way to have something like extended DBReport/DBLookup functionality. My argument was from SOA perspective it's better to have data services as a separate component exposed as 'web services' :) Also from a performance point of view that relieves the ESB from making expensive JDBC calls. With the current model server worker threads are released as soon as they invoke the data services. But with the suggested mediator approach server worker threads will do lot more work thus adding up to decreased throughput. It works in the same way, where the mediator execution comprises simply of in-VM calls, basically calling directly the data services API. The idea was to give more richer functionality, than the DB-* mediators we have now. In the current way, even to do some simple operations such as, reading multiple records from the database, you can't do that with DBLookup, but you'll have to call an external DSS sever to get it done, which may not be the ideal solution all the time, specially, if it makes no sense to have the data related operations as a service. So the proposal was actually, not to necessarily ship this mediator by default with the ESB, but to make it a separate feature and to install it on-demand for anyone interested. In a way this proposal is good because it provides some middle ground between using data services and DB mediators. But OTOH it provides a third option to access databases adding up to the existing confusion with two options. I guess this is one of those things that we can argue forever pointing out various pros and cons without coming to a conclusion :) So I'm ok with having this as an optional feature. As Amila pointed out there will always be some users who find this useful. But lets make this a point to properly document the 3 approaches pointing out strengths, weaknesses and potential use cases of each technique. With the current ESB there are two ways to invoke data services. Using call out mediator or end point. If you use call out mediator then that will block the threads. So we can think of new approach as way of alternative for using call out mediator in terms of reducing system latency. Further the over head ESB have to do for send an XML message I think greater than to do a JDBC call. thanks, Amila. Thanks, Hiranya Cheers, Anjana. Thanks, Hiranya On Sat, Jan 21, 2012 at 11:52 AM, Amila Suriarachchi am...@wso2.comwrote: On Fri, Jan 20, 2012 at 3:00 PM, Dinusha Senanayaka dinu...@wso2.comwrote: Hi Amila, Thanks for the clarifications and feedbacks. On Fri, Jan 20, 2012 at 5:16 PM, Amila Suriarachchi am...@wso2.comwrote: I had a chat with Dinush and suggested to have some thing like this as in rule service. This is also similar to callout mediator calling a data service. Difference is not using the soap/Axis2/tcp layers. dsMediator serviceName= operation= source xpath=// soapBody|soapHeader|$foo|$bar/source target xpath=// resultXpath=soapBody|soapHeader|$foo|$bar/target dbConfig type=inline|registry /dbConfig /dsMediator In this model data service is looked as some thing take an xml and outputs an xml. source is the way mediator finds the xml to invoke DS and target is the place it stores the result xml. Earlier what we have suggested is to map the input parameters one by one using xpath or provide them as inline or map the whole set of parameters @ once using xpath. In new suggested way, we have only above last option and need to have the xml that can be directly used to call operation or do some xslt transformation and make the incoming soap body to have that xml. When you say using xpath then we need to think against which OMElement? that can be soapBody, soapHeader or an xml stored in a property. yes it is better to have parameter xpath support. I thought Data Serivice support that at the .dbs level. If not it may be more meaning full to add that the data service level. Can you please send a sample mediator configuration with the .dbs file
Re: [Carbon-dev] Data Services Mediator for ESB
On Sat, Jan 21, 2012 at 11:54 PM, Anjana Fernando anj...@wso2.com wrote: Hi Hiranya, On Sat, Jan 21, 2012 at 6:37 PM, Hiranya Jayathilaka hira...@wso2.comwrote: I'm not entirely on board with the idea of running ESB functionality and DSS functionality on the same box/JVM. From SOA perspective it is best to keep these components separate as there could be several consumers who are interested in accessing the data exposed by the data service. Also performance wise the existing model is better because we can take advantage of the non-blocking model of the ESB to invoke data services without much overhead on the ESB. What is the exact problem you're trying to solve here? I guess, maybe we didn't describe this properly :) .. The idea is not to deploy a data service as a web service in the ESB. But it's just a way to have something like extended DBReport/DBLookup functionality. It works in the same way, where the mediator execution comprises simply of in-VM calls, basically calling directly the data services API. The idea was to give more richer functionality, than the DB-* mediators we have now. In the current way, even to do some simple operations such as, reading multiple records from the database, you can't do that with DBLookup, but you'll have to call an external DSS sever to get it done, which may not be the ideal solution all the time, specially, if it makes no sense to have the data related operations as a service. I think this is not a problem of data related operations. But for a mediator there is non concept of service and operations. It just take an xml and output an xml. So it is like invoking an operation directly. If you look at the rules service and mediator configuration this service and operations are there only with web service part. Rule mediator does not have them (Event architecturly there is no relationship with web service and mediator). But I also see some use case here as you have mentioned. Where users do need to enrich some xml messages with additional data. (for an example if ESB receives a customer Id this can be used to add all the customer formation with his last orders etc.. which will be send to another service). In this example[1] instead of using a data service we should have used the data service mediator to do that. thanks, Amila. [1] http://wso2.org/library/articles/2012/01/integrating-different-systems-with-wso2-esb So the proposal was actually, not to necessarily ship this mediator by default with the ESB, but to make it a separate feature and to install it on-demand for anyone interested. Cheers, Anjana. Thanks, Hiranya On Sat, Jan 21, 2012 at 11:52 AM, Amila Suriarachchi am...@wso2.comwrote: On Fri, Jan 20, 2012 at 3:00 PM, Dinusha Senanayaka dinu...@wso2.comwrote: Hi Amila, Thanks for the clarifications and feedbacks. On Fri, Jan 20, 2012 at 5:16 PM, Amila Suriarachchi am...@wso2.comwrote: I had a chat with Dinush and suggested to have some thing like this as in rule service. This is also similar to callout mediator calling a data service. Difference is not using the soap/Axis2/tcp layers. dsMediator serviceName= operation= source xpath=// soapBody|soapHeader|$foo|$bar/source target xpath=// resultXpath=soapBody|soapHeader|$foo|$bar/target dbConfig type=inline|registry /dbConfig /dsMediator In this model data service is looked as some thing take an xml and outputs an xml. source is the way mediator finds the xml to invoke DS and target is the place it stores the result xml. Earlier what we have suggested is to map the input parameters one by one using xpath or provide them as inline or map the whole set of parameters @ once using xpath. In new suggested way, we have only above last option and need to have the xml that can be directly used to call operation or do some xslt transformation and make the incoming soap body to have that xml. When you say using xpath then we need to think against which OMElement? that can be soapBody, soapHeader or an xml stored in a property. yes it is better to have parameter xpath support. I thought Data Serivice support that at the .dbs level. If not it may be more meaning full to add that the data service level. Can you please send a sample mediator configuration with the .dbs file for paramter xpath case? thanks, Amila. The source can be soapBody, soapHeader or a property and we can get a portion of that using xpath. Then again when the result came back it can be saved in any place and a part of the result can be selected using resultXpath and can be stored in a location given by xpath. Regards, Dinusha. thanks, Amila. On Thu, Jan 19, 2012 at 7:25 PM, Amila Suriarachchi am...@wso2.comwrote: On Wed, Jan 18, 2012 at 5:03 PM, Dinusha Senanayaka dinu...@wso2.com wrote: Hi All, We are going to develop a ESB mediator which can be shipped as a feature and once this feature is installed within ESB
Re: [Carbon-dev] Data Services Mediator for ESB
On Sun, Jan 22, 2012 at 11:24 AM, Hiranya Jayathilaka hira...@wso2.comwrote: On Sun, Jan 22, 2012 at 8:59 AM, Amila Suriarachchi am...@wso2.comwrote: On Sat, Jan 21, 2012 at 11:54 PM, Anjana Fernando anj...@wso2.comwrote: Hi Hiranya, On Sat, Jan 21, 2012 at 6:37 PM, Hiranya Jayathilaka hira...@wso2.comwrote: I'm not entirely on board with the idea of running ESB functionality and DSS functionality on the same box/JVM. From SOA perspective it is best to keep these components separate as there could be several consumers who are interested in accessing the data exposed by the data service. Also performance wise the existing model is better because we can take advantage of the non-blocking model of the ESB to invoke data services without much overhead on the ESB. What is the exact problem you're trying to solve here? I guess, maybe we didn't describe this properly :) .. The idea is not to deploy a data service as a web service in the ESB. But it's just a way to have something like extended DBReport/DBLookup functionality. It works in the same way, where the mediator execution comprises simply of in-VM calls, basically calling directly the data services API. The idea was to give more richer functionality, than the DB-* mediators we have now. In the current way, even to do some simple operations such as, reading multiple records from the database, you can't do that with DBLookup, but you'll have to call an external DSS sever to get it done, which may not be the ideal solution all the time, specially, if it makes no sense to have the data related operations as a service. I think this is not a problem of data related operations. But for a mediator there is non concept of service and operations. It just take an xml and output an xml. So it is like invoking an operation directly. If you look at the rules service and mediator configuration this service and operations are there only with web service part. Rule mediator does not have them (Event architecturly there is no relationship with web service and mediator). But I also see some use case here as you have mentioned. Where users do need to enrich some xml messages with additional data. (for an example if ESB receives a customer Id this can be used to add all the customer formation with his last orders etc.. which will be send to another service). In this example[1] instead of using a data service we should have used the data service mediator to do that. I prefer data services in this scenario for 2 reasons: 1. Batch operations are really expensive - Better to offload that overhead from the ESB 2. There could be other applications pumping orders into the same DB you can think of reducing ESB over head vs Overall system over head (hence the system response time). As you have said usefulness depends on the use case and overall requirements. thanks, Amila. Thanks, Hiranya thanks, Amila. [1] http://wso2.org/library/articles/2012/01/integrating-different-systems-with-wso2-esb So the proposal was actually, not to necessarily ship this mediator by default with the ESB, but to make it a separate feature and to install it on-demand for anyone interested. Cheers, Anjana. Thanks, Hiranya On Sat, Jan 21, 2012 at 11:52 AM, Amila Suriarachchi am...@wso2.comwrote: On Fri, Jan 20, 2012 at 3:00 PM, Dinusha Senanayaka dinu...@wso2.comwrote: Hi Amila, Thanks for the clarifications and feedbacks. On Fri, Jan 20, 2012 at 5:16 PM, Amila Suriarachchi am...@wso2.comwrote: I had a chat with Dinush and suggested to have some thing like this as in rule service. This is also similar to callout mediator calling a data service. Difference is not using the soap/Axis2/tcp layers. dsMediator serviceName= operation= source xpath=// soapBody|soapHeader|$foo|$bar/source target xpath=// resultXpath=soapBody|soapHeader|$foo|$bar/target dbConfig type=inline|registry /dbConfig /dsMediator In this model data service is looked as some thing take an xml and outputs an xml. source is the way mediator finds the xml to invoke DS and target is the place it stores the result xml. Earlier what we have suggested is to map the input parameters one by one using xpath or provide them as inline or map the whole set of parameters @ once using xpath. In new suggested way, we have only above last option and need to have the xml that can be directly used to call operation or do some xslt transformation and make the incoming soap body to have that xml. When you say using xpath then we need to think against which OMElement? that can be soapBody, soapHeader or an xml stored in a property. yes it is better to have parameter xpath support. I thought Data Serivice support that at the .dbs level. If not it may be more meaning full to add that the data service level. Can you please send a sample mediator configuration with the .dbs file for paramter xpath case
Re: [Carbon-dev] Data Services Mediator for ESB
I had a chat with Dinush and suggested to have some thing like this as in rule service. This is also similar to callout mediator calling a data service. Difference is not using the soap/Axis2/tcp layers. dsMediator serviceName= operation= source xpath=// soapBody|soapHeader|$foo|$bar/source target xpath=// resultXpath=soapBody|soapHeader|$foo|$bar/target dbConfig type=inline|registry /dbConfig /dsMediator In this model data service is looked as some thing take an xml and outputs an xml. source is the way mediator finds the xml to invoke DS and target is the place it stores the result xml. The source can be soapBody, soapHeader or a property and we can get a portion of that using xpath. Then again when the result came back it can be saved in any place and a part of the result can be selected using resultXpath and can be stored in a location given by xpath. thanks, Amila. On Thu, Jan 19, 2012 at 7:25 PM, Amila Suriarachchi am...@wso2.com wrote: On Wed, Jan 18, 2012 at 5:03 PM, Dinusha Senanayaka dinu...@wso2.comwrote: Hi All, We are going to develop a ESB mediator which can be shipped as a feature and once this feature is installed within ESB, the DS mediator can be used to make data services calls in-line, without making actual SOAP requests, but it will use in-memory calls to invoke data service operations. I think first you need to think the features this mediator going provide for an ESB user and hence what type of interface expect from the mediator configuration. For an example I am not seeing much relevance of service/operation resource here. Then think about the mediator configuration according to that and implement. For an example Rules also has to support both as a web service and a mediator. The idea of rule mediator is to use it as 1. Transformer 2. Rule based content routing If we take the mediation aspect there is not need to have the WS- aspects. For an example ws component only shift with BRS server and Mediation component only shift with ESB. For an instance in the transformation case it can either get the soapBody apply rules and send the result to soapBody (or some part given as an Xpath) thanks, Amila. So this will add the capability to have .dbs file in registry or some other file location and invoke the data-service operations without deploying the .dbs as a data-service and process the response within the ESB. Possible mediator configuration will look as follows: !-- normal request -- dsCall serviceName/servicePath=... !-- serviceName is used when calling to a actually deployed data-service within current service configuration servicePath is used to invoke a operation from .dbs file which has not deployed -- operation/resource name/path=.. / !-- operation name or resource path to be invoke -- params expression=xpath !-- xpath expression is optional, which can be defined to take all input parameters. -- param name=name1 value=value1 /!-- if the xpath expression in params is not provided then provide the parameters in line -- param name=arrayName1 value=arrayVal1 / param name=arrayName1 value=arrayVal2 / param name=.. expression=xpath / !-- inline parameter value can be provided through xpath -- params /operation target expression=xpath / !-- If the xpath is not provided, response message after invoking the operation will added as fist child element of the SOAP body. If an xpath expression is provided then it will set in the given location. /dsCall !-- batch request -- dsCall serviceName/servicePath=... operation/resource name/path=../ params expression=xpath batch expression=xpath !-- xpath expression can be used to define parameter set for a one batch -- param name=name1 value=value1 / param name=arrayName1 value=arrayVal1 / param name=arrayName1 value=arrayVal2 / param name=.. expression=xpath / batch batch ./batch params /dsCall !-- boxcarring -- dsCall serviceName/servicePath=... boxcarring request operation/resource name/path=.. / params expression=xpath param name=name1 value=value1 / param name=arrayName1 value=arrayVal1 / param name=arrayName1 value=arrayVal2 / param name=.. expression=xpath / params /operation /request request .../request /boxcarring target expression=xpath / /dsCall Appreciate any feedback and ideas. Regards, Dinusha. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94
Re: [Carbon-dev] Data Services Mediator for ESB
On Fri, Jan 20, 2012 at 3:00 PM, Dinusha Senanayaka dinu...@wso2.comwrote: Hi Amila, Thanks for the clarifications and feedbacks. On Fri, Jan 20, 2012 at 5:16 PM, Amila Suriarachchi am...@wso2.comwrote: I had a chat with Dinush and suggested to have some thing like this as in rule service. This is also similar to callout mediator calling a data service. Difference is not using the soap/Axis2/tcp layers. dsMediator serviceName= operation= source xpath=// soapBody|soapHeader|$foo|$bar/source target xpath=// resultXpath=soapBody|soapHeader|$foo|$bar/target dbConfig type=inline|registry /dbConfig /dsMediator In this model data service is looked as some thing take an xml and outputs an xml. source is the way mediator finds the xml to invoke DS and target is the place it stores the result xml. Earlier what we have suggested is to map the input parameters one by one using xpath or provide them as inline or map the whole set of parameters @ once using xpath. In new suggested way, we have only above last option and need to have the xml that can be directly used to call operation or do some xslt transformation and make the incoming soap body to have that xml. When you say using xpath then we need to think against which OMElement? that can be soapBody, soapHeader or an xml stored in a property. yes it is better to have parameter xpath support. I thought Data Serivice support that at the .dbs level. If not it may be more meaning full to add that the data service level. Can you please send a sample mediator configuration with the .dbs file for paramter xpath case? thanks, Amila. The source can be soapBody, soapHeader or a property and we can get a portion of that using xpath. Then again when the result came back it can be saved in any place and a part of the result can be selected using resultXpath and can be stored in a location given by xpath. Regards, Dinusha. thanks, Amila. On Thu, Jan 19, 2012 at 7:25 PM, Amila Suriarachchi am...@wso2.comwrote: On Wed, Jan 18, 2012 at 5:03 PM, Dinusha Senanayaka dinu...@wso2.comwrote: Hi All, We are going to develop a ESB mediator which can be shipped as a feature and once this feature is installed within ESB, the DS mediator can be used to make data services calls in-line, without making actual SOAP requests, but it will use in-memory calls to invoke data service operations. I think first you need to think the features this mediator going provide for an ESB user and hence what type of interface expect from the mediator configuration. For an example I am not seeing much relevance of service/operation resource here. Then think about the mediator configuration according to that and implement. For an example Rules also has to support both as a web service and a mediator. The idea of rule mediator is to use it as 1. Transformer 2. Rule based content routing If we take the mediation aspect there is not need to have the WS- aspects. For an example ws component only shift with BRS server and Mediation component only shift with ESB. For an instance in the transformation case it can either get the soapBody apply rules and send the result to soapBody (or some part given as an Xpath) thanks, Amila. So this will add the capability to have .dbs file in registry or some other file location and invoke the data-service operations without deploying the .dbs as a data-service and process the response within the ESB. Possible mediator configuration will look as follows: !-- normal request -- dsCall serviceName/servicePath=... !-- serviceName is used when calling to a actually deployed data-service within current service configuration servicePath is used to invoke a operation from .dbs file which has not deployed -- operation/resource name/path=.. / !-- operation name or resource path to be invoke -- params expression=xpath !-- xpath expression is optional, which can be defined to take all input parameters. -- param name=name1 value=value1 /!-- if the xpath expression in params is not provided then provide the parameters in line -- param name=arrayName1 value=arrayVal1 / param name=arrayName1 value=arrayVal2 / param name=.. expression=xpath / !-- inline parameter value can be provided through xpath -- params /operation target expression=xpath / !-- If the xpath is not provided, response message after invoking the operation will added as fist child element of the SOAP body. If an xpath expression is provided then it will set in the given location. /dsCall !-- batch request -- dsCall serviceName/servicePath=... operation/resource name/path=../ params expression=xpath batch expression=xpath !-- xpath expression can be used to define
Re: [Carbon-dev] Data Services Mediator for ESB
On Wed, Jan 18, 2012 at 5:03 PM, Dinusha Senanayaka dinu...@wso2.comwrote: Hi All, We are going to develop a ESB mediator which can be shipped as a feature and once this feature is installed within ESB, the DS mediator can be used to make data services calls in-line, without making actual SOAP requests, but it will use in-memory calls to invoke data service operations. I think first you need to think the features this mediator going provide for an ESB user and hence what type of interface expect from the mediator configuration. For an example I am not seeing much relevance of service/operation resource here. Then think about the mediator configuration according to that and implement. For an example Rules also has to support both as a web service and a mediator. The idea of rule mediator is to use it as 1. Transformer 2. Rule based content routing If we take the mediation aspect there is not need to have the WS- aspects. For an example ws component only shift with BRS server and Mediation component only shift with ESB. For an instance in the transformation case it can either get the soapBody apply rules and send the result to soapBody (or some part given as an Xpath) thanks, Amila. So this will add the capability to have .dbs file in registry or some other file location and invoke the data-service operations without deploying the .dbs as a data-service and process the response within the ESB. Possible mediator configuration will look as follows: !-- normal request -- dsCall serviceName/servicePath=... !-- serviceName is used when calling to a actually deployed data-service within current service configuration servicePath is used to invoke a operation from .dbs file which has not deployed -- operation/resource name/path=.. / !-- operation name or resource path to be invoke -- params expression=xpath !-- xpath expression is optional, which can be defined to take all input parameters. -- param name=name1 value=value1 /!-- if the xpath expression in params is not provided then provide the parameters in line -- param name=arrayName1 value=arrayVal1 / param name=arrayName1 value=arrayVal2 / param name=.. expression=xpath / !-- inline parameter value can be provided through xpath -- params /operation target expression=xpath / !-- If the xpath is not provided, response message after invoking the operation will added as fist child element of the SOAP body. If an xpath expression is provided then it will set in the given location. /dsCall !-- batch request -- dsCall serviceName/servicePath=... operation/resource name/path=../ params expression=xpath batch expression=xpath !-- xpath expression can be used to define parameter set for a one batch -- param name=name1 value=value1 / param name=arrayName1 value=arrayVal1 / param name=arrayName1 value=arrayVal2 / param name=.. expression=xpath / batch batch ./batch params /dsCall !-- boxcarring -- dsCall serviceName/servicePath=... boxcarring request operation/resource name/path=.. / params expression=xpath param name=name1 value=value1 / param name=arrayName1 value=arrayVal1 / param name=arrayName1 value=arrayVal2 / param name=.. expression=xpath / params /operation /request request .../request /boxcarring target expression=xpath / /dsCall Appreciate any feedback and ideas. Regards, Dinusha. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 placeOrder.rsl Description: Binary data ruleMediator xmlns=http://wso2.org/carbon/rules; backendRuntimeFactory=org.wso2.carbon.rule.backend.drools.DroolsBackendRuntimeFactory sourcesoapBody/source targetsoapBody/target ruleSet rule resourceType=drl sourceType=inline ![CDATA[ package OrderApproval; import samples.userguide.OrderAccept; import samples.userguide.OrderReject; import samples.userguide.PlaceOrder; rule Order Approval Rule dialect mvel no-loop true salience 4 when $placeOrder : PlaceOrder( ( symbol == IBM quantity 10 ) || ( symbol == SUN price 100 ) || ( symbol == MSFT price 50 quantity 200 ) ) then OrderAccept orderAccept = new OrderAccept(); orderAccept.setMessage(Accepted order for: + $placeOrder.quantity + stocks of + $placeOrder.symbol
Re: [Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk WSO2 Carbon - Platform Trunk #125 has FAILED (1 tests failed, no failures were new). Change made by janaka and thilini.
Ishara working on this. thanks, Amila. On Tue, Jan 17, 2012 at 1:14 PM, Bamboo cbuil...@wso2.org wrote: [image: Failed] WSO2 Carbon Trunkhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK/› WSO2 Carbon - Platform Trunkhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK/› #125http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-125/ failed This build was manually triggered by BambooBuilderhttp://builder4.us1.wso2.org:/bamboo/browse/user/bamboo_builder . *1/7696* tests failed. Failing Jobshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-125/ Job Duration Tests[image: Failed] WSO2 Carbon Trunk Build Processhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-125/ (Default Stage) 260 minutes 1 of 7696 failed Logshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-125/log| Artifactshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-125/artifact Code Changeshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-125/commit/ View full change detailshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-125/commit/ janaka http://builder4.us1.wso2.org:/bamboo/browse/author/janaka Fixing test failures 119075 thilinihttp://builder4.us1.wso2.org:/bamboo/browse/author/thilini ui msg customization and add label to add archive page 119074 Testshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-125/test View full test detailshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-125/test 1 Existing Test Failures Test Job TestRuleSet testRuleSethttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-125/test/case/5243095 WSO2 Carbon Trunk Build Processhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-125/test 7 Fixed Tests Test Job EndpointTest testServiceAddingEndpointsWithWsdlhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-125/test/case/1618954 WSO2 Carbon Trunk Build Processhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-125/test EndpointTest testAddWsdlWithEndpointshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-125/test/case/1618951 WSO2 Carbon Trunk Build Processhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-125/test ServiceTest testServiceRenamehttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-125/test/case/1619113 WSO2 Carbon Trunk Build Processhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-125/test ServiceTest testServiceAttachmentshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-125/test/case/1618952 WSO2 Carbon Trunk Build Processhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-125/test ServiceTest testServiceSearchhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-125/test/case/1619440 WSO2 Carbon Trunk Build Processhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-125/test WSDLTest testEditWSDLhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-125/test/case/1618949 WSO2 Carbon Trunk Build Processhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-125/test WSDLTest testAddWSDLhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-125/test/case/1618950 WSO2 Carbon Trunk Build Processhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-JOB1-125/test View Onlinehttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-125 | Add Commentshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONTUNK-WSO2CARBONPLATFORMTRUNK-125?commentMode=true This message was sent by Atlassian Bamboohttp://builder4.us1.wso2.org:/bamboo . If you wish to stop receiving these emails edit your user profilehttp://builder4.us1.wso2.org:/bamboo/profile/userNotifications.actionor notify your administratorhttp://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 -- *Amila Suriarachchi* Software Architect WSO2 Inc
Re: [Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk WSO2 Carbon - Platform Trunk #125 has FAILED (1 tests failed, no failures were new). Change made by janaka and thilini.
profilehttp://builder4.us1.wso2.org:/bamboo/profile/userNotifications.actionor notify your administratorhttp://builder4.us1.wso2.org:/bamboo/viewAdministrators.action . -- Srinath Perera, Ph.D. Senior Software Architect, WSO2 Inc. Visiting Faculty, University of Moratuwa Member, Apache Software Foundation Research Scientist, Lanka Software Foundation Blog: http://srinathsview.blogspot.com/ Photos: http://www.flickr.com/photos/hemapani/ Phone: 0772360902 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Moving back to Apache trunks
On Tue, Jan 3, 2012 at 9:13 AM, Thilina Buddhika thili...@wso2.com wrote: Hi Folks, How about the $subject ? At the moment, we are sticking with the released versions of 3.2.0. Moving to Apache trunks requires some changes in certain Carbon components, for example moving to Neethi 3.0 requires some changes in rampart-* orbit bundles, caching and throttling modules. At the moment, Axis2, Axiom, Rampart, Sandesha trunks are quite stable. I think the only reason we are sticking with these released version is to get the Bamboo build plans stable. Shall we start the migration process once we get there ? +1 thanks, Amila. Thanks, Thilina -- 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 -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Empty SOAP body in request message resulting wrong cache retrieval [Error in Response Caching CARBON-11947]
On Mon, Jan 2, 2012 at 6:17 PM, Shelan Perera she...@wso2.com wrote: This is regarding the issue. [1] To reproduce the scenario i have developed a sample service which has two methods ping1() and ping2() which will return two different strings pinging1 and pinging 2.There are no parameters for the request. 1) When invoke from the try it with response caching enabled second operation returns the same string which is pinging1 instead pinging2.When i invoke from a wrapped client it is successful and return the intended strings. 2) The difference with try it is , with tryit : SOAP body is empty with wrapped client : SOAP Body has soapenv:Body ns1:ping1 xmlns:ns1=http://www.wso2.org/types; / /soapenv:Body The reason is when you have an empty body it cannot differentiate two request and mislead as the previous request (which again has an empty body). Since this happens only with the tryit if we are going to fix we need to resolve it there. What is the best approach to handle it? Does the spec allows to send an empty SOAP body ? Can you send us the wsdl generated from the DSS service? I checked with the 2.6.2 version and the DSS wsdl is set to an empty soap body. According to basic profile[1] you can not use the same input message for two different operations. Therefore this is an issue with DSS and need to fix at the DSS wsdl generation. thanks, Amila. [1] http://www.ws-i.org/Profiles/BasicProfile-1.1.html#Operation_Signatures Thanks, [1] https://wso2.org/jira/browse/CARBON-11947 -- *Shelan Perera* Software Engineer ** *WSO2, Inc. : wso2.com* lean.enterprise.middleware. *Home Page* :shelan.org *Blog* : blog.shelan.org *Linked-i*n :http://www.linkedin.com/pub/shelan-perera/a/194/465 *Twitter* :https://twitter.com/#!/shelan *Mobile* : +94 772 604 402 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Empty SOAP body in request message resulting wrong cache retrieval [Error in Response Caching CARBON-11947]
Can you send the .dbs file for this? Seems like this is not a wsdl generated with a data service. thanks, Amila. On Tue, Jan 3, 2012 at 11:19 AM, Shelan Perera she...@wso2.com wrote: Hi, I checked with DSS Data Services 2.6.0,. I am attaching the wsdl with this. Thanks On Tue, Jan 3, 2012 at 11:13 AM, Amila Suriarachchi am...@wso2.comwrote: On Mon, Jan 2, 2012 at 6:17 PM, Shelan Perera she...@wso2.com wrote: This is regarding the issue. [1] To reproduce the scenario i have developed a sample service which has two methods ping1() and ping2() which will return two different strings pinging1 and pinging 2.There are no parameters for the request. 1) When invoke from the try it with response caching enabled second operation returns the same string which is pinging1 instead pinging2.When i invoke from a wrapped client it is successful and return the intended strings. 2) The difference with try it is , with tryit : SOAP body is empty with wrapped client : SOAP Body has soapenv:Body ns1:ping1 xmlns:ns1=http://www.wso2.org/types; / /soapenv:Body The reason is when you have an empty body it cannot differentiate two request and mislead as the previous request (which again has an empty body). Since this happens only with the tryit if we are going to fix we need to resolve it there. What is the best approach to handle it? Does the spec allows to send an empty SOAP body ? Can you send us the wsdl generated from the DSS service? I checked with the 2.6.2 version and the DSS wsdl is set to an empty soap body. According to basic profile[1] you can not use the same input message for two different operations. Therefore this is an issue with DSS and need to fix at the DSS wsdl generation. thanks, Amila. [1] http://www.ws-i.org/Profiles/BasicProfile-1.1.html#Operation_Signatures Thanks, [1] https://wso2.org/jira/browse/CARBON-11947 -- *Shelan Perera* Software Engineer ** *WSO2, Inc. : wso2.com* lean.enterprise.middleware. *Home Page* :shelan.org *Blog* : blog.shelan.org *Linked-i*n :http://www.linkedin.com/pub/shelan-perera/a/194/465 *Twitter* :https://twitter.com/#!/shelan *Mobile* : +94 772 604 402 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Shelan Perera* Software Engineer ** *WSO2, Inc. : wso2.com* lean.enterprise.middleware. *Home Page* :shelan.org *Blog* : blog.shelan.org *Linked-i*n :http://www.linkedin.com/pub/shelan-perera/a/194/465 *Twitter* :https://twitter.com/#!/shelan *Mobile* : +94 772 604 402 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Empty SOAP body in request message resulting wrong cache retrieval [Error in Response Caching CARBON-11947]
On Tue, Jan 3, 2012 at 11:53 AM, Shelan Perera she...@wso2.com wrote: Hi, I just checked with AS and getting the same error there as well. I am attaching pingSample i used for that. This problem (not compatible with basic profile ) was there in the POJO and I am not sure the AS version you test. I test with the current Axis2 trunk and it is fixed there. thanks, Amila. Thanks On Tue, Jan 3, 2012 at 11:19 AM, Shelan Perera she...@wso2.com wrote: Hi, I checked with DSS Data Services 2.6.0,. I am attaching the wsdl with this. Thanks On Tue, Jan 3, 2012 at 11:13 AM, Amila Suriarachchi am...@wso2.comwrote: On Mon, Jan 2, 2012 at 6:17 PM, Shelan Perera she...@wso2.com wrote: This is regarding the issue. [1] To reproduce the scenario i have developed a sample service which has two methods ping1() and ping2() which will return two different strings pinging1 and pinging 2.There are no parameters for the request. 1) When invoke from the try it with response caching enabled second operation returns the same string which is pinging1 instead pinging2.When i invoke from a wrapped client it is successful and return the intended strings. 2) The difference with try it is , with tryit : SOAP body is empty with wrapped client : SOAP Body has soapenv:Body ns1:ping1 xmlns:ns1=http://www.wso2.org/types; / /soapenv:Body The reason is when you have an empty body it cannot differentiate two request and mislead as the previous request (which again has an empty body). Since this happens only with the tryit if we are going to fix we need to resolve it there. What is the best approach to handle it? Does the spec allows to send an empty SOAP body ? Can you send us the wsdl generated from the DSS service? I checked with the 2.6.2 version and the DSS wsdl is set to an empty soap body. According to basic profile[1] you can not use the same input message for two different operations. Therefore this is an issue with DSS and need to fix at the DSS wsdl generation. thanks, Amila. [1] http://www.ws-i.org/Profiles/BasicProfile-1.1.html#Operation_Signatures Thanks, [1] https://wso2.org/jira/browse/CARBON-11947 -- *Shelan Perera* Software Engineer ** *WSO2, Inc. : wso2.com* lean.enterprise.middleware. *Home Page* :shelan.org *Blog* : blog.shelan.org *Linked-i*n :http://www.linkedin.com/pub/shelan-perera/a/194/465 *Twitter* :https://twitter.com/#!/shelan *Mobile* : +94 772 604 402 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Shelan Perera* Software Engineer ** *WSO2, Inc. : wso2.com* lean.enterprise.middleware. *Home Page* :shelan.org *Blog* : blog.shelan.org *Linked-i*n :http://www.linkedin.com/pub/shelan-perera/a/194/465 *Twitter* :https://twitter.com/#!/shelan *Mobile* : +94 772 604 402 -- *Shelan Perera* Software Engineer ** *WSO2, Inc. : wso2.com* lean.enterprise.middleware. *Home Page* :shelan.org *Blog* : blog.shelan.org *Linked-i*n :http://www.linkedin.com/pub/shelan-perera/a/194/465 *Twitter* :https://twitter.com/#!/shelan *Mobile* : +94 772 604 402 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Qpid in Trunk
On Sun, Jan 1, 2012 at 10:20 AM, Senaka Fernando sen...@wso2.com wrote:
Hi Amila,
On Sun, Jan 1, 2012 at 7:51 AM, Amila Suriarachchi am...@wso2.com wrote:
On Sat, Dec 31, 2011 at 7:04 PM, Senaka Fernando sen...@wso2.com wrote:
Hi again,
I was mistaken. In G-Reg 4.1.1, we have imported, event server, event
common and qpid server features. In trunk, the feature imports in P2
profile are the same.
For branch you need to have Qpid feature and for trunk you can remove it.
Ok.
Also after reading through r117481, its just a fix to the versions, and
has no impact on this.
So, it is not the feature imports but something else as it seems. Can
you check?
if you look at the event feature here[1] it does not include the qpid
feature. So if GReg getting it in the distribution it should be some other
problem. Please check from which feature GReg getting Qpid bundle.
In both branch and trunk, the Qpid feature is directly imported from the
product's P2 profile. So, from what I understand, we have not gotten rid of
the Qpid feature from trunk which is what we should be doing.
hi Senaka,
if the GRegs P2 profile import the Qpid feature, I am not sure why you want
me to look at it. What I am saying is it is not through event feature since
it does not import that.
Also, I just tried out eventing on trunk and it is not working. Have you
made any changes to the code or the way it works? I'm getting,
ERROR {org.wso2.carbon.event.core.internal.delivery.Worker} - Can not
send the notification
org.wso2.carbon.event.core.exception.EventBrokerException: Event
dispatcher with name /registry/notifications is not exists
this dispatcher should register from some registry code. Please check
whether it is working.
thanks,
Amila.
at
org.wso2.carbon.event.core.internal.notify.CarbonNotificationManager.sendNotification(CarbonNotificationManager.java:59)
at
org.wso2.carbon.event.core.internal.delivery.Worker.run(Worker.java:52)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
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:619)
The code in the registry eventing component is identical in branch and
trunk, so I believe that this is directly related to something in the event
component. So, in addition to getting rid of Qpid what should I do?
Thanks,
Senaka.
thanks,
Amila.
[1] https://svn.wso2.org/repos/wso2/trunk/carbon/features/event
Thanks,
Senaka.
On Sat, Dec 31, 2011 at 6:40 PM, Senaka Fernando sen...@wso2.comwrote:
Hi Amila,
I found this in G-Reg (checked ESB and it seems to be ok - not sure
about other products), and yes the Qpid feature is not excluded. I believe
that r117481 did not make it to the trunk. I will fix this and commit.
Thanks,
Senaka.
On Sat, Dec 31, 2011 at 6:02 PM, Amila Suriarachchi am...@wso2.comwrote:
On Sat, Dec 31, 2011 at 5:13 PM, Senaka Fernando sen...@wso2.comwrote:
Hi Amila,
I believe that it was decided to get rid of the embedded Qpid Broker
from products, which was done on the 3.2.x branch. Now when starting the
servers on the trunk I see Qpid is still hanging around. Any reason to
why
this was not removed from trunk?
What is the product? Can you please check whether the product has
explicitly imported that?
thanks
Amila.
Thanks,
Senaka.
--
*Senaka Fernando*
Product Manager - WSO2 Governance Registry;
Associate Technical Lead; WSO2 Inc.; http://wso2.com*
Member; Apache Software Foundation; http://apache.org
E-mail: senaka AT wso2.com
**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
Linked-In: http://linkedin.com/in/senakafernando
*Lean . Enterprise . Middleware
--
*Amila Suriarachchi*
Software Architect
WSO2 Inc. ; http://wso2.com
lean . enterprise . middleware
phone : +94 71 3082805
--
*Senaka Fernando*
Product Manager - WSO2 Governance Registry;
Associate Technical Lead; WSO2 Inc.; http://wso2.com*
Member; Apache Software Foundation; http://apache.org
E-mail: senaka AT wso2.com
**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
Linked-In: http://linkedin.com/in/senakafernando
*Lean . Enterprise . Middleware
--
*Senaka Fernando*
Product Manager - WSO2 Governance Registry;
Associate Technical Lead; WSO2 Inc.; http://wso2.com*
Member; Apache Software Foundation; http://apache.org
E-mail: senaka AT wso2.com
**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
Linked-In: http://linkedin.com/in/senakafernando
*Lean . Enterprise . Middleware
--
*Amila Suriarachchi*
Software Architect
WSO2 Inc
Re: [Carbon-dev] Qpid in Trunk
On Sun, Jan 1, 2012 at 10:20 AM, Senaka Fernando sen...@wso2.com wrote:
Hi Amila,
On Sun, Jan 1, 2012 at 7:51 AM, Amila Suriarachchi am...@wso2.com wrote:
On Sat, Dec 31, 2011 at 7:04 PM, Senaka Fernando sen...@wso2.com wrote:
Hi again,
I was mistaken. In G-Reg 4.1.1, we have imported, event server, event
common and qpid server features. In trunk, the feature imports in P2
profile are the same.
For branch you need to have Qpid feature and for trunk you can remove it.
Ok.
Also after reading through r117481, its just a fix to the versions, and
has no impact on this.
So, it is not the feature imports but something else as it seems. Can
you check?
if you look at the event feature here[1] it does not include the qpid
feature. So if GReg getting it in the distribution it should be some other
problem. Please check from which feature GReg getting Qpid bundle.
In both branch and trunk, the Qpid feature is directly imported from the
product's P2 profile. So, from what I understand, we have not gotten rid of
the Qpid feature from trunk which is what we should be doing.
you still have Qpid feature imported here[1]. Please remove it.
thanks,
Amila.
[1]
https://svn.wso2.org/repos/wso2/trunk/carbon/products/greg/modules/p2-profile-gen/product/pom.xml
Also, I just tried out eventing on trunk and it is not working. Have you
made any changes to the code or the way it works? I'm getting,
ERROR {org.wso2.carbon.event.core.internal.delivery.Worker} - Can not
send the notification
org.wso2.carbon.event.core.exception.EventBrokerException: Event
dispatcher with name /registry/notifications is not exists
at
org.wso2.carbon.event.core.internal.notify.CarbonNotificationManager.sendNotification(CarbonNotificationManager.java:59)
at
org.wso2.carbon.event.core.internal.delivery.Worker.run(Worker.java:52)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
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:619)
The code in the registry eventing component is identical in branch and
trunk, so I believe that this is directly related to something in the event
component. So, in addition to getting rid of Qpid what should I do?
Thanks,
Senaka.
thanks,
Amila.
[1] https://svn.wso2.org/repos/wso2/trunk/carbon/features/event
Thanks,
Senaka.
On Sat, Dec 31, 2011 at 6:40 PM, Senaka Fernando sen...@wso2.comwrote:
Hi Amila,
I found this in G-Reg (checked ESB and it seems to be ok - not sure
about other products), and yes the Qpid feature is not excluded. I believe
that r117481 did not make it to the trunk. I will fix this and commit.
Thanks,
Senaka.
On Sat, Dec 31, 2011 at 6:02 PM, Amila Suriarachchi am...@wso2.comwrote:
On Sat, Dec 31, 2011 at 5:13 PM, Senaka Fernando sen...@wso2.comwrote:
Hi Amila,
I believe that it was decided to get rid of the embedded Qpid Broker
from products, which was done on the 3.2.x branch. Now when starting the
servers on the trunk I see Qpid is still hanging around. Any reason to
why
this was not removed from trunk?
What is the product? Can you please check whether the product has
explicitly imported that?
thanks
Amila.
Thanks,
Senaka.
--
*Senaka Fernando*
Product Manager - WSO2 Governance Registry;
Associate Technical Lead; WSO2 Inc.; http://wso2.com*
Member; Apache Software Foundation; http://apache.org
E-mail: senaka AT wso2.com
**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
Linked-In: http://linkedin.com/in/senakafernando
*Lean . Enterprise . Middleware
--
*Amila Suriarachchi*
Software Architect
WSO2 Inc. ; http://wso2.com
lean . enterprise . middleware
phone : +94 71 3082805
--
*Senaka Fernando*
Product Manager - WSO2 Governance Registry;
Associate Technical Lead; WSO2 Inc.; http://wso2.com*
Member; Apache Software Foundation; http://apache.org
E-mail: senaka AT wso2.com
**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
Linked-In: http://linkedin.com/in/senakafernando
*Lean . Enterprise . Middleware
--
*Senaka Fernando*
Product Manager - WSO2 Governance Registry;
Associate Technical Lead; WSO2 Inc.; http://wso2.com*
Member; Apache Software Foundation; http://apache.org
E-mail: senaka AT wso2.com
**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
Linked-In: http://linkedin.com/in/senakafernando
*Lean . Enterprise . Middleware
--
*Amila Suriarachchi*
Software Architect
WSO2 Inc. ; http://wso2.com
lean . enterprise . middleware
phone : +94 71 3082805
--
*Senaka Fernando*
Product Manager
Re: [Carbon-dev] Qpid in Trunk
On Sat, Dec 31, 2011 at 5:13 PM, Senaka Fernando sen...@wso2.com wrote: Hi Amila, I believe that it was decided to get rid of the embedded Qpid Broker from products, which was done on the 3.2.x branch. Now when starting the servers on the trunk I see Qpid is still hanging around. Any reason to why this was not removed from trunk? What is the product? Can you please check whether the product has explicitly imported that? thanks Amila. Thanks, Senaka. -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Qpid in Trunk
On Sat, Dec 31, 2011 at 7:04 PM, Senaka Fernando sen...@wso2.com wrote: Hi again, I was mistaken. In G-Reg 4.1.1, we have imported, event server, event common and qpid server features. In trunk, the feature imports in P2 profile are the same. For branch you need to have Qpid feature and for trunk you can remove it. Also after reading through r117481, its just a fix to the versions, and has no impact on this. So, it is not the feature imports but something else as it seems. Can you check? if you look at the event feature here[1] it does not include the qpid feature. So if GReg getting it in the distribution it should be some other problem. Please check from which feature GReg getting Qpid bundle. thanks, Amila. [1] https://svn.wso2.org/repos/wso2/trunk/carbon/features/event Thanks, Senaka. On Sat, Dec 31, 2011 at 6:40 PM, Senaka Fernando sen...@wso2.com wrote: Hi Amila, I found this in G-Reg (checked ESB and it seems to be ok - not sure about other products), and yes the Qpid feature is not excluded. I believe that r117481 did not make it to the trunk. I will fix this and commit. Thanks, Senaka. On Sat, Dec 31, 2011 at 6:02 PM, Amila Suriarachchi am...@wso2.comwrote: On Sat, Dec 31, 2011 at 5:13 PM, Senaka Fernando sen...@wso2.comwrote: Hi Amila, I believe that it was decided to get rid of the embedded Qpid Broker from products, which was done on the 3.2.x branch. Now when starting the servers on the trunk I see Qpid is still hanging around. Any reason to why this was not removed from trunk? What is the product? Can you please check whether the product has explicitly imported that? thanks Amila. Thanks, Senaka. -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Query on ESB
On Thu, Dec 29, 2011 at 11:33 AM, Amila Suriarachchi am...@wso2.com wrote:
hi,
Lets say I have an xml message like this in an ESB sequence.
ns1:AddOrder
ns1:orderID001/ns1:orderID
ns1:customerID001/ns1:customerID
ns1:date2011-12-26T18:28:48.214+05:30/ns1:date
ns1:price456.76/ns1:price
/ns1:AddOrder
Then I can use dblookup mediator to get email and name for a customer
using customerID.
How can I enrich those details to the xml payload using Enrich mediator?
Assume after dblook up mediator
email and name are in synapse properties as strings.
out put would be like this.
ns1:AddOrder
ns1:orderID001/ns1:orderID
ns1:customerID001/ns1:customerID
ns1:date2011-12-26T18:28:48.214+05:30/ns1:date
ns1:price456.76/ns1:price
ns1:emailmailto:synapse.dem...@gmail.com/ns1:email
ns1:nameamila/ns1:name
/ns1:AddOrder
After this I want to send this message to the mail endpoint. if the data
base only has synapse.dem...@gamil.com how to concatenate the 'mailto:'
part to that before setting the To header using header mediator?
this can be done with the following configuration.
header name=To expression=fn:concat('mailto:', get-property('email'))/
thanks,
Amila.
thanks,
Amila.
--
*Amila Suriarachchi*
Software Architect
WSO2 Inc. ; http://wso2.com
lean . enterprise . middleware
phone : +94 71 3082805
--
*Amila Suriarachchi*
Software Architect
WSO2 Inc. ; http://wso2.com
lean . enterprise . middleware
phone : +94 71 3082805
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] want to work some simple scenarios on wso2 cloud
On Thu, Dec 29, 2011 at 2:08 PM, gnanaguru.sattanat...@wipro.com wrote: Hi ** ** I have done some simple vfs and jms scenarios in wso2 esb. I wanted to do the same in wso2stratos live. Is it possible ?. Is there any document present to do some sample. I have got a free account and was able to access the cloud esb management console. with stratos live you can only use http and https. thanks, Amila. ** ** Please help out. ** ** Regards Guru * Please do not print this email unless it is absolutely necessary. * The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Query on ESB
hi, Lets say I have an xml message like this in an ESB sequence. ns1:AddOrder ns1:orderID001/ns1:orderID ns1:customerID001/ns1:customerID ns1:date2011-12-26T18:28:48.214+05:30/ns1:date ns1:price456.76/ns1:price /ns1:AddOrder Then I can use dblookup mediator to get email and name for a customer using customerID. How can I enrich those details to the xml payload using Enrich mediator? Assume after dblook up mediator email and name are in synapse properties as strings. out put would be like this. ns1:AddOrder ns1:orderID001/ns1:orderID ns1:customerID001/ns1:customerID ns1:date2011-12-26T18:28:48.214+05:30/ns1:date ns1:price456.76/ns1:price ns1:emailmailto:synapse.dem...@gmail.com/ns1:email ns1:nameamila/ns1:name /ns1:AddOrder After this I want to send this message to the mail endpoint. if the data base only has synapse.dem...@gamil.com how to concatenate the 'mailto:' part to that before setting the To header using header mediator? thanks, Amila. -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] [Stack Overflow] WSO2 - Using get-property() function in Property/Xquery Mediators
this works fine if we change the existing xquery sample as follows.
variable xmlns:ax21=http://services.samples/xsd; xmlns:m0=
http://services.samples; name=code
expression=get-property('OperationName') type=STRING /
thanks,
Amila.
On Mon, Dec 19, 2011 at 11:24 PM, Prabath Siriwardena prab...@wso2.comwrote:
http://stackoverflow.com/questions/8402322/wso2-using-get-property-function-in-property-xquery-mediators
Can someone from ESB team please have a look...
--
Thanks Regards,
Prabath
http://blog.facilelogin.com
http://RampartFAQ.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
Re: [Carbon-dev] Look into Axis2 test failures in Carbon trunk
On Wed, Dec 14, 2011 at 9:30 PM, Afkham Azeez az...@wso2.com wrote: Sagara, Can you please look into these? We need to fix these as part of the stabilization effort. Shouldn't carbon trunk point to the axis2 trunk? thanks, Amila. -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *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
Re: [Carbon-dev] No need to start end tenant flows inside Axis2 deployers anymore
On Wed, Dec 14, 2011 at 9:09 PM, Afkham Azeez az...@wso2.com wrote: Earlier we had to call start end tenant flows inside deployer code because the deployment thread was in the Axis2 code. With the recent introduction of CarbonDeploymentScheduler, we have total control we start end the tenant flows inside that scheduler code now. Hence there is no need for the deployers to do that same. Take an update of carbon/core. So if we want to use a custom deployer in carbon (eg. Rules, DSS etc..) do we need to use carbon deployer or does it automatically called Axis2 deployers? thanks, Amila. -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *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
Re: [Carbon-dev] Shall we remove InfoCard feature from the Identity Server product..?
On Mon, Dec 12, 2011 at 3:50 PM, Prabath Siriwardena prab...@wso2.comwrote: $subject.. WDYT..? We can do it in the trunk... +1. if MSFT has already done that there is no reason us to keep it. thanks, Amila. -- Thanks Regards, Prabath http://blog.facilelogin.com http://RampartFAQ.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
Re: [Carbon-dev] List down the product builds which are compatible with maven3
I could build the BRS product with a clean product. But could not build the services since stratos feature could not build at that time. will try to build the service as well. thanks, Amila. On Thu, Dec 8, 2011 at 2:34 PM, Pradeep Fernando prad...@wso2.com wrote: yes, encountered it. removed it. thanks, --Pradeep ___ 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
Re: [Carbon-dev] Fwd: Axis2 error
this seems to be a version problem. when you invoke a back end service with a ws client better thing is to 1. run ant at the bin folder of the distribution. eg. WSO2_ESB/bin this copies all the client jars to repository/lib folder. put repository/lib folder jars to the class path. thanks, Amila. On Wed, Nov 16, 2011 at 5:24 AM, Srinath Perera srin...@wso2.com wrote: have to ask this in our lists .. sending it there. --Srinath -- Forwarded message -- From: Wathsala Vithanage waths...@wso2.com Date: Wed, Nov 16, 2011 at 11:13 AM Subject: Axis2 error To: Srinath Perera srin...@wso2.com Hi I'm getting following error when trying to get User Roles over WS from the IS server. Looks like an Axis2 related problem, what could be the reason? and who should be contacted to get help? 11/11/16 11:11:31 INFO deployment.ModuleDeployer: Deploying module: addressing-1.5.6 - file:/home/wathsala/.m2/repository/org/apache/axis2/axis2/1.5.6/axis2-1.5.6.jar Exception in thread main java.lang.InstantiationError: org.apache.axis2.databinding.ADBDataSource at org.wso2.carbon.authenticator.stub.Login.getOMElement(Login.java:168) at org.wso2.carbon.authenticator.stub.AuthenticationAdminStub.toEnvelope(AuthenticationAdminStub.java:2288) at org.wso2.carbon.authenticator.stub.AuthenticationAdminStub.login(AuthenticationAdminStub.java:642) at org.wso2.carbon.hadoop.authenticator.App.main(App.java:45) Regards -- Srinath Perera, Ph.D. Senior Software Architect, WSO2 Inc. Visiting Faculty, University of Moratuwa Member, Apache Software Foundation Research Scientist, Lanka Software Foundation Blog: http://srinathsview.blogspot.com/ Photos: http://www.flickr.com/photos/hemapani/ ___ 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
Re: [Carbon-dev] compilation error.
I took a full svn up and still failing there. thanks, Amila. On Mon, Nov 7, 2011 at 8:06 PM, Hasini Gunasinghe has...@wso2.com wrote: Hi Amila, Please take svn up in dependencies/rampart. Thanks, Hasini. On Tue, Nov 8, 2011 at 7:26 AM, Amila Suriarachchi am...@wso2.com wrote: hi, I am getting following error when compiling the trunk sts component. any reason for this? [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile (default-compile) on project org.wso2.carbon.sts: Compilation failure: Compilation failure: [ERROR] /home/amila/projects/carbon/components/sts/org.wso2.carbon.sts/src/main/java/org/wso2/carbon/sts/STSDeploymentInterceptor.java:[186,29] cannot find symbol [ERROR] symbol : method setTokenStoreDisabled(boolean) [ERROR] location: class org.apache.rahas.impl.SAMLTokenIssuerConfig [ERROR] [ERROR] /home/amila/projects/carbon/components/sts/org.wso2.carbon.sts/src/main/java/org/wso2/carbon/sts/STSDeploymentInterceptor.java:[197,29] cannot find symbol [ERROR] symbol : method setPersisterClassName(java.lang.String) [ERROR] location: class org.apache.rahas.impl.SAMLTokenIssuerConfig [ERROR] [ERROR] /home/amila/projects/carbon/components/sts/org.wso2.carbon.sts/src/main/java/org/wso2/carbon/sts/STSDeploymentInterceptor.java:[201,52] cannot find symbol thanks, Amila. ___ 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
Re: [Carbon-dev] XPath functions and properties avilable in WSO2 ESB
Can some one please add links to these pages in[1]? thanks, Amila. [1] http://wso2.org/project/esb/java/4.0.2/docs/ On Tue, Nov 8, 2011 at 9:19 AM, Kasun Indrasiri ka...@wso2.com wrote: ESB Properties and Parameters Catalog: http://wso2.org/project/esb/java/4.0.2/docs/properties_guide.html On Tue, Nov 8, 2011 at 10:44 PM, Sadeep Jayasumana sad...@wso2.comwrote: Hi, XPath functions variables: http://wso2.org/project/esb/java/4.0.2/docs/xpath.html Properties: http://wso2.org/project/esb/java/4.0.2/docs/properties_guide.html Thanks, Sadeep On Tue, Nov 8, 2011 at 8:28 PM, Amila Maha Arachchi ami...@wso2.comwrote: Hi, Where can I find a documentation of $Subject. At the moment I have only [1]. Is this available in the ESB Doc. If so, can somebody provide a pointer. [1] http://rajikak.blogspot.com/2010/04/xpath-functions-and-properties-avilable.html Thanks, AmilaM. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sadeep Jayasumana Software Engineer WSO2 Inc. Email - sad...@wso2.com Mobile - +94 77 22 66 507 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Kasun Indrasiri Associate Technical Lead WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 71 536 4128 Blog : http://kasunpanorama.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
Re: [Carbon-dev] compilation error.
I updated and seems to be not working. thanks, Amila. On Tue, Nov 8, 2011 at 8:37 AM, Hasini Gunasinghe has...@wso2.com wrote: Hi Amila, Noticed that there has been some version conflicts in following pom.xml files: trunk/carbon/pom.xml - rampart.osgi.version, rampart.version, rampart.mar.version trunk/carbon/orbit/pom.xml - rampart.version trunk/components/pom.xml -has two rapmpart versions as 'rampart.wso2.version' and 'rampart.version' I changed the above to the latest version -1.6.1-wso2v2. Can you please svn up and check whether above fixed the issue? At the moment, I am unable to build trunk due to some other issues. Thanks, Hasini. On Tue, Nov 8, 2011 at 6:24 PM, Amila Suriarachchi am...@wso2.com wrote: I took a full svn up and still failing there. thanks, Amila. On Mon, Nov 7, 2011 at 8:06 PM, Hasini Gunasinghe has...@wso2.comwrote: Hi Amila, Please take svn up in dependencies/rampart. Thanks, Hasini. On Tue, Nov 8, 2011 at 7:26 AM, Amila Suriarachchi am...@wso2.comwrote: hi, I am getting following error when compiling the trunk sts component. any reason for this? [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile (default-compile) on project org.wso2.carbon.sts: Compilation failure: Compilation failure: [ERROR] /home/amila/projects/carbon/components/sts/org.wso2.carbon.sts/src/main/java/org/wso2/carbon/sts/STSDeploymentInterceptor.java:[186,29] cannot find symbol [ERROR] symbol : method setTokenStoreDisabled(boolean) [ERROR] location: class org.apache.rahas.impl.SAMLTokenIssuerConfig [ERROR] [ERROR] /home/amila/projects/carbon/components/sts/org.wso2.carbon.sts/src/main/java/org/wso2/carbon/sts/STSDeploymentInterceptor.java:[197,29] cannot find symbol [ERROR] symbol : method setPersisterClassName(java.lang.String) [ERROR] location: class org.apache.rahas.impl.SAMLTokenIssuerConfig [ERROR] [ERROR] /home/amila/projects/carbon/components/sts/org.wso2.carbon.sts/src/main/java/org/wso2/carbon/sts/STSDeploymentInterceptor.java:[201,52] cannot find symbol thanks, Amila. ___ 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 ___ 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] compilation error.
hi, I am getting following error when compiling the trunk sts component. any reason for this? [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile (default-compile) on project org.wso2.carbon.sts: Compilation failure: Compilation failure: [ERROR] /home/amila/projects/carbon/components/sts/org.wso2.carbon.sts/src/main/java/org/wso2/carbon/sts/STSDeploymentInterceptor.java:[186,29] cannot find symbol [ERROR] symbol : method setTokenStoreDisabled(boolean) [ERROR] location: class org.apache.rahas.impl.SAMLTokenIssuerConfig [ERROR] [ERROR] /home/amila/projects/carbon/components/sts/org.wso2.carbon.sts/src/main/java/org/wso2/carbon/sts/STSDeploymentInterceptor.java:[197,29] cannot find symbol [ERROR] symbol : method setPersisterClassName(java.lang.String) [ERROR] location: class org.apache.rahas.impl.SAMLTokenIssuerConfig [ERROR] [ERROR] /home/amila/projects/carbon/components/sts/org.wso2.carbon.sts/src/main/java/org/wso2/carbon/sts/STSDeploymentInterceptor.java:[201,52] cannot find symbol thanks, Amila. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] How authenticate my client to a remote carbon server
On Tue, Nov 1, 2011 at 4:43 PM, Pradeep Fernando prad...@wso2.com wrote: Hi, The scenario: * Within a registry handler we deploy a governance registry stored .car file to a remote ESB. (There can be several ESB s and based on the API call to GREG, we decide on the ESB instance) * right now we keep remote ESB servers credentials as , - URL - username - password. and during the client invocation we use these to get hold of the admin cookie and upload the .car file. This works fine, but my concern is, * I dont set the set the system properties such as javax.net.ssl.trustStore since they are already available in the greg runtime. So, I can;t configure these per ESB. (All the remote ESB s as well as the GREG instance has the same set of values for the properties, javax.net.ssl.trustStore, javax.net.ssl.trustStorePassword, etc). I see this as a problem. you don't have to configure a keystore for each an every ESB. if they use different certificates then you need to import the certificate to the keystore. Since all carbon produces share the same certificate it works. * The URL, username and password of each remote instance are stored as a registry artifact in plain text. this is a problem. you may define some content type called password and use a registry handler to encrypt/decrypt that. thanks, Amila. How can I improve the above given scenarios ? Suggestions please. thanks, --Pradeep ___ 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
Re: [Carbon-dev] How to use Apache DS with WSO2 AS to authenticate using kerberos?
On Sun, Oct 30, 2011 at 9:42 PM, Prabath Siriwardena prab...@wso2.comwrote: This fails at the signature validation.. Are you using the exact version [1.5.5] of Apache DS as in the link or 1.5.7? 1.5.5. It is already mentioned. thanks, Amila. Thanks regards, -Prabath On Mon, Oct 31, 2011 at 3:22 AM, Amila Suriarachchi am...@wso2.com wrote: hi, I did the following to authenticate a client who's details are stored in Apache ds to WSO2 AS using kerberos. 1. First I configured the Apache DS kdc server for (1.5.5) as given here[1]. Then I could login to Apache DS server using Apache directory studio using kerberos. So that should be working fine. 2. I started configuring the WSO2 AS 4.0.0. First put the attached files to the repository/conf. Then use the security senario 16 in the wizard to configure the kerberos. Here I put SPN as ldap/localh...@example.com and password as randall (please see the given ldif file in the kerberos guide). Then it generated the policy but when I looked into it password was not there. 3. Finally started the client part following the sample given here[2]. Full client has been attached. I put the repository/lib +xalan 2.7.1 jar to the class path. After running the client it sends the message to the server. This can be seen from the tcp mon. But at the server it gives the following exception. I put the password and edited the server side policy like this as well. rampart:kerberosConfig rampart:property name=service.principal.nameldap/localh...@example.com /rampart:property rampart:property name=service.principal.passwordrandall/rampart:property /rampart:kerberosConfig GSSException: Failure unspecified at GSS-API level (Mechanism level: Integrity check on decrypted field failed (31)) at sun.security.jgss.krb5.Krb5Context.acceptSecContext(Krb5Context.java:741) at sun.security.jgss.GSSContextImpl.acceptSecContext(GSSContextImpl.java:323) at sun.security.jgss.GSSContextImpl.acceptSecContext(GSSContextImpl.java:267) at org.apache.ws.security.processor.KerberosTokenProcessor$1.run(KerberosTokenProcessor.java:475) at org.apache.ws.security.processor.KerberosTokenProcessor$1.run(KerberosTokenProcessor.java:468) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:337) at org.apache.ws.security.processor.KerberosTokenProcessor.acceptSecurityContext(KerberosTokenProcessor.java:468) at org.apache.ws.security.processor.KerberosTokenProcessor.verifyXMLSignature(KerberosTokenProcessor.java:296) at org.apache.ws.security.processor.SignatureProcessor.verifyXMLSignature(SignatureProcessor.java:292) at org.apache.ws.security.processor.SignatureProcessor.handleToken(SignatureProcessor.java:120) at org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:332) at org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:249) at org.apache.rampart.RampartEngine.process(RampartEngine.java:161) at org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:92) 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:206) 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.bridge.BridgeServlet.service(BridgeServlet.java:155) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:240) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:164) at org.apache.catalina.authenticator.AuthenticatorBase.invoke
Re: [Carbon-dev] How to use Apache DS with WSO2 AS to authenticate using kerberos?
On Sun, Oct 30, 2011 at 9:47 PM, Prabath Siriwardena prab...@wso2.comwrote: Also, please check whether you have the following in the policy at the service end [it was in the client side policy you attached] rampart:property name=kdc.des.aes.factor4/rampart:property I tried adding this at both side and removing as well. Could not get it working. thanks, Amila. Thanks regards, -Prabath On Mon, Oct 31, 2011 at 7:12 AM, Prabath Siriwardena prab...@wso2.com wrote: This fails at the signature validation.. Are you using the exact version [1.5.5] of Apache DS as in the link or 1.5.7? Thanks regards, -Prabath On Mon, Oct 31, 2011 at 3:22 AM, Amila Suriarachchi am...@wso2.com wrote: hi, I did the following to authenticate a client who's details are stored in Apache ds to WSO2 AS using kerberos. 1. First I configured the Apache DS kdc server for (1.5.5) as given here[1]. Then I could login to Apache DS server using Apache directory studio using kerberos. So that should be working fine. 2. I started configuring the WSO2 AS 4.0.0. First put the attached files to the repository/conf. Then use the security senario 16 in the wizard to configure the kerberos. Here I put SPN as ldap/localhost@EXAMPLE.COMand password as randall (please see the given ldif file in the kerberos guide). Then it generated the policy but when I looked into it password was not there. 3. Finally started the client part following the sample given here[2]. Full client has been attached. I put the repository/lib +xalan 2.7.1 jar to the class path. After running the client it sends the message to the server. This can be seen from the tcp mon. But at the server it gives the following exception. I put the password and edited the server side policy like this as well. rampart:kerberosConfig rampart:property name=service.principal.nameldap/localh...@example.com /rampart:property rampart:property name=service.principal.passwordrandall/rampart:property /rampart:kerberosConfig GSSException: Failure unspecified at GSS-API level (Mechanism level: Integrity check on decrypted field failed (31)) at sun.security.jgss.krb5.Krb5Context.acceptSecContext(Krb5Context.java:741) at sun.security.jgss.GSSContextImpl.acceptSecContext(GSSContextImpl.java:323) at sun.security.jgss.GSSContextImpl.acceptSecContext(GSSContextImpl.java:267) at org.apache.ws.security.processor.KerberosTokenProcessor$1.run(KerberosTokenProcessor.java:475) at org.apache.ws.security.processor.KerberosTokenProcessor$1.run(KerberosTokenProcessor.java:468) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:337) at org.apache.ws.security.processor.KerberosTokenProcessor.acceptSecurityContext(KerberosTokenProcessor.java:468) at org.apache.ws.security.processor.KerberosTokenProcessor.verifyXMLSignature(KerberosTokenProcessor.java:296) at org.apache.ws.security.processor.SignatureProcessor.verifyXMLSignature(SignatureProcessor.java:292) at org.apache.ws.security.processor.SignatureProcessor.handleToken(SignatureProcessor.java:120) at org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:332) at org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:249) at org.apache.rampart.RampartEngine.process(RampartEngine.java:161) at org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:92) 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:206) 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.bridge.BridgeServlet.service(BridgeServlet.java:155) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304
Re: [Carbon-dev] What is the correct version of qpid-client?
On Wed, Oct 19, 2011 at 2:25 PM, Selvaratnam Uthaiyashankar shan...@wso2.com wrote: Hi Rajika, CEP and MB are still having 0.11.wso2.jar for CEP, it is in ./samples/lib/qpid-client-0.11.wso2v2.jar for MB it is in ./client-lib/qpid-client-0.11.wso2v2.jar Can you have a look? fixed in the branch. thanks, Amila. Thanks Shankar On Wed, Oct 19, 2011 at 10:39 AM, Rajika Kumarasiri raj...@wso2.com wrote: On Wed, Oct 19, 2011 at 10:01 AM, Selvaratnam Uthaiyashankar shan...@wso2.com wrote: Thanks Rajika, but we can't delete 0.11.wso2v2, since it is pointed by 3.2.1 orbit pom.xml. Can you revert deleting 0.11.wso2v2? I reverted the commit. Also, can you include the new features and orbits to 3.2.2 pom.xml? Added new features and into the patch release. Thanks for pointing. Rajika Shankar On Wed, Oct 19, 2011 at 9:48 AM, Rajika Kumarasiri raj...@wso2.com wrote: I fixed the issue by moving the qpid-client oribit bundle version from 0.11.wso2v2 to 0.11.0.wso2v2. Only MB seems to be using qpid-client orbit bundle and it's a old version of 0.11.wso2v1. Rajika On Wed, Oct 19, 2011 at 9:00 AM, Rajika Kumarasiri raj...@wso2.com wrote: Yeah. I'll change the orbit version. It's not much work. But I am not sure if other's depend on qpid-client orbit. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- S.Uthaiyashankar Senior Architect Senior Manager 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 mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- S.Uthaiyashankar Senior Architect Senior Manager 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 mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Issue when engaging a module in a tenant from the UI before invoking the service
On Mon, Oct 10, 2011 at 10:42 AM, Isuru Suriarachchi is...@wso2.com wrote: Hi all, Looks like the recent module changes are causing a NPE when trying to engage a module for a fresh service. I tried this on Stratos 1.5.2. How to reproduce.. 1. Log into a tenant 2. Upload a fresh service 3. Try to engage a module (Throttling, Caching, Security etc.) from the UI This doesn't happen if I try to do it after invoking the service once. I think this is because the modules are only loaded into the AxisConfig when the first request comes in. Amila, can you please fix this? yes there are some issues with the new improvement. We need to fix this with the service deployment. When a service get deployed for the first time, since we don't know the service details it has to load all the modules (if not loaded) and deploy the service at the Ghost deployer level. (service already may engaged those modules) see the MTMR to how to do that. Then need to persists the engaged module details and load the modules at the MTMR level if someone try to invoke the service at the second time. Then need to fix at the module management service level as well. If some one invokes the module management UI (like in service management UI) then again need to load all the modules. Can you please add those features? I am in the support week and need to prepare for an on site work. thanks, Amila. Thanks, ~Isuru -- Isuru Suriarachchi Technical Lead Product Manager, WSO2 Application Server WSO2 Inc. http://wso2.com email : is...@wso2.com blog : http://isurues.wordpress.com/ lean . enterprise . middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] How Data Correlation based on Activity works?
hi, I read this link[1] about the feature. But I could not get what type of use case it try to address and how the client going to see the results. Are there any other document on this? As I understood in order to make this works, client suppose to add a soap header as given and BAM publisher copy that activity id to published message. Otherwise BAM publisher generates an id for each and every request without making any correlation between them. How practical asking clients to set a special soap header which is most probably not given in wsdl? [1] http://wso2.org/project/bam/1.3.0/docs/activity.html ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] How Data Correlation based on Activity works?
The problem statement says like this, We use correlation to keep track of related messages in a sequence of message exchanges. For example, the purchase order and the sales will have the same order number. To ensure that the purchase order and the corresponding sales operations are correlated, we can assign a correlation using the purchase order number. In finding correlation we have to define the elements that are relevant to the messages to be correlated with. For me this can be implemented like this, 1. First let users to engage activity monitoring service based. 2. Then in each service let users to define an xpath to extract the correlation id. That depends on the message format. 3. Since now BAM publisher can send the same activity id for related messages relate them and show in the BAM admin console. thanks, Amila. On Sun, Oct 9, 2011 at 8:43 AM, Amila Suriarachchi am...@wso2.com wrote: hi, I read this link[1] about the feature. But I could not get what type of use case it try to address and how the client going to see the results. Are there any other document on this? As I understood in order to make this works, client suppose to add a soap header as given and BAM publisher copy that activity id to published message. Otherwise BAM publisher generates an id for each and every request without making any correlation between them. How practical asking clients to set a special soap header which is most probably not given in wsdl? [1] http://wso2.org/project/bam/1.3.0/docs/activity.html ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Some comments/issues with BAM 1.3.0
Here are some things I saw after doing some samples with BAM 1.3.0. I have given here my view on that. Please comment if I have mis configured any thing. 1. When I created a monitored server (with https://127.0.0.1:9445) with message type of data BAM automatically creates another monitored sever ( https://10.100.3.118:9445 ) with service type of data. 2. In BAM it is possible to create monitored servers with same ip and port with different type of data. But when selecting the servers in the dash board it only display the ip + port. So users need to remember order it appears the servers. Better to add the type of data or let users to define a server name. 3. BAM collects statistics data from the system statistics module. This gives an accumulative value from the time server starts up. So if the server restarts Service Analytics shows wrong values. Even the server does not restarts min and max values can be wrong. 4. BAM activity publishing is configured globally. But I think it make more sense to allow it at service level through service dashboard. It let users to define xpath values to take data. These xpath values are always service dependant. And also users may need to enable message logging only for some services. 5. An activity service published message (with some xpath values) looks through the dashboard looks like this. message s:Body xmlns:s=http://www.w3.org/2003/05/soap-envelope; p:greet xmlns:p=http://www.wso2.org/types; #comment / name amila /name /p:greet /s:Body /message But it would be clear to have it like this seperating the name value pairs and the soap message. message s:Body xmlns:s=http://www.w3.org/2003/05/soap-envelope; p:greet xmlns:p=http://www.wso2.org/types; #comment / /p:greet /s:Body name amila /name /message thanks, Amila. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Do we have separate registry space for each user
On Fri, Oct 7, 2011 at 3:06 AM, Thilina Buddhika thili...@wso2.com wrote: On Fri, Oct 7, 2011 at 11:09 AM, Tharindu Mathew thari...@wso2.comwrote: On Fri, Oct 7, 2011 at 9:53 AM, Thilina Buddhika thili...@wso2.comwrote: On Fri, Oct 7, 2011 at 1:18 AM, Tharindu Mathew thari...@wso2.comwrote: On Fri, Oct 7, 2011 at 1:07 AM, Nuwan Bandara nu...@wso2.com wrote: Hi Tharindu, If I have explicitly given User-Y read permission for the User-X s resources then its for certain extent fine, but In this case user-Y only have login permission. but anyway if I do a getConfigUserRegistry() I am expecting a registry space which is only accessible for that particular user, else whats the point ? Answer below. Regards, /Nuwan On Fri, Oct 7, 2011 at 1:01 AM, Thilina Buddhika thili...@wso2.comwrote: Then why are we taking an additional parameter username to the method getConfigUserRegistry(String userName, int tenantId) ? Also what is the difference of the registry instances returned from getConfigSystemRegistry(int tenantId) and getConfigUserRegistry(String userName, int tenantId) ? system registry is for system tasks. It has high privileges, just like an admin user or more, which is needed for system tasks. user registry, is for that user's tasks. So, if you get user X's registry, you get the registry with that user's privileges. If he cannot read resource /abc/foo, then you can't get and read that resource, with user X's registry. You are confusing tenant spaces with user spaces. When you pass the tenant id, you get that tenant's registry, which is isolated from other tenants. Tenant spaces and user registry are orthogonal concepts. So this means if we store something in the user registry, it is secured only by the RBAC model. There is no isolation for each user's data, if they do belong to the same role. Yes. I thought this was obvious :) Well, it is not obvious if you look at the method name. For me, getConfigUserRegistry(int tenantId, String username) gives the notion of I am getting a my registry space inside my tenant space. If you think about this way. What is the point of having user isolation? Registry is there to manage artifacts. So artifacts uploaded by one party, can be and should be manipulated by other users. Only if they want these resources to be accessed. This statement is correct, only if you take a look from the G-Reg's angle. But in Carbon, we are using registry for storing almost everything. Only tenant isolation makes sense. Of course, marrying RBAC and CArbon permissions may make sense for some use cases. But, not all the time. I believe this way give the maximum flexibility. Having tenant isolation does not work always. For example, take the usecase Nuwan tries to achieve. That is to maintain individual user's data in the registry separately without allowing each of them to mess with others' data. With this model, it is not possible to do it without creating roles per each user which is not scalable in the case of GS. Not only for GS it is not scalable for SQS and other modules which requires user level permissions. Let me put my thought on this. There are two ways of authorization. 1. Role based 2. User based. The role based authorization is more suitable for giving authorizations for some functionality. For an example we develop Admin console to be used by some set of user we don't know. So at development time we assign permission for a role and when the system is deployed in the real environment real user get imported to the system and they get assigned the roles. Event if we look at the commonly used software engineering processes we analyze the system with roles and assign permissions to the roles. (Even real users are not know at that time). Finally at the deployment time real users get imported and assign to the roles. But when the system is being used, real users come and create the resources for them. Good example is SQS queues. I think same apply for registry resources as well. Now these resources should belong to the user who created it. (hence concept of owner ship). Then they can share it with other real users. Instead of one user it can be done with a user group. (We may use a role as a user group but I feel it is more related to a set of permissions). Therefore any authorization manager should have both these features so that the other developers should be able to use it appropriately. thanks, Amila. Since we are trying to focus more on social aspect of our platform, ability to have user level data isolation makes sense. Thanks, Thilina Thanks, Thilina Thanks, Thilina On Fri, Oct 7, 2011 at 12:54 AM, Tharindu Mathew thari...@wso2.comwrote: For Nuwan's question, the simple answer is no. If you have read permissions for that user Y of user X's resource, user Y can view it. Separate registry spaces are only present per tenant. On Fri, Oct 7, 2011 at 12:40
Re: [Carbon-dev] Some comments/issues with BAM 1.3.0
On Sat, Oct 8, 2011 at 12:30 AM, Buddhika Chamith buddhi...@wso2.comwrote: Hi, On Sat, Oct 8, 2011 at 1:26 AM, Tharindu Mathew thari...@wso2.com wrote: Some comments inline. On Fri, Oct 7, 2011 at 7:52 PM, Amila Suriarachchi am...@wso2.comwrote: Here are some things I saw after doing some samples with BAM 1.3.0. I have given here my view on that. Please comment if I have mis configured any thing. 1. When I created a monitored server (with https://127.0.0.1:9445) with message type of data BAM automatically creates another monitored sever ( https://10.100.3.118:9445 ) with service type of data. This should not happen. Sounds like a bug. I will check this out. 2. In BAM it is possible to create monitored servers with same ip and port with different type of data. But when selecting the servers in the dash board it only display the ip + port. So users need to remember order it appears the servers. Better to add the type of data or let users to define a server name. Agreed. 3. BAM collects statistics data from the system statistics module. This gives an accumulative value from the time server starts up. So if the server restarts Service Analytics shows wrong values. Even the server does not restarts min and max values can be wrong. We too have understood this problem and we have identified that being independent than cumulative is the correct way to go about this. In the new BAM we are getting details per invocation independently and min max calculations would be happening at BAM side. +1. Even in the dashboard view it is more meaning full to show current values. Like in a vehicle dashboard which shows the current speed rather than the total distance came/time. thanks, Amila. 4. BAM activity publishing is configured globally. But I think it make more sense to allow it at service level through service dashboard. It let users to define xpath values to take data. These xpath values are always service dependant. And also users may need to enable message logging only for some services. This seems to be a great idea. We should incorporate this at a service level. +1. 5. An activity service published message (with some xpath values) looks through the dashboard looks like this. Do we need xpath at all. If we dump the message. We just need to be able to xpath the message at the BAM side, and probably have the ability to save this search. message s:Body xmlns:s=http://www.w3.org/2003/05/soap-envelope; p:greet xmlns:p=http://www.wso2.org/types; #comment / name amila /name /p:greet /s:Body /message But it would be clear to have it like this seperating the name value pairs and the soap message. message s:Body xmlns:s=http://www.w3.org/2003/05/soap-envelope; p:greet xmlns:p=http://www.wso2.org/types; #comment / /p:greet /s:Body name amila /name /message thanks, Amila. ___ 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 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] [Architecture] Revamping Message Routing Mediators in ESB
On Thu, Oct 6, 2011 at 1:31 PM, Kasun Indrasiri ka...@wso2.com wrote: I will come up with the set of mediators to be re-factored and the modified syntax for each mediator. I think, backward compatibility will come in to the picture here. So, how should we deal with it? For backward compatibility better option is to deprecate the existing mediators and come up with a new mediators with proper names and parameters. thanks, Amila. On Wed, Oct 5, 2011 at 9:54 AM, Srinath Perera srin...@wso2.com wrote: Are we agreeing to Revamping? Hiranya, do you have any concerns? On Tue, Oct 4, 2011 at 12:15 PM, Amila Suriarachchi am...@wso2.com wrote: On Tue, Oct 4, 2011 at 11:45 AM, Srinath Perera srin...@wso2.com wrote: +1 .. if we can replace all with one mediator .. that is great! but we have to carefully design the syntax to make sure final result is natural for all cases. I think there are two ends for this. One is making it general. Other think is make common case simple. Current filter (it actually does some thing like if) mediator configurations can be as follows. filter xpath=//ns1:foo/ns1:bar/text() == 'test' then / else / /filter filter source=//ns1:foo/ns2:bar/text() regex=test then / else / /filter former 'xpath' is referred to an xpath returning a boolean while the 'source' attribute refer to an xpath returning a text value. Here it has tried to cover different specific scenarios which make that particular occasion to use it easily. But we if follow an method like BPEL by using another copy mediator (in fact I think these are not mediators but some language constructs). It would have written like this. variable name='foo' copy from source='soapbody' xpath=//ns1:foo/ns1:bar/text()/ to source='$foo' / /copy if condition=$foo =='test' then/ else/ /if then it is more generic. And no need to repeat the xpath, source veriables with each mediator. But for a simple xpath based filter need to use another copy mediator etc .. thanks, Amila. --Srinath On Fri, Sep 30, 2011 at 3:03 PM, Kasun Indrasiri ka...@wso2.com wrote: Hi all, In the current ESB implementation we have couple of mediators for message routing. While 'Filter' and 'Switch' mediators provide basic level of message filtering, router mediator is also doing very similar to what filter/switch mediators do. The usage of Router mediator is rare and often got replaced by filter/switch mediators. So, IMO, Router Mediator is redundant, unless it provides some advance/complex routing logic support. In the ESB 4.0.0 release, we introduces 'Conditional Router', which is intended to route messages based on HTTP headers, query parameters and url. However, this doesn't support routing based on message payload. But unlike 'Router', the 'Conditional Router' introduces uses the concepts of 'Evaluators' (And, Or, Match, Equal, Not) that can be utilize to construct complex routing logics. eg: conditionalRouter continueAfter=false conditionalRoute breakRoute=false condition and xmlns= match type=header source=my_custom_header1 regex=foo.*/ match type=url regex=/services/StockQuoteProxy.*/ /and /condition target sequence=cnd2_seq/ /conditionalRoute conditionalRoute breakRoute=false condition and xmlns= match type=header source=my_custom_header2 regex=bar.*/ equal type=param source=qparam1 value=qpv_foo/ or match type=url regex=/services/StockQuoteProxy.*/ match type=header source=my_custom_header3 regex=foo.*/ /or not equal type=param source=qparam2 value=qpv_bar/ /not /and /condition target sequence=cnd3_seq/ /conditionalRoute /conditionalRouter So, we can easily add message level routing capability(so that we can drop Router mediator) to Conditional Router and with that we'll get the power of using evaluators for message level routing as well. Having bunch of mediators that's doing the similar thing, cause a negative effect on ESB's usability. (Most of the pointed listed here, were discussed during last code-review
Re: [Carbon-dev] [Architecture] Revamping Message Routing Mediators in ESB
On Tue, Oct 4, 2011 at 11:45 AM, Srinath Perera srin...@wso2.com wrote: +1 .. if we can replace all with one mediator .. that is great! but we have to carefully design the syntax to make sure final result is natural for all cases. I think there are two ends for this. One is making it general. Other think is make common case simple. Current filter (it actually does some thing like if) mediator configurations can be as follows. filter xpath=//ns1:foo/ns1:bar/text() == 'test' then / else / /filter filter source=//ns1:foo/ns2:bar/text() regex=test then / else / /filter former 'xpath' is referred to an xpath returning a boolean while the 'source' attribute refer to an xpath returning a text value. Here it has tried to cover different specific scenarios which make that particular occasion to use it easily. But we if follow an method like BPEL by using another copy mediator (in fact I think these are not mediators but some language constructs). It would have written like this. variable name='foo' copy from source='soapbody' xpath=//ns1:foo/ns1:bar/text()/ to source='$foo' / /copy if condition=$foo =='test' then/ else/ /if then it is more generic. And no need to repeat the xpath, source veriables with each mediator. But for a simple xpath based filter need to use another copy mediator etc .. thanks, Amila. --Srinath On Fri, Sep 30, 2011 at 3:03 PM, Kasun Indrasiri ka...@wso2.com wrote: Hi all, In the current ESB implementation we have couple of mediators for message routing. While 'Filter' and 'Switch' mediators provide basic level of message filtering, router mediator is also doing very similar to what filter/switch mediators do. The usage of Router mediator is rare and often got replaced by filter/switch mediators. So, IMO, Router Mediator is redundant, unless it provides some advance/complex routing logic support. In the ESB 4.0.0 release, we introduces 'Conditional Router', which is intended to route messages based on HTTP headers, query parameters and url. However, this doesn't support routing based on message payload. But unlike 'Router', the 'Conditional Router' introduces uses the concepts of 'Evaluators' (And, Or, Match, Equal, Not) that can be utilize to construct complex routing logics. eg: conditionalRouter continueAfter=false conditionalRoute breakRoute=false condition and xmlns= match type=header source=my_custom_header1 regex=foo.*/ match type=url regex=/services/StockQuoteProxy.*/ /and /condition target sequence=cnd2_seq/ /conditionalRoute conditionalRoute breakRoute=false condition and xmlns= match type=header source=my_custom_header2 regex=bar.*/ equal type=param source=qparam1 value=qpv_foo/ or match type=url regex=/services/StockQuoteProxy.*/ match type=header source=my_custom_header3 regex=foo.*/ /or not equal type=param source=qparam2 value=qpv_bar/ /not /and /condition target sequence=cnd3_seq/ /conditionalRoute /conditionalRouter So, we can easily add message level routing capability(so that we can drop Router mediator) to Conditional Router and with that we'll get the power of using evaluators for message level routing as well. Having bunch of mediators that's doing the similar thing, cause a negative effect on ESB's usability. (Most of the pointed listed here, were discussed during last code-review of Group-D.) [1] http://wso2.org/project/esb/java/4.0.0/docs/mediator_guide.html Thanks, -- Kasun Indrasiri Associate Technical Lead WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 71 536 4128 Blog : http://kasunpanorama.blogspot.com/ -- Srinath Perera, Ph.D. Senior Software Architect, WSO2 Inc. Visiting Faculty, University of Moratuwa Member, Apache Software Foundation Research Scientist, Lanka Software Foundation Blog: http://srinathsview.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
Re: [Carbon-dev] Error building trunk
I also got this exception when building the registry component since now component-mgt is removed. Please update those references as well. thanks, Amila. On Mon, Oct 3, 2011 at 8:37 AM, Pradeep Fernando prad...@wso2.com wrote: Hi, we were in the process of re-factoring the component manager code. Now its called feature manager. thanks, --Pradeep ___ 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
Re: [Carbon-dev] [Architecture] Revamping Message Routing Mediators in ESB
On Fri, Sep 30, 2011 at 3:03 PM, Kasun Indrasiri ka...@wso2.com wrote: Hi all, In the current ESB implementation we have couple of mediators for message routing. While 'Filter' and 'Switch' mediators provide basic level of message filtering, router mediator is also doing very similar to what filter/switch mediators do. The usage of Router mediator is rare and often got replaced by filter/switch mediators. So, IMO, Router Mediator is redundant, unless it provides some advance/complex routing logic support. In the ESB 4.0.0 release, we introduces 'Conditional Router', which is intended to route messages based on HTTP headers, query parameters and url. However, this doesn't support routing based on message payload. But unlike 'Router', the 'Conditional Router' introduces uses the concepts of 'Evaluators' (And, Or, Match, Equal, Not) that can be utilize to construct complex routing logics. eg: conditionalRouter continueAfter=false conditionalRoute breakRoute=false condition and xmlns= match type=header source=my_custom_header1 regex=foo.*/ match type=url regex=/services/StockQuoteProxy.*/ /and /condition target sequence=cnd2_seq/ /conditionalRoute conditionalRoute breakRoute=false condition and xmlns= match type=header source=my_custom_header2 regex=bar.*/ equal type=param source=qparam1 value=qpv_foo/ or match type=url regex=/services/StockQuoteProxy.*/ match type=header source=my_custom_header3 regex=foo.*/ /or not equal type=param source=qparam2 value=qpv_bar/ /not /and /condition target sequence=cnd3_seq/ /conditionalRoute /conditionalRouter So, we can easily add message level routing capability(so that we can drop Router mediator) to Conditional Router and with that we'll get the power of using evaluators for message level routing as well. Having bunch of mediators that's doing the similar thing, cause a negative effect on ESB's usability. (Most of the pointed listed here, were discussed during last code-review of Group-D.) Another thing we saw was in consistency of naming. Lets take the following two mediators router route expression=//ns1:foo/ns1:bar match=test target / /route /router filter source=//ns1:foo/ns1:bar regex=test then / else / /filter Both say the same thing but different attribute names are used at different mediators. This can be seen in other places as well. Therefore I think it is better to follow one set of naming convention in each mediators. thanks, Amila. * * [1] http://wso2.org/project/esb/java/4.0.0/docs/mediator_guide.html Thanks, -- Kasun Indrasiri Associate Technical Lead WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 71 536 4128 Blog : http://kasunpanorama.blogspot.com/ ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Has Entitlement mediator has been tested in Stratos?
On Mon, Sep 19, 2011 at 7:06 AM, Asela Pathberiya as...@wso2.com wrote: Yes. it has been tested. Fine. How to use entitlement mediator there? I mean what are the modifications needed? entitlementService remoteServiceUrl= https://identity.cloud-test.104cloud.com.tw:9445/services; remoteServiceUserName=admin remoteServicePassword=admin callbackClass=org.wso2.sample.CustomerOrderEntitlementCallback/ how to upload the callback class? thanks, Amila. On Sun, Sep 18, 2011 at 9:16 PM, Amila Suriarachchi am...@wso2.comwrote: hi, it seems some one has tried to use the entitlement mediator in Stratos[1]. thanks, Amila. [1] http://wso2.org/library/articles/2011/06/securing-web-service-integration#comment-23421 ___ 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
[Carbon-dev] Has Entitlement mediator has been tested in Stratos?
hi, it seems some one has tried to use the entitlement mediator in Stratos[1]. thanks, Amila. [1] http://wso2.org/library/articles/2011/06/securing-web-service-integration#comment-23421 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Compilation error
hi, I am getting this error building the carbon core in branch. [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure /home/amila/projects/branch/carbon/3.2.0/core/org.wso2.carbon.core/3.2.1/src/main/java/org/wso2/carbon/core/internal/permission/update/PermissionUpdateServiceComponent.java:[74,57] cannot find symbol symbol : variable PROPERTY_UPDATE_PERM_TREE_PERIODICALLY location: class org.wso2.carbon.user.core.UserCoreConstants.RealmConfig Have I missed any file update? thanks, Amila. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Follow up of previous code review architecture review sessions
On Tue, Aug 30, 2011 at 7:19 AM, Srinath Perera srin...@wso2.com wrote: Hi Azeez, Only real scalable way to do this is PMs to followup. Meanwhile I think we need to open Jiras for issues as well. Not sure how useful will be crucible, but we can try. Lets us discuss. +1 to make PM own that. I think it is PMs responsibility to have a better architecture and code. Even for the code reviews in addition to the code review group PM of the project should be present and he need to take the steps to ensure what ever the changes agrees on code review goes to the code. When we reviewing code of another project we provide opinion on our point of view, that may not always the best way as well. Sometimes it is not feasible to do changes then and there as well. For an example sometimes back I had a BAM mediator publisher code review and suggested to have a lot of changes. Then Sumedha and Tharindu wanted to stop doing those changes at that time and differ it for the correct time. thanks, Amila. --Srinath On Tue, Aug 30, 2011 at 12:43 AM, Afkham Azeez az...@wso2.com wrote: Folks, $subject is something we need to do to ensure that whatever we have discussed during the previous reviews have been implemented. For code reviews, we have the Crucible projects, so the sessions leads please go through those and provide status updates by the end of this week. When it comes to architecture reviews, we only have the notes that are sent after the reviews. IMO, that is a bit harder to manage track. I think we should use Crucible for architecture reviews as well. I will check on how that can be done. In the meantime, we need to go through the old architecture review notes check what has been incorporated what hasn't. Srinath, what is the best way to do that? -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* -- Srinath Perera, Ph.D. Senior Software Architect, WSO2 Inc. Visiting Faculty, University of Moratuwa Member, Apache Software Foundation Research Scientist, Lanka Software Foundation Blog: http://srinathsview.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
Re: [Carbon-dev] Issue with ?WSDL generation for multi-part messages
in this case you need to use the useOriginalWSDL parameter to true. There is not gurantee that ?wsdl will generate the same wsdl you use to generate the code. thanks, Amila. On Sat, Aug 20, 2011 at 6:53 PM, Denis Weerasiri de...@wso2.com wrote: Hi, I'm using 3.2.0 based Carbon product to do all the following stuff. 1. I generated a service skeleton using a multi-part WSDL with RPC-literal binding and deployed in Carbon. wsdl:message name=probeMessage wsdl:part name=probeName type=xsd:string/ wsdl:part name=probeData type=xsd:string/ /wsdl:message wsdl:portType name=probeMessagePT wsdl:operation name=probe wsdl:input name=ProbeInputMessage message=tns:probeMessage wsaw:Action=http://probe/ wsdl:output name=ProbeOutputMessage message=tns:probeMessage/ /wsdl:operation /wsdl:portType wsdl:binding name=probeBinding type=tns:probeMessagePT soap:binding style=rpc transport=http://schemas.xmlsoap.org/soap/http; / wsdl:operation name=probe soap:operation soapAction=http://probe; / wsdl:input soap:body use=literal / /wsdl:input wsdl:output soap:body use=literal / /wsdl:output /wsdl:operation /wsdl:binding 2. Then the ?wsdl for that service generate something like as follows. So here the problem is now it's a single-part message with wrong element name :probe. How can I fix this? xsd:schema wsdl:types xsd:element name=probe xsd:complexType xsd:sequence xsd:element form=unqualified name=probeName nillable=true type= xsd:string/ xsd:element form=unqualified name=probeData nillable=true type= xsd:string/ /xsd:sequence /xsd:complexType /xsd:element /xsd:schema /wsdl:types wsdl:message name=probeMessage ** *wsdl:part name=parameters element=:probe/* /wsdl:message wsdl:portType name=ProbeServicePortType wsdl:operation name=probe wsdl:input message=tns:probeMessage wsaw:Action=http://probe/ wsdl:output message=tns:probeMessage wsaw:Action= http://ode/bpel/unit-test/ProbeService.wsdl/probeMessagePT/ProbeOutputMessage / /wsdl:operation /wsdl:portType wsdl:binding name=probeBinding type=tns:ProbeServicePortType soap:binding transport=http://schemas.xmlsoap.org/soap/http; style= document/ wsdl:operation name=probe soap:operation soapAction=http://probe; style=document/ wsdl:input soap:body use=literal/ /wsdl:input wsdl:output soap:body use=literal/ /wsdl:output /wsdl:operation /wsdl:binding -- Thanks, Denis -- *Denis Weerasiri* Software Engineer; WSO2 Inc.; http://wso2.com, *email: denis http://goog_277208233/** [AT] wso2.com* http://wso2.com/ * * *site: **https://sites.google.com/site/ddweerasiri/*https://sites.google.com/site/ddweerasiri/ *blog: **http://ddweerasiri.blogspot.com*http://ddweerasiri.blogspot.com/ * twitter: **http://twitter.com/ddweerasiri*http://twitter.com/ddweerasiri * linked-in: **http://lk.linkedin.com/in/ddweerasiri*http://lk.linkedin.com/in/ddweerasiri ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] start up error
hi, I am getting this error when try to start the MB (trunk) with the jprofiler. JProfiler Protocol version 28 JProfiler Using JVMTI JProfiler JVMTI version 1.1 detected. JProfiler 64-bit library JProfiler Listening on port: 8849. JProfiler Instrumenting native methods. JProfiler Can retransform classes. JProfiler Native library initialized JProfiler VM initialized JProfiler Waiting for a connection from the JProfiler GUI ... JProfiler Using dynamic instrumentation JProfiler Time measurement: elapsed time JProfiler CPU profiling enabled JProfiler Hotspot compiler enabled JProfiler Starting org/wso2/carbon/bootstrap/Bootstrap ... java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.wso2.carbon.bootstrap.Bootstrap.loadClass(Bootstrap.java:62) at org.wso2.carbon.bootstrap.Bootstrap.main(Bootstrap.java:43) Caused by: java.lang.NoClassDefFoundError: org/apache/axis2/description/Parameter at org.wso2.carbon.utils.multitenancy.CarbonContextHolder.clinit(CarbonContextHolder.java:138) at org.wso2.carbon.server.Main.start(Main.java:113) ... 6 more Caused by: java.lang.ClassNotFoundException: org.apache.axis2.description.Parameter at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) ... 8 more thanks, Amila. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] start up error
On Thu, Aug 18, 2011 at 8:41 PM, Isuru Suriarachchi is...@wso2.com wrote: Yes, for me the complain was for AxisFault and I fixed it and didn't get anything after that. But here it's org.apache.axis2.description.Parameter. Anyway I'll have a look. I can start the server without jprofiler properly. this issue only comes when started with jprofiler. thanks, Amila. Thanks, ~Isuru On Thu, Aug 18, 2011 at 7:44 PM, Afkham Azeez az...@wso2.com wrote: Isuru got something similar. This is because carbon.utils is inside CARBON_HOME/lib. On Thu, Aug 18, 2011 at 6:34 PM, Amila Suriarachchi am...@wso2.comwrote: hi, I am getting this error when try to start the MB (trunk) with the jprofiler. JProfiler Protocol version 28 JProfiler Using JVMTI JProfiler JVMTI version 1.1 detected. JProfiler 64-bit library JProfiler Listening on port: 8849. JProfiler Instrumenting native methods. JProfiler Can retransform classes. JProfiler Native library initialized JProfiler VM initialized JProfiler Waiting for a connection from the JProfiler GUI ... JProfiler Using dynamic instrumentation JProfiler Time measurement: elapsed time JProfiler CPU profiling enabled JProfiler Hotspot compiler enabled JProfiler Starting org/wso2/carbon/bootstrap/Bootstrap ... java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.wso2.carbon.bootstrap.Bootstrap.loadClass(Bootstrap.java:62) at org.wso2.carbon.bootstrap.Bootstrap.main(Bootstrap.java:43) Caused by: java.lang.NoClassDefFoundError: org/apache/axis2/description/Parameter at org.wso2.carbon.utils.multitenancy.CarbonContextHolder.clinit(CarbonContextHolder.java:138) at org.wso2.carbon.server.Main.start(Main.java:113) ... 6 more Caused by: java.lang.ClassNotFoundException: org.apache.axis2.description.Parameter at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) ... 8 more thanks, Amila. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Isuru Suriarachchi Technical Lead Product Manager, WSO2 Application Server WSO2 Inc. http://wso2.com email : is...@wso2.com blog : http://isurues.wordpress.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
Re: [Carbon-dev] Is Axis2 Java2WSDL buggy? {was: WSO2 Gov 4.0 Subscribe/Unsubscribe}
On Tue, Aug 9, 2011 at 11:26 PM, David Carver dcar...@intalio.com wrote: ** Honestly, going from java 2 WSDL has always been a crap shoot with any framework I've ever used. It's always better to do a WSDL First design approach. yes. This service should have created by generating the code for with the wsdl and should have used the generated services.xml file with the original wsdl. You can see this in the SQS service. at least it should have set following parameters. parameter name=useOriginalwsdltrue/parameter parameter name=modifyUserWSDLPortAddresstrue/parameter we will fix those with the next spec version implementation. Regardless, I need something that I can use, as with out it, I can't implement the Subscribe, and Unsubscribe methods of the Turmeric Repository Service. What I says is although the ?wsdl does not show you the correct wsdl, you can use the wsdl I have shown to generate your client. This service actually adhere to the spec but does not show the correct wsdl. thanks, Amila. Full details of the various operations I need to implement can be found here: http://www.ebayopensource.org/hudson/job/turmeric-ci-repository/doclinks/1/ Dave On 08/09/2011 01:30 PM, Senaka Fernando wrote: Hi all, While Amila would perhaps take up the issue on explaining workarounds to Dave, what's crappy with the existing Java2WSDL code? Which is perhaps the reason to why we find it hard to generate code using the attached WSDL file. Can someone have a look into this? Thanks, Senaka. -- Forwarded message -- From: David Carver dcar...@intalio.com Date: 2011/8/9 Subject: Re: [Carbon-dev] WSO2 Gov 4.0 Subscribe/Unsubscribe To: carbon-dev@wso2.org I brought down the WSDL for the EventBrokerService but this really seems to be incomplete. There are no type definitions and none of the messages are point to any types. This makes code generation and generating a client a bit more difficult. I'm attaching the WSDL that was returned from the EventBrokerService. Is there an existing Java library that is known to work with the service that can be used outside of WSO2? Dave On 08/08/2011 03:23 PM, Senaka Fernando wrote: Hi Dave, Yes there is a WS-API as defined in the WS-Eventing specification - which can be used for this purpose. The endpoint is https://localhost:9443/services/EventBrokerService, and the WSDL can be found at https://localhost:9443/services/EventBrokerService?wsdl. You will not see the WSDL unless you set HideAdminServiceWSDLs to false in repository/conf/carbon.xml. Thanks, Senaka. On Tue, Aug 9, 2011 at 12:38 AM, David Carver dcar...@intalio.com wrote: I'm starting work on the Turmeric SOA interfaces into the WSO2 Governance Registry 4.0. One of the options in our WSDL is the ability to subscribe, update, and unsubscribe for Notification of changes or lifecycle movements of a service. I'm looking at the Developer's guide, and see that there is an OSGI API Interface, however described here: https://wso2.org/project/registry/4.0.0/docs/developer_guide/osgi_support.html#registry_eventing_service I also know that the Eventing/Notification implementation is based on the WS-Eventing/Notification specification, but I don't see a way to call or access this either through the RemoteRegistry API or the WS-API. Is there a way to access the OSGI API through a web service, Restful Service, or Remote Registry with out having to create a OSGI plugin? I'm trying to keep the number of layers and customizations down to a minimum. Dave ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388 %2B1%20408%20754%207388; ext: 51736*; *M: +94 77 322 1818 %2B94%2077%20322%201818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware ___ Carbon-dev mailing listCarbon-dev@wso2.orghttp://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 -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] WSO2 Gov 4.0 Subscribe/Unsubscribe
you can find the ws-event sample comes with the WSO2 MB product. Here[1] is the svn location. thanks, Amila. [1] https://svn.wso2.org/repos/wso2/trunk/carbon/products/mb/modules/samples/product/wsclient On Tue, Aug 9, 2011 at 1:09 AM, David Carver dcar...@intalio.com wrote: ** Thanks, do you have any examples showing how to use this API to subscribe and unsubscribe to WSO2 Gov LifeCycle events, and Asset changes? Dave On 08/08/2011 03:23 PM, Senaka Fernando wrote: Hi Dave, Yes there is a WS-API as defined in the WS-Eventing specification - which can be used for this purpose. The endpoint is https://localhost:9443/services/EventBrokerService, and the WSDL can be found at https://localhost:9443/services/EventBrokerService?wsdl. You will not see the WSDL unless you set HideAdminServiceWSDLs to false in repository/conf/carbon.xml. Thanks, Senaka. On Tue, Aug 9, 2011 at 12:38 AM, David Carver dcar...@intalio.com wrote: I'm starting work on the Turmeric SOA interfaces into the WSO2 Governance Registry 4.0. One of the options in our WSDL is the ability to subscribe, update, and unsubscribe for Notification of changes or lifecycle movements of a service. I'm looking at the Developer's guide, and see that there is an OSGI API Interface, however described here: https://wso2.org/project/registry/4.0.0/docs/developer_guide/osgi_support.html#registry_eventing_service I also know that the Eventing/Notification implementation is based on the WS-Eventing/Notification specification, but I don't see a way to call or access this either through the RemoteRegistry API or the WS-API. Is there a way to access the OSGI API through a web service, Restful Service, or Remote Registry with out having to create a OSGI plugin? I'm trying to keep the number of layers and customizations down to a minimum. Dave ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware ___ Carbon-dev mailing listCarbon-dev@wso2.orghttp://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
Re: [Carbon-dev] WSO2 Gov 4.0 Subscribe/Unsubscribe
2011/8/9 David Carver dcar...@intalio.com ** I brought down the WSDL for the EventBrokerService but this really seems to be incomplete. There are no type definitions and none of the messages are point to any types. This makes code generation and generating a client a bit more difficult. I'm attaching the WSDL that was returned from the EventBrokerService. Is there an existing Java library that is known to work with the service that can be used outside of WSO2? you can use the wsdl given in this location[1]. We need to fix EventBrokerservice to show correct wsdl. you can use org.wso2.carbon.event.client.stub jar as the library file. You can down load the WSO2 MB from here[1]. and please have a look at the wsclient sample. thanks, Amila. [1] https://svn.wso2.org/repos/wso2/trunk/carbon/service-stubs/org.wso2.carbon.event.client.stub/src/main/resources/eventing-new.wsdl Dave On 08/08/2011 03:23 PM, Senaka Fernando wrote: Hi Dave, Yes there is a WS-API as defined in the WS-Eventing specification - which can be used for this purpose. The endpoint is https://localhost:9443/services/EventBrokerService, and the WSDL can be found at https://localhost:9443/services/EventBrokerService?wsdl. You will not see the WSDL unless you set HideAdminServiceWSDLs to false in repository/conf/carbon.xml. Thanks, Senaka. On Tue, Aug 9, 2011 at 12:38 AM, David Carver dcar...@intalio.com wrote: I'm starting work on the Turmeric SOA interfaces into the WSO2 Governance Registry 4.0. One of the options in our WSDL is the ability to subscribe, update, and unsubscribe for Notification of changes or lifecycle movements of a service. I'm looking at the Developer's guide, and see that there is an OSGI API Interface, however described here: https://wso2.org/project/registry/4.0.0/docs/developer_guide/osgi_support.html#registry_eventing_service I also know that the Eventing/Notification implementation is based on the WS-Eventing/Notification specification, but I don't see a way to call or access this either through the RemoteRegistry API or the WS-API. Is there a way to access the OSGI API through a web service, Restful Service, or Remote Registry with out having to create a OSGI plugin? I'm trying to keep the number of layers and customizations down to a minimum. Dave ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware ___ Carbon-dev mailing listCarbon-dev@wso2.orghttp://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
Re: [Carbon-dev] Make output topic in CEP query is optional
On Sun, Aug 7, 2011 at 8:38 PM, Kasun Weranga kas...@wso2.com wrote:
Hi,
Can we do the $subject ?
Because I have a requirement for inserting the output of an EPL statement
to another event stream within a query and using that event stream in
another query. Therefore in that case, I don't need to have output topic in
my first query. But in CEP bucket, it is a mandatory field. So can we make
that optional?
is this validation only happens at the schema level or do you get an
exception at the deployment?
If it does not work with an output element it should be an issue and we will
fix that.
thanks,
Amila.
The following format is what I required.
query name=query1
expression type=inline listenerName=queryListener1
insert into stream2 select a,b,c,...,f from stream1 .
/expression
/query
query name=query2
expression type=inline listenerName=queryListener2
select a,b,c,..,e from stream2 where a 3 and
/expression
output topic=outputTopic brokerName=localBroker
xmlmapping
cepData
a{a}/a
b{b}/b
c{c}/c
.
.
e{e}/e
/cepData
/xmlmapping
/output
/query
Thanks,
KasunW
--
*Kasun Weranga*
Software Engineer
**
*WSO2, Inc.
*lean.enterprise.middleware.
mobile : +94 772314602
http://sanjeewamalalgoda.blogspot.com/blog
:http://sanjeewamalalgoda.blogspot.com/
http://kasunweranga.blogspot.com/
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Make output topic in CEP query is optional
hi,
OMElement outputOmElement = queryElement.getFirstChildWithName(new
QName(CEPConstants.CEP_CONF_NAMESPACE,
CEPConstants.CEP_CONF_ELE_OUTPUT));
if (expressionElement != null) {
query.setOutput(OutputHelper.fromOM(outputOmElement));
}
I think the problem is here in QueryHelper (should be outputOmElement !=
null) . please fix this soon.
thanks,
Amila.
On Mon, Aug 8, 2011 at 10:55 AM, Shammi Jayasinghe sha...@wso2.com wrote:
Hi Kasun,
Can you please create a JIRA for this.
Thanks
Shammi
On Mon, Aug 8, 2011 at 10:35 AM, Kasun Weranga kas...@wso2.com wrote:
Hi Amila,
On Mon, Aug 8, 2011 at 8:06 AM, Amila Suriarachchi am...@wso2.comwrote:
On Sun, Aug 7, 2011 at 8:38 PM, Kasun Weranga kas...@wso2.com wrote:
Hi,
Can we do the $subject ?
Because I have a requirement for inserting the output of an EPL
statement to another event stream within a query and using that event
stream
in another query. Therefore in that case, I don't need to have output topic
in my first query. But in CEP bucket, it is a mandatory field. So can we
make that optional?
is this validation only happens at the schema level or do you get an
exception at the deployment?
I am getting exception at deployment time.
This is the exception.
[2011-08-08 10:33:33,119] ERROR
{org.wso2.carbon.cep.core.internal.ds.CEPServiceDS} - Can not create the
cep service
java.lang.NullPointerException
at
org.wso2.carbon.cep.core.internal.config.OutputHelper.fromOM(OutputHelper.java:31)
at
org.wso2.carbon.cep.core.internal.config.QueryHelper.fromOM(QueryHelper.java:56)
at
org.wso2.carbon.cep.core.internal.config.BucketHelper.fromOM(BucketHelper.java:90)
at
org.wso2.carbon.cep.core.internal.builder.CEPBucketBuilder.addNewBucketsToRegistry(CEPBucketBuilder.java:62)
at
org.wso2.carbon.cep.core.internal.builder.CEPServiceBuilder.createCEPService(CEPServiceBuilder.java:73)
at
org.wso2.carbon.cep.core.internal.ds.CEPServiceDS.activate(CEPServiceDS.java:58)
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:230)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:140)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:330)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:560)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:182)
at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:292)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:226)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:124)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:930)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:149)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:757)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:712)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:129)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:206)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:506)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:524)
at
org.wso2.carbon.broker.core.internal.ds.BrokerServiceDS.activate(BrokerServiceDS.java:50)
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:230)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:140)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:330)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:560)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:182
Re: [Carbon-dev] Unable to perform XSLT transformation in Integrate Rules with SOA tutorial
Can you please try with the BRS 1.1.0 as given in the article?
thanks,
Amila.
On Tue, Aug 2, 2011 at 12:57 PM, Jorge Infante Osorio jorg...@uci.cuwrote:
Hi folks.
BRS: 1.2.0
ESB: 4.0.0
I´m working in this tutorial: “Integrate Rules with SOA” and in the
sequence
CustomerOrderOutSequence I have this error:
TID: [] [WSO2 ESB] [2011-08-02 03:02:46,386] ERROR
{org.apache.synapse.mediators.transform.XSLTMediator} - Unable to perform
XSLT transformation using : Value {name ='null', keyValue
='conf:/xslt/OrderSelectorInputTransfer.xslt'} against source XPath :
s11:Body/child::*[position()=1] | s12:Body/child::*[position()=1]
{org.apache.synapse.mediators.transform.XSLTMediator}
org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxEOFException:
Unexpected EOF in prolog
at [row,col {unknown-source}]: [1,0]
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:296)
at
org.apache.axiom.om.impl.llom.OMDocumentImpl.getOMDocumentElement(OMDocument
Impl.java:109)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuil
der.java:570)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuil
der.java:566)
at
org.apache.synapse.util.jaxp.StreamResultBuilder.getNode(StreamResultBuilder
.java:87)
at
org.apache.synapse.mediators.transform.XSLTMediator.performXSLT(XSLTMediator
.java:295)
at
org.apache.synapse.mediators.transform.XSLTMediator.mediate(XSLTMediator.jav
a:191)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediat
or.java:60)
at
org.apache.synapse.config.xml.AnonymousListMediator.mediate(AnonymousListMed
iator.java:30)
at
org.apache.synapse.config.xml.SwitchCase.mediate(SwitchCase.java:66)
at
org.apache.synapse.mediators.filters.SwitchMediator.mediate(SwitchMediator.j
ava:108)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediat
or.java:60)
at
org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.
java:114)
at
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2Syn
apseEnvironment.java:219)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseC
allbackReceiver.java:364)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbac
kReceiver.java:159)
at
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)
at
org.apache.synapse.transport.nhttp.ClientWorker.run(ClientWorker.java:274)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerP
ool.java:173)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.ja
va:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:9
08)
at java.lang.Thread.run(Thread.java:619)
Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
at [row,col {unknown-source}]: [1,0]
at
com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOF(StreamScanner.java:686)
at
com.ctc.wstx.sr.BasicStreamReader.handleEOF(BasicStreamReader.java:2134)
at
com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2040
)
at
com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1069)
at
org.apache.axiom.util.stax.wrapper.XMLStreamReaderWrapper.next(XMLStreamRead
erWrapper.java:225)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java
:681)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:214)
... 21 more
TID: [] [WSO2 ESB] [2011-08-02 03:02:46,402] INFO
{org.apache.synapse.mediators.builtin.LogMediator} - To:
http://www.w3.org/2005/08/addressing/anonymous, WSAction: , SOAPAction: ,
MessageID: urn:uuid:87d96a7c-95c3-4bd1-9c78-bbc9da46adc2, Direction:
response, MESSAGE = Executing default 'fault' sequence, ERROR_CODE = 0,
ERROR_MESSAGE = Unable to perform XSLT transformation using : Value {name
='null', keyValue ='conf:/xslt/OrderSelectorInputTransfer.xslt'} against
source XPath : s11:Body/child::*[position()=1] |
s12:Body/child::*[position()=1], Envelope: ?xml version='1.0'
encoding='utf-8'?soapenv:Envelope
xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope
soapenv:Bodybrs:C
alculatePriceResponse xmlns:brs=http://wso2.org/sample/rule;brs:Order
xmlns:ax26=http://pojo.rule.sample/xsd;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:type=ax26:Orderax26:items
xsi:type=ax26:Itemax26:price50.0/ax26:priceax26:typeTypeA/ax26:typ
Re: [Carbon-dev] Unable to perform XSLT transformation in Integrate Rules with SOA tutorial
On Tue, Aug 2, 2011 at 7:30 PM, Jorge Infante Osorio jorg...@uci.cu wrote:
I don´t have the previous BRS version.
The problem is with the message that came from BRS?
yes. it is different from the BRS 1.1.0 and 1.2.0. The xslt is written suite
for 1.1.0.
Infact this is a bug in 1.1.0 and we have fixed with 1.2.0.
you can change the xslt as given in this article[1].
thanks,
Amila.
[1]
http://wso2.org/library/articles/2011/06/securing-web-service-integration
This is the message out from BRS PriceCalculatorService:
soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;
soapenv:Header /
soapenv:Body
brs:CalculatePriceResponse xmlns:brs=http://wso2.org/sample/rule;
brs:Order xmlns:ax26=http://pojo.rule.sample/xsd;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:type=ax26:Order
ax26:items xsi:type=ax26:Item
ax26:price50.0/ax26:price
ax26:typeTypeA/ax26:type
/ax26:items
ax26:items xsi:type=ax26:Item
ax26:price60.0/ax26:price
ax26:typeTypeB/ax26:type
/ax26:items
ax26:items xsi:type=ax26:Item
ax26:price70.0/ax26:price
ax26:typeTypeC/ax26:type
/ax26:items
ax26:items xsi:type=ax26:Item
ax26:price80.0/ax26:price
ax26:typeTypeA/ax26:type
/ax26:items
ax26:items xsi:type=ax26:Item
ax26:price80.0/ax26:price
ax26:typeTypeA/ax26:type
/ax26:items
ax26:orderIDOrder1/ax26:orderID
ax26:price316.75/ax26:price
/brs:Order
brs:Order xmlns:ax26=http://pojo.rule.sample/xsd;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:type=ax26:Order
ax26:items xsi:type=ax26:Item
ax26:price50.0/ax26:price
ax26:typeTypeA/ax26:type
/ax26:items
ax26:items xsi:type=ax26:Item
ax26:price60.0/ax26:price
ax26:typeTypeA/ax26:type
/ax26:items
ax26:items xsi:type=ax26:Item
ax26:price70.0/ax26:price
ax26:typeTypeC/ax26:type
/ax26:items
ax26:items xsi:type=ax26:Item
ax26:price80.0/ax26:price
ax26:typeTypeA/ax26:type
/ax26:items
ax26:items xsi:type=ax26:Item
ax26:price80.0/ax26:price
ax26:typeTypeA/ax26:type
/ax26:items
ax26:orderIDOrder2/ax26:orderID
ax26:price314.93/ax26:price
/brs:Order
/brs:CalculatePriceResponse
/soapenv:Body
/soapenv:Envelope
Saludos,
Ing. Jorge Infante Osorio.
J´Dpto Soluciones SOA.
CDAE.
Fac. 5.
UCI.
De: Amila Suriarachchi [mailto:am...@wso2.com]
Enviado el: martes, 02 de agosto de 2011 5:14
Para: Jorge Infante Osorio
CC: carbon-dev@wso2.org
Asunto: Re: Unable to perform XSLT transformation in Integrate Rules with
SOA tutorial
Can you please try with the BRS 1.1.0 as given in the article?
thanks,
Amila.
On Tue, Aug 2, 2011 at 12:57 PM, Jorge Infante Osorio jorg...@uci.cu
wrote:
Hi folks.
BRS: 1.2.0
ESB: 4.0.0
I´m working in this tutorial: “Integrate Rules with SOA” and in the
sequence
CustomerOrderOutSequence I have this error:
TID: [] [WSO2 ESB] [2011-08-02 03:02:46,386] ERROR
{org.apache.synapse.mediators.transform.XSLTMediator} - Unable to perform
XSLT transformation using : Value {name ='null', keyValue
='conf:/xslt/OrderSelectorInputTransfer.xslt'} against source XPath :
s11:Body/child::*[position()=1] | s12:Body/child::*[position()=1]
{org.apache.synapse.mediators.transform.XSLTMediator}
org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxEOFException:
Unexpected EOF in prolog
at [row,col {unknown-source}]: [1,0]
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:296)
at
org.apache.axiom.om.impl.llom.OMDocumentImpl.getOMDocumentElement(OMDocument
Impl.java:109)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuil
der.java:570)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuil
der.java:566)
at
org.apache.synapse.util.jaxp.StreamResultBuilder.getNode(StreamResultBuilder
.java:87)
at
org.apache.synapse.mediators.transform.XSLTMediator.performXSLT(XSLTMediator
.java:295)
at
org.apache.synapse.mediators.transform.XSLTMediator.mediate(XSLTMediator.jav
a:191)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediat
or.java:60)
at
org.apache.synapse.config.xml.AnonymousListMediator.mediate(AnonymousListMed
iator.java:30)
at
org.apache.synapse.config.xml.SwitchCase.mediate(SwitchCase.java
Re: [Carbon-dev] WSO2 Carbon Trunk Continuous Build has FAILED
fixed the issue please try to build.
thanks,
Amila.
On Thu, Jul 21, 2011 at 11:42 AM, Ranga Siriwardena ra...@wso2.com wrote:
Hi Supun,
I have already stopped the continuous build. I will start it once the fix
is done.
Thanks.
On Thu, Jul 21, 2011 at 11:00 AM, Supun Malinga sup...@wso2.com wrote:
Hi ranga,
On Thu, Jul 21, 2011 at 10:52 AM, Ranga Siriwardena ra...@wso2.comwrote:
Hi All,
Trunk build failing with following stack trace.
How can we avoid this cyclic reference issue?
Amila will fix it. Stopped the build for now since its continuously
failing.
thanks,
[INFO] Scanning for projects...
Downloading:
http://repo1.maven.org/maven2/org/apache/apache/8/apache-8.pom
Downloading:
http://repo1.maven.org/maven2/org/apache/apache/6/apache-6.pom
Downloading:
http://repo1.maven.org/maven2/org/apache/httpcomponents/httpcomponents-core/4.1/httpcomponents-core-4.1.pom
Downloading:
http://repo1.maven.org/maven2/org/apache/httpcomponents/project/4.1.1/project-4.1.1.pom
Downloading:
http://dist.wso2.org/maven2//org/apache/apache/7/apache-7.pom
14K downloaded (apache-7.pom)
Downloading:
http://repo1.maven.org/maven2/org/sonatype/oss/oss-parent/5/oss-parent-5.pom
Downloading:
http://people.apache.org/repo/m1-snapshot-repository//org.apache.commons/poms/commons-parent-17.pom
[INFO] Unable to find resource 'org.apache.commons:commons-parent:pom:17'
in repository apache.m1 (
http://people.apache.org/repo/m1-snapshot-repository/)
Downloading:
http://repo1.maven.org/maven2/org/apache/commons/commons-parent/17/commons-parent-17.pom
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] The projects in the reactor contain a cyclic reference: Edge
between 'Vertex{label='org.wso2.carbon:org.wso2.carbon.qpid'}' and
'Vertex{label='org.wso2.carbon:org.wso2.carbon.event.core'}' introduces to
cycle in the graph org.wso2.carbon:org.wso2.carbon.event.core --
org.wso2.carbon:org.wso2.carbon.qpid --
org.wso2.carbon:org.wso2.carbon.event.core
[INFO]
[INFO] Trace
org.apache.maven.BuildFailureException: The projects in the reactor
contain a cyclic reference: Edge between
'Vertex{label='org.wso2.carbon:org.wso2.carbon.qpid'}' and
'Vertex{label='org.wso2.carbon:org.wso2.carbon.event.core'}' introduces to
cycle in the graph org.wso2.carbon:org.wso2.carbon.event.core --
org.wso2.carbon:org.wso2.carbon.qpid --
org.wso2.carbon:org.wso2.carbon.event.core
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:295)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: hidden.org.codehaus.plexus.util.dag.CycleDetectedException:
Edge between 'Vertex{label='org.wso2.carbon:org.wso2.carbon.qpid'}' and
'Vertex{label='org.wso2.carbon:org.wso2.carbon.event.core'}' introduces to
cycle in the graph org.wso2.carbon:org.wso2.carbon.event.core --
org.wso2.carbon:org.wso2.carbon.qpid --
org.wso2.carbon:org.wso2.carbon.event.core
at hidden.org.codehaus.plexus.util.dag.DAG.addEdge(DAG.java:143)
at hidden.org.codehaus.plexus.util.dag.DAG.addEdge(DAG.java:123)
at
org.apache.maven.project.ProjectSorter.init(ProjectSorter.java:118)
at
org.apache.maven.execution.ReactorManager.init(ReactorManager.java:99)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:288)
... 11 more
[INFO]
[INFO] Total time: 26 seconds
[INFO] Finished at: Thu Jul 21 00:55:48 EDT 2011
[INFO] Final Memory: 238M/1250M
[INFO]
Thanks.
On Thu, Jul 21, 2011 at 10:07 AM, WSO2 Carbon Trunk Builder (US2)
cbuil...@wso2.org wrote:
Repository Root: https://svn.wso2.org/repos/wso2
Repository UUID: a5903396-d722-0410-b921-86c7d4935375
Revision: 110398
Node Kind: directory
Schedule: normal
Last Changed Author: thilinab
Last Changed Rev: 110387
Last Changed Date: 2011-07-20 15:10:04 -0400 (Wed, 20 Jul 2011) ;;
'features')
run_from_carbon_features
;;
Re: [Carbon-dev] Event InMemory implementation (in memory delivery manager)
On Fri, Jun 24, 2011 at 4:14 PM, Amila Suriarachchi am...@wso2.com wrote: hi, We have completed the $subject and will update the other products once it is tested with private cloud. However there are some other issue to attend as well. We have made Event Broker component directly depend on Qpid over the time. I think we need to remove this dependency and let other products run with inmemory implementation without Qpid being bundle on them. Removed the Qpid dependancy from the event component so that is it is not required by the projects only use eventing. Products except MB shift with the inmemory model by default. If those products want to use the Qpid based delivery manager, they can install the Qpid feature and change the event-broker.xml to use QpidDelivaryManager. thanks, Amila. And also in the topic browse view, it shows the jms subscription details obtain through Qpid service. If we go with an inmemory one jms subscription details are irrelevant. So shall we remove them as well? thanks, Amila. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] [CarbonStudio] Error occurred while creating an Axis2 Service using CS
On Wed, Jul 20, 2011 at 1:37 PM, Harshana Martin harsh...@wso2.com wrote: Hi Sameera, Does your service class included in a Dynamic Web Project in your workspace? As I mentioned we fixed this issue in 1.0.12 release. If it is possible can you try with it? I think this is the same issue I saw to Saminda and reproduce in his machine. Please check with him. thanks, Amila. Thanks and Regards, Harshana On Wed, Jul 20, 2011 at 1:29 PM, Sameera Jayasoma same...@wso2.comwrote: On Wed, Jul 20, 2011 at 1:25 PM, Sameera Jayasoma same...@wso2.comwrote: On Wed, Jul 20, 2011 at 1:19 PM, Harshana Martin harsh...@wso2.comwrote: On Wed, Jul 20, 2011 at 1:17 PM, Harshana Martin harsh...@wso2.comwrote: Hi Sameera, Can you explain what are the steps you followed? Actually I want to know whether you are trying to create a PoJo service or other options :) I tried both options. Axis2 service from a service class and Axis2 service in the workspace. And can you attach the workspace log as well? Where can I find this log file? Attached. Thanks, Sameera . Thanks and Regards, Harshana On Wed, Jul 20, 2011 at 1:06 PM, Sameera Jayasoma same...@wso2.comwrote: Hi devs, I tried to create a simple Axis2 service using Carbon studio. But I got an error saying Error Creating Axis2 Artifact: null. What could be the issue? I've all attached the screenshot and it says everything. Can we get more meaning full errors? I've installed CS 1.0.11 on Eclipse 3.6.2. Any help would be appreciated. Thanks, Sameera -- 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 -- Harshana Martin Software Engineer WSO2 Inc. Web:http://wso2.com http://wso2.org Mobile: +94 716062650 Blog: http://harshana05.blogspot.com Profile: https://www.google.com/profiles/harshana05 Twitter: http://twitter.com/harshana05 -- Harshana Martin Software Engineer WSO2 Inc. Web:http://wso2.com http://wso2.org Mobile: +94 716062650 Blog: http://harshana05.blogspot.com Profile: https://www.google.com/profiles/harshana05 Twitter: http://twitter.com/harshana05 ___ 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 -- Harshana Martin Software Engineer WSO2 Inc. Web:http://wso2.com http://wso2.org Mobile: +94 716062650 Blog: http://harshana05.blogspot.com Profile: https://www.google.com/profiles/harshana05 Twitter: http://twitter.com/harshana05 ___ 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
Re: [Carbon-dev] [CarbonStudio] Error occurred while creating an Axis2 Service using CS
Try starting the project name (local-transport-test) with a Capital letter and without '-'s. One of the issues I got fixed like that. thanks, Amila. On Wed, Jul 20, 2011 at 1:06 PM, Sameera Jayasoma same...@wso2.com wrote: Hi devs, I tried to create a simple Axis2 service using Carbon studio. But I got an error saying Error Creating Axis2 Artifact: null. What could be the issue? I've all attached the screenshot and it says everything. Can we get more meaning full errors? I've installed CS 1.0.11 on Eclipse 3.6.2. Any help would be appreciated. Thanks, Sameera -- 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
Re: [Carbon-dev] Configuring ESB 4.0.0 with Qpid..
This could be the bug that shankar found with the message store Qpid as
well. Please try with ESB 4.0.1
thanks,
Amila.
On Mon, Jul 18, 2011 at 11:16 PM, Vijayaratha Vijayasingam
rat...@wso2.comwrote:
Hi,
This is how i configured ESB to work with qpid..
I uncommented JMS transport receiver and sender in axis2.xml.
And jndi.properties file contains the following configuration
connectionfactory.TopicConnectionFactory = amqp://admin:admin@carbon
/carbon?brokerlist='tcp://localhost:5672'
connectionfactory.QueueConnectionFactory = amqp://admin:admin@carbon
/carbon?brokerlist='tcp://localhost:5672'
destination.dynamicQueues/myqueue=jmsdestinationqueue; {create:always}
destination.myqueue=jmsdestinationqueue; {create:always}
Now, when i create a message store , im getting follwoing exeception;
[2011-07-18 22:57:03,048] ERROR - JMSMessageStore JMS error while
retrieving messages from the store
: testMsgStore
javax.jms.JMSException: Error registering consumer:
org.apache.qpid.AMQException: The name 'testMsgS
tore_Queue' supplied in the address doesn't resolve to an exchange or a
queue
at
org.apache.qpid.client.AMQSession$4.execute(AMQSession.java:2036)
My 'MessageStore' configuration is as follows;
messageStore xmlns=http://ws.apache.org/ns/synapse;
class=org.wso2.carbon.message.store.persistence.jms.JMSMessageStore
name=testMsgStore
parameter
name=java.naming.factory.initialorg.apache.qpid.jndi.PropertiesFileInitialContextFactory/parameter
parameter
name=java.naming.provider.urlrepository/conf/jndi.properties/parameter
/messageStore
How should i create a message store with Qpid?
Thanks
-Ratha.
___
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
Re: [Carbon-dev] Configuring ESB 4.0.0 with Qpid..
On Tue, Jul 19, 2011 at 11:54 AM, Vijayaratha Vijayasingam
rat...@wso2.comwrote:
I got resolved it ..with the following conf..
1) Edit axis2.xml file(ESB_HOME/rpository/conf/axis2.xml) like;
Under transport In section;
!--Transport Ins --
!--Uncomment this and configure as appropriate for JMS transport support
with Apache Qpid --
transportReceiver name=jms
class=org.apache.axis2.transport.jms.JMSListener
parameter name=myTopicConnectionFactory locked=false
parameter name=java.naming.factory.initial
locked=falseorg.apache.qpid.jndi.PropertiesFileInitialContextFactory/parameter
parameter name=java.naming.provider.url
locked=falserepository/conf/jndi.properties/parameter
parameter name=transport.jms.ConnectionFactoryJNDIName
locked=falseTopicConnectionFactory/parameter
parameter name=transport.jms.ConnectionFactoryType
locked=falsetopic/parameter
/parameter
parameter name=myQueueConnectionFactory locked=false
parameter name=java.naming.factory.initial
locked=falseorg.apache.qpid.jndi.PropertiesFileInitialContextFactory/parameter
parameter name=java.naming.provider.url
locked=falserepository/conf/jndi.properties/parameter
parameter name=transport.jms.ConnectionFactoryJNDIName
locked=falseQueueConnectionFactory/parameter
parameter name=transport.jms.ConnectionFactoryType
locked=falsequeue/parameter
/parameter
/transportReceiver
Under Transport Outs section;
!-- uncomment this and configure to use connection pools for sending
messages--
transportSender name=jms
class=org.apache.axis2.transport.jms.JMSSender/
2) At jndi.properties file(ESB_HOME/repository/conf/jndi.properties);
Add following lines to create connectionfactory, queue , topic etc..
connectionfactory.TopicConnectionFactory = amqp://admin:admin@carbon
/carbon?brokerlist='tcp://localhost:5672'
connectionfactory.QueueConnectionFactory = amqp://admin:admin@carbon
/carbon?brokerlist='tcp://localhost:5672'
queue.MyQueue = example.MyQueue
3) Your MessageStore configuartaion should have minimum three parameters;
messageStore xmlns=http://ws.apache.org/ns/synapse;
class=org.wso2.carbon.message.store.persistence.jms.JMSMessageStore
name=testMsgStore
parameter
name=java.naming.factory.initialorg.apache.qpid.jndi.PropertiesFileInitialContextFactory/parameter
parameter
name=java.naming.provider.urlrepository/conf/jndi.properties/parameter
parameter name=store.jms.destinationMyQueue/parameter
/messageStore
Please note that MyQueue parameter you are defining @ jndi.properties
file.
yes that was the problem
destination.dynamicQueues/
myqueue=jmsdestinationqueue; {create:always}
destination.myqueue=jmsdestinationqueue; {create:always}
{create:always} has caused the problem. If your scenario works without that
it is fine.
thanks,
Amila.
Thanks
-Ratha
On 19 July 2011 11:50, Amila Suriarachchi am...@wso2.com wrote:
This could be the bug that shankar found with the message store Qpid as
well. Please try with ESB 4.0.1
thanks,
Amila.
On Mon, Jul 18, 2011 at 11:16 PM, Vijayaratha Vijayasingam
rat...@wso2.com wrote:
Hi,
This is how i configured ESB to work with qpid..
I uncommented JMS transport receiver and sender in axis2.xml.
And jndi.properties file contains the following configuration
connectionfactory.TopicConnectionFactory = amqp://admin:admin@carbon
/carbon?brokerlist='tcp://localhost:5672'
connectionfactory.QueueConnectionFactory = amqp://admin:admin@carbon
/carbon?brokerlist='tcp://localhost:5672'
destination.dynamicQueues/myqueue=jmsdestinationqueue; {create:always}
destination.myqueue=jmsdestinationqueue; {create:always}
Now, when i create a message store , im getting follwoing exeception;
[2011-07-18 22:57:03,048] ERROR - JMSMessageStore JMS error while
retrieving messages from the store
: testMsgStore
javax.jms.JMSException: Error registering consumer:
org.apache.qpid.AMQException: The name 'testMsgS
tore_Queue' supplied in the address doesn't resolve to an exchange or a
queue
at
org.apache.qpid.client.AMQSession$4.execute(AMQSession.java:2036)
My 'MessageStore' configuration is as follows;
messageStore xmlns=http://ws.apache.org/ns/synapse;
class=org.wso2.carbon.message.store.persistence.jms.JMSMessageStore
name=testMsgStore
parameter
name=java.naming.factory.initialorg.apache.qpid.jndi.PropertiesFileInitialContextFactory/parameter
parameter
name=java.naming.provider.urlrepository/conf/jndi.properties/parameter
/messageStore
How should i create a message store with Qpid?
Thanks
-Ratha.
___
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
Re: [Carbon-dev] Issue with timezone
On Wed, Jul 13, 2011 at 5:51 AM, Jorge Infante Osorio jorg...@uci.cuwrote: Hi folks. I have a problem with the time zone in my ESB server. When I start the server, in the UI I see the right time, for example: Server Host 127.0.0.1 Server URL https://127.0.0.1:9445/services/ Server Start Time 2011-07-12 18:48:49 Time zone America/New_York (GMT-05:00) But in the message timestamp I see the right hour + 4, in this case my time = 19:06 and in the timestamp is 23:06 wsu:Timestamp xmlns:wsu= http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurit y-utility-1.0.xsd wsu:Id=Timestamp-4 wsu:Created2011-07-12T23:06:11.796Z/wsu:Created wsu:Expires2011-07-12T23:11:11.796Z/wsu:Expires /wsu:Timestamp when serializing a time stamp xml serialize format is always relative to a time zone. Z indicate it is relative to GMT. I think this Four hour gap is due to daylight saving time. in other words 2011-07-12T23:11:11.796Z == 2011-07-12T19:11:11.796-04:00 thanks, Amila. Any idea on this? Saludos, Ing. Jorge Infante Osorio. J´Dpto Soluciones SOA. CDAE. Fac. 5. UCI. ___ 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
Re: [Carbon-dev] NPE in Qpid service in ESB service 1.5.1
you need to set the owner of the subscription. If there is no logged in user at lease have to set it as CarbonConstants.REGISTRY_SYSTEM_USERNAME And also please update the event version 3.2.0 which users the inmemory model for ESB. thanks, Amila. On Wed, Jul 6, 2011 at 9:48 AM, Rajika Kumarasiri raj...@wso2.com wrote: [2011-07-06 09:41:34,883] ERROR - MediationStatisticsComponent Failed to activate BAM Mediation statistics data publisher bundle org.apache.axis2.AxisFault: Can not subscribe to the event broker at org.wso2.carbon.bam.data.publisher.mediationstats.internal.MediationStatisticsComponent.activate(MediationStatisticsComponent.java:112) 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:230) at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:140) at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:330) at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:560) at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:182) at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:292) at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:226) at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:124) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:930) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220) at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:149) at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:757) at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:712) at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:129) at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:206) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:506) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:524) at org.wso2.carbon.mediation.statistics.MediationStatisticsServiceComponent.activate(MediationStatisticsServiceComponent.java:91) 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:230) at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:140) at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:330) at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:560) at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:182) at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:292) at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:226) at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:124) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:930) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220) at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:149) at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:757) at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:712) at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:129) at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:206) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:506) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:524) at org.wso2.carbon.mediation.initializer.ServiceBusInitializer.activate(ServiceBusInitializer.java:233) at
