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.]
Its ok to make mistakes, its ok to repeat it.
But please make it a point to learn from it :)
Sunday, August 12, 2007
Saturday, August 4, 2007
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....
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....
Subscribe to:
Posts (Atom)