"anil.saldhana(a)jboss.com" wrote :
|
| The right person to answer is Adrian. :)
I can't answer because there is nothiing specific in the question.
anonymous wrote :
| After updating the version of jboss-test.jar from 1.0.3.GA to 1.0.4.GA, I started getting a bunch of security permission failures.
|
| Does anybody know if this is expected?
|
P.S. I didn't change the way this works by default. I just added a better way
to configure alternative security poliicies.
Most likely it is the chage to the codesource checking that has caught you out.
i.e. previously you weren't testing with the proper privileges for the tests.
This would indicate you are missing some privileged blocks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117565#4117565
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117565
anonymous wrote : From my testing of jboss-test/trunk, destroy does work. But it is not yet released and used for AS 5. I think Martin Vecera fixed the logic. Martin, right? AFAICT before Martin's changes it worked on ant exit only effectively breaking the test suite execution.
I made the change for destroying the JBoss process not to break the test suite execution (if some stop-task's parameter is set) - JBAS-2235.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117551#4117551
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117551
"flavia.rainone(a)jboss.com" wrote : In the given example, deciding that interceptors shouldn't be instrumented would be the same as creating a new restriction. However, how many people intercepts an interceptor? Probably not a very common use case, nor a good practice to be followed, IMHO.
I had this discussion with Bill ages ago, and IIRC the outcome was that it should be possible to intercept an interceptor. I don't remember the use cases though!
BTW there is an interface called org.jboss.aop.instrument.Untransformable that can be implemented to "turn off" weaving for a class
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117531#4117531
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117531
thats fine but i thought we had decided that we want to move away from having configuration in the deployment file. so we would have:
jms-deployer-beans.xml
| <bean name="JBM_JBMS_JNDI_Objects" class="org.jboss.messaging.jms.jndi.JNDIObjectDeployer">
| </bean>
|
|
and then a separate config file(s)
jndi-jms.xml
| <queues>
| <entry name="myqueue1"/>
| <entry name="myqueue2"/>
| </queue>
|
| <topics>
| <entry name="mytopic1"/>
| </topic>
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117526#4117526
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117526