I have copied all to a different name and am running that. I don't like to
touch the baseline configurations so I have something to compare to if
something goes wrong.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4263281#4263281
Reply to the post :
The entire stack trace of the exception thrown is the next to last code posting
and starts with
| 2009-10-27 19:11:51,787 TRACE [org.jboss.ha.jndi.HAJNDI] (RMI TCP
Connection(3)-192.168.11.3) lookup
| Locally failed,
I am attempting to deploy an EAR that contains annotated EJB3 beans. I have
already done this on several instances of JBoss, but this one is causing me
problems. I am getting the following exception.
| javax.naming.NamingException: Could not dereference object [Root exception
is
Sorry, forgot to mention this is on JBoss 5.1.0.GA
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4262524#4262524
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4262524
___
Just to add more detail. I turned up the logging on org.jnp.server to TRACE (it
produces a lot of output) and found this in the log:
| 2009-10-27 19:09:23,284 TRACE [org.jnp.server.NamingServer] (main) bind
UserContextManagement=Reference Class Name: Proxy for:
I downloaded a fresh copy of Eclipse (3.4.2) and am connecting to the
development (http://download.jboss.org/jbosstools/updates/development/) and am
trying to load the JBoss Birt Integration feature. I get message indicating
that the org.eclipse.jst.jsf.core (1.1.102.v20080909) was not found.
I am moving a number of EJB3 beans from JBoss 4.2.2 to JBoss 5.0.0. After
making the annotation alterations (everything is being handled by annotation,
no xml deployment descriptors), I repackaged everything in the same manner that
I did under 4.2.2.
The first thing that struck me was that it
I am getting an NPE from the archive builder when selecting the Build Archive
(Full) menu option on the Project Archives. I am running a fresh copy of
Eclipse 3.3 under JDK 1.5.0_12. I have been working with an Eclipse 3.3 version
downloaded earlier this year (1/15/2008) until today also under
Yes, there is if you are creating a new project. However, since JBoss Tools is
targeted at Eclipse 3.3 and the older JBoss IDE plugin doesn't seem to like
Eclipse 3.3 the move the Eclipse 3.3 necessitates an import of projects from
Eclipse 3.2. The import facility does seem to offer any
I am trying to use the new JBossTools Project archives view to construct
packages. I have run into an issue that seem to prevent me from replicating the
old style JBoss IDE packages.
There doesn't seem to be a way to place files or folders in a specific target
folder in the a compressed jar
I have been poking around looking for the libraries that support EJB3
annotations and have been unable to find them within the tools. The JBoss IDE
used to have an EJB3 project type that pulled the libraries from a server
deployment. Is something like that anywhere within the toolset?
Regards,
I know this is not directly related to JBoss Messaging, but since it came up
during its usage I thought this would be a good place to post this problem. It
seems that the ConcurrentHashMap's inner Segment class is not marked as
Serializable (it is in the Doug Lea's source code) and is causing
Tim, as I said at the outset, this is not necessarily a JBoss Messaging issue.
However, that said, the use of AOP with or independently of the JBoss AS
(4.2.0.GA BTW) should not break the implementation of messaging since the jar
in question is provided externally to Red Hat (Doug Lea's
Tim, this post did not start out as a rant against JBoss Messaging and as
stated in the initial post this was not, necessarily, a messaging issue. It is
simply that the problem appeared (and yes it is a problem although not
monumental) during the use of messaging. I and probably most of the
14 matches
Mail list logo
