We have some strange results when trying to sew our application together.
Calling our EJBs from JSP pages worked fine for the EJB dev team, but when
merging the different modules together to make one application after
initial development of base modules didnt work to fine.
We merged a Webapplication and an ejb application to one, and synchronized
the configuration.
But now it seems when browsing the JNDI context within JSP there is no beans
deployed, but when using a java client we get access to the beans, and can
browse the JNDI context ????
Anyone have any ideas??
/Klaus
