Search results for query: *

I think you need to install the jdk141x since the jdk installer sets up your browsers as well for running applets. You can also check that IE is using the sun jvm as well (look under tools->options).

You can open the jboss admin page then click on the jndi link. Then click on the list method. This should give you a list of all avaliable beans referenceable via jndi.

You can download the java SDK + netbeans bundle in the download options for the lates J2SE SDK downloads. Eclipse and Netbeans are decent enough for most types of development. And they're free.

fedtrain: The thing to take note of is that even if J2EE contains a lot of technologies (EJB, JSP, Servlets, JNDI, etc.), you don't have to use all of them to take advantage of J2EE. You can do your project in phases to coincide with you and your team's growing familiarity with JSP/servlet...

Forgot to mention the local references... It depends on what EJB spec you're using. EJB 1.0 doesn't have local references. But who still uses EJB 1.0 now anyway? [pipe]

You need to sign ALL your jar files. Even the libraries that your application uses. The webstart-ed application basically has a more lenient security restrictions than an applet. You can consult the webstart documentation for more info. If you've downloaded the J2SE documentation, it should be...

You basically need to make sure that JNDI is properly configured on both servers. You need to make sure that the server names and the ports are that your pass to the jndi conext are correct. If not, your server applications won't be able to look up the ejbs from each other.

The standard way of accessing EJBs is through JNDI regardless whether your client is a standalone java application or a lightweight JSP web client. JSPs are generally faster since it just outputs text that's rendered by your browser. Standalone java apps are a bit slower when loading for the...

The Netbeans IDE makes *.*~ copies of files that you edit on it. It can be safely ignored or deleted.

You can use an InputSource since it can be constructed from a Reader or an InputStream. There is a method: SAXParser.parse(InputSource, HandlerXXX); Hope this helps.

If you've solved the problem using Chad's solution above or by some other route then ignore this... Here's my 2 cents: You probably need to follow the JMF's package and naming conventions. The Manager looks for processors in: <content package-prefix>.media.processor.<content-type>.Handler...