This is even more simple: 

use strict;
use warnings;
use Mojolicious::Lite;

get '/' => sub {
    my $c   = shift;
    $c->stash( nose => $c->param( 'nose' ) || 'karl' );
    $c->render( template => 'nose', format => 'xml' );
};

app->start;

__DATA__
@@ nose.xml.ep
<?xml version="1.0" encoding="UTF-8"?>
<myapp>
    <nose><%= $nose %></nose>
</myapp>

[download]

I can understand wanting to retain the method you use to create the XML document itself (better validation), but do you really need those objects?

jeffa

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

In reply to Re: RFC: Mojolicious::Lite and Moo: A Very Basic Application Layout by jeffa
in thread RFC: Mojolicious::Lite and Moo: A Very Basic Application Layout by karlgoethebier

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.