[jboss-dev-forums] [Design of POJO Server] - Re: Using AnnotationEnvironment in Seam

[pete.muir@jboss.org]

"alesj" wrote : Basically you're saying you scan the whole classpath,
  | but only do real lookup from the root of those deployments/classpath entries
  | that have some Seam specific resource present?

Yes, we do this to limit the scanning (which in this case isn't relevant), but we need to preserve the behaviour I think.

anonymous wrote : The AnnEnv handles this already since it does lookup at the classloading layer, we could perhaps exclude deployments that don't contain any Seam specific resource before we actually do some reading from AnnEnv.

Sounds good.

"alesj" wrote : "pete.muir at jboss.org" wrote :  so can we get this metadata (files, based on their filename) from the MC?
  | 
  | 
We could add this in a similar way we do annotation scanning - 
as ResourceVisitor on Module.
Or we could visit deployment's root,
excluding deployment's metadata locations.

The result should be then put as attachment to deployment unit's attachments.

Let me know what exactly you need,
and I'll try to put the code into seam-int/microcontainer module.

Currently, I need a way to get all files that end with a suffix (like ".page.xml" or ".jpdl.xml") that exist in archives which are marked to be scanned by Seam (as discussed above).

"alesj" wrote : "pete.muir at jboss.org" wrote : 
  |   | 3) For the future, can we add support for metaannotations support? This will make it supereasy to use for WB.
  |   | 
  |   | 
  | You mean this:
  | 
  |   | @DeploymentType
  |   | public @interface SomeType {}
  |   | 
  |   | @SomeType
  |   | public class MyTypeImpl {}
  |   | 
  | Where you would like to get MyTypeImpl class?
  | 
  | Should be easy to add.
  | I'll have a look.

Exactly. 

"alesj" wrote : "pete.muir at jboss.org" wrote : 
  |   | 4) How does it handle exceptions loading classes? Throw them for us to catch?
  |   | 
  | AnnEnv doesn't load classes. ;-)
  | But it will throw RuntimeException when you ask for it and it fails.
  | Annotation scanning deployer by default doesn't fail if it has some problems 
  | reading the annotations. But this is configurable.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171288#4171288

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171288