Skip to Content
author's profile photo Former Member
Former Member

Language Tutorial Problem

I tried this tutorial:

https://www.sdn.sap.com/sdn/developerareas/webdynpro.sdn?page=TutWD16_International.htm

It says in the PDF <i>In the current version of the Sneak Preview, an error occurs when you save the

*.xlf files. For this reason, you cannot translate the English texts into German as

described below under Translating *_de.xlf.

application.</i>

So I skipped that part. But when I try to build, there's a generated class InternalFormView.java that's not finding com.sap.tut.wd.languages.FormView.

I noticed "Activate Raw Language Support" under "Repair", but I figured if I did that, then the resulting application would not display alternate languages.

If I were to say that it is not possible to run a multi-language example under the sneak preview edition, would I be correct? If not, what would I need to do?

Dale

Edit Point:

I downloaded the complete language application, and it does function properly for English.

But looking back on the tutorial version of the code, I noticed that the generated class "FormView.java" got in a hosed state (everything says 'obsolete'). How does one get out of this state?

// ---- content of obsolete user coding area(s) ----
//@@begin obsolete:javadoc:onActionRent(ServerEvent)
//  /** Declared validating event handler. */
//@@end
//@@begin obsolete:wdDoExit()
//@@end
//@@begin obsolete:imports
//import com.sap.tc.webdynpro.progmodel.controller.MessageManager;
//import com.sap.tut.wd.languages.wdp.IMessageLanguagesComp;
//import com.sap.tut.wd.languages.wdp.IPrivateFormView;
//@@end
//@@begin obsolete:javadoc:wdDoExit()
//  /** Hook method called to clean up controller. */
//@@end
//@@begin obsolete:others
//@@end
//@@begin obsolete:wdDoInit()
//@@end
//@@begin obsolete:onActionRent(ServerEvent)
//	String vehicleType = wdContext.currentContextElement()
//	.getVehicleType();
////	  if no vehicleType was choosen
//	if (vehicleType == null){
//	MessageManager msg = (MessageManager) wdComponentAPI
//	.getMessageManager();
//	msg.reportMessage(IMessageLanguagesComp.NO_CAR,	null,	false);
//	}
////	  if a vehicleType
//	else{  
//		wdThis.wdFirePlugOutRent(vehicleType);
//		}		  
//@@end
// This continues but, you get the idea... everything is commented-out.

Second edit point:

By renaming the generated file in the navigator view (essentially eliminating it), I was able to get past the problem. I had to also eliminate ResultView.java. These may be found in gen_wdp/packages/.../wd/languages.

Message was edited by: Dale Seng

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Jun 18, 2004 at 03:50 PM

    Hi Dale,

    this was a bug in earlier versions of NDS (still evident for your Sneak Preview Version, i'm afraid). Simply <b>don't touch</b> .xlf or language-related property files, it will in most cases lead to the behaviour you mentioned.

    As i've read in another topic, a new WebAS preview version will be available at August this year, where this should be fixed i guess.

    Regards

    Stefan

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.