Oracle cannot connect

Problem:
'Cannot connect to database using existing credentials".
This may happen even though you are damn sure you got the username and password correct.

Possible Solution:
Oracle do not accept certain characters such as '.' and ';' and probably many others. So to be safe, use alphanumeric characters.
* During the setting of username and password, Oracle won't complain of illegal characters, but when it comes to logging in, the above error occurs *

JMS unsupported encoding

Problem:
During runtime of a java application, an unsupported encoding for JMS message might appear during JMS operations.

Solution:
A quick fix would be to use the SDK as the runtime JVM instead.

Clicking on jnlp does not open java app

Problem:
By default, Microsoft's IIS mime extensions do not recognize .jnlp files. So clicking on jnlp links on a web page hosted by IIS will simply open a xml document, as best.

Solution:
In the container of the website hosting the .jnlp files, add a mime type/extension as follows.
extension: .jnlp
content type (mime): application/x-java-jnlp-file

axis2 + weblogic > Cannot load dll

There might be times where your java web service code need to load some dlls (Dynamic Link Libraries) for some of the operations. Usually we would put those dll in the same path of the class files, but in this case, it won't work. I also tried fiddling around with the java.library.path but it doesn't seems to work for me.

So for now, here's a temporary resolution.
Place all the dlls in 'C:\bea\weblogic81\server\bin', or wherever you installed your weblogic.

More axis2 with weblogic

Prob: I keep getting this error on axis2.

org.apache.axis2.AxisFault: Class org/xml/sax/InputSource violates loader constraints
at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:434)
at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:373)
at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294)

There's a conflict for the following jars somewhere.
- xalan-2.7.0.jar, xercesImpl-2.8.1.jar, xml-apis-1.3.03.jar, serializable.jar
Resolve the conflict and thats it.

Tip: I read somewhere that you could edit web.xml to make it load from somewhere else.....

Axis2 (or not)

This is a Keep In View topic

Encountered this new issue with my web service.
I am not familiar with the workings of web services, so ain't too sure if its supposed to behave this way.

I noted my web service's POJO running its constructor (no-args) everytime a client stub calls it. Somehow, the instance variables generated earlier are not being reused, and a new one is created.
Ain't sure whats really wrong.....will keep myself updated here.

[PS: The answer to this issue lies within session management. See comment for details.]

Weblogic 8.1 + Axis2

I was tasked to create a few web services using SOAP, with all the wsdl and stuff. I was recommended to use Axis2 after someone made an evaluation and found it good and easy to use.

So there i was using the bottom up approach by coding my exposed method, thereafter running the Axis2 plugins on my Eclipse 3.1.2. There were a few weird issues,

1) Somehow the archiver plug-in couldn't load some of my jars that was packaged with my base code. I had to pack up the aar file myself after reading some specifications.

2) Upon loading the aar in Weblogic, i realized that the jar files in the archive's lib folder are not being read. Resulting in several NoClassFound exceptions. As a work around, i had to place those jars in a separate directory in Axis2's web-inf/lib folder.

3) You might have guessed, somehow File(filename) codes point to Weblogic's domain folder as the root. I couldn't find my configuration files because of this. No time to mess around and thus have to throw my configuration files in those directories as well.

Its probably because i had implemented Axis2's web services incorrectly, but if the same aar is loading in Tomcat, it works..... go figure....