It even implied that it’s actually a J# file.. take that for skewed view of the world.

http://shell.windows.com/fileassoc/0409/xml/redir.asp?EXT=java

There are three steps to evaluating an EL expression.

1
2
3
4
5
6
7
8
9
10
11

//get current EL context
javax.el.ELContext elContext = javax.faces.context.FacesContext.getCurrentInstance().getELContext();
 
//get the expression factory (for seam). You can probably do ExpressionFactory.newInstance() if not using seam .
javax.el.ExpressionFactory expressionFactory = org.jboss.seam.core.Expressions.instance().getExpressionFactory();
 
//Create value expression as the EL I'm evaluating is a value e.g. #{bean.property} . Create MethodExpression if the EL is a method e.g. #{bean.method()}
javax.el.ValueExpression valueExpression = expressionFactory.createValueExpression(elContext, elExpressionYouAreEvaluating, WhateverYouAreExpecting.class);
 
// get value and dont' forget to cast.
whateverYouAreExpecting = (WhateverYouAreExpecting) valueExpression.getValue(elContext);

Yup.. that’s how convulted this is . It should more be like below

1
2

//NOTE: imaginary code
Object value = ExpressionFactory.getValue("#{bean.property}");

That’s what these guys are asking as well..

http://community.jboss.org/people/kchintoju/blog/2010/08/22/debug-logging-not-working-in-jboss-jboss-5-and-log4j

.
.
Caused by: java.lang.NoSuchMethodError: oracle.sql.converter.CharacterConverters.toUnicodeChars([BI[CII)I
.
.

This happened when I tried to switch databases this morning (both Oracle 9i) . Nothing fixed it till I replaced both the Driver jars(nls_charset12-10.2.0.jar, ojdbc14-10.2.0.jar) , preferrably from somwhere the connection is working, I took them from a colleague.  Or you can try and download the latest drivers as well. But make sure to delete your server work and temp directories.

Enter proxy details into Subversion configuration:

Open servers file in the following location

Window XP

C:\Documents and Settings\MyUserId\Application Data\Subversion\servers

Windows Vista

C:\Users\Clientside\AppData\Roaming\Subversion\servers

Update following lines at the end of file

[global]
http-proxy-exceptions = yourproxy exceptions (e.g. dev.company.com.au)
http-proxy-host = yourproxyhost (e.g. proxy.company.com.au)
http-proxy-port = your proxy port (e.g. 8080)
http-proxy-username = proxyusername
http-proxy-password = proxypassword

This step might not be needed all the time

Update Eclipse Proxy settings

Windows > Preferences

Type ‘proxy‘ in the filter text box. Go to ‘Network Connections’ config page. Choose manual proxy configuration and Update the proxy details.

Have a gazillion projects in RAD/Eclipse which all have to be deployed in server for debugging all the time like I do?

There is an easy way to increase RAD/Eclipse debugger timeout.

1. Go to Windows > Preferences > Java > Debug
   
2. Increase both “Debugger time-out” and “Launch time-out” value to be much larger. Try values like 180000/360000 respectively for time-out values of 3 and 6 mins.

Full article at IBM

http://www-1.ibm.com/support/docview.wss?rs=2042&context=SSRTLW&context=SSJM4G&context=SSSTY3&context=SSCGQ7C&context=SSDV2W&uid=swg21212755&loc=en_US&cs=UTF-8&lang=en

http://www.opensolaris.com/

Check it out for your self.

Sun should do more sites like this ..simple and informative.

Check it out.. I’m sure you will like the cool new look.

http://www.java.com/en/