Michelle Baxter

Edit - select all
tab until it's indented the way you want.
If you want spaces instead of tabs, select the option to replace spaces with tabs on save. There was also some shortcut, like ctrl-shift-i tab, but I don't know how it's different.

I am loading an applet in an HTML page in a frame with the applet params: hspace=0, vspace=0, width=100%, height=100%, but when the applet loads in IE, there is a strip of whitespace on the right that doesn't look very good. The entire applet is visible, but the space looks bad. When I load it in Netscape 4.5, there's white space on the right side as well as on the bottom. Anyone know how to get rid of this?

I haven't tried this, but to run a UNIX command from a window and have it continue after logging out or killing the window, try the nohup command. You should be able to do a man on it, or type nohup --help. Let me know if it works.

I think the compiler is getting confused with the options. Try leaving out the "-d dir" temporarily. Sorry I can't be of more help than this. I'm using WebLogic 6.0, so -nodeploy is not even listed as an ejbc option. The 6.0 version also has a -verbose option to help you see what's going on. You might try that. And finally, the WebLogic newsgroups might be able to help.

There are also methods referred to as "home methods" in the home interface (sorry if the term is confusing). These can be used when a particular bean reference is not needed to do the work, kind of like a static method of a class. These methods names should NOT start with "find" or "create". They also will have a corresponding ejbHomeXXX method in the bean class. So for example, if I have a method in my home interface called getSomeStuff(), I would have a method in the bean class called ejbHomeGetSomeStuff(). This is probably not what you are looking for, but you should be aware that it is available. It's in the EJB 2.0 spec, if you want to read up on it.

This is just a guess, but try putting the -nodeploy option before the -d option.

down (Scotty was too obvious)

Check the section of the specification mentioned in the error message. There is a table that lists what EJB methods can be called and when. Your ejbCreate is probably doing something that it shouldn't. I'm guessing that you may need to move whatever you're doing that isn't allowed to the ejbPostCreate, though you should check if it's allowed there too. The spec does a decent job, I think, of explaining why you can't do certain things. I'd paraphrase it for you, but I'd probably say it wrong. Look at the EJB lifecycle too, if you want more info. Hope this helps!

Yes, it's the same as any Java inheritance. You might check the spec on how inheritance is supported for beans.

I have seen this error before when trying to run WebLogic's ejbc from a command line, but never when just compiling from in JB4. The problem for us seemed to be related to using the "wrong" compiler. We specifically used the compiler packaged with WebLogic 6.0 and that fixed it. WebLogic 6.0 requires that you use a JDK with the HotSpot VM, so make sure whatever version you are using will work.

Look at the Java Advanced Imaging API for image processing. How useful it will be depends on what you are trying to do.