Re: [Carbon-dev] Carbon 3.0.1 RC1 Build
Milinda Pathirage wrote: Looks like all secure conversation related scenarios are failing due to a NullPointer exception in Rampart SymmetricBindingBuilder. We need to fix this before releasing. Given that we have released Rampart related components in chunk1, we need to patch rampart for chunk 2. This can be fixed by enabling addressing. Cause - In order to secure conversation to function addressing must be enabled. In the given environment addressing was not enabled and due to that a null pointer exception is raised. (I agree, that the error is not descriptive enough.) Thanks AmilaJ Can someone from the security team shed some light on this matter. Milinda On Tue, Sep 21, 2010 at 8:25 AM, Yumani Ranaweera yum...@wso2.com mailto:yum...@wso2.com wrote: Hi, GS-RC2 testing started only since yesterday noon and is still in progress. Except for few normal jiras, there weren't blockers found. Anyways, need more testing to be done throughout the day. Thanks, Yumani On Mon, Sep 20, 2010 at 8:09 PM, pavithra madurangi pavit...@wso2.com mailto:pavit...@wso2.com wrote: There are no blockers in BPS. There was a security issue which was related to partner service invoke and I've raised a jira for it [1]. The load tests done so far presented no issues with regard to data sources. [1] https://wso2.org/jira/browse/CARBON-7753 Regards, Pavithra On Mon, Sep 20, 2010 at 6:39 PM, Charitha Kankanamge chari...@wso2.com mailto:chari...@wso2.com wrote: Just got the DSS pack and some blockers are supposed to be fixed there. We need to verify them and decide. Pavithra/Yumani, please update the thread with GS and BPS testing status. Regards Charitha On Mon, Sep 20, 2010 at 6:30 PM, Samisa Abeysinghe sam...@wso2.com mailto:sam...@wso2.com wrote: Are these packs good enough for release? On Mon, Sep 20, 2010 at 5:51 PM, Asela Pathberiya as...@wso2.com mailto:as...@wso2.com wrote: On Fri, Sep 17, 2010 at 5:27 PM, Asela Pathberiya as...@wso2.com mailto:as...@wso2.com wrote: On Fri, Sep 17, 2010 at 5:18 PM, Charitha Kankanamge chari...@wso2.com mailto:chari...@wso2.com wrote: On Fri, Sep 17, 2010 at 4:08 PM, Asela Pathberiya as...@wso2.com mailto:as...@wso2.com wrote: On Thu, Sep 16, 2010 at 10:20 PM, Charitha Kankanamge chari...@wso2.com mailto:chari...@wso2.com wrote: Can we have DS, GS and BPS RC2 builds please? AFAIK, we need to release these packs in order to do CStudio release. Please find the GS and BPS RC2 builds here [1] . [1] http://builder.wso2.org/~carbon/releases/carbon/3.0.1/RC2/ http://builder.wso2.org/%7Ecarbon/releases/carbon/3.0.1/RC2/ DS? Can we have DS as well? there are issues which need to be verified. Please find the DS pack from same location Thanks, Asela. There is an issue with DS doc packs. Anjana will look into it. When it is fixed, will update. Thanks, Asela. Regards Charitha Thanks, Asela. Regards Charitha On Mon, Sep 6, 2010 at 12:38 PM, Asela Pathberiya as...@wso2.com mailto:as...@wso2.com wrote: On Mon, Sep 6, 2010 at 10:20 AM, Samisa Abeysinghe sam...@wso2.com mailto:sam...@wso2.com wrote: On Mon, Sep 6, 2010 at 10:15 AM, Asela Pathberiya
[Carbon-dev] Compilation failure in sequence editor
[INFO] Building WSO2 Carbon - Sequence Editor BE [INFO]task-segment: [clean, install] [INFO] [INFO] [clean:clean] [INFO] Deleting directory /home/isuru/checkouts/wso2/carbon/components/sequence-editor/org.wso2.carbon.sequences/target [INFO] [resources:resources] [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 2 resources [INFO] [compiler:compile] Compiling 4 source files to /home/isuru/checkouts/wso2/carbon/components/sequence-editor/org.wso2.carbon.sequences/target/classes [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure /home/isuru/checkouts/wso2/carbon/components/sequence-editor/org.wso2.carbon.sequences/src/main/java/org/wso2/carbon/sequences/internal/SequenceEditorServiceComponent.java:[102,48] cannot find symbol symbol : method getInstance() location: class org.apache.synapse.deployers.SynapseArtifactDeploymentStore [INFO] [INFO] For more information, run Maven with the -e switch [INFO] Thanks, ~Isuru -- Isuru Suriarachchi Technical Lead Product Manager, WSO2 Web Services 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 https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Compilation failure in sequence editor
This was fixed in the morning. Please take a svn up and build. On Tue, Sep 21, 2010 at 2:07 PM, Isuru Suriarachchi is...@wso2.com wrote: [INFO] Building WSO2 Carbon - Sequence Editor BE [INFO]task-segment: [clean, install] [INFO] [INFO] [clean:clean] [INFO] Deleting directory /home/isuru/checkouts/wso2/carbon/components/sequence-editor/org.wso2.carbon.sequences/target [INFO] [resources:resources] [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 2 resources [INFO] [compiler:compile] Compiling 4 source files to /home/isuru/checkouts/wso2/carbon/components/sequence-editor/org.wso2.carbon.sequences/target/classes [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure /home/isuru/checkouts/wso2/carbon/components/sequence-editor/org.wso2.carbon.sequences/src/main/java/org/wso2/carbon/sequences/internal/SequenceEditorServiceComponent.java:[102,48] cannot find symbol symbol : method getInstance() location: class org.apache.synapse.deployers.SynapseArtifactDeploymentStore [INFO] [INFO] For more information, run Maven with the -e switch [INFO] Thanks, ~Isuru -- Isuru Suriarachchi Technical Lead Product Manager, WSO2 Web Services 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 https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Regards, Heshan Suriyaarachchi Software Engineer WSO2 Inc.; http://wso2.com/ Blog: http://heshans.blogspot.com/ ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Eclipse ESB (Tree View) Editor Review Notes - 20.09.2010
Some more points based on my personal experience with the plugins: 0. Please update the documentation and clearly mention that the installation procedure can take a while 1. Underscore is not allowed in project names. Why? 2. What is the empty rectangle just below the text Existing Artifacts? - Ok got it :) - But when there is nothing to display in this area better to show a text message saying No artifacts added yet or something like that - Also increase the default height of this panel (it looks more like a text box otherwise) - Same applies for dependency view panels 3. Selecting an endpoint or a sequence on the UI should automatically expand the properties tab (if it's hidden or collapsed) 4. Endpoint message format dropdown - Soap 1.1, Soap 1.2 should be changed to SOAP 1.1 and SOAP 1.2 respectively 5. For boolean parameters (tracing, stats etc) provide checkboxes instead of dropdowns 6. Need tooltip texts for all the important properties in the properties window 7. Endpoint properties tab - Rename 'Basic' to 'General' - Rename 'Suspend progression factor' to 'Suspend duration progression factor' 8. Ability to create endpoints of different types is crucial. This should be a blocker for this release. Address endpoints and WSDL endpoints are the mostly used endpoint types. Default endpoint is used only under very specific conditions. 9. When you open an endpoint, the endpoint object should be already selected and the properties tab should be opened up - Same goes for sequences 10. Better use lower case letters for directory names (Artifacts - artifacts) 11. Sequence editor - For the root sequence object show 'Add Mediator' instead of 'New Child' - When changing to the source view from the design view without saving all the changes, the unsaved changes do not show up in the source view - It would be great if we can fix this - XSLT mediator source xpath null? - Please fix the serilizers to serialize only the required elements. In case of endpoints they serialize a whole bunch of unwanted stuff thus resulting in rediculously long configuration files - Hitting ctrl+s while a proeprty in the properties window is selected do not save the parent configuration - Arrange the mediators in the menus in alphabetical order (this should be done in the web UI too) - We need unique icons for each mediator (Currently there are some overlaps) - How do I associate the 'onError' sequence with a sequnce 12. When a new proxy service is created it contains an in-sequence with a log mediator. This is not necessary. - IMO this UI is not good enough. A proxy service cannot be modelled as a tree. But since you are already working on a different graphical view for proxy services we can live with this for the moment. - When pointing to a named reference (sequence or endpoint) should display the existing artifacts in a dropdown for the user to select from - In case of WSDLs we need to think of a way to tie in with the GReg gar files concept (future work) 13. We need local entry support asap (I wouldn't even mind considering this as a blocker for this release). Otherwise one must always use the registry to store XSLTs etc 14. Created a proxy service named proxyservice1 and it was saved to a file named proxyservice1.xml. Then I renamed the file to proxy_service1.xml. Opened up the corresponding artifact.xml but the path to deployable field has not been updated. Similarly I renamed the proxy service itself. Still the name displayed in the artifact.xml was not changed. I think the same happens with other types of artifacts. Thanks, Hiranya On Tue, Sep 21, 2010 at 10:48 AM, Saminda Wijeratne samin...@wso2.comwrote: Hi All, Following points were raised discussed at the review :- 1. Properties view should reveal when double clicking an element on the esb editor 2. Create endpoint menu should give other address / wsdl endpoint options (capp). 3. Get rid of default configurations of an endpoint / sequence (because they are understood and adding them are just making the configuration longer) 4. Endpoint error codes should be hard-coded (because the error codes are well knowns and they do not change) and allowed as checked boxes. 5. There is no such thing as endpoint timeout enable / disable. Get rid of that true / false field and show the timeout properties always. 6. Check “phsyco path” eclipse plugin to be used as an xpath editor for esb editor or write our own simple xpath editor. 7. In the tree view sequences / endpoints should show its caption as “sequence/endpoint_name [type]” 8. Tighten capp - esb editor integration - eg: sequences send mediator pointing to endpoints in the same project. 9. How to specify sequences send mediator pointing to a endpoint which would be deployed in a registry later. 10. Would be nice to have a proxy service as a flow rather than a tree kind of view (Graphical Editor) - It’s hard to represent a proxy service
Re: [Carbon-dev] Eclipse ESB (Tree View) Editor Review Notes - 20.09.2010
Hi Hiranya, Many thanks for this review, we're currently working on fixing the most prominent issues (some of which you have raised) and then plan to move into others. - Asiri On Tue, Sep 21, 2010 at 2:42 PM, Hiranya Jayathilaka hira...@wso2.comwrote: Some more points based on my personal experience with the plugins: 0. Please update the documentation and clearly mention that the installation procedure can take a while 1. Underscore is not allowed in project names. Why? 2. What is the empty rectangle just below the text Existing Artifacts? - Ok got it :) - But when there is nothing to display in this area better to show a text message saying No artifacts added yet or something like that - Also increase the default height of this panel (it looks more like a text box otherwise) - Same applies for dependency view panels 3. Selecting an endpoint or a sequence on the UI should automatically expand the properties tab (if it's hidden or collapsed) 4. Endpoint message format dropdown - Soap 1.1, Soap 1.2 should be changed to SOAP 1.1 and SOAP 1.2 respectively 5. For boolean parameters (tracing, stats etc) provide checkboxes instead of dropdowns 6. Need tooltip texts for all the important properties in the properties window 7. Endpoint properties tab - Rename 'Basic' to 'General' - Rename 'Suspend progression factor' to 'Suspend duration progression factor' 8. Ability to create endpoints of different types is crucial. This should be a blocker for this release. Address endpoints and WSDL endpoints are the mostly used endpoint types. Default endpoint is used only under very specific conditions. 9. When you open an endpoint, the endpoint object should be already selected and the properties tab should be opened up - Same goes for sequences 10. Better use lower case letters for directory names (Artifacts - artifacts) 11. Sequence editor - For the root sequence object show 'Add Mediator' instead of 'New Child' - When changing to the source view from the design view without saving all the changes, the unsaved changes do not show up in the source view - It would be great if we can fix this - XSLT mediator source xpath null? - Please fix the serilizers to serialize only the required elements. In case of endpoints they serialize a whole bunch of unwanted stuff thus resulting in rediculously long configuration files - Hitting ctrl+s while a proeprty in the properties window is selected do not save the parent configuration - Arrange the mediators in the menus in alphabetical order (this should be done in the web UI too) - We need unique icons for each mediator (Currently there are some overlaps) - How do I associate the 'onError' sequence with a sequnce 12. When a new proxy service is created it contains an in-sequence with a log mediator. This is not necessary. - IMO this UI is not good enough. A proxy service cannot be modelled as a tree. But since you are already working on a different graphical view for proxy services we can live with this for the moment. - When pointing to a named reference (sequence or endpoint) should display the existing artifacts in a dropdown for the user to select from - In case of WSDLs we need to think of a way to tie in with the GReg gar files concept (future work) 13. We need local entry support asap (I wouldn't even mind considering this as a blocker for this release). Otherwise one must always use the registry to store XSLTs etc 14. Created a proxy service named proxyservice1 and it was saved to a file named proxyservice1.xml. Then I renamed the file to proxy_service1.xml. Opened up the corresponding artifact.xml but the path to deployable field has not been updated. Similarly I renamed the proxy service itself. Still the name displayed in the artifact.xml was not changed. I think the same happens with other types of artifacts. Thanks, Hiranya On Tue, Sep 21, 2010 at 10:48 AM, Saminda Wijeratne samin...@wso2.comwrote: Hi All, Following points were raised discussed at the review :- 1. Properties view should reveal when double clicking an element on the esb editor 2. Create endpoint menu should give other address / wsdl endpoint options (capp). 3. Get rid of default configurations of an endpoint / sequence (because they are understood and adding them are just making the configuration longer) 4. Endpoint error codes should be hard-coded (because the error codes are well knowns and they do not change) and allowed as checked boxes. 5. There is no such thing as endpoint timeout enable / disable. Get rid of that true / false field and show the timeout properties always. 6. Check “phsyco path” eclipse plugin to be used as an xpath editor for esb editor or write our own simple xpath editor. 7. In the tree view sequences / endpoints should show its caption as “sequence/endpoint_name [type]” 8. Tighten capp - esb editor integration - eg: sequences
[Carbon-dev] java.lang.ClassNotFoundException: org.wso2.carbon.utils.ServerConfiguration
I'm getting the following CNF exception on WSAS startup and when trying to
log into ESB. I can see that the ServerConfiguration is moved into
carbon.base and it is only in root lib. Any special reason for that?
[2010-09-21 15:33:51,563] FATAL
{org.wso2.carbon.core.init.CarbonServerManager} - WSO2 Carbon
initialization Failed
java.lang.NoClassDefFoundError: org/wso2/carbon/utils/ServerConfiguration
at
org.wso2.carbon.webapp.mgt.WebappDeployer.init(WebappDeployer.java:68)
at
org.apache.axis2.deployment.DeploymentEngine.initializeDeployers(DeploymentEngine.java:1143)
at
org.apache.axis2.deployment.DeploymentEngine.setConfigContext(DeploymentEngine.java:1132)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:89)
at
org.wso2.carbon.core.CarbonConfigurationContextFactory.createNewConfigurationContext(CarbonConfigurationContextFactory.java:65)
at
org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:384)
at
org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:282)
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)
Caused by: java.lang.ClassNotFoundException:
org.wso2.carbon.utils.ServerConfiguration
at
org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:443)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:405)
Thanks,
~Isuru
--
Isuru Suriarachchi
Technical Lead Product Manager, WSO2 Web Services 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
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Carbon 3.0.1 RC1 Build
We can go ahead with the release. This happens in BPS because we have disabled WS-Addressing by default when calling external services. Thanks Milinda On Tue, Sep 21, 2010 at 1:37 PM, Amila Jayasekara ami...@wso2.com wrote: Milinda Pathirage wrote: Looks like all secure conversation related scenarios are failing due to a NullPointer exception in Rampart SymmetricBindingBuilder. We need to fix this before releasing. Given that we have released Rampart related components in chunk1, we need to patch rampart for chunk 2. This can be fixed by enabling addressing. Cause - In order to secure conversation to function addressing must be enabled. In the given environment addressing was not enabled and due to that a null pointer exception is raised. (I agree, that the error is not descriptive enough.) Thanks AmilaJ Can someone from the security team shed some light on this matter. Milinda On Tue, Sep 21, 2010 at 8:25 AM, Yumani Ranaweera yum...@wso2.com mailto:yum...@wso2.com wrote: Hi, GS-RC2 testing started only since yesterday noon and is still in progress. Except for few normal jiras, there weren't blockers found. Anyways, need more testing to be done throughout the day. Thanks, Yumani On Mon, Sep 20, 2010 at 8:09 PM, pavithra madurangi pavit...@wso2.com mailto:pavit...@wso2.com wrote: There are no blockers in BPS. There was a security issue which was related to partner service invoke and I've raised a jira for it [1]. The load tests done so far presented no issues with regard to data sources. [1] https://wso2.org/jira/browse/CARBON-7753 Regards, Pavithra On Mon, Sep 20, 2010 at 6:39 PM, Charitha Kankanamge chari...@wso2.com mailto:chari...@wso2.com wrote: Just got the DSS pack and some blockers are supposed to be fixed there. We need to verify them and decide. Pavithra/Yumani, please update the thread with GS and BPS testing status. Regards Charitha On Mon, Sep 20, 2010 at 6:30 PM, Samisa Abeysinghe sam...@wso2.com mailto:sam...@wso2.com wrote: Are these packs good enough for release? On Mon, Sep 20, 2010 at 5:51 PM, Asela Pathberiya as...@wso2.com mailto:as...@wso2.com wrote: On Fri, Sep 17, 2010 at 5:27 PM, Asela Pathberiya as...@wso2.com mailto:as...@wso2.com wrote: On Fri, Sep 17, 2010 at 5:18 PM, Charitha Kankanamge chari...@wso2.com mailto:chari...@wso2.com wrote: On Fri, Sep 17, 2010 at 4:08 PM, Asela Pathberiya as...@wso2.com mailto:as...@wso2.com wrote: On Thu, Sep 16, 2010 at 10:20 PM, Charitha Kankanamge chari...@wso2.com mailto:chari...@wso2.com wrote: Can we have DS, GS and BPS RC2 builds please? AFAIK, we need to release these packs in order to do CStudio release. Please find the GS and BPS RC2 builds here [1] . [1] http://builder.wso2.org/~carbon/releases/carbon/3.0.1/RC2/ http://builder.wso2.org/%7Ecarbon/releases/carbon/3.0.1/RC2/ DS? Can we have DS as well? there are issues which need to be verified. Please find the DS pack from same location Thanks, Asela. There is an issue with DS doc packs. Anjana will look into it. When it is fixed, will update. Thanks, Asela. Regards Charitha Thanks, Asela. Regards Charitha On Mon, Sep 6, 2010 at 12:38 PM, Asela Pathberiya as...@wso2.com mailto:as...@wso2.com wrote: On Mon, Sep 6, 2010 at 10:20 AM, Samisa Abeysinghe
Re: [Carbon-dev] java.lang.ClassNotFoundException: org.wso2.carbon.utils.ServerConfiguration
Hi isuru, after moving ServerConfiguration class, you have to take an up and rebuild webapp-mgt component. Thanks ajithn ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Eclipse ESB (Tree View) Editor Review Notes - 20.09.2010
Hi, - When changing to the source view from the design view without saving all the changes, the unsaved changes do not show up in the source view - It would be great if we can fix this FYI, this is a bug and i fixed it today morning. Thanks. - Asiri ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] java.lang.ClassNotFoundException: org.wso2.carbon.utils.ServerConfiguration
On Tue, Sep 21, 2010 at 5:14 PM, Ajith Vitharana aji...@wso2.com wrote: Hi isuru, after moving ServerConfiguration class, you have to take an up and rebuild webapp-mgt component. Yes. I had already built it. But there was an issue with my maven profiles and now its sorted out. Thanks, ~Isuru Thanks ajithn ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Isuru Suriarachchi Technical Lead Product Manager, WSO2 Web Services 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 https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Reading ESB log when running the automation test framework
When running log mediator tests manually, we usually scan carbon log to read log messages and decide the success or failure of the tests . But how can this be done through admin service automated framework? Currently we have written a primitive method to capture log messages based on timestamp and then read the log message.But it seems to be a error-prone mechanism.can someone please provide us guidance with a better mechanism in reading logs while running automated tests? Thank you, Chamara/ -- Suminda Chamara Silva WSO2 Inc. Mobile: +94 718 302858 blog: http://chamaras.blogspot.com ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Carbon Announcement URL
At the moment, this feature seems to be used only in Stratos, and the URL is; http://wso2.com/announcements/gaas/v1.0.0-006/news-feed.xml http://wso2.com/announcements/gaas/v1.0.0-006/news-feed.xmlWe need a proper fixed URL, and proper announcement updates. -- *Afkham Azeez* Senior Software Architect Senior Manager; 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 https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] endpoint component build broken
Compiling 6 source files to /home/stratos/build/carbon/components/endpoint/org.wso2.carbon.endpoint/target/classes [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure /home/stratos/build/carbon/components/endpoint/org.wso2.carbon.endpoint/src/main/java/org/wso2/carbon/endpoint/EndpointServiceComponent.java:[84,58] getSynapseConfigAbsPath(org.apache.synapse.ServerContextInformation) in org.wso2.carbon.mediation.initializer.ServiceBusUtils cannot be applied to () /home/stratos/build/carbon/components/endpoint/org.wso2.carbon.endpoint/src/main/java/org/wso2/carbon/endpoint/EndpointServiceComponent.java:[101,50] getSynapseConfigAbsPath(org.apache.synapse.ServerContextInformation) in org.wso2.carbon.mediation.initializer.ServiceBusUtils cannot be applied to () Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] endpoint component build broken
Fixed, Thanks, Supun. On Wed, Sep 22, 2010 at 9:38 AM, Samisa Abeysinghe sam...@wso2.com wrote: Compiling 6 source files to /home/stratos/build/carbon/components/endpoint/org.wso2.carbon.endpoint/target/classes [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure /home/stratos/build/carbon/components/endpoint/org.wso2.carbon.endpoint/src/main/java/org/wso2/carbon/endpoint/EndpointServiceComponent.java:[84,58] getSynapseConfigAbsPath(org.apache.synapse.ServerContextInformation) in org.wso2.carbon.mediation.initializer.ServiceBusUtils cannot be applied to () /home/stratos/build/carbon/components/endpoint/org.wso2.carbon.endpoint/src/main/java/org/wso2/carbon/endpoint/EndpointServiceComponent.java:[101,50] getSynapseConfigAbsPath(org.apache.synapse.ServerContextInformation) in org.wso2.carbon.mediation.initializer.ServiceBusUtils cannot be applied to () Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Supun Kamburugamuva Technical Lead WSO2 Inc.; http://wso2.org E-mail: su...@wso2.com; Mobile: +94 77 431 3585 Blog: http://supunk.blogspot.com ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Eventing component build broken.
[ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure /home/ajith/builds/trunk-3.1.0/carbon/components/eventing/org.wso2.carbon.eventing.eventsource/src/main/java/org/wso2/carbon/eventing/eventsource/EventSourceServiceComponent.java:[78,50] getSynapseConfigAbsPath(org.apache.synapse.ServerContextInformation) in org.wso2.carbon.mediation.initializer.ServiceBusUtils cannot be applied to () /home/ajith/builds/trunk-3.1.0/carbon/components/eventing/org.wso2.carbon.eventing.eventsource/src/main/java/org/wso2/carbon/eventing/eventsource/EventSourceServiceComponent.java:[97,58] getSynapseConfigAbsPath(org.apache.synapse.ServerContextInformation) in org.wso2.carbon.mediation.initializer.ServiceBusUtils cannot be applied to () Thanks ajithn ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Eventing component build broken.
Already Fixed. Please take a svn up and rebuild. On Wed, Sep 22, 2010 at 10:43 AM, Ajith Vitharana aji...@wso2.com wrote: [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure /home/ajith/builds/trunk-3.1.0/carbon/components/eventing/org.wso2.carbon.eventing.eventsource/src/main/java/org/wso2/carbon/eventing/eventsource/EventSourceServiceComponent.java:[78,50] getSynapseConfigAbsPath(org.apache.synapse.ServerContextInformation) in org.wso2.carbon.mediation.initializer.ServiceBusUtils cannot be applied to () /home/ajith/builds/trunk-3.1.0/carbon/components/eventing/org.wso2.carbon.eventing.eventsource/src/main/java/org/wso2/carbon/eventing/eventsource/EventSourceServiceComponent.java:[97,58] getSynapseConfigAbsPath(org.apache.synapse.ServerContextInformation) in org.wso2.carbon.mediation.initializer.ServiceBusUtils cannot be applied to () Thanks ajithn ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Kasun Indrasiri Senior Software Engineer 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 https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] What is the status of the WS-Discovery implementation?
Hi folks, $subject Can we use this to run our sample Acme shopping cart application on Stratos? Please note that we need to have this running before the Stratos 1.0 release. Thanks -- *Afkham Azeez* Senior Software Architect Senior Manager; 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 https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Reading ESB log when running the automation test framework
On Tue, Sep 21, 2010 at 7:27 PM, cham...@wso2.com cham...@wso2.com wrote: When running log mediator tests manually, we usually scan carbon log to read log messages and decide the success or failure of the tests . But how can this be done through admin service automated framework? Currently we have written a primitive method to capture log messages based on timestamp and then read the log message.But it seems to be a error-prone mechanism.can someone please provide us guidance with a better mechanism in reading logs while running automated tests? How about using the LogViewer admin service to retrieve the logs programmatically? Anyway I don't think you can use timestamp values as a basis of verification. You have to solely depend on the content of the log messages. Thanks, Hiranya Thank you, Chamara/ -- Suminda Chamara Silva WSO2 Inc. Mobile: +94 718 302858 blog: http://chamaras.blogspot.com ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Hiranya Jayathilaka Senior Software Engineer; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] [Stratos-dev] What is the status of the WS-Discovery implementation?
Also, what are the relationships between discovery endpoint unification? How much of that we plan to have by Stratos 1.0? On Wed, Sep 22, 2010 at 11:04 AM, Afkham Azeez az...@wso2.com wrote: Hi folks, $subject Can we use this to run our sample Acme shopping cart application on Stratos? Please note that we need to have this running before the Stratos 1.0 release. Thanks -- *Afkham Azeez* Senior Software Architect Senior Manager; 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* ___ Stratos-dev mailing list stratos-...@wso2.org https://wso2.org/cgi-bin/mailman/listinfo/stratos-dev Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
