[JBoss Seam] - Re: JBoss Seam is just a toy in front of the user using Spri
by dhartford
Good post Norman!
I am very strong on standards -- particularly when there are multiple implementations of a standard that each of strengths and weaknesses on both the implementation level as well as showing where the standard is weak and learn from it.
I personally did not look heavily at Seam until the Web Beans JSR and it's future inclusion with the Java EE standards stack. I am hoping for the day a Jboss-competitor will create a Web Beans implementation to compete against Seam on an apple-to-apple comparison (spring vs Java EE is just theological apple-to-orange comparison).
Going back to Seto's original post, take a look at bfo81's reply - AppFuse was one of the faster way to develop a web application, but even now people are migrating towards Seam. In the long run Seam may prove to be the better value, but short-term it's dependent on your skill set.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957412#3957412
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957412
19 years, 9 months
[JNDI/Naming/Network] - CommunicationException -
by andrew.rw.robinson
I am trying to track down some slow code in my JBoss/JBoss-Seam JSF code. After debugging into the source, I have found the culprit. The problem is in the code that is attempting a JNDI lookup. This lookup is resulting in a CommunicationException with the message "Receive timed out".
The code that is being used:
return (UserTransaction) Naming.getInitialContext().lookup(userTransactionName);
This is Seam code. The initial properties it is using are:
java.naming.factory.url.pkgs = org.jboss.naming:org.jnp.interfaces
java.naming.factory.initial = org.jnp.interfaces.NamingContextFactory
The "lookup" method on the naming context is what is throwing the CommunicationException
This is resulting in really bad performance from our application as it takes some time to time out (a few seconds makes a big difference when you are dealing with 100s of web requests).
I am not all that familiar with JBoss and its JNDI configuration. Is there someone that can point me in the right direction for determining what is wrong? (I cannot even find what URL it is trying to use to lookup the object).
Thanks,
Andrew
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957402#3957402
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957402
19 years, 9 months