Dennis Labajo

Greenhorn
+ Follow
since Dec 12, 2009
MN
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Dennis Labajo

Hi!

Is there a way to externalize the list of custom properties I have defined in WAS' JVM to a file?  I'm able to do this for the JVM arguments using -Xoptionsfile but was wondering if there's a similar feature for the JVM custom properties.

Thanks!
5 years ago

Alna Jingan wrote:Basic clustering with Weblogic 12c and Apache Web Server
http://blog.c2b2.co.uk/2012/10/basic-clustering-with-weblogic-12c-and.html



Hmmm, just curious... how does clustering solve the validation error? Or maybe, how is clustering even related to the issue at hand?
8 years ago
Sorry, I'm running out of ideas. I did ask my friend google and the very first that came up that may possibly be related to your issue is this: https://forums.oracle.com/thread/902618

Good luck. I'd be interested to learn what you come up with as a fix.
8 years ago
You're #1 approach is similar to what I do at work except for the part where you use

'<handler-chains xmlns="http://www.bea.com/xml/ns/jws">' from your SimpleChain.xml. I'm not sure if that is a requirement for you because you are using Oracle/BEA server? But that seems to be where the validation error is coming from (quoted below and in bold). Can you try changing this to '<handler-chains xmlns="http://java.sun.com/xml/ns/javaee">' and see if that works?

yashi jain wrote:
[jwsc] [ERROR] - Handler chain file validation error for file: file:/C:/Doc
uments and Settings/njain2/Release10_Handlers_POC/RxCWebServiceGateway/src/com/c
vs/rxconnect/resi/SimpleChain.xml. C:\Documents and Settings\njain2\Release10_Ha
ndlers_POC\RxCWebServiceGateway\file:\C:\Documents and Settings\njain2\Release10
_Handlers_POC\RxCWebServiceGateway\src\com\cvs\rxconnect\resi\SimpleChain.xml:0:
error: The document is not a handler-config@http://www.bea.com/xml/ns/jws: docu
ment element local name mismatch expected handler-config got handler-chains


8 years ago
... and just a bit of additional info:

I am noticing that the delay when calling context.getMessage() are on request (outbound) service calls. On inbound, regardless of how big data is returned from a service, the response time on the function call is quick. SO... why should inbound/outbound matter especially if the size of data on outbound is significantly less?
8 years ago
Hi y'all

I'm using a handler to log web service request/response. I put a timer around the 'context.getMessage()' call and surprised how long the call takes to get the soap message. For example, a soap message with 2,151 characters would take 2156 milliseconds. On a different service call, a soap message having 2003 characters takes 2954 milliseconds. However, I've seen a soap message having 29,149 characters that would only take 93 milliseconds! Has anybody noticed this? Is there a trick to consistently get good response time from calling getMessage()? Or a better performance alternative to logging service calls?

8 years ago
Not sure if this would really help you... I do the same thing except that I did not use the 'Client sample' but created my own client set policy set binding. This allows me to clean configurations that I do not need. Another difference is that I did not use the NodeDefaultTrustStore but a custom store (.p12 file) with the cert (.cer) inside it.
8 years ago
I was just checking out the book from Amazon, is it really just 64 pages or am I seing a typo?
9 years ago
Hi y'all (and a Big Hi to Deepak of course!)

I have a web service consumer application calling a web service synchronously. Recently there's been a push to make this call asynchronous. What's a quick and easy way of doing this? I was thinking if there's a way to just set a property in the BindingProvider request context telling it to send as asynchronous and the supporting runtime would know what/how to handle it. Or, does this require a WSDL modification or regeneration of WSDL stubs?

Thanks!

dnz


9 years ago
I've done logging of this sort in the past but using jax-ws SOAPHandler and SOAPMessageContext. I'm not familiar with Axis but if you could find something equivalent in Axis that will enable you to intercept inbound/outbound soap message, I would recommend using it.
10 years ago
I see...ok, let me try this again tonight and will provide a much better detail. I have to change gears and work on something else right now. Thanks Dave.
11 years ago

David Newton wrote:Forwarding?

You still haven't said precisely what you're trying to do.



geesh, thanks anyway!
11 years ago

David Newton wrote:Action chaining is almost always never the best answer (or even a good one). It leads to difficult-to-maintain applications.



Why is that? So what's the best or good answer? Am I back to making dispatcher work and is that a better approach? If it is, I guess I'm back to my first question...what's the trick to making this work? I can get it to forward to a servlet but not for an action. Forwarding to an action results in a '404' error.
11 years ago

Ananth Chellathurai wrote:Hi,
Are you aware of action chaining in struts2? This URL should help you.



Ananth, that's exactly what I was looking for. Thanks!
11 years ago

David Newton wrote:What do you mean, "calling one action from another"? What specifically are you trying to do?



I'm trying to make action class First execute, return 'success', and then make action Second run without doing a "redirect". So far the only way I am able to run First and then Second is if I explicitly use result type="redirect" which I do not want, e.g.




David Newton wrote:There's no reason it would magically "continue" to another action.






Anyways, by not explicitly specifying a result type I am expecting a "dispatcher" result type as my default (which acts as a forward in lieu of redirect?) because my struts xml extends struts-default.


11 years ago