Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    1. COI read the info you pointed to and it was very helpful. I used jboss' maven archetype "org.jboss.spec.archetypes:jboss-javaee6-ear-webapp" to generate the project and it did not include Dependencies or Class-Path manifest entries although it did have an ejb -- see [here](http://stackoverflow.com/a/8776267/984932) to see the project the archetype generated -- probably because JBoss' <ear-subdeployments-isolated/> defaults to false. The ejb in the project has a producer method that is accessed from a facelet view and it works fine without any JBoss configuration modifications.
      singulars
    2. COBut the problem I'm having is unrelated to modules within an EAR being able to access other classes within the EAR. In order to debug I removed ViewExpiredExceptionHandler from the application and discovered that the underlying problem is that classes in the EJB module cannot reference any object in faces.context.* packages, else a ClassNotFoundException is thrown. When I remove references to FacesContext, ActionEvent, etc. objects the application deploys without error. It's got to be a bug with JBoss AS7. There is a discussion about it [here](https://community.jboss.org/thread/194780).
      singulars
    3. COOkay, ready on the forum it does look like there are some dependencies you need to add to your EJB deployment. It does look like you're getting better help there, so I'll leave it to the forums :-)
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload