[jboss-dev-forums] [Design of EJB 3.0] - Re: EJBTHREE-1423 Test case for @RemoteBinding

[jaikiran]

"ALRubinger" wrote : 
  | I just checked current HEAD of SVN; Proxy is still on Beta35:
  | 
  | $ mvn dependency:tree -Dincludes=org.jboss.metadata |grep metadata
  |   | [INFO] \- org.jboss.metadata:jboss-metadata:jar:1.0.0.Beta35:compile
  | 

That's one thing i found strange, this morning, when i started on this. The ejb3-build pom had this:

  |    <dependency>
  |         <groupId>org.jboss.metadata</groupId>
  |         <artifactId>jboss-metadata</artifactId>
  |         <version>1.0.0.Beta36</version>
  |       </dependency>


But from the maven build logs (i did a clean install), i saw that only beta 35 was downloaded. So just as a hack, i added the         1.0.0.Beta36 to the ejb3-proxy module and rebuild the proxy module. This time i did see that the Beta36 was downloaded.

"ALRubinger" wrote : 
  | The error you're seeing is because the interceptors themselves are declared in a configured interceptor stack, which is required.  @see ejb3-interceptors-aop.xml (either in EJB3 Core src/main/resources or EJB3 Proxy src/test/resources).  Problem is that you need for your test to load up these definitions;
  | 

Makes sense.

"ALRubinger" wrote : 
  |  this is what I'd meant by "Add to setupBeforeClass the boilerplate for deploying *-aop.xml, example in JndiSessionRegistrarTestCaseBase (else tests will fail)". :)
  | 

Hadn't grasped it when i read it earlier. But i understand now :)




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

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