[infinispan-dev] [jboss-dev] Infinispan configuration - all in one solution

[Manik Surtani]

Everyone star this!  :-)

 From what I gather from the comments on the link below, the  
blacklisting can be worked around to some degree.  Has anyone tried an  
alternate JAXB implementation like JBossXB, perhaps using the impl  
classes directly rather than the javax interfaces?


On 17 Jul 2009, at 20:03, Adrian Cole wrote:

> By design as far as I can tell: The important jaxb classes are  
> restricted.
>
> http://code.google.com/p/googleappengine/issues/detail?id=1267
>
> -A
>
> On Fri, Jul 17, 2009 at 8:56 PM, Emmanuel Bernard <emmanuel at hibernate.org 
> > wrote:
> You mean JAXB by design or the JAXB implementation you have tried?
>
> On  Jul 17, 2009, at 14:47, Adrian Cole wrote:
>
>> The only problem with using jaxb is that it doesn't work in google  
>> app engine.  Switching to jaxb implies adding another roadblock on  
>> the way to gae/j support.  This is the only reason I'm not using  
>> jaxb for jclouds, even though it would make things simpler.
>>
>> -Adrian
>>
>> On Fri, Jul 17, 2009 at 5:38 PM, Vladimir Blagojevic <vblagoje at redhat.com 
>> > wrote:
>> On 7/17/09 5:16 PM, Bill Burke wrote:
>> > Wouldn't it be better to write a javadoc-like generator that
>> > introspected for JAXB and Inifispan annotations instead of  
>> writing your
>> > own XML parser and schema generator?  Or maybe I'm  
>> misunderstanding your
>> > post.
>> >
>> > In other words, use JAXB for marshalling/unmarshalling/schema
>> > generation.  Use inifinispan javadoc generator for documentation.
>> >
>> I looked around a bit more to see that now in JAXB 2.x we have
>> annotations as well :) If we annotate our configuration beans with  
>> JAXB
>> annotations I suppose we can do exactly what you suggest - use JAXB  
>> for
>> marshalling/unmarshalling/schema generation and at the same time use
>> those annotation in a custom tool that creates reference  
>> documentation.
>> > By creating your own XML parsing you've just complicated the  
>> maintenance
>> > problems for future maintainers of infinispan.
>> >
>> I agree.
>>
>> Cheers,
>> Vladimir
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>>
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev

--
Manik Surtani
manik at jboss.org
Lead, Infinispan
Lead, JBoss Cache
http://www.infinispan.org
http://www.jbosscache.org




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/infinispan-dev/attachments/20090720/a76a1b7b/attachment-0002.html