With the new composite.jee functionality, jars found inside
contributions are processed by the EjbArchiveProcessor. There is a
validation test that has an OSGi jar in the contribution but which
isn't an EJB jar. This is still picked up by the EjbArchiveProcessor
and if falls over as, in my case, contribution.jee.impl isn't on the
classpath. Should EjbArchiveProcessor process all jars?

Simon

Reply via email to