[JBoss Seam] - Seam deploying a class from my war file from path WEb-INF/cl
by birwin
I am trying to deploy a very basic bean as a seam backing bean.
I am deploying the class in the WEB-INF/classes directory. The JBoss logs indicate that seam scans the war file and finds the annotated class. I beleive Seam then attempts to deploy it as a backing bean, but does not know the classes are in the classes directory. It appears to deploy from the root of the war file. It thinks the classes should be in the package WEB-INF/classes/web/utils. Any ideas why? Here is the error I am getting:
2007-08-09 11:39:09,592 DEBUG [org.jboss.seam.deployment.ComponentScanner] found component class: WEB-INF/classes/web/utils/Test.class
| 2007-08-09 11:39:09,608 DEBUG [org.jboss.seam.deployment.ComponentScanner] could not load class (missing dependency): WEB-INF.classes.web.utils.Test
| java.lang.NoClassDefFoundError: WEB-INF/classes/web/utils/Test (wrong name: web/utils/Test)
Here is the class:
import org.jboss.seam.ScopeType;
|
| import org.jboss.seam.annotations.Name;
| import org.jboss.seam.annotations.Scope;
|
| @Scope(ScopeType.CONVERSATION)
| @Name("test")
| public class Test
| {
| private String text = "hello";
|
| public String getText()
| {
| return text;
| }
|
| public void setText(String text)
| {
| this.text = text;
| }
| }
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4072665#4072665
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4072665
18Â years, 10Â months
[Remoting] - Re: JNDIDetector removes detections
by aih1013
Hi Ron,
No I did not resolve the problem completely. However, I am more aware about cause of the problem now.
As I said there are two kind of servers, coordinators and slaves. The slaves are run with very high concurrency factor. i.e. load average is around 6-7. So sometimes they are unable to answer ping requests quickly enough.
To make things work I patched JBoss Remoting source to increase connection checker timeout and tries number. This decreased failures rate downto acceptable level. Now we have failure event one or two times per hour.
However, it would be good to improve JBoss Remoting by providing customization for the server failure detection parameters. Moreover, I think ConnectionValidator should make pauses between validity checks. Now it fires all validations in a row, so all of them may be ignored by overloaded slave server.
Also it would be good idea to optimize jndi detector somehow. Now, all servers check liveness of others. With a big number of nodes, if only one server failed to connect by whatever reasons, global record in JNDI will be updated. But other servers may continue to see it. While number of cluster nodes will grow, the problem will appear more frequently.
- Alexey
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4072663#4072663
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4072663
18Â years, 10Â months