An internal error occurred during: "Starting Oracle WebLogic Server 10gR3 at". java.lang.NoSuchMethodError: org.w3c.dom.Node.getTextContent()Ljava/la

An internal error occurred during: "Starting Oracle WebLogic Server 10gR3 at".

java.lang.NoSuchMethodError: org.w3c.dom.Node.getTextContent()Ljava/lang/String;

its been quite long, i have not been blogging as the work load in my new company is so freakin heavy. Well, just want to share up some small thing but its very annoying and noisy. Well, here is the story behind this error.

Previously, I had a problem on using BIRT on Maximo. and it seems that the problem is caused by some incompatible library. After googling around, I found out that a few people experiencing the same problem as me even not specifically for the use in BIRT and Maximo.

Then, I followed what the suggestion told me to. Yet, the result is not as what I had expected. It does not work at all. Seeing that this problem took too much of time and also the due date of the project is quite close, then I was moving forward to deal with another stuff. The day after, I got my PC restarted and then I got the problem as the above. After troubleshooting the problem, I found out that the problem relies on the endorsed method which I took to sort out the problem of maximo and BIRT.

Rolling back all the changes, will give back your eclipse to normal.

The path does not contain a valid WebLogic Server install

Its been a while for not blogging. huehue... now im working in a different company and different business. Most of the time, I deal a lot with weblogic and etc. Alright, the first time dealing this application server with eclipse, I have a problem saying a non existence of home directory as in the title of this blog.

Upon googling around, I found out some discussion about this message. We need to point eclipse to some part of the directory of weblogic which is /weblogic81 or whatever version that maybe another user uses. Well, as most of the beginner, many people will not be aware of bea home and bea installation directory (I havent tried to differ between bea home and bea installation directory). Anyway, it is sorted out by pointing the explained-above directory.

Project properties of JIRA

Currently, I am doing plugin development of JIRA. A request of my friend in hongkong. The functionality of this plugin is to clone the existing project with all the issues and the configuration of the project. Thus, this project will be akin of template to create 'real' project.

One interesting part of developing this plugin is cloning the issue type scheme. As we know that JIRA has issue type scheme to differentiate the type of the issue. JIRA divides the issue type scheme to be global and not global. By default, the global issue type scheme is Default Issue Type Scheme. But, strange thing is happening when I try to fetch the entity of Default Issue Type Scheme. When I use the following line to get the entity:

FieldConfigScheme fieldConfigScheme = issueTypeSchemeManager.getConfigScheme(existingProject);

and the above result is checked against the isGlobal() method of object fieldConfigScheme. The result is false which I think, it is supposed to be true. However, what i did to solve the problem is to check the object against the default fieldConfigScheme and it works.

Guice-ing your code

During my learning on shindig, i found out that shindig using guice a lot on its code. Of course, I try to find out what is this tool about. After a little bit searching, I found out that the it is a bit similar with Spring. However, the authors say that it is different. They say that guice is not container and it is too light to be container. Anyway, just cut the bullshit and try to find out what is this tool about.

The first impression on my side after trying this tool is simple. Well, yes... it is indeed very simple as a dependency injection framework. What you need to do is the annotation. It makes all the things very simple.

The things that you need to remember (well, at least on my simple try) on regard of guice-ing your codes is the injector. The injector will try to lookup what are the fields, methods or constructor which need to be injected with object. Then, guice will inject it for you.

Below is a little bit example on it:

public static void main(String[] args) {
// TODO Auto-generated method stub
Injector injector = Guice.createInjector();
Customer customer = injector.getInstance(Customer.class);
customer.changeItem("barangnya");
}

The method injector.getInstance(Customer.class) will give you a complete object of customer with the injected notifier object. Below is the class of Customer:

public class Customer {
@Inject
public Notifier notifier;
public void changeItem(String message)
{
notifier.sendNotification(message);
}
}

Notifier is an interface. Guice will lookup on this interface to find out what class implement Notifier interface. In order to know what class which implemet Notifier interface, the interface should define annotation to tell the guice. Below is the interface of Notifier.

@ImplementedBy(SendSms.class)
public interface Notifier {
public void sendNotification(String message);
}

Its easy, isnt it (well, at least for this try :P)?