This content has been marked as final.
Show 6 replies
-
2. Re: centralize cache configurations
tom.baeyens Nov 23, 2007 7:40 AM (in response to tom.baeyens)not yet committed. it will be committed soon
-
3. Re: centralize cache configurations
porcherg Dec 4, 2007 8:22 AM (in response to tom.baeyens)I forgot to post in the forum but the parsing of the cache configuration from a resource works.
I'll modify it to add support for inclusion from a file or an url.
I wrote a method to import an xml tree to a node, I'll check if it can be used for the variables type detection.
regards,
Guillaume -
4. Re: centralize cache configurations
tom.baeyens Dec 4, 2007 8:33 AM (in response to tom.baeyens)"porcherg" wrote:
I forgot to post in the forum but the parsing of the cache configuration from a resource works.
I'll modify it to add support for inclusion from a file or an url.
ok"porcherg" wrote:
I wrote a method to import an xml tree to a node, I'll check if it can be used for the variables type detection.
what do you mean with this ? -
5. Re: centralize cache configurations
porcherg Dec 4, 2007 8:54 AM (in response to tom.baeyens)"tom.baeyens@jboss.com" wrote:
"porcherg" wrote:
I wrote a method to import an xml tree to a node, I'll check if it can be used for the variables type detection.
what do you mean with this ?
The parsing of included files needs to be done in the context of the element that includes the file. To achieve that, a solution is to import the xml elements and add them to the dom tree of the node that includes the file. Then you just parse the content of the tree just as if there was no import at all. (I think we can do that without adding the imported nodes to the dom tree, I'll check).
This mechanism can maybe be used to import and parse the file "pvm.type.resolver.xml" used for variable type detection.
Guillaume -
6. Re: centralize cache configurations
tom.baeyens Dec 4, 2007 9:34 AM (in response to tom.baeyens)looks good. i'll have a look when it is done.