[
https://issues.jboss.org/browse/SEAMCATCH-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Porter resolved SEAMCATCH-40.
-----------------------------------
Resolution: Done
> New example w/o REST
> --------------------
>
> Key: SEAMCATCH-40
> URL: https://issues.jboss.org/browse/SEAMCATCH-40
> Project: Seam Catch
> Issue Type: Task
> Components: Example
> Reporter: Jason Porter
> Assignee: Jason Porter
> Fix For: 3.0.0.Beta2
>
>
> A new example should be done and the current one retired. Here's the email
> thread talking about an idea between myself and Dan Allen:
> From Jason:
> Since we're being asked for examples to give to QE and Jozef has
> integrated catch into his module (and has some tests for it, and also
> asked me to remove the jaxrs example) I'm not quite sure what to do
> for a new example that wouldn't confuse because because Rest, Faces
> and Servlet all have Catch integrations. I could do one for wicket,
> but once wicket has an integration I'd need to retire that one as
> well. Do you have any ideas?
> From Dan:
> I would go with simple and easy :) In your case, the example is going to be
> about show-and-tell more than test coverage. My suggestion would be to create
> an index page with a couple buttons.
> Catch error and:
> Show pretty error
> Redirect to page
> Log error and ignore
> You can just base the examples on a failing Servlet. You could also include
> an example of throwing an exception to Catch explicitly (instead of waiting
> for it to bubble from Servlet). But again, keep it simple.
> Just give the user a feel for what they can do. Make sure you have the
> simplest possible example in there, so that they can see the big picture.
> Then, add others that are fancier as you see fit.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues
