headers
Jason Porter | 1 Nov 2011 06:37
Picon
Gravatar

I need a little help

I have below a list of 38 open issues in Seam (excluding most of the Wicket ones as the Wicket module, from my understanding, has been pulled into the wicket project itself. If that's not the case please let me know) which are Blockers, Critical or have a high vote count (when I say "high" I mean more than two as most issues don't have many votes). I'm going to be focusing as much as I can until Beta5 on bug fixing, however, any help I can get from you would be very greatly appreciated. In help it may not exactly be a bug fix, but could be as simple as verifying an issue is still a problem. Many of these issues extend back to early in the year or even last year. Thank you very much in advance for anyone who can spare some time to help out with this. If you are able to help, please globally respond to this list so others don't end up repeating the work.


I also think this is a good list for us to work from as they're problem our users have identified as impacting them from using Seam 3.

* https://issues.jboss.org/browse/SEAMFACES-79 -- Provide <s:restrictView> tag for securing pages
* https://issues.jboss.org/browse/SOLDER-99 -- javax.el.ExpressionFactory can not be injected because it has final methods
* https://issues.jboss.org/browse/SEAMSECURITY-83 -- IdentityImpl.logout not invalidating session
* https://issues.jboss.org/browse/SEAMSECURITY-71 -- Improve LDAP integration in general
* https://issues.jboss.org/browse/SEAMREMOTING-6 -- Comet requests for Seam Remoting
* https://issues.jboss.org/browse/SEAMPERSIST-18 -- <at> Transactional not inherited in larger hierarchies
* https://issues.jboss.org/browse/SEAMFACES-208 -- Support for resolving no argument methods in an EL value expression
* https://issues.jboss.org/browse/SEAMFACES-147 -- Add support for binding methods (view actions) to view enums
* https://issues.jboss.org/browse/SOLDER-268 -- Conversation are only for JSF: Please make then available for plain servlets and JSP
* https://issues.jboss.org/browse/SEAMSECURITY-22 -- Basic authentication with no security drools and no picketlink defined in seam-beans.xml throws exception
* https://issues.jboss.org/browse/SEAMSECURITY-17 -- Servlet Filter to pick up security information for Seam after Java EE web container security
* https://issues.jboss.org/browse/SEAMREMOTING-16 -- constraint by inclusion on remote calls object fields
* https://issues.jboss.org/browse/SEAMREMOTING-14 -- use ExceptionFilter in Remoting
* https://issues.jboss.org/browse/SEAMREMOTING-12 -- Messages component gets wrong locale in when called with seam remoting ( <at> WebRemote)
* https://issues.jboss.org/browse/SEAMREMOTING-8 -- Support for transient remoting types
* https://issues.jboss.org/browse/SEAMPERSIST-59 -- Implement EntityHome from Seam 2
* https://issues.jboss.org/browse/SEAMFACES-193 -- PrettyFaces URL rewriting is not happening when intercepted via <at> LoginView
* https://issues.jboss.org/browse/SEAMFACES-114 -- DeploymentException: WELD-001408
* https://issues.jboss.org/browse/SEAMFACES-76 -- Cannot deploy using Beta2 inside a WAR inside an EAR on Jboss6 Final
* https://issues.jboss.org/browse/SEAMPERSIST-72 -- Seam Persistence does not work in Tomcat
* https://issues.jboss.org/browse/SOLDER-220 -- Seam-config ignores WEB-INF/beans.xml (and WEB-INF/seam-beans.xml) in jboss 7 and tomcat 6 for seam-config configuration (but not weld configuration)
* https://issues.jboss.org/browse/SOLDER-51 -- Decouple service handler annotation from implementation class
* https://issues.jboss.org/browse/SEAMPERSIST-67 -- LazyInitializationException threw when persist a Many to Many collection of an entity.
* https://issues.jboss.org/browse/SEAM-99 -- java.lang.IllegalStateException: BaseTransaction.checkTransactionState - thread is already associated with a transaction!
* https://issues.jboss.org/browse/SOLDER-284 -- It should be decided if seam-beans.xml should still be called seam-beans.xml in solder.
* https://issues.jboss.org/browse/SOLDER-277 -- Add <distributable/> to web-fragment.xml
* https://issues.jboss.org/browse/SOLDER-240 -- ServletContextAttributeProvider uses wrong servlet ctx. attribute name to lookup the bean manager
* https://issues.jboss.org/browse/SOLDER-116 -- BeanBuilder create beans that don't support InjectionPoint injection
* https://issues.jboss.org/browse/SEAMSECURITY-123 -- JpaIdentityStore findIdentityObject has hardcoded entity classes in the query
* https://issues.jboss.org/browse/SEAMSECURITY-121 -- [Regression] 3.1.0.Beta4 eats exceptions in IdentityImpl + returns RESPONSE_LOGIN_FAILED instead of RESPONSE_LOGIN_EXCEPTION
* https://issues.jboss.org/browse/SEAMREMOTING-39 -- Add <distributable/> to web-fragment.xml
* https://issues.jboss.org/browse/SEAMPERSIST-69 -- Transacation is problematic when save data
* https://issues.jboss.org/browse/SEAMINTL-19 -- Develop i18n module example based on timeanddate.com
* https://issues.jboss.org/browse/SEAMFACES-182 -- BeanManager from ServletContext in RewriteConfiguration is NULL with OWB
* https://issues.jboss.org/browse/SEAMFACES-164 -- Unable to deploy short.ly example to glassfish 3.1 and JBossAS 6
* https://issues.jboss.org/browse/SEAM-91 -- API declares compile-time dependency on CDI API


--
Jason Porter
http://lightguard-jp.blogspot.com
http://twitter.com/lightguardjp

Software Engineer
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling

PGP key id: 926CCFF5
PGP key available at: keyserver.net, pgp.mit.edu
<div>
<p>I have below a list of 38 open issues in Seam (excluding most of the Wicket ones as the Wicket module, from my understanding, has been pulled into the wicket project itself. If that's not the case please let me know) which are Blockers, Critical or have a high vote count (when I say "high" I mean more than two as most issues don't have many votes). I'm going to be focusing as much as I can until Beta5 on bug fixing, however, any help I can get from you would be very greatly appreciated. In help it may not exactly be a bug fix, but could be as simple as verifying an issue is still a problem. Many of these issues extend back to early in the year or even last year. Thank you very much in advance for anyone who can spare some time to help out with this. If you are able to help, please globally respond to this list so others don't end up repeating the work.</p>
<div>

<br>
</div>
<div>I also think this is a good list for us to work from as they're problem our users have identified as impacting them from using Seam 3.<br><div><br></div>
<div>
<div>* <a href="https://issues.jboss.org/browse/SEAMFACES-79">https://issues.jboss.org/browse/SEAMFACES-79</a> -- Provide &lt;s:restrictView&gt; tag for securing pages</div>

<div>* <a href="https://issues.jboss.org/browse/SOLDER-99">https://issues.jboss.org/browse/SOLDER-99</a> -- javax.el.ExpressionFactory can not be injected because it has final methods</div>
<div>* <a href="https://issues.jboss.org/browse/SEAMSECURITY-83">https://issues.jboss.org/browse/SEAMSECURITY-83</a> -- IdentityImpl.logout not invalidating session</div>

<div>* <a href="https://issues.jboss.org/browse/SEAMSECURITY-71">https://issues.jboss.org/browse/SEAMSECURITY-71</a> -- Improve LDAP integration in general</div>
<div>* <a href="https://issues.jboss.org/browse/SEAMREMOTING-6">https://issues.jboss.org/browse/SEAMREMOTING-6</a> -- Comet requests for Seam Remoting</div>

<div>* <a href="https://issues.jboss.org/browse/SEAMPERSIST-18">https://issues.jboss.org/browse/SEAMPERSIST-18</a> --  <at> Transactional not inherited in larger hierarchies</div>
<div>* <a href="https://issues.jboss.org/browse/SEAMFACES-208">https://issues.jboss.org/browse/SEAMFACES-208</a> -- Support for resolving no argument methods in an EL value expression</div>

<div>* <a href="https://issues.jboss.org/browse/SEAMFACES-147">https://issues.jboss.org/browse/SEAMFACES-147</a> -- Add support for binding methods (view actions) to view enums</div>
<div>* <a href="https://issues.jboss.org/browse/SOLDER-268">https://issues.jboss.org/browse/SOLDER-268</a> -- Conversation are only for JSF: Please make then available for plain servlets and JSP</div>

<div>* <a href="https://issues.jboss.org/browse/SEAMSECURITY-57">https://issues.jboss.org/browse/SEAMSECURITY-57</a> -- EL based authorization</div>
<div>* <a href="https://issues.jboss.org/browse/SEAMSECURITY-22">https://issues.jboss.org/browse/SEAMSECURITY-22</a> -- Basic authentication with no security drools and no picketlink defined in seam-beans.xml throws exception</div>

<div>* <a href="https://issues.jboss.org/browse/SEAMSECURITY-17">https://issues.jboss.org/browse/SEAMSECURITY-17</a> -- Servlet Filter to pick up security information for Seam after Java EE web container security</div>
<div>

* <a href="https://issues.jboss.org/browse/SEAMREMOTING-16">https://issues.jboss.org/browse/SEAMREMOTING-16</a> -- constraint by inclusion on remote calls object fields</div>
<div>* <a href="https://issues.jboss.org/browse/SEAMREMOTING-14">https://issues.jboss.org/browse/SEAMREMOTING-14</a> -- use ExceptionFilter in Remoting</div>

<div>* <a href="https://issues.jboss.org/browse/SEAMREMOTING-12">https://issues.jboss.org/browse/SEAMREMOTING-12</a> -- Messages component gets wrong locale in when called with seam remoting ( <at> WebRemote)</div>
<div>* <a href="https://issues.jboss.org/browse/SEAMREMOTING-8">https://issues.jboss.org/browse/SEAMREMOTING-8</a> -- Support for transient remoting types</div>

<div>* <a href="https://issues.jboss.org/browse/SEAMPERSIST-59">https://issues.jboss.org/browse/SEAMPERSIST-59</a> -- Implement EntityHome from Seam 2</div>
<div>* <a href="https://issues.jboss.org/browse/SEAMFACES-193">https://issues.jboss.org/browse/SEAMFACES-193</a> -- PrettyFaces URL rewriting is not happening when intercepted via  <at> LoginView</div>

<div>* <a href="https://issues.jboss.org/browse/SEAMFACES-114">https://issues.jboss.org/browse/SEAMFACES-114</a> -- DeploymentException: WELD-001408</div>
<div>* <a href="https://issues.jboss.org/browse/SEAMFACES-76">https://issues.jboss.org/browse/SEAMFACES-76</a> -- Cannot deploy using Beta2 inside a WAR inside an EAR on Jboss6 Final</div>

<div>* <a href="https://issues.jboss.org/browse/SEAMFACES-6">https://issues.jboss.org/browse/SEAMFACES-6</a> -- s:debug</div>
<div>* <a href="https://issues.jboss.org/browse/SEAMPERSIST-72">https://issues.jboss.org/browse/SEAMPERSIST-72</a> -- Seam Persistence does not work in Tomcat</div>

<div>* <a href="https://issues.jboss.org/browse/SOLDER-220">https://issues.jboss.org/browse/SOLDER-220</a> -- Seam-config ignores WEB-INF/beans.xml (and WEB-INF/seam-beans.xml) in jboss 7 and tomcat 6 for seam-config configuration (but not weld configuration)</div>

<div>* <a href="https://issues.jboss.org/browse/SOLDER-51">https://issues.jboss.org/browse/SOLDER-51</a> -- Decouple service handler annotation from implementation class</div>
<div>* <a href="https://issues.jboss.org/browse/SEAMPERSIST-67">https://issues.jboss.org/browse/SEAMPERSIST-67</a> -- LazyInitializationException threw when persist a Many to Many collection of an entity.</div>

<div>* <a href="https://issues.jboss.org/browse/SEAM-99">https://issues.jboss.org/browse/SEAM-99</a> -- java.lang.IllegalStateException: BaseTransaction.checkTransactionState - thread is already associated with a transaction!</div>

<div>* <a href="https://issues.jboss.org/browse/SOLDER-284">https://issues.jboss.org/browse/SOLDER-284</a> -- It should be decided if seam-beans.xml should still be called seam-beans.xml in solder.</div>
<div>* <a href="https://issues.jboss.org/browse/SOLDER-277">https://issues.jboss.org/browse/SOLDER-277</a> -- Add &lt;distributable/&gt; to web-fragment.xml</div>

<div>* <a href="https://issues.jboss.org/browse/SOLDER-240">https://issues.jboss.org/browse/SOLDER-240</a> -- ServletContextAttributeProvider uses wrong servlet ctx. attribute name to lookup the bean manager</div>
<div>* <a href="https://issues.jboss.org/browse/SOLDER-116">https://issues.jboss.org/browse/SOLDER-116</a> -- BeanBuilder create beans that don't support InjectionPoint injection</div>

<div>* <a href="https://issues.jboss.org/browse/SEAMSECURITY-123">https://issues.jboss.org/browse/SEAMSECURITY-123</a> -- JpaIdentityStore findIdentityObject has hardcoded entity classes in the query</div>
<div>* <a href="https://issues.jboss.org/browse/SEAMSECURITY-121">https://issues.jboss.org/browse/SEAMSECURITY-121</a> -- [Regression] 3.1.0.Beta4 eats exceptions in IdentityImpl + returns RESPONSE_LOGIN_FAILED instead of RESPONSE_LOGIN_EXCEPTION</div>

<div>* <a href="https://issues.jboss.org/browse/SEAMREMOTING-39">https://issues.jboss.org/browse/SEAMREMOTING-39</a> -- Add &lt;distributable/&gt; to web-fragment.xml</div>
<div>* <a href="https://issues.jboss.org/browse/SEAMPERSIST-69">https://issues.jboss.org/browse/SEAMPERSIST-69</a> -- Transacation is problematic when save data</div>

<div>* <a href="https://issues.jboss.org/browse/SEAMINTL-19">https://issues.jboss.org/browse/SEAMINTL-19</a> -- Develop i18n module example based on <a href="http://timeanddate.com">timeanddate.com</a>
</div>
<div>* <a href="https://issues.jboss.org/browse/SEAMFACES-182">https://issues.jboss.org/browse/SEAMFACES-182</a> -- BeanManager from ServletContext in RewriteConfiguration is NULL with OWB</div>

<div>* <a href="https://issues.jboss.org/browse/SEAMFACES-164">https://issues.jboss.org/browse/SEAMFACES-164</a> -- Unable to deploy <a href="http://short.ly">short.ly</a> example to glassfish 3.1 and JBossAS 6</div>
<div>

* <a href="https://issues.jboss.org/browse/SEAM-91">https://issues.jboss.org/browse/SEAM-91</a> -- API declares compile-time dependency on CDI API</div>
</div>
<div><br></div>
<div>
<div><br></div>-- <br>Jason Porter<br><a href="http://lightguard-jp.blogspot.com" target="_blank">http://lightguard-jp.blogspot.com</a><br><a href="http://twitter.com/lightguardjp" target="_blank">http://twitter.com/lightguardjp</a><br><br>Software Engineer<br>Open Source Advocate<br>Author of Seam Catch - Next Generation Java Exception Handling<br><br>PGP key id: 926CCFF5<br>

PGP key available at: <a href="http://keyserver.net" target="_blank">keyserver.net</a>, <a href="http://pgp.mit.edu" target="_blank">pgp.mit.edu</a><br>
</div>
</div>
</div>
Permalink | Reply | 0 comments |
headers
Shane Bryzak | 1 Nov 2011 13:18
Picon
Favicon

Third party dependencies

Hi everyone,

Could I please get a list from all module leads of the third party 
dependencies that your module depends on, whether the dependency is 
optional or required, and if possible a brief description (just a few 
words will do) on what the dependency is used for.  Please exclude other 
Seam modules from this list. ;)  If you also know which license the 
dependency is available under, that would be much appreciated too 
however if you're not sure, then no problem.

Thanks!

Shane
Permalink | Reply | 9 comments |
headers
Jozef Hartinger | 1 Nov 2011 15:50
Picon
Favicon

Re: Third party dependencies

For Seam REST the dependencies are listed at 
http://docs.jboss.org/seam/3/rest/snapshot/reference/en-US/html/rest.dependencies.html. 
All of them are optional. Test dependencies include: arquillian, 
shrinkwrap, jboss-osgi and apache httpclient.

On 11/01/2011 01:18 PM, Shane Bryzak wrote:
> Hi everyone,
>
> Could I please get a list from all module leads of the third party
> dependencies that your module depends on, whether the dependency is
> optional or required, and if possible a brief description (just a few
> words will do) on what the dependency is used for.  Please exclude other
> Seam modules from this list. ;)  If you also know which license the
> dependency is available under, that would be much appreciated too
> however if you're not sure, then no problem.
>
> Thanks!
>
> Shane
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev
Permalink | Reply | 0 comments |
headers
Jason Porter | 1 Nov 2011 21:37
Picon
Gravatar

Re: Third party dependencies

You also need EE API don't you? Like Solder needs Servlet and the CDI deps, Persistence needs JPA, etc.

On Tue, Nov 1, 2011 at 06:18, Shane Bryzak <sbryzak-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
Hi everyone,

Could I please get a list from all module leads of the third party
dependencies that your module depends on, whether the dependency is
optional or required, and if possible a brief description (just a few
words will do) on what the dependency is used for.  Please exclude other
Seam modules from this list. ;)  If you also know which license the
dependency is available under, that would be much appreciated too
however if you're not sure, then no problem.

Thanks!

Shane
_______________________________________________
seam-dev mailing list
seam-dev-yyZXR9kdEHCUeimprIcsAw@public.gmane.org
https://lists.jboss.org/mailman/listinfo/seam-dev



--
Jason Porter
http://lightguard-jp.blogspot.com
http://twitter.com/lightguardjp

Software Engineer
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling

PGP key id: 926CCFF5
PGP key available at: keyserver.net, pgp.mit.edu
<div>
<p>You also need EE API don't you? Like Solder needs Servlet and the CDI deps, Persistence needs JPA, etc.<br><br></p>
<div class="gmail_quote">On Tue, Nov 1, 2011 at 06:18, Shane Bryzak <span dir="ltr">&lt;<a href="mailto:sbryzak@...">sbryzak@...</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">Hi everyone,<br><br>
Could I please get a list from all module leads of the third party<br>
dependencies that your module depends on, whether the dependency is<br>
optional or required, and if possible a brief description (just a few<br>
words will do) on what the dependency is used for. &nbsp;Please exclude other<br>
Seam modules from this list. ;) &nbsp;If you also know which license the<br>
dependency is available under, that would be much appreciated too<br>
however if you're not sure, then no problem.<br><br>
Thanks!<br><br>
Shane<br>
_______________________________________________<br>
seam-dev mailing list<br><a href="mailto:seam-dev@...">seam-dev@...</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>
</div>
<br><br clear="all"><div><br></div>-- <br>Jason Porter<br><a href="http://lightguard-jp.blogspot.com" target="_blank">http://lightguard-jp.blogspot.com</a><br><a href="http://twitter.com/lightguardjp" target="_blank">http://twitter.com/lightguardjp</a><br><br>Software Engineer<br>Open Source Advocate<br>Author of Seam Catch - Next Generation Java Exception Handling<br><br>PGP key id: 926CCFF5<br>PGP key available at: <a href="http://keyserver.net" target="_blank">keyserver.net</a>, <a href="http://pgp.mit.edu" target="_blank">pgp.mit.edu</a><br>
</div>
Permalink | Reply | 4 comments |
headers
Gunnar Morling | 1 Nov 2011 21:44
Gravatar

Re: Third party dependencies

Hi,

for Seam Validation that is

* Hibernate Validator (required, used for method validation. Apache
Software License 2.0)

Required for tests/example:
* Jetty 6.x (Apache Software License 2.0, see
http://www.eclipse.org/jetty/licenses.php)
* Arquillian
* slf4j
* ShrinkWrap
* JUnit
* Weld
* Several API Jars (CDI, Servlet/JSP, EL)

--Gunnar

2011/11/1 Shane Bryzak <sbryzak@...>:
> Hi everyone,
>
> Could I please get a list from all module leads of the third party
> dependencies that your module depends on, whether the dependency is
> optional or required, and if possible a brief description (just a few
> words will do) on what the dependency is used for.  Please exclude other
> Seam modules from this list. ;)  If you also know which license the
> dependency is available under, that would be much appreciated too
> however if you're not sure, then no problem.
>
> Thanks!
>
> Shane
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev
>
Permalink | Reply | 0 comments |
headers
Jason Porter | 1 Nov 2011 22:53
Picon
Gravatar

This week's meeting

Unless people have something they feel needs to be discussed as a group, I'm going to cancel the meeting for this week and instead focus on bug fixes for 3.1.0 Beta5. I would appreciate any help on the list of issues I mailed out earlier in lieu of the meeting :)


--
Jason Porter
http://lightguard-jp.blogspot.com
http://twitter.com/lightguardjp

Software Engineer
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling

PGP key id: 926CCFF5
PGP key available at: keyserver.net, pgp.mit.edu
<div>
<p>Unless people have something they feel needs to be discussed as a group, I'm going to cancel the meeting for this week and instead focus on bug fixes for 3.1.0 Beta5. I would appreciate any help on the list of issues I mailed out earlier in lieu of the meeting :)<br clear="all"></p>
<div><br></div>-- <br>Jason Porter<br><a href="http://lightguard-jp.blogspot.com" target="_blank">http://lightguard-jp.blogspot.com</a><br><a href="http://twitter.com/lightguardjp" target="_blank">http://twitter.com/lightguardjp</a><br><br>Software Engineer<br>Open Source Advocate<br>Author of Seam Catch - Next Generation Java Exception Handling<br><br>PGP key id: 926CCFF5<br>PGP key available at: <a href="http://keyserver.net" target="_blank">keyserver.net</a>, <a href="http://pgp.mit.edu" target="_blank">pgp.mit.edu</a><br>
</div>
Permalink | Reply | 0 comments |
headers
Shane Bryzak | 1 Nov 2011 23:29
Picon
Favicon

Re: Third party dependencies

Yes, but I should have mentioned that we take these for granted.

On 02/11/11 06:37, Jason Porter wrote:
You also need EE API don't you? Like Solder needs Servlet and the CDI deps, Persistence needs JPA, etc.

On Tue, Nov 1, 2011 at 06:18, Shane Bryzak <sbryzak-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
Hi everyone,

Could I please get a list from all module leads of the third party
dependencies that your module depends on, whether the dependency is
optional or required, and if possible a brief description (just a few
words will do) on what the dependency is used for.  Please exclude other
Seam modules from this list. ;)  If you also know which license the
dependency is available under, that would be much appreciated too
however if you're not sure, then no problem.

Thanks!

Shane
_______________________________________________
seam-dev mailing list
seam-dev-yyZXR9kdEHBP7FacOaXjNw@public.gmane.org.org
https://lists.jboss.org/mailman/listinfo/seam-dev



--
Jason Porter
http://lightguard-jp.blogspot.com
http://twitter.com/lightguardjp

Software Engineer
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling

PGP key id: 926CCFF5
PGP key available at: keyserver.net, pgp.mit.edu

<div>
    Yes, but I should have mentioned that we take these for granted.<br><br>
    On 02/11/11 06:37, Jason Porter wrote:
    <blockquote cite="mid:CAF9TksOLN3Sca8u_M1kHD-gFJUYyYc-hWFSF+L7FDCdw5adrZw@...l.com" type="cite">You also need EE API don't you? Like Solder needs
      Servlet and the CDI deps, Persistence needs JPA, etc.<br><br><div class="gmail_quote">On Tue, Nov 1, 2011 at 06:18, Shane
        Bryzak <span dir="ltr">&lt;<a moz-do-not-send="true" href="mailto:sbryzak@...">sbryzak@...</a>&gt;</span>
        wrote:<br><blockquote class="gmail_quote">Hi
          everyone,<br><br>
          Could I please get a list from all module leads of the third
          party<br>
          dependencies that your module depends on, whether the
          dependency is<br>
          optional or required, and if possible a brief description
          (just a few<br>
          words will do) on what the dependency is used for. &nbsp;Please
          exclude other<br>
          Seam modules from this list. ;) &nbsp;If you also know which
          license the<br>
          dependency is available under, that would be much appreciated
          too<br>
          however if you're not sure, then no problem.<br><br>
          Thanks!<br><br>
          Shane<br>
          _______________________________________________<br>
          seam-dev mailing list<br><a moz-do-not-send="true" href="mailto:seam-dev@...">seam-dev@....org</a><br><a moz-do-not-send="true" href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
</blockquote>
      </div>
      <br><br clear="all"><div><br></div>
      -- <br>
      Jason Porter<br><a moz-do-not-send="true" href="http://lightguard-jp.blogspot.com" target="_blank">http://lightguard-jp.blogspot.com</a><br><a moz-do-not-send="true" href="http://twitter.com/lightguardjp" target="_blank">http://twitter.com/lightguardjp</a><br><br>
      Software Engineer<br>
      Open Source Advocate<br>
      Author of Seam Catch - Next Generation Java Exception Handling<br><br>
      PGP key id: 926CCFF5<br>
      PGP key available at: <a moz-do-not-send="true" href="http://keyserver.net" target="_blank">keyserver.net</a>, <a moz-do-not-send="true" href="http://pgp.mit.edu" target="_blank">pgp.mit.edu</a><br>
</blockquote>
    <br>
</div>
Permalink | Reply | 0 comments |
headers
Adrian Gonzalez | 2 Nov 2011 20:59
Picon
Favicon

Re : Re : Re : Re : SEAMFACES-147 viewActions

Hello,

First preview is available here : https://github.com/gonzalad/faces/tree/SEAMFACES-147
The 3 approaches  <at> ViewActionBindingType,  <at> ViewController and  <at> ViewAction are implemented.
I've included a basic sample in viewconfig webapp.
Java source : https://github.com/gonzalad/faces/tree/SEAMFACES-147/examples/viewconfig/src/main/java/org/jboss/seam/faces/examples/viewconfig
JSF pages : https://github.com/gonzalad/faces/tree/SEAMFACES-147/examples/viewconfig/src/main/webapp

What's remaining :

1. order between restrict actions and view pages actions.
   I'm quite stuck here : CDI events aren't ordered, and both kind of action use the JSF/CDI bridge based on
CDI events.
   2 options come to my mind :
   * go back to basic JSF phase listeners.
   * Modify SecurityPhaseListener to propagate the original event with one qualifier more on success
( <at> AfterRestriction for instance) - don't like this, because SecurityPhaseListener is optionnal
(depends on presence of seam-security).

2. [optional] introduce a  <at> BeforeAction annotation
  This annotation would be called before a JSF action (whether immediate or not).
  WDYT ? Is it necessary ? If not, I don't introduce it (the less, the better).

3. create some unit test.
  Don't know where to start, there's no unit test for restrictions (for my inspiration).

4. Refactor
  a. Don't like dependency from *Store to *Extension (should be the other way around).
  b. ViewConfigStoreImpl could perhaps use Qualifier / Annotation algorithm from
ViewConfigDescriptor (my fault : I've duplicated them).

----- Mail original -----
De : Adrian Gonzalez <adr_gonzalez@...>
À : "seam-dev@..." <seam-dev@...>
Cc : 
Envoyé le : Lundi 31 Octobre 2011 19h59
Objet : [seam-dev] Re :  Re :  Re : SEAMFACES-147 viewActions

Hello,

An update on this one and 2 more questions (oups....;) ) 

I've a really first draft for View Controllers (similar to CODI).

I can now do this ( <at> ViewController annotation) :
 <at> ViewConfig
public interface MyAppViewConfig {
   <at> UrlMapping(pattern = "/item/#{id}/")
   <at> ViewPattern("/item.xhtml")
   <at> ViewController(PageController.class)
   <at> Owner
  ITEM
}

With PageController :
 <at> ViewScoped
 <at> Named
public class PageController implements Serializable {
     <at> BeforeRenderView
    public void loadEntry( <at> Current Item item) {
      System.out.println("loadEntry called "+item);
    }
}
WDYT ?

So here are my questions : 
1. I would like to use  <at> RenderResponseand  <at> Before annotations here, but I cannot for the moment since they
don't target METHOD type.

  Could we add METHOD target for those annotations ?
2. I've needed to convert a java.lang.reflect.Method to AnnotatedMethod.
  Could you confirm that it's possible by doing this :

AnnotatedType annotatedType = beanManager.createAnnotatedType(method.getDeclaringClass());
Set<AnnotatedMethod> annotatedMethods = annotatedType.getMethods();
AnnotatedMethod annotatedMethod = null;
for (AnnotatedMethod current : annotatedMethods) {
  if (current.getJavaMember().equals(method)) {
      annotatedMethod = current;
  }
}

Thanks !

________________________________
De : Adrian Gonzalez <adr_gonzalez@...>
À : Jason Porter <lightguard.jp@...>
Cc : "seam-dev@..." <seam-dev@...>
Envoyé le : Samedi 29 Octobre 2011 17h31
Objet : [seam-dev] Re :  Re : SEAMFACES-147 viewActions

Thanks for the update

I'm enjoying my weekend - no developement - so no need to hurry ;)

Also, I was wondering if it wouldn't be nice to add some Page  or Controller notion to viewActions (similar
to CODI PageBean notion : https://cwiki.apache.org/EXTCDI/jsf-usage.html#JSFUsage-PageBeans).

The end used would be able to choose between 3 possible use case :

1. Untyped approach (not so CDI like - but dead simple)
 <at> ViewConfig
public interface ApplicationViewConfig {
    static enum View1 {
         <at> ViewPattern("/item.xhtml")
         <at> ViewAction("#{bean.doSomething()}")
        VIEW_ITEM;
    }
}

2. Typed
 <at> ViewConfig
public interface ApplicationViewConfig {
    static enum View1 {
         <at> ViewPattern("/item.xhtml")
        VIEW_ITEM;
    }
}
public class ItemAction {
 <at> ViewAction(VIEW_ITEM)
public void loadItem() {
   ...
}
}

3. Page Controller
 <at> ViewConfig
public interface ApplicationViewConfig {
    static enum View1 {
         <at> ViewPattern("/item.xhtml")
         <at> Controller(ItemController.class)
        VIEW_ITEM;
    }
}
public class ItemController {
 <at> BeforePhase(RENDER_RESPONSE)
public void loadItem() {
   ...
}
}

________________________________
De : Jason Porter <lightguard.jp@...>
À : Adrian Gonzalez <adr_gonzalez@...>
Cc : "seam-dev@..." <seam-dev@...>
Envoyé le : Samedi 29 Octobre 2011 4h02
Objet : Re: [seam-dev] Re : SEAMFACES-147 viewActions

I think Brian is planning on issuing an in depth response in a day or two. Thanks for your help!

On Thu, Oct 27, 2011 at 10:00, Adrian Gonzalez <adr_gonzalez@...> wrote:

Additionnal thoughts :
>
>As I understand ViewConfigStore for now, any extension can use ViewConfigStore to store about any
metadata (event if it's limited to Annotation for the moment).
>So this is great for additionnal features.
>
>If we go for solution 4, Page/View will be typed and future extensions will be limited.
>We can however add a metadatas field in Page/View for extensions to store about anything in a view.
>
>IMO, solution 4 would make the code easier to understand (more typed) - but breaks a lot of code, and since
I'm a newbie here...
>
>
>
>________________________________
>De : Adrian Gonzalez <adr_gonzalez@...>
>À : "seam-dev@..." <seam-dev@...>
>Envoyé le : Jeudi 27 Octobre 2011 17h44
>Objet : [seam-dev] SEAMFACES-147 viewActions
>
>
>Hello,
>
>I'm working a bit on this issue.
>
>But I'm stuck now and would like to know the better way to continue (sorry to bother once more ;( ).
>
>For the moment I've :
>1. registered all viewActionBindings into the viewConfigStore.
>2. more or less replicated SecurityPhaseListener functionnality into a ViewActionPhaseListener.
>
>But... viewConfigStore can only store Annotations. I need to store AnnotatedMethod (have a link back to
the Method I'll need to call).
>
>I see 4 possible solutions :
>
> 1 - Duplicate ViewConfigStoreImpl to store AnnotatedMethod elements.
> Ugly, no ?
> 2 - Make ViewConfigStore manage all kind of AnnotatedElements with a wrapper interface like
>interface AnnotatedElement<T> {
>Annotation<T> annotation;
>Object value;
>}
>ViewConfigStore :
>public interface ViewConfigStore {
>public abstract void addAnnotationData(String viewId, AnnotatedElement annotation);
>public abstract AnnotatedElement<T> T getAnnotationData(String viewId, Class<T> type);
>public abstract List<AnnotatedElement<T>> getAllAnnotationData(String viewId, Class<T> type);
>public abstract List<AnnotatedElement> getAllQualifierData(String viewId, Class<? extends
Annotation> qualifier);
>public <T extends Annotation> Map<String, Annotation> getAllAnnotationViewMap(Class<T> type);
>}
>3 - ViewConfigStore could store Annotated elements instead of Annotations
> This would make ViewConfigStore usage a little more complicated though.
>4 - Have somes typed Page or View objects.
> This need really more reflection since we need to know what is a View (security, view actions, ...).
>And it's a big impact on current code.
>The ViewConfigStore would be sthing like (really incomplete) :
>ViewConfigStore :
>public Map<String,ViewInfo> getView(String viewId);
>public List<View> getViews();
>}
>with for instance :
>class/interface View {
>List<Restriction> getRestrictions();
>List<ViewAction> getViewActions(); //or event List<Action> getAction(PhaseId)
>}
>
>WDYT ?
>
>P.S. Sorry for the rather long mail........
>
>
>More details on what I have done for now :
>
>As noted in the ticket, I can now create a viewAction annotation like this one :
>
>
> <at> ViewActionBindingType
> <at> Retention(RetentionPolicy.RUNTIME)
> <at> Target({ElementType.FIELD, ElementType.METHOD, ElementType.TYPE})
>public  <at> interface MyViewAction {
>MyAppViewConfig.Pages value();
>}
>
>MyAppViewConfig being the sample  <at> ViewConfig annotated class in viewconfig sample.
>
>I can then use MyViewAction like this :
>
>
> <at> ViewScoped
> <at> Named
>public class PageController implements Serializable {
>     <at> MyViewAction(Pages.ITEM)
>    public void loadEntry() {
>    System.out.println("loadEntry called");
>    }
>}
>
>For the moment, my code doesn't call this method (I'll just need to copy Seam Security code for it ;) ).
>
>
>I've also created the following annotation that you can use to annotate your own viewAction annotation :
> -  <at> Condition(condition=String) -> not really type safe.....
> -  <at> Immediate(immediate=Boolean)
> -  <at> OnPostback(onPostback=boolean)
> -  <at> Phase(value=PhaseIdType)
>
>Also, if you need to customise those behaviour per-usage, you can add attributes into your viewAction
annotation :
> <at> MyViewAction(Pages.ITEM, immediate=true, condition="#{myBean.eager}")
>public void loadEntry()
>
>_______________________________________________
>seam-dev mailing list
>seam-dev@...
>https://lists.jboss.org/mailman/listinfo/seam-dev
>
>_______________________________________________
>seam-dev mailing list
>seam-dev@...
>https://lists.jboss.org/mailman/listinfo/seam-dev
>

-- 
Jason Porter
http://lightguard-jp.blogspot.com
http://twitter.com/lightguardjp

Software Engineer
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling

PGP key id: 926CCFF5
PGP key available at: keyserver.net, pgp.mit.edu

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev  

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev
Permalink | Reply | 1 comment |
headers
Adrian Gonzalez | 2 Nov 2011 21:06
Picon
Favicon

Re : Re : Re : Re : Re : SEAMFACES-147 viewActions

Sorry, forgot in what's remaining :

5. Modify  <at> ViewAction
  Per default,  <at> ViewAction("#{myController.handle()}") is called before RENDER_RESPONSE.
  You can change this by using  <at> Before/After with another jsf phase (i.e.  <at> ApplyRequestValues).
  You get sthing like :
         <at> UrlMapping(pattern = "/item/#{id}/")
         <at> ViewPattern("/item.xhtml")
         <at> ViewController(PageController.class)
         <at> Owner
         <at> ViewAction("#{pageController.viewAction(pageController.item)}")
         <at> Before  <at> ApplyRequestValues
        ITEM

  Not really happy here, because :
  a. link between ViewAction annotation and Before / ApplyRequestValues is not straighforward.
  b. if someone develops another extension relying on the same annotations (Before, etc...) we can have a conflict.

  Wouldn't it be better if we introduced before and phase attributes into  <at> ViewAction ?
  The cons of it is that it won't be symetric with  <at> ViewActionBindingType and  <at> ViewController which rely
on Before / ApplyRequestValues annotations.

Sorry for the rather long topic..

----- Mail original -----
De : Adrian Gonzalez <adr_gonzalez@...>
À : "seam-dev@..." <seam-dev@...>
Cc : 
Envoyé le : Mercredi 2 Novembre 2011 20h59
Objet : [seam-dev] Re :  Re :  Re :  Re : SEAMFACES-147 viewActions

Hello,

First preview is available here : https://github.com/gonzalad/faces/tree/SEAMFACES-147
The 3 approaches  <at> ViewActionBindingType,  <at> ViewController and  <at> ViewAction are implemented.
I've included a basic sample in viewconfig webapp.
Java source : https://github.com/gonzalad/faces/tree/SEAMFACES-147/examples/viewconfig/src/main/java/org/jboss/seam/faces/examples/viewconfig
JSF pages : https://github.com/gonzalad/faces/tree/SEAMFACES-147/examples/viewconfig/src/main/webapp

What's remaining :

1. order between restrict actions and view pages actions.
   I'm quite stuck here : CDI events aren't ordered, and both kind of action use the JSF/CDI bridge based on
CDI events.
   2 options come to my mind :
   * go back to basic JSF phase listeners.
   * Modify SecurityPhaseListener to propagate the original event with one qualifier more on success
( <at> AfterRestriction for instance) - don't like this, because SecurityPhaseListener is optionnal
(depends on presence of seam-security).

2. [optional] introduce a  <at> BeforeAction annotation
  This annotation would be called before a JSF action (whether immediate or not).
  WDYT ? Is it necessary ? If not, I don't introduce it (the less, the better).

3. create some unit test.
  Don't know where to start, there's no unit test for restrictions (for my inspiration).

4. Refactor
  a. Don't like dependency from *Store to *Extension (should be the other way around).
  b. ViewConfigStoreImpl could perhaps use Qualifier / Annotation algorithm from
ViewConfigDescriptor (my fault : I've duplicated them).

----- Mail original -----
De : Adrian Gonzalez <adr_gonzalez@...>
À : "seam-dev@..." <seam-dev@...>
Cc : 
Envoyé le : Lundi 31 Octobre 2011 19h59
Objet : [seam-dev] Re :  Re :  Re : SEAMFACES-147 viewActions

Hello,

An update on this one and 2 more questions (oups....;) ) 

I've a really first draft for View Controllers (similar to CODI).

I can now do this ( <at> ViewController annotation) :
 <at> ViewConfig
public interface MyAppViewConfig {
   <at> UrlMapping(pattern = "/item/#{id}/")
   <at> ViewPattern("/item.xhtml")
   <at> ViewController(PageController.class)
   <at> Owner
  ITEM
}

With PageController :
 <at> ViewScoped
 <at> Named
public class PageController implements Serializable {
     <at> BeforeRenderView
    public void loadEntry( <at> Current Item item) {
      System.out.println("loadEntry called "+item);
    }
}
WDYT ?

So here are my questions : 
1. I would like to use  <at> RenderResponseand  <at> Before annotations here, but I cannot for the moment since they
don't target METHOD type.

  Could we add METHOD target for those annotations ?
2. I've needed to convert a java.lang.reflect.Method to AnnotatedMethod.
  Could you confirm that it's possible by doing this :

AnnotatedType annotatedType = beanManager.createAnnotatedType(method.getDeclaringClass());
Set<AnnotatedMethod> annotatedMethods = annotatedType.getMethods();
AnnotatedMethod annotatedMethod = null;
for (AnnotatedMethod current : annotatedMethods) {
  if (current.getJavaMember().equals(method)) {
      annotatedMethod = current;
  }
}

Thanks !

________________________________
De : Adrian Gonzalez <adr_gonzalez@...>
À : Jason Porter <lightguard.jp@...>
Cc : "seam-dev@..." <seam-dev@...>
Envoyé le : Samedi 29 Octobre 2011 17h31
Objet : [seam-dev] Re :  Re : SEAMFACES-147 viewActions

Thanks for the update

I'm enjoying my weekend - no developement - so no need to hurry ;)

Also, I was wondering if it wouldn't be nice to add some Page  or Controller notion to viewActions (similar
to CODI PageBean notion : https://cwiki.apache.org/EXTCDI/jsf-usage.html#JSFUsage-PageBeans).

The end used would be able to choose between 3 possible use case :

1. Untyped approach (not so CDI like - but dead simple)
 <at> ViewConfig
public interface ApplicationViewConfig {
    static enum View1 {
         <at> ViewPattern("/item.xhtml")
         <at> ViewAction("#{bean.doSomething()}")
        VIEW_ITEM;
    }
}

2. Typed
 <at> ViewConfig
public interface ApplicationViewConfig {
    static enum View1 {
         <at> ViewPattern("/item.xhtml")
        VIEW_ITEM;
    }
}
public class ItemAction {
 <at> ViewAction(VIEW_ITEM)
public void loadItem() {
   ...
}
}

3. Page Controller
 <at> ViewConfig
public interface ApplicationViewConfig {
    static enum View1 {
         <at> ViewPattern("/item.xhtml")
         <at> Controller(ItemController.class)
        VIEW_ITEM;
    }
}
public class ItemController {
 <at> BeforePhase(RENDER_RESPONSE)
public void loadItem() {
   ...
}
}

________________________________
De : Jason Porter <lightguard.jp@...>
À : Adrian Gonzalez <adr_gonzalez@...>
Cc : "seam-dev@..." <seam-dev@...>
Envoyé le : Samedi 29 Octobre 2011 4h02
Objet : Re: [seam-dev] Re : SEAMFACES-147 viewActions

I think Brian is planning on issuing an in depth response in a day or two. Thanks for your help!

On Thu, Oct 27, 2011 at 10:00, Adrian Gonzalez <adr_gonzalez@...> wrote:

Additionnal thoughts :
>
>As I understand ViewConfigStore for now, any extension can use ViewConfigStore to store about any
metadata (event if it's limited to Annotation for the moment).
>So this is great for additionnal features.
>
>If we go for solution 4, Page/View will be typed and future extensions will be limited.
>We can however add a metadatas field in Page/View for extensions to store about anything in a view.
>
>IMO, solution 4 would make the code easier to understand (more typed) - but breaks a lot of code, and since
I'm a newbie here...
>
>
>
>________________________________
>De : Adrian Gonzalez <adr_gonzalez@...>
>À : "seam-dev@..." <seam-dev@...>
>Envoyé le : Jeudi 27 Octobre 2011 17h44
>Objet : [seam-dev] SEAMFACES-147 viewActions
>
>
>Hello,
>
>I'm working a bit on this issue.
>
>But I'm stuck now and would like to know the better way to continue (sorry to bother once more ;( ).
>
>For the moment I've :
>1. registered all viewActionBindings into the viewConfigStore.
>2. more or less replicated SecurityPhaseListener functionnality into a ViewActionPhaseListener.
>
>But... viewConfigStore can only store Annotations. I need to store AnnotatedMethod (have a link back to
the Method I'll need to call).
>
>I see 4 possible solutions :
>
> 1 - Duplicate ViewConfigStoreImpl to store AnnotatedMethod elements.
> Ugly, no ?
> 2 - Make ViewConfigStore manage all kind of AnnotatedElements with a wrapper interface like
>interface AnnotatedElement<T> {
>Annotation<T> annotation;
>Object value;
>}
>ViewConfigStore :
>public interface ViewConfigStore {
>public abstract void addAnnotationData(String viewId, AnnotatedElement annotation);
>public abstract AnnotatedElement<T> T getAnnotationData(String viewId, Class<T> type);
>public abstract List<AnnotatedElement<T>> getAllAnnotationData(String viewId, Class<T> type);
>public abstract List<AnnotatedElement> getAllQualifierData(String viewId, Class<? extends
Annotation> qualifier);
>public <T extends Annotation> Map<String, Annotation> getAllAnnotationViewMap(Class<T> type);
>}
>3 - ViewConfigStore could store Annotated elements instead of Annotations
> This would make ViewConfigStore usage a little more complicated though.
>4 - Have somes typed Page or View objects.
> This need really more reflection since we need to know what is a View (security, view actions, ...).
>And it's a big impact on current code.
>The ViewConfigStore would be sthing like (really incomplete) :
>ViewConfigStore :
>public Map<String,ViewInfo> getView(String viewId);
>public List<View> getViews();
>}
>with for instance :
>class/interface View {
>List<Restriction> getRestrictions();
>List<ViewAction> getViewActions(); //or event List<Action> getAction(PhaseId)
>}
>
>WDYT ?
>
>P.S. Sorry for the rather long mail........
>
>
>More details on what I have done for now :
>
>As noted in the ticket, I can now create a viewAction annotation like this one :
>
>
> <at> ViewActionBindingType
> <at> Retention(RetentionPolicy.RUNTIME)
> <at> Target({ElementType.FIELD, ElementType.METHOD, ElementType.TYPE})
>public  <at> interface MyViewAction {
>MyAppViewConfig.Pages value();
>}
>
>MyAppViewConfig being the sample  <at> ViewConfig annotated class in viewconfig sample.
>
>I can then use MyViewAction like this :
>
>
> <at> ViewScoped
> <at> Named
>public class PageController implements Serializable {
>     <at> MyViewAction(Pages.ITEM)
>    public void loadEntry() {
>    System.out.println("loadEntry called");
>    }
>}
>
>For the moment, my code doesn't call this method (I'll just need to copy Seam Security code for it ;) ).
>
>
>I've also created the following annotation that you can use to annotate your own viewAction annotation :
> -  <at> Condition(condition=String) -> not really type safe.....
> -  <at> Immediate(immediate=Boolean)
> -  <at> OnPostback(onPostback=boolean)
> -  <at> Phase(value=PhaseIdType)
>
>Also, if you need to customise those behaviour per-usage, you can add attributes into your viewAction
annotation :
> <at> MyViewAction(Pages.ITEM, immediate=true, condition="#{myBean.eager}")
>public void loadEntry()
>
>_______________________________________________
>seam-dev mailing list
>seam-dev@...
>https://lists.jboss.org/mailman/listinfo/seam-dev
>
>_______________________________________________
>seam-dev mailing list
>seam-dev@...
>https://lists.jboss.org/mailman/listinfo/seam-dev
>

-- 
Jason Porter
http://lightguard-jp.blogspot.com
http://twitter.com/lightguardjp

Software Engineer
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling

PGP key id: 926CCFF5
PGP key available at: keyserver.net, pgp.mit.edu

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev
Permalink | Reply | 0 comments |
headers
Antoine Sabot-Durand | 4 Nov 2011 22:18
Gravatar

Re: Third party dependencies

Regarding Seam Social, dependencies are:

Jackson framework for JSON mapping (ASL2)
Java Scribe to deal with OAuth lifecycle (MIT license)
Apache commons Lang3 for Strings helper (ASL2)
Google Guava for special collection and functional (ASL2)


Antoine


Le 1 nov. 2011 à 13:18, Shane Bryzak a écrit :

Hi everyone,

Could I please get a list from all module leads of the third party
dependencies that your module depends on, whether the dependency is
optional or required, and if possible a brief description (just a few
words will do) on what the dependency is used for.  Please exclude other
Seam modules from this list. ;)  If you also know which license the
dependency is available under, that would be much appreciated too
however if you're not sure, then no problem.

Thanks!

Shane
_______________________________________________
seam-dev mailing list
seam-dev-yyZXR9kdEHCUeimprIcsAw@public.gmane.org
https://lists.jboss.org/mailman/listinfo/seam-dev

<div>Regarding Seam Social, dependencies are:<div><br></div>
<div>Jackson framework for JSON mapping (ASL2)</div>
<div>Java Scribe to deal with OAuth lifecycle (MIT license)</div>
<div>Apache commons Lang3 for Strings helper (ASL2)</div>
<div>Google Guava for special collection and functional (ASL2)</div>
<div>
<br><div>
<span class="Apple-style-span"><span class="Apple-style-span"><span class="Apple-style-span"><div><span class="Apple-style-span"><div><span class="Apple-style-span"><div><div><div><div><div>
<br class="Apple-interchange-newline">Antoine</div></div></div></div></div></span></div></span></div></span></span></span><br class="Apple-interchange-newline">
</div>
<br><div>
<div>Le 1 nov. 2011 &agrave; 13:18, Shane Bryzak a &eacute;crit :</div>
<br class="Apple-interchange-newline"><blockquote type="cite"><div>Hi everyone,<br><br>Could I please get a list from all module leads of the third party <br>dependencies that your module depends on, whether the dependency is <br>optional or required, and if possible a brief description (just a few <br>words will do) on what the dependency is used for. &nbsp;Please exclude other <br>Seam modules from this list. ;) &nbsp;If you also know which license the <br>dependency is available under, that would be much appreciated too <br>however if you're not sure, then no problem.<br><br>Thanks!<br><br>Shane<br>_______________________________________________<br>seam-dev mailing list<br><a href="mailto:seam-dev@...">seam-dev@...</a><br>https://lists.jboss.org/mailman/listinfo/seam-dev<br>
</div></blockquote>
</div>
<br>
</div>
</div>
Permalink | Reply | 1 comment |

Gmane