January 2012 - switchyard-issues - Jboss List Archives

[JBoss JIRA] (SWITCHYARD-625) Add and add-reference command to Forge plugins

by Mario Antollini (JIRA)

Mario Antollini created SWITCHYARD-625: ------------------------------------------ Summary: Add and add-reference command to Forge plugins Key: SWITCHYARD-625 URL: https://issues.jboss.org/browse/SWITCHYARD-625 Project: SwitchYard Issue Type: Feature Request Components: tooling Reporter: Mario Antollini Fix For: 0.4 Switchyard's forge plugins do not currently have an add-reference command. Such command would be very useful for the users. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-624) Add HornetQ reference binding quickstart

by Tomohisa igarashi (JIRA)

Tomohisa igarashi created SWITCHYARD-624: -------------------------------------------- Summary: Add HornetQ reference binding quickstart Key: SWITCHYARD-624 URL: https://issues.jboss.org/browse/SWITCHYARD-624 Project: SwitchYard Issue Type: Task Components: component-hornetq, quickstarts Affects Versions: 0.4 Reporter: Tomohisa igarashi hornetq-binding quickstart is an example of HornetQ service binding and we also need an example of HornetQ reference binding. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-623) enable publishing of SwitchYard 0.4 bits to download.jboss.org nightly staging composite

by Nick Boldt (JIRA)

Nick Boldt created SWITCHYARD-623: ------------------------------------- Summary: enable publishing of SwitchYard 0.4 bits to download.jboss.org nightly staging composite Key: SWITCHYARD-623 URL: https://issues.jboss.org/browse/SWITCHYARD-623 Project: SwitchYard Issue Type: Task Components: build, deployment Affects Versions: 0.4 Reporter: Nick Boldt Fix For: 0.4 1. tweak https://hudson.qa.jboss.com/hudson/job/SwitchYard-Tools job to: a) pull sources into a sources/ folder in the Jenkins job workspace b) run http://anonsvn.jboss.org/repos/jbosstools/trunk/build/publish.sh {code} # publish to http://download.jboss.org/jbosstools/ cd ${WORKSPACE} curl http://anonsvn.jboss.org/repos/jbosstools/trunk/build/publish.sh > publish.sh . ${WORKSPACE}/publish.sh {code} 2. once published, add the new folder to the composite by editing these files [1] so that the SOA Tooling site build can resolve the new content (that is, the switchyard feature listed in site.xml [2] can be found while building: [1] http://anonsvn.jboss.org/repos/jbosstools/trunk/download.jboss.org/jbosst..., compositeContent.xml [2] http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/soa-site/... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-622) trunk builds should use latest JBT target platform w/ Indigo SR2

by Nick Boldt (JIRA)

Nick Boldt created SWITCHYARD-622: ------------------------------------- Summary: trunk builds should use latest JBT target platform w/ Indigo SR2 Key: SWITCHYARD-622 URL: https://issues.jboss.org/browse/SWITCHYARD-622 Project: SwitchYard Issue Type: Bug Components: build Affects Versions: 0.4 Reporter: Nick Boldt Fix For: 0.4 Had a quick read thru of your root pom (https://hudson.qa.jboss.com/hudson/job/SwitchYard-Tools/ws/eclipse/pom.xml) and noticed that you use jbosstools-target-site = http://download.jboss.org/jbosstools/updates/target-platform_3.3.indigo/l... However, we've got a newer one which includes Indigo SR2 bits (well, maintenance builds leading up to SR2) which you could use instead: http://download.jboss.org/jbosstools/updates/target-platform_3.3.indigo.S... Note that this URL will change again when SR2 is actually released. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-621) hornetq-binding quickstart cannot be re-deployed

by Tomohisa igarashi (JIRA)

Tomohisa igarashi created SWITCHYARD-621: -------------------------------------------- Summary: hornetq-binding quickstart cannot be re-deployed Key: SWITCHYARD-621 URL: https://issues.jboss.org/browse/SWITCHYARD-621 Project: SwitchYard Issue Type: Bug Components: component-hornetq Affects Versions: 0.4 Reporter: Tomohisa igarashi Only the first deployment succeeds and the other trial of deploy will fail if you do it without stopping AS7. {quote} 17:11:02,170 INFO [org.jboss.weld] (MSC service thread 1-7) Stopping weld service 17:11:02,191 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) Stopped deployment switchyard-quickstarts-hornetq-binding.jar in 42ms 17:11:02,194 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) Starting deployment of "switchyard-quickstarts-hornetq-binding.jar" 17:11:02,221 INFO [org.jboss.weld] (MSC service thread 1-1) Processing CDI deployment: switchyard-quickstarts-hornetq-binding.jar 17:11:02,236 INFO [org.jboss.weld] (MSC service thread 1-8) Starting Services for CDI deployment: switchyard-quickstarts-hornetq-binding.jar 17:11:02,240 INFO [org.switchyard] (MSC service thread 1-8) Deploying SwitchYard application 'switchyard-quickstarts-hornetq-binding.jar' 17:11:02,243 INFO [org.jboss.weld] (MSC service thread 1-8) Starting weld service 17:11:02,307 INFO [org.switchyard] (MSC service thread 1-4) Starting SwitchYard service 17:11:02,407 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.unit."switchyard-quickstarts-hornetq-binding.jar".SwitchYardService: org.jboss.msc.service.StartException in service jboss.deployment.unit."switchyard-quickstarts-hornetq-binding.jar".SwitchYardService: org.switchyard.exception.SwitchYardException: org.switchyard.exception.SwitchYardException: java.lang.IllegalStateException: Cannot create session factory, server locator is closed (maybe it has been garbage collected) at org.switchyard.as7.extension.services.SwitchYardService.start(SwitchYardService.java:93) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22] at java.lang.Thread.run(Thread.java:679) [:1.6.0_22] Caused by: org.switchyard.exception.SwitchYardException: org.switchyard.exception.SwitchYardException: java.lang.IllegalStateException: Cannot create session factory, server locator is closed (maybe it has been garbage collected) at org.switchyard.component.hornetq.deploy.HornetQActivator.start(HornetQActivator.java:229) at org.switchyard.deploy.internal.Activation.start(Deployment.java:524) at org.switchyard.deploy.internal.Deployment.deployServiceBindings(Deployment.java:402) at org.switchyard.deploy.internal.Deployment.doStart(Deployment.java:135) at org.switchyard.deploy.internal.AbstractDeployment.start(AbstractDeployment.java:200) at org.switchyard.as7.extension.deployment.SwitchYardDeployment.start(SwitchYardDeployment.java:105) at org.switchyard.as7.extension.services.SwitchYardService.start(SwitchYardService.java:86) ... 5 more Caused by: org.switchyard.exception.SwitchYardException: java.lang.IllegalStateException: Cannot create session factory, server locator is closed (maybe it has been garbage collected) at org.switchyard.component.hornetq.deploy.InboundHandler.start(InboundHandler.java:96) at org.switchyard.component.hornetq.deploy.HornetQActivator.start(HornetQActivator.java:227) ... 11 more Caused by: java.lang.IllegalStateException: Cannot create session factory, server locator is closed (maybe it has been garbage collected) at org.hornetq.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:548) at org.switchyard.component.hornetq.deploy.InboundHandler.start(InboundHandler.java:90) ... 12 more 17:11:02,417 INFO [org.jboss.weld] (MSC service thread 1-7) Stopping weld service 17:11:02,429 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) Stopped deployment switchyard-quickstarts-hornetq-binding.jar in 15ms 17:11:02,431 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) Starting deployment of "switchyard-quickstarts-hornetq-binding.jar" 17:11:02,431 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS015863: Replacement of deployment "switchyard-quickstarts-hornetq-binding.jar" by deployment "switchyard-quickstarts-hornetq-binding.jar" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"switchyard-quickstarts-hornetq-binding.jar\".SwitchYardService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"switchyard-quickstarts-hornetq-binding.jar\".SwitchYardService: org.switchyard.exception.SwitchYardException: org.switchyard.exception.SwitchYardException: java.lang.IllegalStateException: Cannot create session factory, server locator is closed (maybe it has been garbage collected)"}} 17:11:02,449 INFO [org.jboss.weld] (MSC service thread 1-7) Processing CDI deployment: switchyard-quickstarts-hornetq-binding.jar 17:11:02,462 INFO [org.jboss.weld] (MSC service thread 1-7) Starting Services for CDI deployment: switchyard-quickstarts-hornetq-binding.jar 17:11:02,467 INFO [org.switchyard] (MSC service thread 1-7) Deploying SwitchYard application 'switchyard-quickstarts-hornetq-binding.jar' 17:11:02,470 INFO [org.jboss.weld] (MSC service thread 1-5) Starting weld service 17:11:02,526 INFO [org.switchyard] (MSC service thread 1-4) Starting SwitchYard service 17:11:02,608 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.unit."switchyard-quickstarts-hornetq-binding.jar".SwitchYardService: org.jboss.msc.service.StartException in service jboss.deployment.unit."switchyard-quickstarts-hornetq-binding.jar".SwitchYardService: org.switchyard.exception.SwitchYardException: org.switchyard.exception.SwitchYardException: java.lang.IllegalStateException: Cannot create session factory, server locator is closed (maybe it has been garbage collected) at org.switchyard.as7.extension.services.SwitchYardService.start(SwitchYardService.java:93) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22] at java.lang.Thread.run(Thread.java:679) [:1.6.0_22] Caused by: org.switchyard.exception.SwitchYardException: org.switchyard.exception.SwitchYardException: java.lang.IllegalStateException: Cannot create session factory, server locator is closed (maybe it has been garbage collected) at org.switchyard.component.hornetq.deploy.HornetQActivator.start(HornetQActivator.java:229) at org.switchyard.deploy.internal.Activation.start(Deployment.java:524) at org.switchyard.deploy.internal.Deployment.deployServiceBindings(Deployment.java:402) at org.switchyard.deploy.internal.Deployment.doStart(Deployment.java:135) at org.switchyard.deploy.internal.AbstractDeployment.start(AbstractDeployment.java:200) at org.switchyard.as7.extension.deployment.SwitchYardDeployment.start(SwitchYardDeployment.java:105) at org.switchyard.as7.extension.services.SwitchYardService.start(SwitchYardService.java:86) ... 5 more Caused by: org.switchyard.exception.SwitchYardException: java.lang.IllegalStateException: Cannot create session factory, server locator is closed (maybe it has been garbage collected) at org.switchyard.component.hornetq.deploy.InboundHandler.start(InboundHandler.java:96) at org.switchyard.component.hornetq.deploy.HornetQActivator.start(HornetQActivator.java:227) ... 11 more Caused by: java.lang.IllegalStateException: Cannot create session factory, server locator is closed (maybe it has been garbage collected) at org.hornetq.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:548) at org.switchyard.component.hornetq.deploy.InboundHandler.start(InboundHandler.java:90) ... 12 more 17:11:02,613 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report JBAS014777: Services which failed to start: service jboss.deployment.unit."switchyard-quickstarts-hornetq-binding.jar".SwitchYardService: org.jboss.msc.service.StartException in service jboss.deployment.unit."switchyard-quickstarts-hornetq-binding.jar".SwitchYardService: org.switchyard.exception.SwitchYardException: org.switchyard.exception.SwitchYardException: java.lang.IllegalStateException: Cannot create session factory, server locator is closed (maybe it has been garbage collected) {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-620) insufficient error message from bean component

by Tomohisa igarashi (JIRA)

Tomohisa igarashi created SWITCHYARD-620: -------------------------------------------- Summary: insufficient error message from bean component Key: SWITCHYARD-620 URL: https://issues.jboss.org/browse/SWITCHYARD-620 Project: SwitchYard Issue Type: Task Components: component-bean Affects Versions: 0.4 Reporter: Tomohisa igarashi When we got a following message, root cause was swallowed by DefaultHandlerChain#handleMessage() and got hard to understand what happened. {quote} 16:07:00,618 ERROR [org.switchyard.internal.DefaultHandlerChain] (Thread-1 (group:HornetQ-client-global-threads-1898555459)) org.switchyard.component.bean.BeanComponentException: Invocation of operation 'processOrder' on bean component 'org.switchyard.quickstarts.transform.json.ProcessOrderServiceBean' failed with exception. See attached cause. 16:07:00,620 WARN [org.switchyard.internal.ExchangeImpl] (Thread-1 (group:HornetQ-client-global-threads-1898555459)) Fault generated during exchange without a handler: org.switchyard.component.bean.BeanComponentException: Invocation of operation 'processOrder' on bean component 'org.switchyard.quickstarts.transform.json.ProcessOrderServiceBean' failed with exception. See attached cause. {quote} The root cause was following in this case. {quote} java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.switchyard.component.bean.ServiceProxyHandler.handle(ServiceProxyHandler.java:126) at org.switchyard.component.bean.ServiceProxyHandler.handleMessage(ServiceProxyHandler.java:81) at org.switchyard.internal.DefaultHandlerChain.handleMessage(DefaultHandlerChain.java:146) at org.switchyard.internal.DefaultHandlerChain.handle(DefaultHandlerChain.java:121) at org.switchyard.internal.LocalDispatcher.dispatch(LocalExchangeBus.java:72) at org.switchyard.internal.ExchangeImpl.sendInternal(ExchangeImpl.java:255) at org.switchyard.internal.ExchangeImpl.send(ExchangeImpl.java:178) at org.switchyard.component.hornetq.deploy.InboundHandler.onMessage(InboundHandler.java:118) at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:866) at org.hornetq.core.client.impl.ClientConsumerImpl.access$100(ClientConsumerImpl.java:44) at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:983) at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) Caused by: java.lang.IllegalStateException: Singleton not set for ModuleClassLoader for Module "org.hornetq:main" from local module loader @36d1c778 (roots: /opt/switchyard-as7-0.4/modules) at org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton.get(ModuleGroupSingletonProvider.java:73) at org.jboss.weld.Container.instance(Container.java:54) at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:67) at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:104) at org.jboss.weld.proxies.JsonOrderService$1366014918$Proxy$_$$_WeldClientProxy.submitOrder(JsonOrderService$1366014918$Proxy$_$$_WeldClientProxy.java) at org.switchyard.quickstarts.transform.json.ProcessOrderServiceBean.processOrder(ProcessOrderServiceBean.java:17) ... 19 more {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-619) Need a convention for plugin "create" methods and optional parameters

by Tom Cunningham (JIRA)

Tom Cunningham created SWITCHYARD-619: ----------------------------------------- Summary: Need a convention for plugin "create" methods and optional parameters Key: SWITCHYARD-619 URL: https://issues.jboss.org/browse/SWITCHYARD-619 Project: SwitchYard Issue Type: Task Components: tooling Affects Versions: 0.4 Reporter: Tom Cunningham Fix For: 0.4 BPMServicePlugin.java has a create method with 7 parameters - many of which are optional. Many of our other plugins have a similar situation - the ClojurePlugin's create has 6 parameters, and the RulesServicePlugin's create has 3 optional parameters as well. Need a strategy for dealing with this - should the optional parameters be pulled out and put into their own separate modifyX methods? from Keith from irc : 12:37:57 PM) kcbabo: tcunning: I'm not sure, there are a couple of options with separate pros and cons (12:38:10 PM) kcbabo: tcunning: one thing with forge is that you can "cd" into a resource, IIRC (12:38:20 PM) kcbabo: tcunning: which gives you context-senstive command access (12:38:42 PM) kcbabo: tcunning: so you could CD into a service component (for example) and have localized commands to modify stuff (12:38:57 PM) kcbabo: tcunning: another option is to simply add more commands that can be used to modify stuff (12:39:10 PM) kcbabo: tcunning: the drawback there is that you could end up with loads of commands (12:39:27 PM) kcbabo: tcunning: I think a JIRA is a good idea - not sure we'll reach agreement in time for 0.4, but you never know :-) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-618) Register resource dependencies with container during deployment

by Rob Cernich (JIRA)

Rob Cernich created SWITCHYARD-618: -------------------------------------- Summary: Register resource dependencies with container during deployment Key: SWITCHYARD-618 URL: https://issues.jboss.org/browse/SWITCHYARD-618 Project: SwitchYard Issue Type: Enhancement Components: deployment Reporter: Rob Cernich AS7 provides a mechanism for registering dependencies on resources. Make sure SwitchYard is using this mechanism appropriately. (For example, registering a dependency on a queue, datasource or specific JNDI name and type.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-617) We should require a minimum version of ant for the installer

by Tom Cunningham (JIRA)

Tom Cunningham created SWITCHYARD-617: ----------------------------------------- Summary: We should require a minimum version of ant for the installer Key: SWITCHYARD-617 URL: https://issues.jboss.org/browse/SWITCHYARD-617 Project: SwitchYard Issue Type: Task Components: distribution Affects Versions: 0.4 Reporter: Tom Cunningham Assignee: Tom Cunningham Priority: Minor Fix For: 0.4 We should require a minimum version of ant for running the installer - it would cut down on our test matrix. dward is seeing : Running the installer (from the expanded target zip): (02:02:54 PM) errantepiphany: [echo] Unzipped SwitchYard forge plugin. (02:02:55 PM) errantepiphany: [echo] Installing forge plugin to /home/errantepiphany/.forge ... (02:02:55 PM) errantepiphany: [java] javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found (02:03:21 PM) errantepiphany: tcunning: java version "1.6.0_29" Using ant 1.7.1. We may want to require ant 1.8.1 for running the script. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWITCHYARD-616) Server hangs during shutdown when application references JMS queues

by Rob Cernich (JIRA)

Rob Cernich created SWITCHYARD-616: -------------------------------------- Summary: Server hangs during shutdown when application references JMS queues Key: SWITCHYARD-616 URL: https://issues.jboss.org/browse/SWITCHYARD-616 Project: SwitchYard Issue Type: Bug Components: component-camel, component-hornetq, quickstarts Affects Versions: 0.3 Reporter: Rob Cernich When running the policy transaction quickstart, the server appears to hang during shutdown. Shutdown usually completes in 3-5 minutes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

switchyard-issues January 2012