[Carbon-dev] Adding a comment tag to synapse configuration
How about adding a comment tag to synapse configuration? Users prefer to leave comments in the XML configuration. But XML comments are not possible if they use the ESB console. So one option is to add a comment tag to the configuration. Synapse may not need this as it always uses the file system. Thanks, Supun.. ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Adding a comment tag to synapse configuration
So if we have comments now, do we strip them, when we open with management console? Samisa... On Wed, Jun 16, 2010 at 11:31 PM, Supun Kamburugamuva su...@wso2.comwrote: How about adding a comment tag to synapse configuration? Users prefer to leave comments in the XML configuration. But XML comments are not possible if they use the ESB console. So one option is to add a comment tag to the configuration. Synapse may not need this as it always uses the file system. Thanks, Supun.. ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev 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] Adding a comment tag to synapse configuration
I just had someone comment on this: when looking at the sequence flow there is no idea what each step is for. For instance if there is an XSLT, the only way of understand what the transformation is doing is to go into the specifics of the XSLT mediator and then maybe even into the actual XSLT file. So +1 for giving mediators names and comments. Paul On 16 June 2010 19:01, Supun Kamburugamuva su...@wso2.com wrote: How about adding a comment tag to synapse configuration? Users prefer to leave comments in the XML configuration. But XML comments are not possible if they use the ESB console. So one option is to add a comment tag to the configuration. Synapse may not need this as it always uses the file system. Thanks, Supun.. ___ Carbon-dev mailing list Carbon-dev@wso2.org https://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 Office: +44 844 484 8143 Cell: +44 798 447 4618 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 https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Exception at Server startup
Hi guys,
I am still getting this server startup error,
We are at the moment working towards deploying XAware in WSAS (AS), I built
the latest trunk and built wsas, but when starting the server I get,
[2010-06-16 13:41:33,572] WARN
{org.apache.axis2.transport.base.TransportMBeanSupport} - Error registering
a MBean with objectname '
org.apache.axis2:Type=Transport,ConnectorName=tcp-sender ' for JMX
management
javax.management.InstanceAlreadyExistsException:
org.apache.axis2:Type=Transport,ConnectorName=tcp-sender
at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482)
at
org.apache.axis2.transport.base.TransportMBeanSupport.register(TransportMBeanSupport.java:91)
at
org.apache.axis2.transport.base.AbstractTransportSender.init(AbstractTransportSender.java:84)
at
org.apache.axis2.context.ConfigurationContextFactory.initTransportSenders(ConfigurationContextFactory.java:300)
at
org.apache.axis2.context.ConfigurationContextFactory.init(ConfigurationContextFactory.java:231)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:93)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:210)
at
org.wso2.carbon.core.init.CarbonServerManager.getClientConfigurationContext(CarbonServerManager.java:501)
at
org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:404)
at
org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:248)
at
org.wso2.carbon.core.init.PreAxis2ConfigItemListener.bundleChanged(PreAxis2ConfigItemListener.java:100)
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)
[2010-06-16 13:41:33,574] INFO
{org.apache.axis2.transport.tcp.TCPTransportSender} - TCP Sender started
Can this be a build issue in my set up ? Please advise
Thanks regards
/Nuwan
On Fri, Jun 4, 2010 at 12:05 AM, Nuwan Bandara nu...@wso2.com wrote:
Hi guys,
I am getting the following exception while starting the server.
[2010-06-04 12:33:23,146] WARN - Error registering a MBean with
objectname ' org.apache.axis2:Type=Transport,ConnectorName=tcp-sender ' for
JMX management
javax.management.InstanceAlreadyExistsException:
org.apache.axis2:Type=Transport,ConnectorName=tcp-sender
at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482)
at
org.apache.axis2.transport.base.TransportMBeanSupport.register(TransportMBeanSupport.java:91)
at
org.apache.axis2.transport.base.AbstractTransportSender.init(AbstractTransportSender.java:84)
at
org.apache.axis2.context.ConfigurationContextFactory.initTransportSenders(ConfigurationContextFactory.java:300)
at
org.apache.axis2.context.ConfigurationContextFactory.init(ConfigurationContextFactory.java:231)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:93)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:210)
at
org.wso2.carbon.core.init.CarbonServerManager.getClientConfigurationContext(CarbonServerManager.java:480)
at
org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:386)
at
org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:242)
at
org.wso2.carbon.core.init.PreAxis2ConfigItemListener.bundleChanged(PreAxis2ConfigItemListener.java:100)
at
Re: [Carbon-dev] Adding a comment tag to synapse configuration
On Wed, Jun 16, 2010 at 2:12 PM, Samisa Abeysinghe sam...@wso2.com wrote: So if we have comments now, do we strip them, when we open with management console? Yes. Thanks, Supun.. Samisa... On Wed, Jun 16, 2010 at 11:31 PM, Supun Kamburugamuva su...@wso2.com wrote: How about adding a comment tag to synapse configuration? Users prefer to leave comments in the XML configuration. But XML comments are not possible if they use the ESB console. So one option is to add a comment tag to the configuration. Synapse may not need this as it always uses the file system. Thanks, Supun.. ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev 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 ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Adding a comment tag to synapse configuration
+1 Ruwan Supun Kamburugamuva wrote: On Wed, Jun 16, 2010 at 2:12 PM, Samisa Abeysinghe sam...@wso2.com wrote: So if we have comments now, do we strip them, when we open with management console? Yes. Thanks, Supun.. Samisa... On Wed, Jun 16, 2010 at 11:31 PM, Supun Kamburugamuva su...@wso2.com wrote: How about adding a comment tag to synapse configuration? Users prefer to leave comments in the XML configuration. But XML comments are not possible if they use the ESB console. So one option is to add a comment tag to the configuration. Synapse may not need this as it always uses the file system. Thanks, Supun.. ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev 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 ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Ruwan Linton Software Architect Product Manager, WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware phone: +1 408 754 7388 ext 51789 email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org linkedin: http://www.linkedin.com/in/ruwanlinton tweet: http://twitter.com/ruwanlinton ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Adding a comment tag to synapse configuration
Hi, On Wed, Jun 16, 2010 at 11:31 PM, Supun Kamburugamuva su...@wso2.comwrote: How about adding a comment tag to synapse configuration? Users prefer to leave comments in the XML configuration. But XML comments are not possible if they use the ESB console. So one option is to add a comment tag to the configuration. This comment tag will be available for each mediator definition, end point definition or ? what would be the general rule? I'm just asking because we're developing the eclipse editor which is supposed to generate synapse configuration files. +1 for the idea. Thanks. - Asiri Synapse may not need this as it always uses the file system. Thanks, Supun.. ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Using a wiki to write our online product documentation
Hi Supun, +1 from me ;) I've worked with wiki engines a bit (specially xwiki [1]) and I could help setting up an xwiki farm [2] if needed. [1] http://enterprise.xwiki.org/xwiki/bin/view/Main/Features [2] http://manager.xwiki.org/xwiki/bin/view/Main/WebHome - Asiri On Wed, Jun 16, 2010 at 11:14 PM, Supun Kamburugamuva su...@wso2.comwrote: How about using a wiki to write our online documentation. One advantage is we can keep on improving the document after we release the product as well. Right now even if we find a typo in the online documentation it is hard to fix. I know this kind of things are hard to do. But just thought of brining this up to see how others think. Thanks, Supun.. ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Adding a comment tag to synapse configuration
I don't think we need a special comments tag, rather we should be able to preserve generic XML comments, it is going to be hard but not impossible. New comment tag means more trouble for the user, lets stick to the XML comments. Ruwan Lahiru Gunathilake wrote: +1 for adding defined comment tag for synapse configuration. Regards Lahiru On Thu, Jun 17, 2010 at 6:05 AM, Ruwan Linton ru...@wso2.com mailto:ru...@wso2.com wrote: +1 Ruwan Supun Kamburugamuva wrote: On Wed, Jun 16, 2010 at 2:12 PM, Samisa Abeysinghe sam...@wso2.com mailto:sam...@wso2.com wrote: So if we have comments now, do we strip them, when we open with management console? Yes. Thanks, Supun.. Samisa... On Wed, Jun 16, 2010 at 11:31 PM, Supun Kamburugamuva su...@wso2.com mailto:su...@wso2.com wrote: How about adding a comment tag to synapse configuration? Users prefer to leave comments in the XML configuration. But XML comments are not possible if they use the ESB console. So one option is to add a comment tag to the configuration. Synapse may not need this as it always uses the file system. Thanks, Supun.. ___ Carbon-dev mailing list Carbon-dev@wso2.org mailto:Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org ___ Carbon-dev mailing list Carbon-dev@wso2.org mailto:Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org mailto:Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Ruwan Linton Software Architect Product Manager, WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware phone: +1 408 754 7388 ext 51789 email: ru...@wso2.com mailto:ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org linkedin: http://www.linkedin.com/in/ruwanlinton tweet: http://twitter.com/ruwanlinton ___ Carbon-dev mailing list Carbon-dev@wso2.org mailto:Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Lahiru Gunathilake Senior Software Engineer - WSO2 Inc. www.wso2.com http://www.wso2.com Email:lah...@wso2.com mailto:email%3alah...@wso2.com Blog: www.lahiru.org http://www.lahiru.org Mobile: +94716381143 Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Ruwan Linton Software Architect Product Manager, WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware phone: +1 408 754 7388 ext 51789 email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org linkedin: http://www.linkedin.com/in/ruwanlinton tweet: http://twitter.com/ruwanlinton ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Adding a comment tag to synapse configuration
Asiri, as I mentioned earlier, I think we should be preserving XML comments where ever they appear... yes it is hard, but should be able to do it. Thanks, Ruwan Asiri Rathnayake wrote: Hi, On Wed, Jun 16, 2010 at 11:31 PM, Supun Kamburugamuva su...@wso2.com mailto:su...@wso2.com wrote: How about adding a comment tag to synapse configuration? Users prefer to leave comments in the XML configuration. But XML comments are not possible if they use the ESB console. So one option is to add a comment tag to the configuration. This comment tag will be available for each mediator definition, end point definition or ? what would be the general rule? I'm just asking because we're developing the eclipse editor which is supposed to generate synapse configuration files. +1 for the idea. Thanks. - Asiri Synapse may not need this as it always uses the file system. Thanks, Supun.. ___ Carbon-dev mailing list Carbon-dev@wso2.org mailto:Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Ruwan Linton Software Architect Product Manager, WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware phone: +1 408 754 7388 ext 51789 email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org linkedin: http://www.linkedin.com/in/ruwanlinton tweet: http://twitter.com/ruwanlinton ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Adding a comment tag to synapse configuration
On Wed, Jun 16, 2010 at 10:57 PM, Ruwan Linton ru...@wso2.com wrote: I don't think we need a special comments tag, rather we should be able to preserve generic XML comments, it is going to be hard but not impossible. +1 from me, but not sure how.. Is there a way to do this? Thanks, Supun.. New comment tag means more trouble for the user, lets stick to the XML comments. Ruwan Lahiru Gunathilake wrote: +1 for adding defined comment tag for synapse configuration. Regards Lahiru On Thu, Jun 17, 2010 at 6:05 AM, Ruwan Linton ru...@wso2.com mailto:ru...@wso2.com wrote: +1 Ruwan Supun Kamburugamuva wrote: On Wed, Jun 16, 2010 at 2:12 PM, Samisa Abeysinghe sam...@wso2.com mailto:sam...@wso2.com wrote: So if we have comments now, do we strip them, when we open with management console? Yes. Thanks, Supun.. Samisa... On Wed, Jun 16, 2010 at 11:31 PM, Supun Kamburugamuva su...@wso2.com mailto:su...@wso2.com wrote: How about adding a comment tag to synapse configuration? Users prefer to leave comments in the XML configuration. But XML comments are not possible if they use the ESB console. So one option is to add a comment tag to the configuration. Synapse may not need this as it always uses the file system. Thanks, Supun.. ___ Carbon-dev mailing list Carbon-dev@wso2.org mailto:Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org ___ Carbon-dev mailing list Carbon-dev@wso2.org mailto:Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org mailto:Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Ruwan Linton Software Architect Product Manager, WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware phone: +1 408 754 7388 ext 51789 email: ru...@wso2.com mailto:ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org linkedin: http://www.linkedin.com/in/ruwanlinton tweet: http://twitter.com/ruwanlinton ___ Carbon-dev mailing list Carbon-dev@wso2.org mailto:Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Lahiru Gunathilake Senior Software Engineer - WSO2 Inc. www.wso2.com http://www.wso2.com Email:lah...@wso2.com mailto:email%3alah...@wso2.com Blog: www.lahiru.org http://www.lahiru.org Mobile: +94716381143 Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Ruwan Linton Software Architect Product Manager, WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware phone: +1 408 754 7388 ext 51789 email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org linkedin: http://www.linkedin.com/in/ruwanlinton tweet: http://twitter.com/ruwanlinton ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Using a wiki to write our online product documentation
You may consider using DocBook. DocBook is a standard for writing technical documentations. You can find more at: http://www.devx.com/Java/Article/35301 Here's an example on how the output would look like. http://docs.fedoraproject.org/en-US/Fedora/13/html/Installation_Quick_Start_Guide/index.html DocBook Community: http://www.docbook.org/ Regards, /KasunG On Wed, Jun 16, 2010 at 11:14 PM, Supun Kamburugamuva su...@wso2.comwrote: How about using a wiki to write our online documentation. One advantage is we can keep on improving the document after we release the product as well. Right now even if we find a typo in the online documentation it is hard to fix. I know this kind of things are hard to do. But just thought of brining this up to see how others think. Thanks, Supun.. ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Kasun Gajasinghe Intern E-mail: kasung AT wso2 DOT com WSO2, Inc.; http://wso2.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] Adding a comment tag to synapse configuration
On Thu, Jun 17, 2010 at 8:28 AM, Ruwan Linton ru...@wso2.com wrote: Asiri, as I mentioned earlier, I think we should be preserving XML comments where ever they appear... yes it is hard, but should be able to do it. This seems to be the right choice. But we need to have a way to map XML comments to various component definitions in the synapse.xml. Otherwise we won't be able to properly serialize it. Thanks, Hiranya Thanks, Ruwan Asiri Rathnayake wrote: Hi, On Wed, Jun 16, 2010 at 11:31 PM, Supun Kamburugamuva su...@wso2.com mailto:su...@wso2.com wrote: How about adding a comment tag to synapse configuration? Users prefer to leave comments in the XML configuration. But XML comments are not possible if they use the ESB console. So one option is to add a comment tag to the configuration. This comment tag will be available for each mediator definition, end point definition or ? what would be the general rule? I'm just asking because we're developing the eclipse editor which is supposed to generate synapse configuration files. +1 for the idea. Thanks. - Asiri Synapse may not need this as it always uses the file system. Thanks, Supun.. ___ Carbon-dev mailing list Carbon-dev@wso2.org mailto:Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Ruwan Linton Software Architect Product Manager, WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware phone: +1 408 754 7388 ext 51789 email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org linkedin: http://www.linkedin.com/in/ruwanlinton tweet: http://twitter.com/ruwanlinton ___ 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] Adding a comment tag to synapse configuration
Hiranya Jayathilaka wrote: On Thu, Jun 17, 2010 at 8:28 AM, Ruwan Linton ru...@wso2.com mailto:ru...@wso2.com wrote: Asiri, as I mentioned earlier, I think we should be preserving XML comments where ever they appear... yes it is hard, but should be able to do it. This seems to be the right choice. But we need to have a way to map XML comments to various component definitions in the synapse.xml. Otherwise we won't be able to properly serialize it. Right, that is what exactly I meant by it is hard, but should be able to. :-) Ruwan Thanks, Hiranya Thanks, Ruwan Asiri Rathnayake wrote: Hi, On Wed, Jun 16, 2010 at 11:31 PM, Supun Kamburugamuva su...@wso2.com mailto:su...@wso2.com mailto:su...@wso2.com mailto:su...@wso2.com wrote: How about adding a comment tag to synapse configuration? Users prefer to leave comments in the XML configuration. But XML comments are not possible if they use the ESB console. So one option is to add a comment tag to the configuration. This comment tag will be available for each mediator definition, end point definition or ? what would be the general rule? I'm just asking because we're developing the eclipse editor which is supposed to generate synapse configuration files. +1 for the idea. Thanks. - Asiri Synapse may not need this as it always uses the file system. Thanks, Supun.. ___ Carbon-dev mailing list Carbon-dev@wso2.org mailto:Carbon-dev@wso2.org mailto:Carbon-dev@wso2.org mailto:Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org mailto:Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Ruwan Linton Software Architect Product Manager, WSO2 ESB; http://wso2.org/esb WSO2 http://wso2.org/esb%0AWSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware phone: +1 408 754 7388 ext 51789 email: ru...@wso2.com mailto:ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org linkedin: http://www.linkedin.com/in/ruwanlinton tweet: http://twitter.com/ruwanlinton ___ Carbon-dev mailing list Carbon-dev@wso2.org mailto: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 mailto: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 -- Ruwan Linton Software Architect Product Manager, WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware phone: +1 408 754 7388 ext 51789 email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org linkedin: http://www.linkedin.com/in/ruwanlinton tweet: http://twitter.com/ruwanlinton ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Adding a comment tag to synapse configuration
If we are going to support XML comment preservation, every mediator should be aware of this. I cannot see a way other than changing every mediator. If that is the case we have lot of work to do as well as there can be lot of changes. There may be other approaches that I cannot see but for now lets assume we have to change every mediator. Then my first question is, is it worth to change every mediator so that they can store XML comments? With our current framework we can achieve this easily by introducing a new tag. It is easy and changes are not as distributed as the XML comment approach. Another thing is if we go for the comment approach, because of the changes it require it may never get done. So isn't it better to go for a simpler solution? Also to enable XML comments we may have to change mediator UI's as well. Thanks, Supun.. On Thu, Jun 17, 2010 at 12:47 AM, Ruwan Linton ru...@wso2.com wrote: Hiranya Jayathilaka wrote: On Thu, Jun 17, 2010 at 8:28 AM, Ruwan Linton ru...@wso2.com mailto:ru...@wso2.com wrote: Asiri, as I mentioned earlier, I think we should be preserving XML comments where ever they appear... yes it is hard, but should be able to do it. This seems to be the right choice. But we need to have a way to map XML comments to various component definitions in the synapse.xml. Otherwise we won't be able to properly serialize it. Right, that is what exactly I meant by it is hard, but should be able to. :-) Ruwan Thanks, Hiranya Thanks, Ruwan Asiri Rathnayake wrote: Hi, On Wed, Jun 16, 2010 at 11:31 PM, Supun Kamburugamuva su...@wso2.com mailto:su...@wso2.com mailto:su...@wso2.com mailto:su...@wso2.com wrote: How about adding a comment tag to synapse configuration? Users prefer to leave comments in the XML configuration. But XML comments are not possible if they use the ESB console. So one option is to add a comment tag to the configuration. This comment tag will be available for each mediator definition, end point definition or ? what would be the general rule? I'm just asking because we're developing the eclipse editor which is supposed to generate synapse configuration files. +1 for the idea. Thanks. - Asiri Synapse may not need this as it always uses the file system. Thanks, Supun.. ___ Carbon-dev mailing list Carbon-dev@wso2.org mailto:Carbon-dev@wso2.org mailto:Carbon-dev@wso2.org mailto:Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org mailto:Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Ruwan Linton Software Architect Product Manager, WSO2 ESB; http://wso2.org/esb WSO2 http://wso2.org/esb%0AWSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware phone: +1 408 754 7388 ext 51789 email: ru...@wso2.com mailto:ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org linkedin: http://www.linkedin.com/in/ruwanlinton tweet: http://twitter.com/ruwanlinton ___ Carbon-dev mailing list Carbon-dev@wso2.org mailto: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 mailto: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 -- Ruwan Linton Software Architect Product Manager, WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware phone: +1 408 754 7388 ext 51789 email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://blog.ruwan.org linkedin: http://www.linkedin.com/in/ruwanlinton tweet: http://twitter.com/ruwanlinton ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
