Seam Social module in (pre)-alpha
by Antoine Sabot-Durand
Hi,
For those who don't know me let me introduce myself. I'm a french senior consultant specialized in Java EE architecture (i don't work for Redhat but I manage a consultant team in a business unit of a small IT company in Paris)). I joined the Seam 3 project a few months ago after Devoxx and Lincoln invitation to work on Seam Social. The goal of this module is to provide CDI beans to manage communication with major Social Network (Twitter, Foursquare, LinkedIn, ...).
I lost a lot of time exploring the available technical options to implement this module. I also had to learn CDI which is very different than Seam 2.X ;-) and had to wait for stabilization of some of the core module, to be sure of my choices.
I've just pushed The Seam Social module on Github : https://github.com/antoinesd/seam-social
At the moment, it contains an web application that can manage an OAuth connexion to Twiiter and send an update status (I know it's not very spectacular, but there is more to come :-) ).
I'm not quite sure of the next step, but I'll probably need some help to make the best out of CDI to use extension or decorators for instance mapping JSON to pojo with Jackson. As i'm not an API designer guy your feedback and critics for improvement are off course more than welcomed.
Regards,
Antoine SABOT-DURAND
---------------------------------------
Twitter ; http://twitter.com/antoine_sd
LinkedIn : http://fr.linkedin.com/in/antoinesabotdurand
12 years, 9 months
OpenID-op example application
by Marek Smigielski
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
12 years, 9 months
Looking up beans for Producers in AfterBeanDiscovery
by Jordan Ganoff
All,
I've run into an issue that I haven't been able to resolve. I am collecting
producers during ProcessProducer and I'd like to be able to invoke them
during AfterBeanDiscovery to operate on the produces objects. When I run the
application with Arquillian the beans can be looked up successfully. When
the application runs as a web app they are not.
The sample app is producer-test on this branch of seam-jms:
https://github.com/jganoff/jms/tree/producer-test/producer-test
The relevant code is here:
https://github.com/jganoff/jms/blob/producer-test/producer-test/src/main/...
Anyone have any ideas?
Follow up question: Is this a decent way for users to configure JMS routing
information (send CDI event X to JMS destination Y, etc)? The original idea
was to allow users to annotate methods with @RoutingConfig and what they
returned would be registered as a route. The producer idea seemed like a
better fit though.
--
Jordan Ganoff
12 years, 9 months
Help with ERRAI-123 needed
by Martin Gencur
Hi all,
can anybody help out with this issue, please?
(https://issues.jboss.org/browse/ERRAI-123 - Errai-cdi throwing an
exception when used along with seam-solder)
The current status is that Seam3 doesn't work with ERRAI due to this
problem (at least all modules which use seam-solder as their
dependencies)
Feel free to re-assign it.
Thank you
--
Martin Gencur
Seam QA Associate
12 years, 9 months
SEAMFACES-82
by Brian Leathem
Hello All,
I'm a little stumped with SEAMFACES-82 [1] - "Injection of managed beans
in face converter fails"
I reproduced the error with a simple test case, and did some
tracing/debugging, where I concluded the root of the problem to be that
beanManager.getBeans(type) returns an empty set, when type is a Faces
Converter class. (See the issue for more details).
So why would this be the case? Could this be a Weld bug? Or is
something just missing? What do I have to do to enable the BeanManager
to provide instances of these Converters?
Thanks,
Brian Leathem
[1] https://issues.jboss.org/browse/SEAMFACES-82
12 years, 9 months
Seam JMS Alpha 2 Incoming...
by Jordan Ganoff
Shane, Dan, et al,
The list of issues slated for Seam JMS Alpha 2 [1] are nearly completion.
I'd like to be able to release Alpha 2 early next week and, provided the API
is complete at that point, release a beta shortly after. I'll need help
pushing out the release so I don't end up spending hours on it so here's
your fair warning! ;)
Again, anyone interested in helping out is more than welcome. We could use
some help in nearly all areas but specifically creating an example or two. I
plan on updating the doc before any release is made.
Best Regards,
Jordan
[1]: https://issues.jboss.org/browse/SEAMJMS/fixforversion/12315281
--
Jordan Ganoff
12 years, 9 months
Is this the mail API you always wanted?
by Dan Allen
Seam devs,
Cody is looking for some feedback on the mail module [1] before he drafts a
reference guide and puts the API on ice.
Seam mail is important because, let's face it, the Java Mail API needs a
makeover. Thankfully, the CDI programming model offers the necessary hooks
to create a modernized mail API capable of deep integration with the Java EE
platform (specifically the Java Mail API and container-managed sessions).
Seam Mail offers a fluent API that makes sending e-mail in Java a painless
experience. But an e-mail is nothing without the content. That's why Seam
Mail offers several templating options, such as Velocity, as well as an
extensible template SPI, to allow you to select your templating solution of
choice. With Seam Mail, you'll be sending e-mail from your application in no
time.
Is this how you imagined it would be?
Basic:
@Inject
private Instance<MailMessage> mailMessage;
@Inject
private Session session;
mailMessage.get()
.from("Seam Framework", "seam(a)jboss.org")
.to("John Smith", "john.smith(a)acme.com")
.subject("Text Message from Seam Mail - " +
java.util.UUID.randomUUID().toString())
.textBody(text)
.send(session);
Velocity:
@Inject
private Instance<VelocityMailMessage> velocityMailMessage;
@Inject
private Session session;
velocityMailMessage.get().from("Seam Framework", "seam(a)jboss.org")
.to(person.getName(), person.getEmail())
.subject("HTML Message from Seam Mail - " +
java.util.UUID.randomUUID().toString())
.templateHTMLFromClassPath("template.html.vm")
.put("version", "Seam 3")
.importance(MessagePriority.HIGH)
.addAttachment(new URL("
http://www.seamframework.org/themes/sfwkorg/img/seam_icon_large.png"),
"seamLogo.png", ContentDisposition.INLINE);
.send(session);
We look forward to your feedback.
-Dan
[1] http://github.com/seam/mail
http://seamframework.org/Seam3/Mail
--
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
12 years, 9 months
Re: [seam-dev] RES: Is this the mail API you always wanted?
by Dan Allen
On Mon, Feb 7, 2011 at 14:56, José Rodolfo Carrijo de Freitas <
jose.freitas(a)softplan.com.br> wrote:
> It Looks really nice!
>
>
>
> If I may suggest something, maybe we can add the possibility to use just *
> “.send()”* ( keeping the send(session) method ).
>
> If there’s no specific session argument, the module could handle the
> injection within itself.
>
Yep, Emmanuel mentioned that as well. And I'll second both of you :)
Even if you use send(), you would still have flexibility in how the mail
session is picked, because you could provide an alternative producer to
create your own custom session. All that matters is that Seam Mail
references a bean with type Session. So that version of send() will likely
be preferred.
-Dan
--
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
12 years, 9 months
