Yes, the plan is that seam-mock will be entirely standalone. I want to use the seam prefix for identification/recognition purposes.<br><br>I discussed with legal and I know understand the rules for using APL code. I simply have to maintain the header, add the JBoss copyright w/o license information, include apl.txt and NOTEICE.txt in the distribution. So were are all good ;)<br>
<br>I'll be working on merging all the mocks from Seam 2, restbay, and Wicket into the Seam 3 seam-mock module this week. Please feel free to provide feedback as I get stuff checked in. What is in there now is just a dump from Seam 2.<br>
<br>-Dan<br><br><div class="gmail_quote">On Tue, May 5, 2009 at 9:34 AM, Jay Balunas <span dir="ltr"><<a href="mailto:tech4j@gmail.com">tech4j@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
agreed - as long as RF can grab the individual module from seam ( and not pull in others ) it should be fine. The concern would be too many cross project dependencies making working with just one of the projects tricky ( and harder to productize ).<div>
<div></div><div class="h5"><br>
<br><br><div class="gmail_quote">On Tue, May 5, 2009 at 8:33 AM, Pete Muir <span dir="ltr"><<a href="mailto:pmuir@redhat.com" target="_blank">pmuir@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Can we share these mocks like we discussed for graph validation - RF imports the module from the "Seam" space - but the Seam module doesn't depend on other Seam code?<div><div></div><div><br>
<br>
On 30 Apr 2009, at 15:13, Jay Balunas wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
You may also want to check out <a href="http://www.jboss.org/community/wiki/TestDrivenJSFDevelopment" target="_blank">http://www.jboss.org/community/wiki/TestDrivenJSFDevelopment</a><br>
<br>
Alex Smirnov has been working on this to help with RF 4.0 development. Perhaps we can collaborate.<br>
<br>
On Wed, Apr 29, 2009 at 11:10 AM, Dan Allen <<a href="mailto:dan.j.allen@gmail.com" target="_blank">dan.j.allen@gmail.com</a>> wrote:<br>
It's hard to believe that for as long as JSF has been around, the only decent repository of mocks for the JSF API comes not from the implementation, but rather from all but dead and irrelevant project at Apache (Shale). Of course, Seam 2 forged it's own path and has a healthy set of mocks, although still somewhat incomplete and vagrant. In the Seam 3 spirit of modularity, I would like to migrate the Seam 2 mocks into a mock module in Seam 3 that provides mock/stub object for various Java EE APIs. I plan to categorize them by spec under the org.jboss.seam.mock folder<br>
<br>
JSF - org.jboss.seam.mock.faces<br>
Servlet - org.jboss.seam.mock.servlet<br>
etc<br>
<br>
This module should not depend on any other module so that it is easy to reuse, perhaps even outside of the Seam framework. Perhaps seam-mock can end up replacing Shale test. Who knows. We'll just let it play out. Please contribute your ideas/use cases!<br>
<br>
<a href="http://anonsvn.jboss.org/repos/seam/modules/trunk/mock/" target="_blank">http://anonsvn.jboss.org/repos/seam/modules/trunk/mock/</a><br>
<br>
As for the functionality, my feeling is that the mocks should be functional as long as each class behaves like a bean. That means it shouldn't parse XML documents or make similar assumptions. But they should be easy enough to extend that perhaps you can add that functionality in your test case or we can think about providing an additional subclass or helper if the need is common (perhaps parsing an web.xml document).<br>
<br>
-Dan<br>
<br>
-- <br>
Dan Allen<br>
Senior Software Engineer, Red Hat | Author of Seam in Action<br>
<br>
<a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br>
<a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br>
<a href="http://in.relation.to/Bloggers/Dan" target="_blank">http://in.relation.to/Bloggers/Dan</a><br>
<br>
NOTE: While I make a strong effort to keep up with my email on a daily<br>
basis, personal or other work matters can sometimes keep me away<br>
from my email. If you contact me, but don't hear back for more than a week,<br>
it is very likely that I am excessively backlogged or the message was<br>
caught in the spam filters. Please don't hesitate to resend a message if<br>
you feel that it did not reach my attention.<br>
<br>
_______________________________________________<br>
seam-dev mailing list<br>
<a href="mailto:seam-dev@lists.jboss.org" target="_blank">seam-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
<br>
<br>
<br>
<br>
-- <br>
blog: <a href="http://in.relation.to/Bloggers/Jay" target="_blank">http://in.relation.to/Bloggers/Jay</a><br>
_______________________________________________<br>
seam-dev mailing list<br>
<a href="mailto:seam-dev@lists.jboss.org" target="_blank">seam-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
</blockquote>
<br>
--<br></div></div><div>
Pete Muir<br>
<a href="http://www.seamframework.org" target="_blank">http://www.seamframework.org</a><br>
</div><a href="http://in.relation.to/Bloggers/Pete" target="_blank">http://in.relation.to/Bloggers/Pete</a><br>
<br>
</blockquote></div><br><br clear="all"><br>-- <br>blog: <a href="http://in.relation.to/Bloggers/Jay" target="_blank">http://in.relation.to/Bloggers/Jay</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br>
<a href="http://in.relation.to/Bloggers/Dan">http://in.relation.to/Bloggers/Dan</a><br><br>NOTE: While I make a strong effort to keep up with my email on a daily<br>basis, personal or other work matters can sometimes keep me away<br>
from my email. If you contact me, but don't hear back for more than a week,<br>it is very likely that I am excessively backlogged or the message was<br>caught in the spam filters. Please don't hesitate to resend a message if<br>
you feel that it did not reach my attention.<br>