<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: @route decorator - path was not found in Splunk Dev</title>
    <link>https://community.splunk.com/t5/Splunk-Dev/route-decorator-path-was-not-found/m-p/107775#M1604</link>
    <description>&lt;P&gt;I wound up placing the additional end points into a controller class. This seemed to work fine, it would be nice to keep that code in the same class though.&lt;/P&gt;</description>
    <pubDate>Tue, 01 May 2012 05:18:13 GMT</pubDate>
    <dc:creator>jamesaarondevli</dc:creator>
    <dc:date>2012-05-01T05:18:13Z</dc:date>
    <item>
      <title>@route decorator - path was not found</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/route-decorator-path-was-not-found/m-p/107774#M1603</link>
      <description>&lt;P&gt;Hi guys,&lt;/P&gt;

&lt;P&gt;I've been putting together a custom Splunk module and encountered some trouble trying to make one of my module handlers methods available via a URI. I have been trying to make the method available by using the @route decorator as per the below.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;@route('/:action=setAlarmState')
def setAlarmState():
       logger.info('setAlarmState reached for alarm')
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I am then trying to access this method via the following URL:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&lt;A href="http://localhost:8443/en-US/module/system/Splunk.Module.AlarmManager/setAlarmState" target="test_blank"&gt;http://localhost:8443/en-US/module/system/Splunk.Module.AlarmManager/setAlarmState&lt;/A&gt;
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Any advice as to how this ought to be done would be great.&lt;/P&gt;

&lt;P&gt;EDIT - My handler class inherits from ModuleHandler, if that information is of any use.&lt;/P&gt;

&lt;P&gt;Cheers,&lt;BR /&gt;
James&lt;/P&gt;</description>
      <pubDate>Tue, 03 Apr 2012 06:05:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/route-decorator-path-was-not-found/m-p/107774#M1603</guid>
      <dc:creator>jamesaarondevli</dc:creator>
      <dc:date>2012-04-03T06:05:44Z</dc:date>
    </item>
    <item>
      <title>Re: @route decorator - path was not found</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/route-decorator-path-was-not-found/m-p/107775#M1604</link>
      <description>&lt;P&gt;I wound up placing the additional end points into a controller class. This seemed to work fine, it would be nice to keep that code in the same class though.&lt;/P&gt;</description>
      <pubDate>Tue, 01 May 2012 05:18:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/route-decorator-path-was-not-found/m-p/107775#M1604</guid>
      <dc:creator>jamesaarondevli</dc:creator>
      <dc:date>2012-05-01T05:18:13Z</dc:date>
    </item>
  </channel>
</rss>

