speak about your module at JUDCon!
by Dan Allen
Module leads and committers,
Part of being a key contributor to Seam is having the opportunity to
demonstrate your hard work. JUDCon [1] (and also local JBoss or Java user
groups) is an ideal venue for getting out there and building your resume as
a speaker (if it appeals to you). I'd rather you speak about your module
then for the Seam leads to speak on your behalf. Don't hesitate to submit an
abstract before the deadline this Friday (or anytime for user groups).
http://jboss.org/events/JUDCon
The conference is free. We can't promise to cover travel costs, but
SouthWest flights to Boston are quite cheap and we can find a local JBossian
to host you if you can't pay for a hotel room. I've got you covered for
drinks. Don't let excuses get in the way. Go for it!
-Dan
p.s. There is a JUDCon in both US and Europe. This one is in the US, after
which the European one will be likely announced. Another option is to speak
at a JBoss User Group or start your own: http://www.jboss.org/usergroups
[1] http://jboss.org/events/JUDCon
--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://www.google.com/profiles/dan.j.allen#about
http://mojavelinux.com
http://mojavelinux.com/seaminaction
13 years, 9 months
Re: [seam-dev] OpenID-op example application
by Marek Śmigielski
Hi,
I have just opened pull request for openid provider example. I've also
added simple test case for deployment process and login request.
I must say that Arquillian framework, deeply changed the way I develop
the code. I can't imagine how could I live without it. Thanks for this
great tool.
On Mon, Feb 28, 2011 at 5:14 PM, PicketBox JBoss <picketbox(a)gmail.com> wrote:
> Look at the Seam PicketLink integration that Marcel has produced. It would
> be beneficial to start there.
>
> On Mon, Feb 14, 2011 at 9:07 AM, Marek Smigielski
> <marek.smigielski(a)gmail.com> wrote:
>>
>> Hi,
>> Yesterday, when I try to deploy openid-op example on jboss 6.0, I have
>> found that it has some major problems and need refactoring in some places.
>> Basically it isn't integrated with PicketLink and has some minor dependency
>> injections problems.
>> I have some experience using seam and have some time , so it shouldn't be
>> too hard for me to fix that. Of course if you allow me to do so.
>> I think that to bring back this example it should be done:
>> 1. Makes OpenIdRpAuthenticationService ApplicationScobe component
>> (circular dependency problem).
>> 2. Add whole seam-security as a dependency (there was classNotFound
>> exception)
>> 3. Rename and re-factor Login class to Authenticator which will extend
>> BaseAuthenticator.
>> 4. Rename and re-factor Identity class to User which
>> implements org.picketlink.idm.api.User.
>> 5. Add arquillian test for this functionality.
>> regards,
>> Marek
>>
>>
>> _______________________________________________
>> seam-dev mailing list
>> seam-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>
>
>
13 years, 9 months
seam jcr
by George Gastaldi
I forked the repository. Please browse my initial code to see if it
matches your expectations.
Also, what do you think about creating two maven modules for testing
(jackrabbit and modeshape) ?
13 years, 9 months
Module documentation
by Shane Bryzak
To assist with the bundled documentation build, could everyone please
ensure that you prefix your docbook id tags with the name of your
module. This is unfortunately necessary as docbook requires unique ID
values and will fail otherwise. To illustrate what I mean, let's
pretend that two of our modules, faces and security both have
introduction chapters:
<chapter id="introduction">
<title>Seam Faces - Introduction</title>
...
<chapter id="introduction">
<title>Seam Security - Introduction</title>
...
Since both chapters have an id of "introduction", docbook fails when
attempting to build the bundled docs. To workaround this restriction,
we can simply add the module name:
<chapter id="faces-introduction">
<title>Seam Faces - Introduction</title>
...
<chapter id="security-introduction">
<title>Seam Security - Introduction</title>
...
Can you also please apply the same naming standard to the docbook source
files, and chapter titles (this will help to keep the bundled
documentation more consistent).
Lastly, if you need to add a new chapter to your module documentation
(or rename an existing one), can you please let one of the core team
devs know. Our bundled documentation build has its own master.xml file
containing all the individual chapters from each module, and new
chapters need to be manually added to this file [1]. Alternatively, you
can make the modification yourself and send a pull request.
Thanks,
Shane
[1]
https://github.com/seam/dist/blob/master/docs/src/main/docbook/en-US/mast...
13 years, 9 months
