[kcbabo]

Thanks, Gary.

[dward]

When creating a new switchyard project using the tooling - specficically one with a rules component - I noticed that it created an action by default.  I question if we should really be doing this.  It's not required by the runtime, which will assume it's own default.  That being said, if we want a default action in the generated configuration, then the action type should be EXECUTE, not FIRE_ALL_RULES.  This would match the runtime default.

[dward]

For any mapping (whether it be an input, output or global), only expression is required.  scope, variable and expressionType should all be nullable, and not show up at all in the xml if not specified (right now it shows as an empty string in the generated xml, and can't be removed).  An example of this is when specifying input mappings for a rules component, a variable name means nothing.  They are just facts for drools to chew on.  Now, for global mappings, a variable makes sense.

[dward]

I tested using the tooling 100% (no external vi editing...) to create a new in-out rules-component service, with both a java interface and a wsdl interface + soap binding.  Besides the comments I already made about defaults above, everything worked well.  If interested, you can check it out, as I attached it for an end-user who needed help, here.  MyTest.java is the best place to start.

[dward]

There is a missing action type for the rules component: INSERT.  This gets added to EXECUTE, FIRE_ALL_RULES, and FIRE_UNTIL_HALT.

[mageshbk]

All-in-one distribution: Seem to run fine on Windows. I tested some QS and they went well.

BPEL QS: Should we have the Readme.md updated in the root folder about XTS samples? - trivial

More QS tests underway...

[kcbabo]

Some updates on my testing:

• Installer against AS 7.1.1.Final
  • Installed console - good
  • Installed BPEL - good
  • Installed Forge - bad (https://issues.jboss.org/browse/SWITCHYARD-1240)
  • Tested clustered setup
• All-in-one distribution
  • Tested bean-service quickstart
  • Verified console populates metrics correctly

The Forge issue is ugly but it has a workaround which involves disabling Rules and BPM support.  Not a stopper for 0.7, IMHO.

[igarashitm]

On Fedora17 OpenJDK 1.7 64bit

• All-in-one
  • Tested jca-inflow-hornetq, policy-transaction, transform-xslt, validate-xml works fine
  • console showed those correctly including Transformers and Validators

[kcbabo]

I have completed the 0.7 Release Overview.  Feel free to make corrections and additions:

https://community.jboss.org/wiki/SwitchYardReleaseOverview-07

[dward]

I've finally updated the documentation regarding BPM and Rules services to match the new configuration.  Here are the links:

• Knowledge Services
  • BPM Services
  • Rules Services

If you find anything I messed up, please let me know.  Thanks!

[phk]

Hi,

I just downloaded "JBoss Developer Studio 6.0.0 Stand Alone Universal Binary" from redhat.com followed by the switchyard-site-assembly-0.7.0.Final.zip from the http://www.jboss.org/switchyard/downloads site.

When following the guide https://docs.jboss.org/author/display/SWITCHYARD/Installing+Eclipse+Tooling things come to a grinding halt when adding the tools to JBDS:

Platform is Windows 7 64-bit with "default JDK" chosen during installation.

JBDS is:

Version: 6.0.0.GA

Build id: GA-v20121206-1855-B186

Build date: 20121206-1855

Not sure whether it's complaining over some EMF modeling things that are apparently missing from the stock distribution of JBDS ?

Any pointers?

Cheers,

Paul

[rcernich]

Hey Paul,

I've finally gotten around to updating the install documentation for JBDS.  Please see the new step 3, which requires you to add the following update sites to your Install/Update preferences prior to installing SwitchYard:

• http://download.eclipse.org/modeling/emf/compare/updates/releases/1.3/
• http://download.eclipse.org/tools/orbit/downloads/drops/R20120526062928/repository/

The updated documentation can be found here:  https://docs.jboss.org/author/display/SWITCHYARD/Installing+Eclipse+Tooling

Hope that helps.

Best,

Rob

[phk]

Hi Rob,

A quick followup - just ran through the installation again adding the new update sites and everything works out nicely now (using the 0.7.0 assembly file).

Thanks for taking time out to fix this.

/Paul