Team,
To simplify building up a WINK-based JAX-RS application, I wanted to float some ideas. Currently, if I'm a JAX-RS app developer and want to use WINK, I have to pull the SVN repo, build from trunk, then build samples, then go break open a sample .war and see what it looks like. To simplify this process for app developers wanting to use WINK, here are a few ideas: 1) provide a template area where app developers can drop their app source code, and an ANT script that will build everything up, including the final .war file the user will need. Pros: simple! Developers don't have to crack open any .war files, learn any new IDEs, etc. Could become part of a future tools suite, allowing developers (or IDE tool) to pick and choose what libraries to include in the .war, and build up the proper data in the deployment metadata. Cons: requires developers to have ANT installed. Probably requires developers to pull WINK source (depending on how this type of solution might be provided) 2) build a template war file, where app developers can drop in their already-built app Pros: also simple. Smaller amount of work for the WINK team to develop this solution, I think. Does not require pulling WINK source from SVN, no need for ANT or an IDE. Cons: WAR file may have much more than the app developer actually needs, thus a heavy disk footprint, but developer could simply remove libs or components that are not needed. Personally, I like (2). This isn't intended to open a big tools discussion, I just wanted to propose an idea about making life easy for app developers wanting to prototype their JAX-RS apps with WINK. What other ideas are there? What kind of tools does Symphony provide? Thanks. mike
