Hey Scot Bellamy wrote: > > The VM needs this because it contains the classes used in looking up information > in the JNDI database. If your client is an HTML browser, you might want to > consider using a servlet or JSP to serve up the HTML pages to the browser. > Otherwise, an applet might get a little heavy when having to include classes for > doing JNDI lookups and for dealing with Home and Remote interfaces. Well, not really. The amount of classes needed are truly minimal. I don't have the numbers but I think it's below 50k (even quite a bit below that). If you're doing an Intranet app, then it's not a problem. /Rickard -- -------------------------------------------------------------- To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Problems?: [EMAIL PROTECTED]
- [jBoss-User] Re: [jBoss-User]java.lang.NoClassDefFoundError:... Rickard �berg
- [jBoss-User] javax.naming.NoInitialContextException Pedro
- Re: [jBoss-User] javax.naming.NoInitialContextException Scot Bellamy
- Re: [jBoss-User] javax.naming.NoInitialContextException Pedro
- Re: [jBoss-User] javax.naming.NoInitialContextException Aaron Mulder
- Re: [jBoss-User] javax.naming.NoInitialContextException Rickard �berg
- Re: [jBoss-User] javax.naming.NoInitialContextException Pedro
- Re: [jBoss-User] javax.naming.NoInitialContextException Pedro
- RE: [jBoss-User] javax.naming.NoInitialContextException marc fleury
- Re: [jBoss-User] javax.naming.NoInitialContextException Scot Bellamy
- Re: [jBoss-User] javax.naming.NoInitialContextException Rickard �berg
- Re: [jBoss-User] javax.naming.NoInitialContextException Tom Cook
