List of wishes and questions.

List of stuff i'd like there to be, and philosophical questions relating said things.

• Eclipse, debug mode, change values of variables on the fly.
• Dynamic breakpoints (conditional breakpoints that depend on other debugging evaluations)
• Scripting language for debugging ((previous wish)++)
• Professional debugging book

JMX and java.lang.instrument

gotta check those things out.

Weblogic mysql connectorJ classpath

problems?

go to %WL_HOME%\user_projects\domains\\bin\setDomainEnv.cmd

add these 2 lines at the end

set MYSQL_CLASSPATH=%WL_HOME%\server\lib\mysql-connector-java-5.1.18-bin.jar

set CLASSPATH=%MYSQL_CLASSPATH%;%JAVA_HOME%\lib\tools.jar;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar;%CLASSPATH

3 XDoclet 1.2.3 bugs

Came across 2 bugs in XDoclet 1.2.3,

figured out the work-around.

1: Generics:

-Doesn't know that.

--Workaround: You will have to parameterize the generated methods/classes yourself.

---How-To: Since the only class you Modify with XDoclet is (are) the XxxBean class, which is translated into the Xxx (and XxxLocal) interface(s) in the YYYClient, just make it so that the Xxx and XxxLocal interfaces contain the method signatures of your XxxBean class.... as EJB's should do.

---Observation: This is safe to do, since your XxxBean in the YYY project and the Xxx in the YYYClient project classes are the only ones that keep record of your methods.

2: Messed-up generation:

-Sometimes, it generates an extra (incomplete) interface in the wrong project

--Workaround: just delete the interface.

---Observation: This is safe to do because it appears the deployment descriptors and all the generated interfaces are intact and functional.

3: "List", and "Class":

-Once a reference to java.util.List is included, the bug specified at section 2 happens.... Ima guess this happens on a whole lot of other classes...Ima also guess any class that can be made generic is gonna make XDoclet act this way.