[jboss-as7-dev] Detecting deployment location errors for xml files using a JEE schema

[Paul Robinson]

On 24/02/12 16:01, Scott Marlow wrote:
> At some point, I'd like to see an optional monitor that could collect
> details about what occurs in each JTA transaction and report on it.  The
> purpose being to reduce the time it takes to understand what happened in
> a transaction that didn't complete successfully or to find out how long
> each step took. Also, being able to see what happens inside of each
> transaction.  We would need a cross project SPI for this that could be
> used by JCA/JPA/TM (and some AS.futureVersion).
I'm not sure this is related to this issue. However, this is something 
I've thought would be handy for many years. I was thinking about a tool 
that would visualise a transaction, showing what boundaries it crossed 
and what resources where enlisted within each boundary. You could also 
see participant votes in 2PC and any other reason why a rollback occured 
(presumed abort, for example). Also, we now have bridging between 
different transaction types (currently WS-AT to JTA and visa versa, but 
more to come). It could be useful to visualize the transaction types and 
where bridging occurs.

Is this the type of thing you where thinking about?

I originally offered a simplification of this as an internship project. 
I'll see if I can dig out the spec.

Paul.

>
>
> On 02/24/2012 09:36 AM, Paul Robinson wrote:
>> A common problem I see again and again is when people miss-spell the
>> filenames of XML artefacts that live in the META-INF and WEB-INF
>> directories of a JEE archive. I also see people (myself included)
>> putting these artefacts in the wrong location, For example, putting the
>> beans.xml file in the META-INF of a .war when it belongs in the WEB-INF.
>> This can cause a big headache as it looks like you have created the
>> right artifact, but it is not taking effect. It would be great if we
>> could detect this type of thing and warn the developer at deploy time.
>> There seems to be a move towards using marker files (beans.xml,
>> faces-config.xml) to enable technologies, so this issue could become
>> more prevalent.
>>
>> One solution, I was thinking about, is to check the schema type of all
>> the XML files in the META-INF and WEB-INF directories. For each schema
>> that we recognize (http://java.sun.com/xml/ns/persistence for example),
>> we check that it's file name is correct and it is in a location where it
>> will be processed.
>>
>> Does this sound like a sensible thing for us to do?
>>
>> Paul.
>>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

-- 
Paul Robinson
Web service transactions lead
paul.robinson at redhat.com

JBoss, a Division of Red Hat
Registered in England and Wales under Company Registration No. 03798903
Directors: Michael Cunningham (USA), Brendan Lane (Ireland), Matt Parson
(USA), Charlie Peters (USA)