Here's the offline site assembly:
To test the tools, follow these instructions:
For step 2, you would use the above URL instead of the link on the downloads page for the site assembly.
BTW, to test building an application using the staged 0.5.0.Final artifacts, you will need to add a mirror to your Maven settings.xml (located in $HOME/.m2/) :
<mirrors> <mirror> <id>jboss-staging-repository-group</id> <mirrorOf>jboss-public-repository-group</mirrorOf> <name>JBoss.org Staging Repository Group</name> <url>https://repository.jboss.org/nexus/content/groups/staging/</url> </mirror> </mirrors>
Tested on Fedora 17 x86_64 with:
java version "1.7.0_03-icedtea"
OpenJDK Runtime Environment (fedora-2.2.1.fc17.8-x86_64)
- Unzipped and started AS7 with SY - SUCCESS
- Built all quickstarts with no SY artifacts in M2 repo - SUCCESS
- Deployed following quickstarts to SY AS7 and tested according to README.md
demos/helpdesk-webapp - got an error - http://pastebin.com/vtnhaeBw
demos/orders - succeeded, but old port 18001 in README.md should be 8080
Almost all of them works with JDK7 I have seen a few build error in core repo though.
Tools=Minimal SwitchYard install (as documented under Development Builds here: https://docs.jboss.org/author/display/SWITCHYARD/Installing+Eclipse+Tooling)
Built an application from the ground up using the Eclipse tooling:
- Create a new project
- Create a "bean" component
- Flesh out service interface
- Implement service methods in bean
- Create service test
- Implement service test
- Run service test (Run As => JUnit Test)
- Generate WSDL
- Promote service
- Add SOAP binding
- Code transformers
- Deploy (from tooling)
- Test using Eclipse Web Services Tester
The process is documented here https://docs.jboss.org/author/display/SWITCHYARD/Quick+Start (still need to add screen shots).
- Need to point to the JBT 3.3 stable update site or install becomes unstable (updated doc)
- From/to for scanned transformers are reversed in properties view (i.e. the from column actually shows the to type and vice versa)
Other than that, everything worked well.
I just ran through the helpdesk-webapp, going down various paths, with no issues. Of course, our environments are a bit different: I'm on Mac OSX 10.7.4 using Apple JDK 1.6.0_33. Still, I'm curious what step(s) you were doing in the web application to cause the stack trace. Do you remember? Can you recreate and let me know?