[EJB 3.0 Development] New message: "Re: EJBTHREE-2007: VFS Abstraction"
by Andrew Rubinger
User development,
A new message was posted in the thread "EJBTHREE-2007: VFS Abstraction":
http://community.jboss.org/message/525144#525144
Author : Andrew Rubinger
Profile : http://community.jboss.org/people/ALRubinger
Message:
--------------------------------------------------------------
To use this, apply the following patch to projects/ejb3/trunk/build:
Index: pom.xml
===================================================================
--- pom.xml (revision 100755)
+++ pom.xml (working copy)
@@ -186,8 +186,20 @@
<requireMavenVersion>
<version>[2.0.9,2.1)</version>
</requireMavenVersion>
+ <noCompileDependencyRule implementation="org.jboss.maven.plugins.enforcer.rules.nocompiledep.NoCompileDependencyRule">
+ <excludes>
+ <exclude>org.jboss:jboss-vfs</exclude>
+ </excludes>
+ </noCompileDependencyRule>
</rules>
</configuration>
+ <dependencies>
+ <dependency>
+ <groupId>org.jboss.maven.plugins.enforcer.rules</groupId>
+ <artifactId>nocompiledep</artifactId>
+ <version>1.0.0-alpha-1</version>
+ </dependency>
+ </dependencies>
</plugin>
<plugin>
S,
ALR
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/525144#525144
16 years, 5 months
[JNDI and Naming] New message: "Re: Remote vs. Local client lookup of same JNDI object"
by Brian Stansberry
User development,
A new message was posted in the thread "Remote vs. Local client lookup of same JNDI object":
http://community.jboss.org/message/525135#525135
Author : Brian Stansberry
Profile : http://community.jboss.org/people/bstansberry@jboss.com
Message:
--------------------------------------------------------------
If you can put your remote client in a debugger and put a breakpoint in the org.jnp.interfaces.NamingContext.lookup(Name) method, that's probably your best approach to figuring out what's going on.
I don't know what version you're using so won't quote line numbers, but a breakpoint here would be good:
res = naming.lookup(n);
That shouldn't return null. Then the code drops out of a try/catch block and goes through a bunch of if tests to deal with various types of objects that can be returned, resolve javax.naming.Reference etc. What will happen here very much depends on what was bound into JNDI.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/525135#525135
16 years, 5 months
[EJB 3.0 Development] New message: "Re: EJBTHREE-2007: VFS Abstraction"
by Andrew Rubinger
User development,
A new message was posted in the thread "EJBTHREE-2007: VFS Abstraction":
http://community.jboss.org/message/525131#525131
Author : Andrew Rubinger
Profile : http://community.jboss.org/people/ALRubinger
Message:
--------------------------------------------------------------
Looks like it does the job. I think I'll cut a release and see if it's too eager or breaks anything:
[WARNING] Rule 2: org.jboss.maven.plugins.enforcer.rules.nocompiledep.NoCompileDependencyRule failed with message:
Prohibited dependency from compilation: Dependency {groupId=org.jboss, artifactId=jboss-vfs, version=2.0.0.CR1, type=jar}
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed.
S,
ALR
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/525131#525131
16 years, 5 months