This content has been marked as final.
Show 3 replies
-
1. Re: Some of my unscheduled jira issues that I think should b
matt.drees Sep 25, 2007 1:01 PM (in response to matt.drees)Oh, silly forum.
The title should read "Some of my unscheduled jira issues that I think should be slated for 2.0" -
2. Re: Some of my unscheduled jira issues that I think should b
pmuir Sep 25, 2007 1:09 PM (in response to matt.drees)"matt.drees" wrote:
1.
http://jira.jboss.com/jira/browse/JBSEAM-1762
- Very simple fix; bug breaks session usage in tests
+1, I've scheduled it (though Norman might deschedule it ;) )2.
http://jira.jboss.com/jira/browse/JBSEAM-1257
- This can be very confusing, especially if a newbie tries to put components in collections. Potentially a two-sentence documentation fix. Or apply my patch.
I want Gavin to review this, so I don't think its going to happen in the GA timeframe. Can you add an item to the SeamProblemsFAQ as a start?3.
http://jira.jboss.com/jira/browse/JBSEAM-1647
- This could be a one-sentence fix. And I think it's a very important thing to document. Otherwise, a newbie might do something like@In String name; setName(String name){ this.name = name; }
and be very confused why component.setName("joe") is effectively a no-op.
+14.
http://jira.jboss.com/jira/browse/JBSEAM-1940
Wrong documentation is very bad. Easy to fix (remove a paragraph).
This needs double checking (that the docs are wrong, and its not a bug.)If there are ways I can contribute to fixing these, let me know.
Documentation patches (especially when it's a concept thats badly documented) are great as then we get a better understanding of whats wrong with the current explanation!
Thanks Matt! -
3. Re: Some of my unscheduled jira issues that I think should b
matt.drees Sep 27, 2007 2:13 AM (in response to matt.drees)Hey Pete, any chance you could also ask Gavin to make a call on http://jira.jboss.com/jira/browse/JBSEAM-1814? It'd be nice to have that cleared up soon.
Thanks