3:03 p.m.
Petr H [http://community.jboss.org/people/hostalp] created the discussion
"Re: How to stop my WAR loading JBoss's provided 3rd party classes?"
To view the discussion, visit: http://community.jboss.org/message/578813#578813
--------------------------------------------------------------
You just need to <javabean> the right filter instance. ;-)
e.g. <-- pseudo code -- I need to check this into more details (it's been a while
since I wrote this javabean' stuff :) )...
Yeah, something of that sort would
do it - CombiningClassFilter::
public static CombiningClassFilter create(ClassFilter... filters) ...
public static CombiningClassFilter create(boolean and, ClassFilter... filters) ...
public CombiningClassFilter(boolean and, ClassFilter[] filters) ...
so passing filters via array would probably work if it's implemented that way. Anyway
use of JavaOnlyClassFilter or EverythingClassFilter will still be an issue due to their
private constructors.
Well, the "plain default" knows about deployment type:
* ear --> isolation --> look locally first == parent-first=false
* war, which has parent-first=false by default
Whereas jb-cl-domain.xml is deployment type agnostic, hence uses the more natural
default.
Right, understood, it's just unfortunate that it's not so simple to
change the classloading back to plain ear default then..
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/578813#578813]
Start a new discussion in JBoss Microcontainer at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
3:10 p.m.
Ales Justin [http://community.jboss.org/people/alesj] created the discussion
"Re: How to stop my WAR loading JBoss's provided 3rd party classes?"
To view the discussion, visit: http://community.jboss.org/message/578815#578815
--------------------------------------------------------------
so passing filters via array would probably work if it's
implemented that way.
Yeah, array usage would work.
But unfortuantely <javabean> xml handling is too simplistic (just checked),
it doesn't support arrays -- by design we didn't over do it --> we have MC
beans.
But you can always simply add your own jar with custom filter impls,
and then simple use <javabean> to instantiate them.
Anyway use of JavaOnlyClassFilter or EverythingClassFilter will
still be an issue due to their private constructors.
Like I already said, this is
simple to duplicate - just check how we do it.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/578815#578815]
Start a new discussion in JBoss Microcontainer at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
4 p.m.
Petr H [http://community.jboss.org/people/hostalp] created the discussion
"Re: How to stop my WAR loading JBoss's provided 3rd party classes?"
To view the discussion, visit: http://community.jboss.org/message/578828#578828
--------------------------------------------------------------
But you can always simply add your own jar with custom filter impls,
and then simple use <javabean> to instantiate them.
...
Like I already said, this is simple to duplicate - just check how we do it.
Yes I know, that's how I'll try it (after we manage to get the app at least fully
starting on JBAS 6) but the main idea was to avoid the need for messing up with the
JBoss-level code as much as possible - so try to make it possible with standard JBoss code
and just "configuration changes".
As for that IncompatibleClassChangeError discussed in parallel - yes I think you're
right with JPA stuff being in the app, I was seeing very similar issues when having JAXB
and JTA stuff in there in my case. Here, parent-first=true would very likely
"fix" that as well.
However parent-first=false is easier in my case, for example because of logging - I've
got a log4j property file on classpath, initializing it via Spring
(org.springframework.web.util.Log4jConfigListener) and with parent-first=false it logs
more or less (well it steals JBoss' own logging but
whatever)"out-of-the-box" while with parent-first=true everything naturally goes
into JBoss server log. I recall there was supposed to be implemented some possibility to
let it working properly with these multiple log4j configs etc (I think this was it but
I'm not that sure at the moment: http://community.jboss.org/docs/DOC-13346
http://community.jboss.org/wiki/LoggingPOJOServiceRequirements) but haven't looked at
it yet.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/578828#578828]
Start a new discussion in JBoss Microcontainer at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
5057
days inactive
5057
days old
2 comments
2 participants
participants (2)
-
Ales Justin -
Petr H