Hi Valentine, Thanks it makes a little sense now! I was little confused b'cause the url, like you mentioned is pointing to void!
I'm wondering it what are the other options/features this BluePrint-ext has! Any ideas? Thanks Matt On Thu, May 12, 2011 at 1:08 AM, Valentin Mahrwald <[email protected] > wrote: > Hi Matt, > > the blueprint-ext namespace (unfortunately the URL as usual points into the > void) contains property placeholders (for the old config admin work), i.e. > properties containing placeholders like ${user.name}, and field injection > (what the RedBook referred to). The namespace itself is included and handled > by the core Aries Blueprint bundle so it will always be available. > > Hope this helps, > > Valentin > > On 11 May 2011, at 19:55, Matt Madhavan wrote: > > Hi Tim, > Thanks for the reply! Meanwhile yesterday I tested all the annotation > configuration (Beta) from the blueprint. They all worked great! The sample > was missing the service tracking and I enhanced the test to include those > tests as well. They seem to work just fine! > > IBM Redbook mentions the following link! > > http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0 > > Any idea about this BluePrint extension from Aries? > > I'm very busy setting the OSGi dev env for my client at this point. Also I > promised the PAX folks I will contribute to them as well. Not sure how much > time I have at this point. Let me see what I can do! > > Thanks > Matt > > > On Wed, May 11, 2011 at 12:48 PM, Timothy Ward <[email protected]>wrote: > >> >> Hi Matt, >> >> I'm afraid there is currently no support for annotation-based >> configuration in aries blueprint. We are prototyping annotation >> configuration for blueprint, but this doesn't currently include support for >> custom namespaces like transactions. If you have anything you'd like to >> contribute in this area you'd be more than welcome! >> >> Regards, >> >> Tim >> >> ________________________________ >> > Date: Wed, 11 May 2011 09:56:29 -0500 >> > Subject: Blueprint JTA Annotations? >> > From: [email protected] >> > To: [email protected] >> > >> > Hello, >> > We are using Aries Blueprint and OpenJPA 2.0. I'm investigating how to >> > mark my methods transactional using annotational! >> > >> > >> > >> > Going forward we would like to use Blueprint based annotations instead >> > of verbose xml files. >> > >> > I would like to annotate my class as follows: >> > >> > public class BlogPersistenceServiceImpl implements >> BlogPersistenceService { >> > >> > @PersistenceContext(unitName="blogExample") >> > private EntityManager em; >> > >> > >> > @TransactionAttribute=Required >> > public void createAuthor(String email, Date dob, String name, >> > String displayName, String bio) { >> > AuthorImpl a = new AuthorImpl(); >> > .... >> > } >> > >> > Is it possible to do @TransactionAttribute in Aries? Any help will be >> > appreciated! >> > >> > Currently my persistence service class is defined in blueprint.xml as >> > follows: >> > >> > > class="com.xxxxx.jpa.dao.BlogPersistenceServiceImpl"> >> > >> > >> > >> > >> > > interface="com.xxxxx.jpa.api.persistence.BlogPersistenceService"> >> > >> > > key="osgi.jndi.service.name" >> > value="persistence/bpJPAPersistenceService"/> >> > >> > >> > >> > Thanks in advance! >> > Matt >> > >> > > > >
