[jbosstools-dev] How to import switchyard tools?

[Rob Cernich]

Hey Rob,

I think it's great that you're taking an interest in the SwitchYard tooling.  I've added comments inline.

Any and all feedback is welcome.  Please feel free to meet up with us in #switchyard on freenode and https://community.jboss.org/en/switchyard/dev?view=discussions.

Here's the link to our developer guidelines:  https://community.jboss.org/wiki/DevelopmentOnSwitchYard
And a crude list of required features in your dev environment (we're not using a target platform, yet): https://community.jboss.org/wiki/DevelopmentOnSwitchYard-EclipsePlug-ins

Best,
Rob

----- Original Message -----
> Hi all:
> 
> I've cloned the repo git://github.com/jboss-switchyard/tools.git but
> for
> some reason I can't import the projects. They contain no .project
> file,
> so I assume I must import them as a maven project? In a clean
> workspace,
> trying to import them as a maven project, the maven project importer
> wizard simply freezes. ANy ideas?

Yes.  You import them as Maven projects.  We will not be committing any .project, etc. files.  Personally, I feel this is bad form, and with m2e it is completely unnecessary.

One problem you will encounter is that we repackage some jars in the tools, so you will need to run "mvn process-sources" which will download the required jar files.  (You may want to run "mvn install" prior to importing, just to make your life easy.)

> 
> If anyone's curious why I'm trying to import this, it's because the
> project structure was forked / cloned / adapted from the esb project,
> which, as we've all seen lately, has tons of problems associated with
> it. So I'd like to get the jump on cleaning up the switchyard project
> structure before it reaches 1.0, to help avoid a lot of these issues,
> and to make use of all of the recent additions to API available in
> webtools which the esb project has NOT been using at all.

Actually, the project structure was created from scratch and follows the same pattern as other Eclipse projects built using Tycho.  That said, I would love to hear about problems you've had in the past.

FYI, the SwitchYard facet version is aligned with application version (i.e. config version), which is (will be) distinct from any runtime version.  In addition, there is no runtime integration in SwitchYard.  It simply allows association with any server that provides a JEE runtime.  SwitchYard capabilities can be added to any JEE project.  By default, a new SwitchYard project will be a "Utility Module" project.  SwitchYard adds a low priority module factory that exposes the core JEEDeployableFactory to the system so a SwitchYard utility module may be deployed from the workspace (i.e. run as-->run on server; you can still deploy to the server without this, but not using "run as").

Part of the reason for integrating this way is that while the SwitchYard runtime may be installed in AS7, it is possible to construct a self-contained SwitchYard application that can be deployed to any JEE/web server (we used to have a quickstart that ran on tomcat; not sure if that's been kept up to date or not).

> 
> Anyway, any advice is definitely appreciated.
>