[jboss-jira] [JBoss JIRA] (AS7-3010) jboss-javaee6-webapp-blank-archetype needs to generate "resources" folder at WEB-INF level for JSF 2.0 resource libraries

> Hi Pete, > > I am using the snapshot and the folders you mentioned are indeed getting generated. I am talking about JSF 2.0 specs section 2.6.1 which says that in the deployed .war file, we can have folder called "resources" at "WEB-INF" level and any subfolder underneath that will be referred to as "library" in components like <h:outputscript library="..." ...>, <h:graphicImage library="..." .../> So with the folders that you mentioned, I am not sure, which one will generate the .war structure like : > > MyJSFApp.war > | > |---resources > |---myscripts > |--- myscript.js > |--images > |--foo.gif > | > |---WEB-INF > > and then I can write <h:outputscript library="myscripts" name="myscript.js" .../> > > > right now, to get this packaging structure, I am manually creating the "resources" folder in the generated code under "src\main\webapp" > > Thx > > Vimal > > On 14/12/2011 1:43 AM, Pete Muir wrote: > >> If you use the snapshots of the archetypes I built, it should generate a full set of folders (src/main/java, src/main resources, src/test/java, src/test/resources). If you are using the snapshot archetype and this isn't working, open an AS7 issue assigned to me. > >> > >> On 12 Dec 2011, at 00:56, Vimal Kansal wrote: > >> >> >>> Hi Pete, >> >>> >> >>> I was just wondering if a "resources" folder should also be generated as part of web app archetype, to take care of JSF 2.0 feature of libraries? >> >>> >> >>> Thx >> >>> >> >>> Vimal >> >>> >> >>> On 7/12/2011 9:41 PM, Pete Muir wrote: >>> >>>> BTW you can file AS7 issues in the docs category assigned to me for the archetypes. >>> >>>> >>> >>>> On 7 Dec 2011, at 10:37, Vimal Kansal wrote: >>> >>>> >>>> >>>>> Thanks guys. The snapshot archetype is working just fine now :-) >>>> >>>>> >>>> >>>>> On 7/12/2011 9:29 PM, Max Rydahl Andersen wrote: >>>>>>>> >>>>>>>>> I am sure, I am must be doing things the wrong way, but can you please writeup something(probably with a sample application which has one or 2 pages, CDI bean and a resource bundle etc) to show the typical workflow like this : >>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>>> • User creates a blank webapp from inside the eclipse using the "blank" archetype. >>>>>>>> >>>>>>>>> • After creating the blank project, user goes ahead with adding stuff like java classes, CDI beans, other resources using the eclipse wizards, as usual. >>>>>>>> >>>>>>>>> • User then deploys the app using the eclipse wizards. >>>>>>> >>>>>>>> I'll pass this one over to the tools team if they can take it? >>>>> >>>>>> we'll get on writing up docs after M5 is ready. >>>>> >>>>>> >>>>> >>>>>> Until then there is nothing special about these compared to normal eclipse usage (assuming you know those ;). >>>>> >>>>>> >>>>> >>>>>> i.e. the steps after I create a project in http://vimeo.com/17669512 is the same for these AFAICS. >>>>> >>>>>> >>>>> >>>>>> The only thing to be aware of with Maven is what Fred points out - if you do changes to the project pom.xml run Update Project Configuration from the Maven menu to be sure all of Eclipse is aware of your changes. >>>>> >>>>>> >>>>> >>>>>> /max >>>>> >>>>>> http://about.me/maxandersen >>>>> >>>>>> >>>>> >>>>>> >>>>> >>>>>> >

jboss-javaee6-webapp-blank-archetype needs to generate "resources" folder at WEB-INF level for JSF 2.0 resource libraries ------------------------------------------------------------------------------------------------------------------------- Key: AS7-3010 URL: https://issues.jboss.org/browse/AS7-3010 Project: Application Server 7 Issue Type: Bug Components: Documentation Reporter: Vimal Kansal Assignee: Pete Muir Generate src/main/webapp/resources folder. The JSF 2.0 specs section 2.6.1 which says that in the deployed .war file, we can have folder called "resources" at "WEB-INF" level and any subfolder underneath that will be referred to as "library" in components like <h:outputscript library="..." ...>, <h:graphicImage library="..." .../>.