Blog That!

Blog Topic: XMLHttpRequest
By Tom Janofsky
(www.tomjanofsky.com/blog.html)
So I've been doing a bit of work with XMLHttpRequest lately to do dynamic updates on Web application pages behind the scenes and type-ahead drop downs. I thought this demo (www.papermountain.org/demos/live/) was a great example and I've made some modifications for better IE support (z-order with drop downs on the page, deal with IE caching GET requests, and some minor interaction bugs).

Pretty cool stuff really. I'll post those updates soon.

Blog Topic: WebLogic Workshop on Mac OS X (from Linux Installer)
By Simon Brown
(www.simongbrown.com/blog/2004/07/21/ weblogic_workshop_on_mac_os_x_from_linux_installer.html)
If you choose to install Workshop from the GUI installer, it gets installed underneath $BEA_HOME/weblogic81/workshop. In this directory is a script called Workshop.sh and this is used to run the tool. Unfortunately it doesn't run "as is" and some tweaking is needed. First of all, you'll need to "fix" your JDK (www.oreillynet.com/cs/user/view/cs_msg/31140) so that it looks like a typical install (with jre/bin/java and jre/lib/rt.jar). If you've ever looked at the Apple JDK then you'll know what I mean.

Next you need to edit that script and I've done this as follows. I basically changed the path to Java, some of the JVM options, and stopped output being redirected to dev/null (so I can see the stack traces when it blows up, which it hasn't yet).

java -Xmx256m -Xms64m -client
  -Djava.system.class.loader="workshop.core.AppClassLoader"
  -cp "/Users/simon/bea/weblogic81/workshop/wlw-ide.jar"
  workshop.core.Workshop

That's pretty much it. Run the script and Workshop will start up.

Of course, since it's another Java application, WebLogic Builder also runs fine. I've loaded an application into these tools and I was able to deploy and redeploy from it just fine, editing the code and/or config as necessary. WebLogic on Mac is certainly a viable development platform for J2EE.

Blog Topic: Debug J2EE Apps Deployed on Weblogic with Eclipse
By Jeremy Whitlock
(http://dev2dev.bea.com/blog/jcscoobyrs/archive/2005/04/)
PREREQUISITES:

• Eclipse 3.0 - www.eclipse.org
• Weblogic 6.1/7.0/8.1 - www.dev2dev.com/wlserver
• Weblogic-Eclipse Plugin 1.1.1 - https://eclipse-plugin.projects.dev2dev.bea.com

GETTING STARTED
Once you have your environment properly setup (Eclipse installed, Weblogic-Eclipse plugin installed, and Weblogic installed with a working domain configured) we need to setup the Eclipse-Weblogic plugin.

Window > Preferences > Weblogic

• Select the "7.0 or higher" radio button for the Version
• Input your BEA Home
• Input your Weblogic Home
• Input your Domain Name
• Input your Domain Directory
• Input your Server Name
• Input your User capable of starting the server
• Input your Password
• Input your Hostname
• Input your Port

Window > Preferences > Weblogic > Classpath

• Input your required classpath entries. [Optional]

Window > Preferences > Weblogic > JavaVM Options

• Input your required Java VM Arguments. There are some required WebLogic arguments already predefined. [Optional]
• Input your JNI path. This is useful if you want to use the WebLogic native I/O libraries in $WL_HOME/server/bin. [Optional]

Window > Preferences > Weblogic > Project

• Input a reference to an existing Eclipse project with the source/classpath for your J2EE app that you have deployed to Weblogic. [Optional]

Some of the above mentioned as [Optional] are optional to make the plugin find your sources and such, but are not required for making the plugin start/stop WebLogic.

Now that we have everything setup, click the green triangle in the toolbar. This should start WebLogic. If you get errors they will show up in the Console and should be able to be fixed easily. Now deploy an application to WebLogic, if you haven't already, that has its corresponding source in an existing Eclipse project that you should have referenced in the WebLogic Preferences. Once it's deployed, open any of the .java files for the deployed application and put a breakpoint in the source by double clicking the gray bar to the left of your source document. You should be updated with a blue orb in the gray bar on the line you double clicked beside. Now run your J2EE app and when you hit that breakpoint, Eclipse should alert you and you can step through the J2EE application to debug. While brief, this should supply you with all you need to debug your J2EE apps deployed to WebLogic inside of Eclipse. If you need any help or run into problems let me know and we'll remedy them.

Add Your Feedback

In order to post a comment you need to be registered and logged in.

Register | Log in

Please wait while we process your request...