Ahh, All is well now!
Must have made a typo in my ear name previously.
thanks again!
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3962527#3962527
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3962527
_
Hi Sateesh,
We appreciate your help.
Here is the contents of our console.log:
| 10:35:23,693 INFO [EARDeployer] Init J2EE application:
file:/var/lib/jbossas/server/all/deploy/projectMgmt.ear
| 10:35:26,474 INFO [Ejb3DescriptorHandler] adding class annotation
org.jboss.annotation.interna
Hi Sateesh,
Thanks again for your reply.
I checked under the JNDIView service from the JMX Console and invoked the
"list" operation. (Did I do that right?)
I looked under Global JNDI Namespace and got this:
| +- EventDispatcher (class: org.jboss.ws.eventing.mgmt.DispatcherDelegate)
| +- U
Hi Sateesh,
Thanks for your reply.
In both cases (either using seam.properties, or an empty seam.properties and
the information in web.xml) we encounter the same error.
javax.naming.NameNotFoundException: projectMgmt not bound
| at org.jnp.server.NamingServer.getBinding(NamingServer.j
| public class LoginAction implements Login
| {
|
|@In
|@Out
|private User user;
|
|@PersistenceContext
|private EntityManager em;
|
|@Logger
|private Log log;
|
|public String login()
|{
|
Hi Everyone,
We are making a Seam application and we started with configuration files very
similar to those in the booking and registration examples.
To start off we are creating a simple login screen very similar to the one
found in the registration example.
However, when the login button we g
Oops, that didn't come out too well:
| com.sun.facelets.FaceletViewHandler
|
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3962248#3962248
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=396224
We have resolved the problem.
I believe the issue was that we did not have the following in our
faces-config.xml file:
com.sun.facelets.FaceletViewHandler
We made a lot of modifications since then, which is why I'm not 100% sure if
this was the change we made to fix this iss
Hi,
We are having this exact same problem. Were you able to solve this issue?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3961992#3961992
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3961992
