DeltaSpike Logging
by Ken Finnigan
As per today's Seam meeting, below is a draft of an email I'll send to the
DeltaSpike mailing list to re ignite the logging discussion, as it is on
hold at present.
Please provide feedback on content and language used, as I want this to get
the discussion off on the right foot.
Ken
=============================
All,
As we approach a 0.1 release of DeltaSpike, congratulations to everyone on
the good work so far, I feel it's a good time to begin discussing how we
want to handle logging within DeltaSpike. I certainly don't expect this
discussion to result in code for 0.1, but the earlier we begin this
discussion, then it increases the likelihood of it being ready for 0.2
Having been heavily involved in the logging work for Solder, I know the
pain that can be experienced in not getting it right, and also how long it
can take to get right.
I see that there are several goals that we want for logging in DeltaSpike:
1. Make it simple for both extension writers and end users. If it's too
difficult to implement, use or even get right, then we'll frustrate and
alienate developers.
2. It must perform. We don't want to introduce large overhead to
logging.
3. There should be an option to allow/provide type safe logging.
4. An end user should be able to have DeltaSpike log against whichever
logging library they want to utilize in their application. We can
certainly support a specific framework as a default, but it's important to
allow a developer to have the same control over how DeltaSpike is logged as
their own application.
Thoughts?
Regards
Ken Finnigan
============================
13 years, 12 months
Outline - Seam 2 to JEE 6 migration - topics
by Hanneli Tavante
Hello everyone! While we don't create a repo at Github for this, I wrote
some topics that i think we should cover in a Seam 2 o JEE6 migration
tutorial. WDYT?
Seam 2 to JEE6 migration - Full tutorial
Chapter 1
Seam 2 app - describe the features (Like DI features, Conversation Scope,
enhanced EL, EJB integration...)
Chapter 2 - JEE 6 basics **
** Very important. Ppl dont google about it and they know too few to
understand the meaning of CDI by theirselves, so this tutorial must have
JEE basics
2.1 JEE 6 new specs
2.2 DI Spec
2.3 CDI - fix DI missing context points
Chapter 3 - Migrating to JSF 2
Assuming that your base project is made with JSF, lets migrate them to JSF
to. We solve here some EL problems and scope problems that we did not have
for JSF1. Also show that some seam 2 EL enhancements now are useless.
Chapter 4 - Applying CDI into your existing Seam 2 project
-> Show here how DI features from Seam 2 are now useless and meaningless
due CDI spec
Note that step by step we show that seam 2 lost their reason to exist
inside a JEE 6 environment
Chapter 5 - Point CDI problems (E.g no VieScoped, etc)
Chapter 6 - Show how we fix these CDI problems and missing points
--
Hanneli Carolina Andreazzi Tavante
@hannelita
Caelum - Ensino e Inovação
13 years, 12 months
2012-01-11 Meeting
by Jason Porter
Agenda
I only have one item I would like to discuss: What you the community would
like to see happen with Seam 3. In light of DeltaSpike gaining traction and
how things are going with it.
I have my ideas, which I have shared with you earlier. I'd like to hear
what you think or if you have any other ideas. Please, if you cannot make
it to the meeting please respond to this and we'll include it in the irc
discussion. Thank you all and I hope for an excellent 2012!
--
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
14 years
Seam JCR and multiple repos
by Ove Ranheim
Hi,
I'm trying to connect to two different JCR (ModeShape) repos in my app, but based on current documentation and some testing, I'm not able to figure it out.
Producer bean:
@Produces
@Named(ConfigParams.JCR_REPOSITORY_CONFIG_MAP)
@RepositorySessionQualifer
public Map<String, String> produceJcrConfig(@Resource("contentRepository.xml") URL url) {
String modeshapeUrl = url.toExternalForm() + "?repositoryName=ContentRepository";
return Collections.singletonMap(MODESHAPE_URL, modeshapeUrl);
}
@Produces
@Named(ConfigParams.JCR_REPOSITORY_CONFIG_MAP)
@RepositoryEmailSessionQualifer
public Map<String, String> produceJcrConfig2(@Resource("contentRepository.xml") URL url) {
String modeshapeUrl = url.toExternalForm() + "?repositoryName=EmailRepository";
return Collections.singletonMap(MODESHAPE_URL, modeshapeUrl);
}
Other bean:
@Inject
@RepositorySessionQualifer
private Instance<Session> sessionInstance;
Exception:
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001414 Bean name is ambiguous. Name jcrRepositoryConfigMap resolves to beans [Producer Method [Map<String, String>] with qualifiers [@Any @RepositorySessionQualifer @Named] declared as [[method] @Produces @Named @RepositorySessionQualifer public com.parts.content.faq.metadata.JcrConfigProducer.produceJcrConfig(URL)], Producer Method [Map<String, String>] with qualifiers [@Any @RepositoryEmailSessionQualifer @Named] declared as [[method] @Produces @Named @RepositoryEmailSessionQualifer public com.parts.content.faq.metadata.JcrConfigProducer.produceJcrConfig2(URL)]]
What would be the correct way to wire up correctly?
Ove
14 years
Welcome Ron Smeral
by Ondřej Skutka
Hello!
Let me introduce a new member of the QA team - Ron Šmeral ('ron 'ʃmɛral; ron shmeh-rull). He came as the backfill for Jozef and as such will be working on QA for Seam and related JBoss products. Please join me welcoming him and be ready to help him finding bugs in your code.
More words from himself:
> Up to this day, my experience with Java development has been purely
> non-commercial, with the most relevant contribution being my bachelor's
> thesis in the field of natural language processing. I try to remain
> optimistic about my lack of experience with development (and, a
> fortiori, testing), regarding it as an opportunity to gain new skills
> quickly, coming untainted with bad habits and preconceptions.
> In my never-ending search of perfection, I hope to be a good addition to
> the team whose primary focus is quality.
> I love jazz music, good books and absurd humour.
>
>> Ron
>
Thanks and good luck in JBoss
Ondra
14 years
Transaction Events
by Dave Oxley
Hi,
I've been attempting to add persistence to the seam-cron module for
which I need to use transaction events. Unfortunately I cannot get them
to work. They always get called immediately rather than when the
transaction is completed. So I turned to the seam-booking example
(https://github.com/seam/examples/tree/master/booking) which I saw was
using transaction events and added some logging (attached), but this
appears to have the same issue. The output from the log is:
17:13:16,580 INFO
[org.jboss.seam.examples.booking.booking.BookingAgent]
(http--127.0.0.1-8080-1) confirm begin
17:13:16,587 INFO
[org.jboss.seam.examples.booking.booking.BookingHistory]
(http--127.0.0.1-8080-1) Adding new booking to user's cached booking history
17:13:16,588 INFO
[org.jboss.seam.examples.booking.booking.BookingAgent]
(http--127.0.0.1-8080-1) onBookingComplete begin
17:13:16,589 INFO
[org.jboss.seam.examples.booking.booking.BookingAgent]
(http--127.0.0.1-8080-1) New booking at the W New York - Union Square
confirmed for Shane Bryzak.
17:13:16,599 INFO
[org.jboss.seam.examples.booking.booking.BookingAgent]
(http--127.0.0.1-8080-1) onBookingComplete end
17:13:16,600 INFO
[org.jboss.seam.examples.booking.booking.BookingAgent]
(http--127.0.0.1-8080-1) confirm end
But in theory the order of the logging should be:
confirm begin
confirm end
onBookingComplete begin
onBookingComplete end
I did note that there was nothing specifying a transaction was required
for the entirety of the confirm method so I also added
@TransactionAttribute(TransactionAttributeType.REQUIRED) to the method
(also in attached patch), but that had the same result.
I've been trying this in jboss-as-web-7.0.2.Final. I'm probably doing
something wrong but I don't know what. Does anyone have any ideas?
Cheers,
Dave.
14 years
unsubscribe
by Breychak, Andrew (NIH/CIT) [C]
unsubscribe
14 years
