1:07 p.m.
Lincoln and Paul, thanks for the responses, the DependencyFacet and
ResourceFacet have both worked very well for my purposes.
At this point, I am trying to code a command which will create a simple
Spring MVC controller from a given entity. Thus, it is very similar to
the current scaffold from-entity command in Forge, the main difference
being that it will use Spring. I have been looking at that command as
an inspiration for its Spring counterpart.
However, the bulk of the work seems to be done by the
generateFromEntity() method, which I cannot find a definition for in the
Forge core.
I was hoping that someone on forge-dev could potentially recommend a
starting point for creating and manipulating a Java class using Forge tools.
Thanks,
Ryan
On 11/14/2011 05:24 PM, Lincoln Baxter, III wrote:
I'd still recommend using the DependencyFacet before you start
using
the Maven facets :)
On Mon, Nov 14, 2011 at 11:18 PM, Paul Bakker
<paul.bakker.nl(a)gmail.com <mailto:paul.bakker.nl@gmail.com>> wrote:
Hey Ryan,
What do you want to do exactly with the POM? Probably there is a
facet already, and if not we should consider adding one…
Besides that the ResourceFacet and JavaSourceFacet are for low
level resource access and there are facets related to working with
Maven facet and plugins which probably covers most of what you
would need.
Paul
p.s. Spring? Really…? ;-)
http://www.slideshare.net/ertmanb/javaone-2011-migrating-spring-applicati...
On Nov 14, 2011, at 11:09 PM, Lincoln Baxter, III wrote:
> Hey Ryan,
>
> Copying forge-dev so everyone can give thoughts. We (I) really
> need to get the website up with the tutorials so things like this
> are more straightforward. Sorry!
>
> If you use the built-in "new-plugin" command, you get the POM
> creation stuff for free. I don't see a reason to duplicate that.
> It'll basically just give you a java maven project, which can
> then be customized using the DependencyFacet, and other facets
> like JavaSourceFacet.
>
> Mostly we don't assume we need to create projects, because we
> just operate on a "new-project" or any other existing project.
>
> For examples of this, take a look at the javaee-impl/ module in
> the forge core/ project on GitHub. This is a pretty comprehensive
> example of the intended architecture (facets to abstract
> functionality away from the project, then plugins to interact
> with the facets.)
>
> Glad to see this! Looking forward to doing some spring stuff!
> ~Lincoln
>
> On Mon, Nov 14, 2011 at 10:52 PM, Ryan Bradley
> <rbradley(a)redhat.com <mailto:rbradley@redhat.com>> wrote:
>
> Hi Lincoln,
>
> I'm not sure if you remember, but Marius introduced us at the
> JBoss face-to-face meeting in Toronto a few months ago. I've
> just started working on a Forge plugin that can be used to
> create Spring web applications.
>
> However, Marius doesn't have much experience with the Forge
> API, so I was wondering if I could ask you a question. I was
> wondering how I could use Forge to create and edit new files.
> For example, when the user creates a new project, the plugin
> should create files such as a POM for the web app. If
> there's a simple answer, or a good spot to look within the
> Forge core, that would be much appreciated.
>
> Thanks,
> Ryan
>
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.com <http://ocpsoft.com/>
> http://scrumshark.com <http://scrumshark.com/>
> "Keep it Simple"
> _______________________________________________
> forge-dev mailing list
> forge-dev(a)lists.jboss.org <mailto:forge-dev@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/forge-dev
--
Lincoln Baxter, III
http://ocpsoft.com
http://scrumshark.com
"Keep it Simple"