no, that would just instruct convention to scan from that package
down, what you need to do (I have no idea how archetypes work), is to
get the package name, and substring from "actions.", replace "." by
"/" and that will be the path under WEB-INF/content. If you can't
determine were to put the files at runtime, then you can either 1)
don't let users pick the package, 2) use @Result annotations to
indicate where the results are (kind of defeating the purpose of using
Convention)
musachy
On Wed, Apr 8, 2009 at 10:24 AM, Lukasz Lenart
<lukasz.len...@googlemail.com> wrote:
> 2009/4/8 Musachy Barroso <musa...@gmail.com>:
>> The archetype is generating the jsps in the wrong location, it is
>> missing the namespace in the patch. For example, if I enter
>> "actions.test" for the package, the jsp is generated as
>> WEB-INF/content/hello.jsp, it should be WEB-INF/content/test/hello.jsp
>
> Archetype will setup actions.test as a basePackage in struts.xml, it
> should be ok then?
>
> <constant name="struts.convention.package.locators.basePackage"
> value="${package}"/>
>
>
> Regards
> --
> Lukasz
> http://www.lenart.org.pl/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
> For additional commands, e-mail: user-h...@struts.apache.org
>
>
--
"Hey you! Would you help me to carry the stone?" Pink Floyd
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org
