[JBoss Microcontainer] - Hiding the True Error
by Andrew Rubinger
Andrew Rubinger [http://community.jboss.org/people/ALRubinger] created the discussion
"Hiding the True Error"
To view the discussion, visit: http://community.jboss.org/message/541661#541661
--------------------------------------------------------------
Hey guys:
I'm getting the following error message which looks wrong, and I suspect is hiding the true problem. I've seen this before due to different underlying causes.
12:06:43,718 ERROR [org.jboss.profileservice.bootstrap] Failed to load profile:: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
DEPLOYMENTS MISSING DEPENDENCIES:
Deployment "org.jboss.ejb3.EmbeddedEJBContainerASAdaptor" is missing the following dependencies:
Dependency "interface org.jboss.bootstrap.api.mc.server.MCServer" (should be in state "Installed", but is actually in state "** NOT FOUND Depends on 'interface org.jboss.bootstrap.api.mc.server.MCServer' **")
DEPLOYMENTS IN ERROR:
Deployment "interface org.jboss.bootstrap.api.mc.server.MCServer" is in error due to the following reason(s): ** NOT FOUND Depends on 'interface org.jboss.bootstrap.api.mc.server.MCServer' **
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1253) [:2.2.0.Alpha4]
at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:905) [:2.2.0.Alpha4]
at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.checkComplete(MainDeployerPlugin.java:87) [:6.0.0-SNAPSHOT]
at org.jboss.profileservice.deployment.ProfileDeployerPluginRegistry.checkAllComplete(ProfileDeployerPluginRegistry.java:118) [:0.1.0.Alpha1]
at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:133) [:6.0.0-SNAPSHOT]
at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:56) [:6.0.0-SNAPSHOT]
at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(AbstractServer.java:827) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]
at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:417) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_14]
All that's being done is a simple injection by type; my unit tests which do the same pass, but this fails when coming into AS.
<bean name="org.jboss.ejb3.EmbeddedEJBContainerASAdaptor">
<constructor>
<parameter name="server">
<inject />
</parameter>
</constructor>
</bean>
public EmbeddedEJBContainerASAdaptor(@Inject final MCServer server) throws IllegalStateException,
IllegalArgumentException
S,
ALR
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/541661#541661]
Start a new discussion in JBoss Microcontainer at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 8 months
[EJB 3.0] - EJB3.1 Singleton Beans in AS 6.0.0 M3
by jaikiran pai
jaikiran pai [http://community.jboss.org/people/jaikiran] modified the document:
"EJB3.1 Singleton Beans in AS 6.0.0 M3"
To view the document, visit: http://community.jboss.org/docs/DOC-15105
--------------------------------------------------------------
h5. Overview
JBoss AS 6.0.0.M3 which was released on May 5th 2010, introduces support for EJB3.1 Singleton beans.
h5. What to download and how to use
You can download JBoss AS 6.0.0.M3 from http://www.jboss.org/jbossas/downloads.html here. After downloading the AS, start and stop it once to make sure it boots without any issues.
The next step would be to deploy a EJB3.1 Singleton bean into this server.
h5. EJB3.1 Singleton bean:
Note that the examples shown below are just for the sake of illustrating the usage of singleton beans and as such don't hold much meaning.
Let's deploy a very simple singleton bean which exposes a remote view:
package org.jboss.ejb3.singleton.example;
public interface Counter
{
void incrementCount();
void decrementCount();
int getCount();
}
package org.jboss.ejb3.singleton.example;
import javax.ejb.EJB;
import javax.ejb.Remote;
import javax.ejb.Singleton;
import org.jboss.ejb3.annotation.RemoteBinding;
@Singleton
@Remote(Counter.class)
@RemoteBinding (jndiBinding = "SimpleCounterRemoteJNDIName")
public class SimpleCounter implements Counter
{
// we use a calculator to increment/decrement the count
@EJB
private Calculator calculator;
// Maintains the current count
private int count;
@Override
public int getCount()
{
return this.count;
}
@Override
public void incrementCount()
{
this.count = this.calculator.add(this.count, 1);
}
@Override
public void decrementCount()
{
this.count = this.calculator.subtract(this.count, 1);
}
}
package org.jboss.ejb3.singleton.example;
import javax.ejb.Singleton;
@Singleton
public class Calculator
{
public int add(int a, int b)
{
return a + b;
}
public int subtract(int a, int b)
{
return a - b;
}
}
So in the example above, we have a Counter interface which is exposed as the remote view for the SimpleCounter Singleton bean. Notice that the SimpleCounter class is marked with @Singleton annotation:
@Singleton
@Remote(Counter.class)
@RemoteBinding (jndiBinding = "SimpleCounterRemoteJNDIName")
public class SimpleCounter implements Counter
{
...
The SimpleCounter internally uses a Calculator to do the increment and decrement operations. As you can see, the Calculator is being injected into the SimpleCounter by using a @EJB annotation:
// we use a calculator to increment/decrement the count
@EJB
private Calculator calculator;
If you look at the Calculator class, you will notice that it is a singleton bean with a no-interface view:
@Singleton
public class Calculator
{
...
So effectively, in this example, we have 2 singleton beans. One is exposing a remote view and the other is exposing a no-interface view.
Now package all these classes into a .jar and deploy it to the server which you downloaded earlier. That's it! You now have the beans deployed on the server. The next step is to write a simple client which access the Counter to perform the operations. In this example, let's use a standalone java class which through its main() method, looks up the remote view of the SimpleCounter and invokes the operations. Here's the client:
package org.jboss.ejb3.singleton.example.client;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import org.jboss.ejb3.singleton.example.Counter;
public class Client
{
public static void main(String args[]) throws Exception
{
Context ctx = new InitialContext();
// lookup the counter bean
Counter counter = (Counter) ctx.lookup("SimpleCounterRemoteJNDIName");
System.out.println("Initial count is " + counter.getCount());
// let's increment once
counter.incrementCount();
System.out.println("Count after increment is " + counter.getCount());
// now let's just look up the counter once more
// and see whether the incremented state is still maintained (it should be!)
Counter oneMoreCounter = (Counter) ctx.lookup("SimpleCounterRemoteJNDIName");
// should be 1
System.out.println("Count from another counter is " + oneMoreCounter.getCount());
// now let's decrement
oneMoreCounter.decrementCount();
// should be 0
System.out.println("Count after decrementing is " + counter.getCount());
}
}
In the client code, we first lookup the SimpleCounter singleton bean and try out a couple of operations through it. We then again lookup the same singleton bean and try out some more operations on it. Remember that since it's a singleton bean, all these operations will finally end up being called on the same singleton bean instance. So effectively, you will have a single state irrespective of the proxy instance on which you are invoking the operations.
h5. What should I try next?
The above example was just to get you started with EJB3.1 Singleton beans. Try out the singleton beans within your own applications and let us know if you run into any issues. Feel free to start a discussion about any issues around this, in our http://community.jboss.org/community/ejb3 EJB3 user forum or ping us on http://www.jboss.org/ejb3/chat.html IRC. The more issues you find now, the better - because we can get some of them fixed before AS 6.0.0.M3 is released.
h5. I have some tutorial for singleton beans, Can I contribute?
Similar to our other EJB3 tutorials, we are going to include a tutorial for singleton beans. Infact, the example that is posted here in the wiki, can perhaps be just added as a tutorial in SVN. If anyone of you wants to contribute a different tutorial and a chapter in our guide, then feel free to let us know - either through the forums or IRC.
h5. Known issues:
Currently there are a couple of known-issues in the singleton bean implementation:
1) PostConstruct/PreDestroy are not invoked in a transactional context https://jira.jboss.org/jira/browse/EJBTHREE-2070 EJBTHREE-2070
2) The @DependsOn for a Singleton bean is not yet implemented
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-15105]
Create a new document in EJB 3.0 at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
14 years, 8 months