Using "we" I reckon you mention you and SAP and if that's the case you just heard my opinion. After the second time I had to open an SAP Ticket I decided myself to never use that channel again - I'd rather try my odds in SDN because most of the people (Consultants) around here are far more skilled than the general SAP Support I've dealt in the past.
do not get me wrong, we highly appreciate your opinion and we'd love to hear more if you have concrete examples. I only wanted to draw your attention to the proper channel. Though I am not working any more on support incidents related to webdynpro java I would be surprised if it was a joke but of course no doubt everyone can have negative experiences, still I'd like to ask you to be more specific and use the proper channel on one hand in order to avoid influencing negatively others who received proper support, and on the other hand to get heard so we can grow from it and provide better support for you in future.
I don't want to "avoid" influencing negatively - it is what it is and I want it down here in a thread in SDN so anyone can see that I had terrible service when I needed... people can decide themselves if my experiences are so different from theirs... About "proper channel", I reckon SDN is better because it's more "public" - it gets more eyes, and the more the merrier.
As examples:
When I attach a DC which has 4 lines of code on wdDoInit just to reproduce the issue sending all installed SC's / DC's with version to your support and I receive back a "sorry we cannot reproduce the issue" - this is a joke...
When I got a simple random answer which has nothing to do with the issue I raised (perhaps because they had to do some action for some KPI) means "well, this is a joke"..
When I escalate the issue to "very high" (after three months of useless back and forth nonsense communication) to get some attention the *only* contact made was not from technical support itself but rather some other lady "asking" revert the status back to what it was because it makes them look back if it's not resolved within "x hours".. this is obviously a joke.
After all, SAP is not investing in the product anymore (WDJ) why would they really invest in "supporting it" - I still cannot understand this formula as great minds won't stick around with dead end technologies.
First of all I'd like to point out that I hear you, I am with you and I am sorry that you had this experience with webdynpro java support. Still I believe this is not the best channel and therefore I try to be brief.
Until your opinion is not conflicting with any points of -- notice we are a little hijacking this thread and this is the other reason I'll most likely not reflect to further posts -- you have every rights to vent and to tell your opinion. Other question is whether your support related thoughts will find their way to the involved parties; whether the goal is only to vent and to get attention or to tell your improvement ideas and complaints to those who can make a difference.This is why I suggested you the CIC (to show you that my intention is to help and to make things better, you can refer my name if you decide to contact them).
Until you raise technical questions here on SDN SCN, you are right, from that point of view it is perhaps more effective that this is a 1 to N discussion. Two heads are better than one, I agree. SCN is full of brilliant minds and it is fun as you also pointed out.
Not implementing new features for a product (maintenance mode) does not mean we are not delivering fixes and not providing support. Imagine your car would not be repaired only because currently the given car company is not introducing new features to your car type.
Thank you for your understanding and Best Regards,
I will try to be brief as well.. - the op asked about "support" - it's my opinion support in WD Java it's a joke - and by that I mean it's terrible. And you insist in collecting information in a channel I do not want to provide, this is a bit insane.. I'm providing it in this channel, you and your company can either take it or leave it - it is this simple, so no reason to base another reply on such.
About the car metaphor, it's not applicable - as soon you have a real problem in your car that needs expertise or parts that doesn't exist anymore you're screwed - and it's the same in here, there are no "parts" (code) or "expertise" (people) anymore in the market... needless to say, there's no investment and in IT this is sort of a deal breaker.
We're clear here, let's face it I won't convince you and there's no way you're sweet talking me.
Exactly why I wanted to know about the official documents.
I checked this URLs, but nothing is official. one is announcement or discussion @ TechEd and other is a blog. Apparently SAP will not stop but also no more enhancements or upgrades for WD Java.
The only official document is and it was recently updated (2015-10-12). Web Dynpro Java is very much still in the picture and being supported. No need for trolling around this subject, move on...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.