Netbeans
I’ve this draft and since I’ve seen that a friend is now in the magic net beans team perhaps is time to publish it 
Maybe he can help me and telling me if I am wrong or just change somehow that tool…
I’m writing some code with netbeans and I would like to note here what I don’t like of this tool. Especially compared to Eclipse.
- Lack of the magic CTRL+1 code assist, this is really slowing down my productivity
- Crap code generation: why is generating always the empty public contructor? With also a smelly comment /** Creates a new instance of … **/
- The generator of code of the Mobility pack is pure crap. I had to open the MIDlet code with wordpad, delete all the crap from the code to be able to change something also inside netbeans. There were import with the star also. Now, of course, I am using netbeans as a simple text editor.
- Refactoring: as fair as I’ve seen the refactoring tool is very poor. You can’t for instance extract a variable as a local variable or field…
- Using create Method when the method is still not implemented netbeans sets the visibility to package and write a stupid UnsupportedOperationException exception.
Beanlet – JSE Application Container – Beanlet and Jarcraft Confluence
Following the bile blog comments/discussion on XML wiring is for girls I found this very interesting link:
Beanlet – JSE Application Container – Beanlet and Jarcraft Confluence
Why use Beanlet?….These are the top ten reasons for using Beanlet technology:
1. Beanlet provides a unique agile non-intrusive container framework.
2. Beanlet API is concise and (soon) well documented.
3. Beanlet respects API compatibility.
4. Beanlet is easy to learn.
5. Beanlet integrates with most popular frameworks.
6. Beanlet is extensible, add your own plug-ins.
7. Beanlet promotes a defensive programming style.
8. Beanlet is open source.
9. Beanlet is free.
10. Nobody has ever beanlet down by it.
Problem in WebSphere 6.0 ejbdeploy
JavaRanch Big Moose Saloon: Problem in WebSphere 6.0 ejbdeploy
Unable to parse setupCmdLine: null\bin\setupCmdLine.bat (The system cannot find the path specified)
I was trying to avoid to call bat files from ant. I hate that. First cos are platform (and what a platform…) dependent, second cos you can always have problems with error codes and the build can be successful even if something bad happens there…
There are 2 correct responses in this thread:
I had the same problem last month, and struggled for a while. I found the point is, we have to use \profiles\AppSrv01\bin\ws_ant.bat to call ant, instead of calling ant directly. By using ws_ant.bat, it will initialize some env variables, and using IBM’s JVM to do the job. Another thing is, in build script, I need to define property “wasinstall” as websphere install home. This property will be used as ejb deploy task’s attribute “wasHome”‘s value.
The first is this, so I’ll roll back my changes. The .bat file is plenty of SET blabla=blabla/bla so I have no choice.
The second is the best one but unfortunately I can’t do that:
There is one fix, delete WAS and never install it
.
Indeed, WAS is an antipattern.