Snippet (allow debugging ... comportement ??)

Je remarque avec LV2013 un éventuel soucis avec la fonctionnalité "VI Snippet".
Quand je crée un "Snippet" au départ d'un VI dans lequel "allow debugging" est OFF
... quand je "re-dépose" le dit snippet sur un BD vierge .... "allow debugging" est ON
J'ai fait la manip plusieurs fois
- je place "allow debugging" OFF à la création du snippet
(le VI sauvegardé et ensuite rechargé en tant que fichier conserve bien "allow debugging" OFF)
- mais le snippet ... replacé sur un BD .... m'indique toujours "allow debugging ON"
un (ou plusieurs) d'entre vous peut-il confirmer (LV2013)
merci.
EDIT
pour être (encore) plus clair ... voici la manip à exécuter :
a) créer un VI (peu importe)
b) placer "allow debugging" OFF
c) sauvegarder le VI
d) fermer le VI
e) re-charger le VI
f) vérifier que "allow debugging" est bien OFF .... oui, il est OFF (normal)
g) créer un Snippet de ce VI
h) sauvegarder ce Snippet
i) fermer le VI
j) ouvrir un VI vierge
k) y déposer le dit snippet (créé en -g- )
l) .... allow debugging est "ON" (???)
Résolu !
Accéder à la solution.

Bonjour Benjamin,
merci pour ta réponse.
Un snippet est du code ... sous une forme différente ... et à chaque code correspond une certain nombre de paramètres.
@Benjamin : " cette notion est lié à un VI dans l'environnement de développement LabVIEW."
oui ... et quand je glisse un snippet sur mon BD ... justement .... ce snippet devient instantanément du code dans l'environnement de développement LabVIEW.
mais ... ce code n'est plus configuré conformément au code d'origine.
Dans le même ordre d'idée ....
Pourquoi un snippet conserve-t-il toutes les autres caractéristiques du code d'origine (en rapport avec cet environnement de développement)
.... mais pas "allow debugging". (??)
Pourquoi, alors, dans un snippet, ne pas mettre tous les paramètres de "vi properties" à ON ou OFF d'office.
Un snippet est une "photo" d'un code (au sens d'une transposition ... rien avoir avec l'extension png).
Et "un code" est caractérisé par un ensemble de fonctions et par "son" environnement ... qui lui est propre.
Un snippet doit conserver la totalité des paramètres de cet environnement.
Ce qu'il fait parfaitement .... sauf pour "allow debugging". (seul paramètre qui est mis à la poubelle et transformé en constante "ON")
Pour moi, je ne parlerai pas de "bug" ... mais c'est un manquement ... un comportement illogique et incohérent

Similar Messages

Does un-checking "Allow Debuging" in VI properties- execution improves overall application performance?

Does un-checking "Allow Debuging" in VI properties->execution improves overall application performance?

> Does un-checking "Allow Debuging" in VI properties->execution improves
> overall application performance?
Yes, though it is hard to predict by how much. When debugging is
enabled, after each node on the diagram there will be a small amount of
compiled code to test if the VI has a probe, a breakpoint, execution
hiliting, or the pause button is pressed. The code is quite small,
about two or three instructions, but if you have twenty nodes in a loop
and the nodes are doing simple math, these instructions could be 25%
overhead. For more complex nodes or datatypes, these instructions turn
into a fraction of a percent.
Turn it off and measure. If you have other performance problems, read
the documentation on the profiler and use it to help you find yo
ur
bottlenecks.
Greg McKaskle

Hosting company doesn't allow debugging on

If my hosting company (crystaltech.com) doesn't allow the coldfusion adminstrator debugging to be turned on, is there anyway I can still get the debug message to display on my broken page? I have an old cf app (MS SQL 2005) I'm trying to debug. It's currently on a coldfusion 9 shared server, written with fusebox. Any ideas? Thanks! -Jim

copy the app to a development location which has debugging enabled.

Debugging RFC function module from ECC to CRM

Hi All,
My requirement is to debug an RFC function module present in CRM(7.0) system from ECC(6.0) system. A report program in ECC will call CRM custom FM. I found many posts in SDN with the same issue and tried to implement suggestions provided there. But I couldn't succeed. The approach I followed is:
I logged in to ECC report program and kept an external breakpoint just before the function module call.
I logged in to CRM system, opened the function module and kept an external breakpoint there.
In both the systems I provided the dialogue userid( id through which I log in to SAPGUI) in the system->settings->debugging option.
In CRM I activated the external break point in transaction SRDEBUG.
Now when I execute the report program in ECC, control stops at the breakpoint. If I press F5 at the function call, control is not going to the external break point set in the CRM FM. I am getting output of FM directly.
I tried with different settings like turning on the check box for IP matching and session breakpoint active immediate, switching to classic debugger etc. I also tried to provide the RFC user id instead of dialogue user but system throws exception saying only dialogue userids are allowed. I found that by inserting an infinite loop statement, control goes inside the RFC CRM FM but I prefer not to change the code.
Please let me know if I missed anything.
Thanks and Regards,
Naren

Hi,
Debug RFC calls
When an RFC function module is called it is usually not possible to debug the call, using the below techniques we can achieve the same. For this example we are calling an RFC enabled FM in ECC system from CRM system.
Scenario 1: Calling a custom RFC FM
STEP 1: Add an infinite loop in the remote custom Function Module (adding a u201CDO. ENDDO.u201D statement at the start of the FM would be enough).
STEP 2: Execute your program in the CRM system. The execution stops at the RFC call, because of the infinite loop.
STEP 3: Now login to the ECC system and go to transaction SM51 select the process which is executing the RFC and navigate to the menu: u201CProgram/Session->Program->Debuggingu201D this triggers the debugger session in a separate window.
Scenario 2: Calling a Standard RFC FM
When we are debugging a standard program we cannot add the infinite loop, hence we cannot go to SM51 and debug the work process. The RFC destination for the ECC system has a User specified, the RFC function module gets executed using this users credentials. Usually the basis team set up the RFC user as non Dialog user, this does not allow debugging. Contact your Basis team and get this changed to a dialog user enabling you to debug RFC function calls via the normal debugger.
Note: User name configured in the RFC destination (transaction SM59)
Note: User type for the RFC User (transaction SU01D)
Hope this will be helpful..

Gung Ho security team vs Debug with replace in development

Hi fellow developers. I'm trying to talk our security team off the ledge and I want to conduct an informal poll regarding the responsible use of debug with replace in a DEVELOPMENT environment. For the newer developers.. replace is much more powerful in debugging because you can change the values of variables and some system fields like sy-subrc which makes it very powerful.
Our development environment is setup as follows:
Client 300, ABAP Development \config. We promote to QA, and Prod from here but can't unit test because no data allowed. Debug with NO replace allowed here.
Client 320 Unit testing, debug with replace is allowed.
both of these clients are on the same instance, same sid so they share client independent information.
Our security team claims that it's a security risk to allow debug with replace in our Client 300 because someone could change a security profile or something like that. Here's my question...
Are you authorized to debug with replace in your development environment and if not, what's the reason you were given? I'm looking for arguments one way or the other to use as precedent for a meeting.
Your prompt response is appreciated.
Dan

Hi
I think the option can be dangerous in QA or PROD system because you can skip some control and change the data normally can't be changed.
A classicl example is trx SE16: by debug you can change directly the data of the most of tables.
But I don't believe can be a risk in development system, in this enviroment the developer should have no limit, otherwise to work and test can belong very hard.
Max

File 2 RFC scenario debugging

Morning all,
I have a very simple A sync. scenario File to RFC.
To allow debugging of the Interface,my ABAP programmer has created an endless loop.
What's strange is that on SM50 I can track a new Process created by the XI user and after
a few more seconds another session with a new ID appears....
Have you encountered a similar issue before? what is the reason for it then?
Any way, after removing the "debugging loop " everything runs fine.
Points will be awarded for the most reasonable answer....
Nimrod Gisis

Hi,
I do agree , see the below reason and links also
you can see that many dialog work processes are occupied with the program SAPLARFC. You might also see update or batch processes with the status stopped RFC.
This is because in transaction SMQS as many tRFCs were started at the same time as the parameter settings allow and this has resulted in the user contexts losing their rollability. This situation arises for instance when mass data is processed. See SAP note 726148 for more information and possible solutions.
http://help.sap.com/saphelp_nw2004s/helpdata/en/8a/145db7b9c3c64e8af1c0be1dae6f37/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/be/470dc21ca4447b828597f614aaaec1/frameset.htm
regards
Chilla
<i>reward points if it is helpful..</i>

Debug from a Remote Location

I installed the update to Flash 8 that allows for remote
debugging, and I had it all set up and working over the past week
or two. But, all of a sudden it's not working for me anymore. I was
able to access it by right clicking my movie from within the
browser and selecting "Debugger", but for some reason the option
isn't available anymore. I've rechecked my settings according to
the livedocs, and ensured the swd file is in the same dir as the
swf, but no dice... Anyone have an idea on how to bring this back?
or what I could be missing?
Thanks.

Any one help me?
Can you find out why after doing the following the flash debugger is not stopping at break points.
I have my action script in separate .as files (Action Script 3.0).
I have installed flash debugger 10.
The publish settings are set to allow debugging and allow trace statements.
I run the remote debugger for 3.0.
Open my browser (IE8), it asks me to connect to the Localhost which I do.
I can now see the trace statements as I play around with my .swf.
However even though I have set breakpoints in the AS it is not stopping at them.
This is my problem why can I see the trace statements but it doesn’t stop at the breakpoints.
I am using Flash CS4 and the files are being exported as flash 9 with AS3.

HTML tag problem when adding Google rich snippets in templates?

The new Google plus Rich Snippets allow us to add a schema tag like this example:
<html itemscope itemtype="http://schema.org/Article">
I can do this on my .html pages but as soon as I make any changes to the .dwt template for the page it reverts all of the tags back to <html>
How do I stop this happening?
I have tried:
Changing preferences in Dreamweaver's default code rewrite settings to "'Never Rewrite Code' for HTML document type " but this does not appear to fix things.
Very frustrating as I have lost days of work.
Any help would be appreciated
many thanks
Craig

I've done what you have said (I think) however something is not quite right. I am asssuming that I need to add the schema below the <BODY> tag if I make the changes to the template as you have suggested.
This is my practice page which is in a template:
http://www.psychics.co.uk/lovepsychic/index.html
Following the Adobe instruction on the forum: High at the top of the header section we get this code:

For the customised body tag we get this:
<body itemscope itemtype="http://schema.org/Product">
Then on the left column of the page and below the navigation and below the <body> I have added this:

<h1 itemprop="name" content="Love Psychics Readings">Love Psychics - Psychic Love Predictions Online</h1>
<img itemprop="image" content="http://www.psychics.co.uk/images/schema/love.jpg" src="/images/stars.gif" width="160" height="76" alt="Psychics and Mediums Network"></img>
<p itemprop="description" content="Getting a reading with love psychics to find out about relationships, love, romance, marriage and family. Article about our Love psychics readings onlineservices.">Copyright Psychics & Mediums Network - QKE Ltd.</p>

I must be getting close but it just shows the normal Google plus stuff.
I need to get your microdata markup into the body of the document somewhere - otherwise Google will use the something like <title> and <meta description> tags and guess at an image.
Any idea where I am going wrong or is it a quirk in Dreamweaver?

Debugging on Mac - Active Architecture ppc is not present in AE CS4

When I try to debug using XCode, I get the message
"The active architeture ppdc is not present in the executable 'AE CS4' which contains i386."
So how do I configure the build to allow debugging?

I was using CS4 sdk and not being able to debug.
I switched to CS3 SDK as you suggested and found a way to debug.
In the project build properties I changed architectures from"ppc i86" to "32-bit universal".
Now I can debug!
So what architecture should I use for the release version?
(maybe a stupid question, but I'm not a Mac person)

Can I revoke DEBUG Privilege ?

In a database, We have a (customization) schema, say XYZ & Oracle APPS schema. The business logic are processed in XYZ then process (call) to Oracle side using API on XYZ schema, say create Oracle Order.
The XYZ's API will call the package on APPS.
My problem comes when debugging -
When I process the code from XYZ schema, I will be able to see all steps until the program call APPS' package. My guess the APPS has set to not allow debug through its programs. Is there a way to revoke it (so I will be able to see what's happening)? Possible anything to be done from XYZ schema?
Thank you for any idea!

Any one?
Thank you

Are you able to "debug" the default "live" service in FMIS?If

Maybe I'm doing this wrong...
In my: "fms_install / applications / live" folder I've added the Application.xml code to allow debugging:
Looks something like this:
<Application>
<AllowDebugDefault>true</AllowDebug Default>
<AllowHTTPTunnel>true></AllowHTTPTunnel>
<StreamManager>
<VirtualDirectory>

<Streams>/;${LIVE_DIR}</Streams>
</VirtualDirectory>
</StreamManager>
When I load up the FMS admin console though I can't preview the Live video streams. Am I doing something wrong?
( Live streams ARE working correctly.. this is just annoying me that I can't preview them through the admin console. )

Ah HA!
Thanks SE.
That's enabled the debug options in the admin console again.
Unfortunately I am still unable to view the streams.
When I select a stream and hit the "play stream" button the video player is blank and the log spits this out:
"Object encoding error; terminating connection : rtmp://_defaultRoot_/_defaultVHost_/live/streamName"
What's weird is that my client can view the stream correctly.
I've also fired up liveMediaEncoder and broadcasted a test stream to the live app.
( That stream I can preview in the admin console... so whatever this is its limited to my broadcasting web app and the FMS console... +_+ )

Can't see variables when debugging

I'm just moving up from AS2 to AS3, using CS3. After
searching through the help, I'm finding out most of the stuff I
need to debug with, but I can't seem to see the variables in the
variable window.
I've looked through the documentation, and tried touching all
the buttons they say to touch and setting the publish settings to
allow debugging. Nothing seems to be working.
And, unlike AS2, the program seems to start all by itself, it
doesn't wait till I click on the arrow to begin, and I can't get
the step into and step through buttons to not be greyed out.
What am I doing wrong?
Thanks.

Yes, unfortunately it's not too obvious what you have to do,
which is, when the movie is testing, and with Flash (not Flash
Player) in front, go to the Window menu and in the Debug Panels
check the Debug Console and Variables items. It should remember
next time, until you get a Flash crash, in which case those
settings may reset again.
Once you're used to the AS3 debugging, going back to the AS2
one is mildly depressing!

C%23 Codemodule Debuging TestStand2013

Hi,
I have focused that debugging is not working when i am trying to debug "old" codemodules in TS 5.1 (2013) which where build with VS2010SP1 using
.Net Framework lower/equal 3.5
By switching to TS5.0 OR setting .Net Framework to 4.0 debugging is working.
Is there a workaround that allows debugging without modifications ?
Regards
Juergen
=s=i=g=n=a=t=u=r=e= Click on the Star and see what happens :-) =s=i=g=n=a=t=u=r=e=
Solved!
Go to Solution.

All .NET code called by the .NET adapter in TestStand 2013 actually runs in the .NET 4.0 clr even if the assemblies were compiled as supporting .NET 3.5. So you should be able to debug your assemblies by setting the debugger to debug the .NET 4.0 clr. Newer versions of the .NET clr are generally highly backwards compatible with the old version. When a .NET 4.0 app loads a .NET 3.5 assembly that assembly is generally loaded into the .NET 4.0 clr so that it can be called from the .NET 4.0 code which the app is already running.
Hope this helps clarify things. To help you understand the difference between CLR version and framework version see the following:
a) .NET Frameworks 2.0, 3.0, and 3.5 all use the .NET 2.0 CLR. Assemblies compiled against these frameworks can generally also be loaded in the .NET 4.0 CLR (the one exception being C++/CLI assemblies which require an app config file setting to allow them to be loaded in the .NET 4.0 CLR).
b) .NET Frameworks 4.0, 4.5, and 4.5.1 all use the .NET 4.0 CLR.
c) There is only one of each CLR on a machine, so if you have .NET 3.5 installed on your machine you have a .NET 2.0 CLR installed which supports .NET 3.5. Similarly if you have .NET 4.5.1 installed on your machine, you have a .NET 4.0 CLR which supports 4.5.1. So basically .NET Framework 4.5.1 installs over and replaces .NET Framework 4.0.
I know it's a bit confusing. Let me know if you have any questions.
-Doug

How to get the values returned by a function in a drop down?

Hi All,
Can anyone please help in getting the values returned by a function into a drop down? I have a java class file where in i have written a function called getWeeks() which give all the week dates and i want to display these week dates in a drop down box in a JSP page.
Please help me in this regard.
Thanks in Advance!!
Lakshman.

Hi Lakshman,
the following code can help you do what you want :
<hbj:dropdownListBox id="calendar" tooltip="Calendar" selection="<%= selected %>">
<%
String[] weeks = myObjectBean.getWeeks();
for (int i = 0; i < weeks.length; i++) {
%>
<hbj:listBoxItem key="<%= i %>" value="<%= weeks<i> %>"/>
<%
%>
</hbj: dropdownListBox>
The <%= selected %> snippet allows you to pre-select one of the options (provided that the variable 'selected' is equal to one of the listBoxItem keys).
You can also add onSelect to the tag (e.g. = "setSelectedItem"). It corresponds to a method in the corresponding JSPDynPage class. This means that when you select another item in the dropdown list, the method in your Java class is performed (allowing you to save the selected value and performing actions with it)
I hope this helped you enough,
kind regards,
Frederic
Edited seven times by: Frederic Taes on Nov 5, 2008 11:24 AM -> the onSelect element was in the hbj tag and in the text with "='setSelectedItem'" next to it and when I tried to post my message, I got a 501 error all the time ! Seems like a SDN bug to me ...

Error in the standard htmlb.jar from EP6 SP9 (HTMLx)

I've successfully migrated my custom developed applications from EP5 SP5 to EP6 SP9. I've used the well known 3rd party
HTMLxframework for the DatePicker and Locale corrections only (I am a brazilian developer).
In the org.sapportals.htmlb.rendering there is a class named RenderUtil.
This class has two places with this specific code:
ResourceBundle r = ResourceBundle.getBundle("java.text.resources.LocaleElements", locale);
Which is very wrong as the "java.text.resources.LocaleElements" is available only until j2sdk 1.3. In the EP5 that runs under 1.3 there's no problem but EP6 uses j2sdk 1.4 and this packages has been relocated from the standard package to a "ext" (extension) package and been renamed as "sun.text.resources.LocaleElements".
So, as HTMLx uses this RenderUtil class, I had to decompile the original from the htmlb.jar using JAD and corrected the above line with the following new line or code:
ResourceBundle r = ResourceBundle.getBundle("sun.text.resources.LocaleElements", locale);
More than that, I had to change several places of the HTMLx's HxInputFieldRenderer to reflect the class name changes made to the CSSs of the EP6. In the new version SAP does not open a pop-up window for the DatePicker. Instead they chose to rewrite it as a dynamic layer. So the HTMLx code has to change to reflect that.
Here follows the workaround version of HxInputFieldRenderer.java (notice that some strings are not internationalized, I just copied and pasted the parts I needed, so it's not a definitive version, but will help you get a clue of what to do):
* HxInputFieldRenderer.java
* Copyright (C) 2003 Alan Hobbs
* This library is free software; you can redistribute it and/or
* modify it under the terms of the GNU Lesser General Public
* License as published by the Free Software Foundation; either
* version 2.1 of the License, or (at your option) any later version.
* This library is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
* Lesser General Public License for more details.
* You should have received a copy of the GNU Lesser General Public
* License along with this library; if not, write to the Free Software
* Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
package org.open.sapportals.htmlx.rendering;
import javax.servlet.jsp.PageContext;
import org.open.sapportals.htmlx.HxField;
import org.open.sapportals.htmlx.HxInputField;
import org.open.sapportals.htmlx.HxLocaleUtil;
import com.sapportals.htmlb.Component;
import com.sapportals.htmlb.Form;
import com.sapportals.htmlb.InputField;
import com.sapportals.htmlb.enum.DataType;
import com.sapportals.htmlb.enum.InputFieldDesign;
import com.sapportals.htmlb.enum.ResourceType;
import com.sapportals.htmlb.rendering.DefaultInputFieldRenderer;
import com.sapportals.htmlb.rendering.IPageContext;
import com.sapportals.htmlb.type.AbstractDataType;
import com.sapportals.htmlb.type.DataDate;
import com.sapportals.htmlb.type.DataString;
import com.sapportals.htmlb.type.Date;
import com.sapportals.portal.prt.component.IPortalComponentRequest;
import com.sapportals.portal.prt.component.IPortalComponentResponse;
import com.sapportals.portal.prt.logger.ILogger;
import com.sapportals.portal.prt.runtime.PortalRuntime;
import com.sapportals.portal.prt.service.urlgenerator.IUrlGeneratorService;
import com.sapportals.portal.prt.service.urlgenerator.specialized.IPortalUrlGenerator;
import com.sapportals.portal.prt.service.urlgenerator.specialized.ISpecializedUrlGenerator;
* @author Alan.Hobbs
* To change the template for this generated type comment go to
* Window>Preferences>Java>Code Generation>Code and Comments
* Render the HxInputField.
* Version   Date         Author     Description
* 0.1.0     1-Aug-2003   AHobbs     Origional
* 0.1.0     4-Aug-2003   AHobbs     Added resource bundle
* 0.1.1     6-Aug-2003   AHobbs     Write hidden fields to store the locale
* 0.1.1     8-Aug-2003   AHobbs     Don't show the date picker button if the field is disabled
* 0.1.2    10-Aug-2003   AHobbs     Only generate the month and day name javascript once per form
* 1.1.0     1-Apr-2004   AHobbs     Added render methods to allow a HTMLB InputField
*                                   to be used instead of a HxInputField
* 1.1.0     6-Apr-2004   AHobbs     Changed the names for the hidden fields to "_HTMLX_xxxxx"
* 1.1.0    20-Apr-2004   AHobbs     Allow debug code to be written to the console with System.out.println()
* 1.3.0      4-May-2004 AHobbs     Added PopUp rendering
public class HxInputFieldRenderer extends DefaultInputFieldRenderer {
    protected ILogger m_logger = PortalRuntime.getLogger("htmlx");
    private static boolean writingDebugToConsole;
    public HxInputFieldRenderer() {
        super();
    public void render(Component component, IPageContext pc)
        m_logger.info("Entry: HxInputFieldRenderer.render()");
        if (!(component instanceof HxInputField)) {
            m_logger.warning(
                "HxInputFieldRenderer.render() component is not instanceof HxInputField " +
                "(component.getClass().getName()='" + component.getClass().getName() + "')");
            return;
        HxInputField inf = (HxInputField)component;
        DataType type = inf.getType();
        if (writingDebugToConsole) {
            System.out.println("Start    rendering HxInputField (id='" + inf.getId() + "') ...");
        m_logger.info(" id='" + inf.getId() + "'");
        m_logger.info(inf.toString());
/* Only include for PDK version 5.0.5.0 and above - may not be required ???
//        m_logger.info(" VersionInfo.getVersion()='" + VersionInfo.getVersion() + "'");
//      if (VersionInfo.?????) {
//            if (pc.isUsingSession() && !inf.isVisible() && inf.getParkInSession()) {
//                String uniqueName = pc.getParamIdForComponent(inf);
//                Object value = inf.getValue();
//                String valueString = null;
//                if (value != null) {
//                    if (value instanceof AbstractDataType) {
//                        AbstractDataType dataValue = (AbstractDataType)value;
//                        if (dataValue != null)
//                            if (dataValue.isValid())
//                                valueString = dataValue.toString(pc);
//                            else
//                            if (dataValue instanceof DataString)
//                                valueString = dataValue.toString(pc);
//                            else
//                                valueString = dataValue.getValueAsString();
//                    else {
//                        valueString = value.toString();
//                else {
//                    valueString = "";
//                pc.getParamList().put(uniqueName, valueString);
//                return;
        boolean showDateHelp = false;
        if (DataType.DATE.equals(type)
        && inf.isShowHelp()
        && !inf.isDisabled()) {
            showDateHelp = true;
        boolean showPatternHint = false;
        if (inf.isShowPatternHint()
        && (DataType.DATE.equals(type)
        || DataType.TIME.equals(type))
        || ((inf.getPatternHint() != null) && (inf.getPatternHint().length() > 0))) {
            showPatternHint = true;
        boolean showStatusMsg = false;
        if (inf.isShowStatusMsg() && (inf.getStatusMsg() != null) && (inf.getStatusMsg().length() > 0)) {
            showStatusMsg = true;
        if (showDateHelp || showPatternHint || showStatusMsg) {
            pc.write("<table cellspacing="0" cellpadding="0" border="0" id="");
            pc.write(""><tr><td>");
          String uniqueName = pc.getParamIdForComponent(inf);
        if (inf.isVisible()) {
             pc.write("<span id="");
               pc.write(uniqueName);
             pc.write("-r" class="urEdfHelpWhl">");
            if (inf.isPassword())
                pc.write("<input type="password" class="sapEdf");
            else
                pc.write("<input type="text" class="sapEdf");
            if (inf.isInvalid())
                pc.write("i");
            if (inf.isRequired())
                pc.write("Req");
            else
                pc.write("Txt");
            if (inf.isDisabled())
                pc.write("Dsbl");
            else
                pc.write("Enbl");
            if (inf.getDesign() == InputFieldDesign.SMALL)
                pc.write("Sml");
            pc.write("" autocomplete="off");
            int mySize = inf.getSize();
            if (mySize > 0) {
                pc.write("" size="");
                pc.write(mySize);
            int maxlength = inf.getMaxlength();
            if (maxlength > 0) {
                pc.write("" maxlength ="");
                pc.write(maxlength);
            java.lang.String value = inf.getWidth();
            if (value != null && !"".equals(value)) {
                pc.write("" style="width:");
                pc.write(value);
                pc.write(";");
            java.lang.String tooltip = inf.getTooltip();
            if (tooltip != null) {
                pc.write("" title="");
                pc.writeEncoded(tooltip);
               pc.write(" onchange="return htmlbDoEvent(this,'TV','onchange','0','");
               pc.write(uniqueName);
               pc.write("',1,1,'',0);" ");
               pc.write(" onblur="return htmlbDoEvent(this,'TV','onblur','0','");
               pc.write(uniqueName);
               pc.write("',1,1,'',0);" ");
            if(inf.isDisabled())
                pc.write("" readonly="");
        else {
            pc.write("<input type="hidden");
        pc.write("" name="");
        pc.write(uniqueName);
        if (inf.isLabeled()) {
            pc.write("" id="");
            pc.write(uniqueName);
        Object value = inf.getValue();
        pc.write("" value="");
        if (value != null) {
            String valueString = null;
            if (value instanceof AbstractDataType) {
                m_logger.info("-- Abstract Data Type");
                AbstractDataType dataValue = (AbstractDataType)value;
                if (dataValue != null) {
                    m_logger.info("-- dataValue != null");
                    if (dataValue.isValid()) {
                        m_logger.info("-- dataValue.isValid()");
                        if (dataValue instanceof DataDate) {
                            m_logger.info("-- dataValue instanceof DataDate");
                            Date date = ((DataDate)dataValue).getValue();
                            valueString = HxLocaleUtil.formatDate(date, pc.getLocale());
                        else {
                            m_logger.info("-- NOT dataValue instanceof DataDate");
                            valueString = dataValue.toString(pc);
                    else if (dataValue instanceof DataString) {
                        m_logger.info("-- dataValue instanceof DataString");
                        valueString = dataValue.toString(pc);
                    else {
                        m_logger.info("-- dataValue.getValueAsString()");
                        valueString = dataValue.getValueAsString();
            else {
                // Not Abstract Data Type
                m_logger.info("-- Not Abstract Data Type");
                valueString = value.toString();
            pc.writeEncoded(valueString);
        pc.write(""/>");
        if (showDateHelp) {
            String dateFormat = HxLocaleUtil.getSapDatePatternNumber(pc.getLocale());
               pc.write("</td><td align='left'><button id='");
               pc.write(uniqueName);
               pc.write("-btn' type="button" tabindex="-1" ti="-1" class="urEdfHlpDate" onclick="htmlb_showDateHelp(event,'");
               pc.write(uniqueName);
               pc.write("','");
               pc.write(dateFormat);
               pc.write("','1')"></button>");
               pc.write("<script>htmlb_addTexts('pt_BR',{SAPUR_OCTOBER:"Outubro",SAPUR_MSG_LOADING:"Processo de carga em andamento"," +
                    "SAPUR_SUNDAY_ABBREV:"Do",SAPUR_F4FIELD_TUTOR:"Pressionar F4 para exibir as entradas possíveis"," +
                    "SAPUR_INVALID:"Não válido",SAPUR_FEBRUARY:"Fevereiro",SAPUR_F4FIELD:"F4- campo de entrada"," +
                    "SAPUR_FRIDAY_ABBREV:"6ª",SAPUR_WEDNESDAY_ABBREV:"4ª",SAPUR_MAY:"Maio",SAPUR_MSG_WARNING:"Advertência"," +
                    "SAPUR_DECEMBER:"Dezembro",SAPUR_SEPARATOR:"-",SAPUR_MSG_SUCCESS:"Com êxito",SAPUR_SATURDAY_ABBREV:"Sa"," +
                    "SAPUR_THURSDAY_ABBREV:"5ª",SAPUR_MSG:"{0} {1} {2}",SAPUR_BUTTON_WHL:"{0} - {1} - {2} - {3}",SAPUR_JULY:"Julho"," +
                    "SAPUR_APRIL:"Abril",SAPUR_FIELD_TIME:"Hora",SAPUR_MSG_ERROR:"Erro",SAPUR_REQUIRED:"Necessário"," +
                    "SAPUR_BUTTON_WHL3:"{0} - {1} - {2}",SAPUR_SEPTEMBER:"Setembro",SAPUR_NOVEMBER:"Novembro",SAPUR_AUGUST:"Agosto"," +
                    "SAPUR_JANUARY:"Janeiro",SAPUR_BUTTON:"Botão",SAPUR_FIELD_PW:"Senha",SAPUR_FIELD:"Texto editável"," +
                    "SAPUR_DISABLED:"Não disponível",SAPUR_FIELD_DATE:"Data",SAPUR_MARCH:"Março",SAPUR_FIELD_NUMBER:"N°"," +
                    "SAPUR_MSG_STOP:"Stop",SAPUR_BUTTON_WHL4:"{0} - {1} - {2} - {3}"," +
                    "SAPUR_BUTTON_ENABLED:"Para ativar, utilizar a barra de espaço",SAPUR_TUESDAY_ABBREV:"3ª",SAPUR_READOLNY:""," +
                    "SAPUR_MSG_JUMPKEY:"Pressionar a barra de espaço para navegar para o campo correspondente",SAPUR_JUNE:"Junho"," +
                    "SAPUR_MONDAY_ABBREV:"2ª"});</script>");
        if (showPatternHint) {
            String pattern        = "";
            String patternTooltip = "";
            if (DataType.DATE.equals(type)) {
                pattern        = HxLocaleUtil.getDatePatternInLocaleLanguage(pc.getLocale());
                patternTooltip = HxLocaleUtil.formatHxMsg(pc.getLocale(), "HxInputField.DatePatternTooltip", pattern);
            else if (DataType.TIME.equals(type)) {
                pattern        = HxLocaleUtil.getTimePatternInLocaleLanguage(pc.getLocale());
                patternTooltip = HxLocaleUtil.formatHxMsg(pc.getLocale(), "HxInputField.TimePatternTooltip", pattern);
                pattern = " " + pattern;
            else if ((inf.getPatternHint() != null) && (inf.getPatternHint().length() > 0)) {
                pattern = " " + inf.getPatternHint();
                patternTooltip = HxLocaleUtil.formatHxMsg(pc.getLocale(), "HxInputField.PatternTooltip", pattern);
            pc.write("</td><td align='left'>");
            pc.write("<span class='sapTxtLeg' title='" + patternTooltip + "'><nobr>");
            pc.write("<font color='666666' face='Microsoft Sans Serif' style='vertical-align:super' size='1'><b>" + pattern + "</b></font>");
            pc.write("</nobr></span>");
        if (showStatusMsg) {
            if (inf.getStatusMsgPosition().equalsIgnoreCase("RIGHT")) {
                pc.write("</td><td align='left'>");
                pc.write("<font color='990000' face='Microsoft Sans Serif' size='1'>");
            else if (inf.getStatusMsgPosition().equalsIgnoreCase("BELOW")) {
                pc.write("</td></tr><tr>");
                if (showDateHelp && showPatternHint) {
                    pc.write("<td align='left' colspan='3'>");
                else if (showDateHelp ^ showPatternHint) {      // '^' is Exclusive OR (XOR)
                    pc.write("<td align='left' colspan='2'>");
                else {
                    pc.write("<td align='left'>");
                pc.write("<font color='990000' face='Microsoft Sans Serif' style='verticle-align:super' size='1'>");
            pc.write("<nobr>" + inf.getStatusMsg() + "</nobr>");
            pc.write("</font>");
        if (showDateHelp || showPatternHint || showStatusMsg) {
            pc.write("</td></tr></table>");
        // Generate code to store the current Locale in the HTML form,
        // and make the month and day names available in javascript arrays.
        // The form's Language attribute is used as a flag so that this is only
        // done once for each form.
        Form form = pc.getCurrentForm();
        if ((form.getLanguage() == null)
        || (!form.getLanguage().equals(pc.getLocale().toString()))) {
            // Save the locale in the html form as hidden fields so that the
            // same locale can be used to parse returned data.
            pc.write("<input type="hidden" name="_HTMLX_LANGUAGE_" value="" + pc.getLocale().getLanguage() + "">");
            pc.write("<input type="hidden" name="_HTMLX_COUNTRY_" value="" + pc.getLocale().getCountry() + "">");
            pc.write("<input type="hidden" name="_HTMLX_VARIANT_" value="" + pc.getLocale().getVariant() + "">");
            // Write javascript arrays of month and day names in the locale language
            StringBuffer sb = new StringBuffer(250);
            String javaScriptPath = pc.getJavascriptPath();
            sb.append("var javaScriptPath='");
            sb.append(javaScriptPath);
            sb.append("';");
            java.lang.String dayNames[] = RenderUtil.getDayAbbreviations(pc.getLocale());
            if (dayNames.length != 7) {
                throw new IllegalStateException("Only locales with 7 days are supported!");
            sb.append("var htmlbDayNames = new Array('");
            for (int i = 0; i < 6; i++) {
                sb.append(dayNames<i>);
                sb.append("','");
            sb.append(dayNames[6]);
            sb.append("');n");
            sb.append("var htmlbMonthNames = new Array('");
            java.lang.String monthNames[] = RenderUtil.getMonthNames(pc.getLocale());
            for (int i = 0; i < 11; i++) {
                sb.append(monthNames<i>);
                sb.append("','");
            sb.append(monthNames[11]);
            sb.append("');n");
            java.lang.String jscript = sb.toString();
            pc.getDocument().getIncludes().addBodyEndResource(ResourceType.DIRECTJSCRIPT, "HTMLB_INPUTFIELD_DATEHELP", jscript);
            // Set the language in the form so we don't do this again
            form.setLanguage(pc.getLocale().toString());
        if (writingDebugToConsole) {
            System.out.println("Finished rendering HxInputField (id='" + inf.getId() + "')");
        m_logger.info("Exit: HxInputFieldRenderer.render()");
    // Methods to allow the Standard HTMLB InputField to Mimic HxInputField
    // The key idea here is to use the standard InputField ONLY as a String
    // field (never Date) so that we have total control over the display format
    // and then HTMLX looks after ofrmating the string, abd displaying the
    // help icons, status messages etc.
     * Render the HTML placed before a HTMLB InputField, an InputField,
     * and the code placed after the InputFIeld, so that it behaves like a
     * HTMLX HxInputField
     * @param field
     * @param pc
    public static InputField mimicRender(HxField hxField, IPageContext pc) {
        HxInputField hxInputField = new HxInputField(hxField, pc.getLocale());
        return mimicRender(hxInputField, pc);
     * Render the HTML placed before a HTMLB InputField, an InputField,
     * and the code placed after the InputFIeld, so that it behaves like a
     * HTMLX HxInputField
     * @param field
     * @param pc
    public static InputField mimicRender(HxInputField hxInputField, IPageContext pc) {
        // Render stuff before InputField
        renderBeforeInputTag(hxInputField, pc);
        // Render InputField
        InputField inputField = new InputField(hxInputField.getId());
        setUpInputField(hxInputField, inputField, pc);
        // This is a kludge to make a field read only. It is achieved by
        // adding the flag to the 'width' attribute. HTMLB then unknowingly
        // adds the flag when it renders the 'width' attribute.
        if (hxInputField.isReadOnly()) {
            inputField.setWidth( inputField.getWidth() + ";" readonly="");
        inputField.render(pc);
        String uniqueName = pc.getParamIdForComponent(inputField);
        String popUpKeyUniqueName = "";
        // If the field has a Pop Up add a hidden field for the Key populated by the Pop Up
        if (hxInputField.isShowPopUp()) {
            InputField keyInputField = new InputField(hxInputField.getId() + "PopUpKey");
            keyInputField.setVisible(false);
            keyInputField.setValue(hxInputField.getPopUpKeyValue());
            keyInputField.render(pc);
            popUpKeyUniqueName = pc.getParamIdForComponent(keyInputField);
        // Render stuff after InputField
        renderAfterInputTag(hxInputField, pc, uniqueName, popUpKeyUniqueName);
        return inputField;
     * Render the HTML to be placed before a HTMLB InputField so that it
     * behaves like a HTMLX HxInputField
     * @param field
     * @param pc
    public static void renderBeforeInputTag(HxField field, IPageContext pc) {
        renderBeforeInputTag(new HxInputField(field), pc);
     * Render the HTML to be placed before a HTMLB InputField so that it
     * behaves like a HTMLX HxInputField
     * @param inf
     * @param pc
    public static void renderBeforeInputTag(HxInputField inf, IPageContext pc)
        if (writingDebugToConsole) {
            System.out.println("Start    rendering mimic HxInputField (id='" + inf.getId() + "') ...");
        if (showDateHelp(inf) || showPopUp(inf) || showPatternHint(inf) || showStatusMsg(inf)) {
            pc.write("<table cellspacing="0" cellpadding="0" border="0" id="");
            pc.write(""><tr><td>");
     * Set a HMTLB InputField with the values stored in the HxField.
     * This makes for less code in the JSP, and some versions of the PDK/EP
     * do not support some paramters in the TAG (e.g. Tooltip)
     * @param hxField
     * @param myContext
     * @param pageContext
    public static InputField setUpInputField(HxField hxField, IPageContext pc, PageContext pageContext) {
        Component component = (Component)pageContext.getAttribute(hxField.getId());
        if (!(component instanceof InputField)) {
            String msg =
                "HxInputFieldRenderer.setUpInputTag() component is not instanceof InputField " +
                "(hxField.getId()='" + hxField.getId() + "' " +
                " component.getClass().getName()='" + component.getClass().getName() + "')";
            PortalRuntime.getLogger("htmlx").severe(msg);
            throw new IllegalArgumentException(msg);
        InputField inf = (InputField)pageContext.getAttribute(hxField.getId());
        setUpInputField(hxField, inf, pc);
        return inf;
     * Set a HMTLB InputField with the values in the HxField.
     * This makes for less code in the JSP, and some versions of the PDK/EP
     * do not allow you to set some paramters in the TAG (e.g. Tooltip)
     * @param hxField
     * @param myContext
     * @param pageContext
    public static void setUpInputField(HxField hxField, InputField inf, IPageContext pc) {
        inf.setDisabled(hxField.isDisabled());
        inf.setInvalid(hxField.isInvalid());
        inf.setMaxlength(hxField.getMaxLength());
        inf.setRequired(hxField.isRequired());
        inf.setShowHelp(false);
        inf.setTooltip(hxField.getTooltip());
        inf.setType(DataType.STRING);
        inf.setValue(hxField.getValueAsString(pc.getLocale()));
        inf.setVisible(hxField.isVisible());
        inf.setSize(hxField.getMaxLength());
     * Set a HMTLB InputField with the values stored in the HxField.
     * This makes for less code in the JSP, and some versions of the PDK/EP
     * do not support some paramters in the TAG (e.g. Tooltip)
     * @param hxField
     * @param myContext
     * @param pageContext
    public static void setUpInputField(HxInputField hxInputField, InputField inf, IPageContext pc) {
        inf.setDisabled(hxInputField.isDisabled());
        inf.setInvalid(hxInputField.isInvalid());
        inf.setMaxlength(hxInputField.getMaxlength());
        inf.setRequired(hxInputField.isRequired());
        inf.setShowHelp(false);
        inf.setTooltip(hxInputField.getTooltip());
        inf.setType(DataType.STRING);
        inf.setValue(hxInputField.getPreformattedValueAsString());
        inf.setVisible(hxInputField.isVisible());
        inf.setSize(hxInputField.getSize());
     * Render the HTML to be placed after a HTMLB InputField so that it
     * behaves like a HTMLX HxInputField
     * @param field
     * @param myContext
     * @param pageContext
    public static void renderAfterInputTag(HxField field, IPageContext pc, PageContext pageContext) {
        renderAfterInputTag(new HxInputField(field), pc, pageContext);
     * Render the HTML to be placed after a HTMLB InputField so that it
     * behaves like a HTMLX HxInputField
     * @param inf
     * @param myContext
     * @param pageContext
    public static void renderAfterInputTag(HxInputField inf, IPageContext pc, PageContext pageContext) {
        Component component = (Component)pageContext.getAttribute(inf.getId());
        String uniqueName = pc.getParamIdForComponent(component);
        String popUpKeyUniqueName = "";
        if (inf.isShowPopUp()) {
            component = (Component)pageContext.getAttribute(inf.getId() + "PopUpKey");
            popUpKeyUniqueName = pc.getParamIdForComponent(component);
        renderAfterInputTag(inf, pc, uniqueName, popUpKeyUniqueName);
     * Render the HTML to be placed after a HTMLB InputField so that it
     * behaves like a HTMLX HxInputField
     * @param inf
     * @param pc
     * @param uniqueName
     * @param popUpKeyUniqueName
    public static void renderAfterInputTag(
        HxInputField inf,
        IPageContext pc,
        String       uniqueName,
        String       popUpKeyUniqueName)
        if (showDateHelp(inf)) {
            String dateFormat = HxLocaleUtil.getSapDatePatternNumber(pc.getLocale());
            pc.write("</td><td align='left'><button id='");
               pc.write(uniqueName);
               pc.write("-btn' type="button" tabindex="-1" ti="-1" class="urEdfHlpDate" onclick="htmlb_showDateHelp(event,'");
            pc.write(uniqueName);
            pc.write("','");
            pc.write(dateFormat);
            pc.write("','1')"></button>");
               pc.write("<script>htmlb_addTexts('pt_BR',{SAPUR_OCTOBER:"Outubro",SAPUR_MSG_LOADING:"Processo de carga em andamento"," +
                    "SAPUR_SUNDAY_ABBREV:"Do",SAPUR_F4FIELD_TUTOR:"Pressionar F4 para exibir as entradas possíveis"," +
                    "SAPUR_INVALID:"Não válido",SAPUR_FEBRUARY:"Fevereiro",SAPUR_F4FIELD:"F4- campo de entrada"," +
                    "SAPUR_FRIDAY_ABBREV:"6ª",SAPUR_WEDNESDAY_ABBREV:"4ª",SAPUR_MAY:"Maio",SAPUR_MSG_WARNING:"Advertência"," +
                    "SAPUR_DECEMBER:"Dezembro",SAPUR_SEPARATOR:"-",SAPUR_MSG_SUCCESS:"Com êxito",SAPUR_SATURDAY_ABBREV:"Sa"," +
                    "SAPUR_THURSDAY_ABBREV:"5ª",SAPUR_MSG:"{0} {1} {2}",SAPUR_BUTTON_WHL:"{0} - {1} - {2} - {3}",SAPUR_JULY:"Julho"," +
                    "SAPUR_APRIL:"Abril",SAPUR_FIELD_TIME:"Hora",SAPUR_MSG_ERROR:"Erro",SAPUR_REQUIRED:"Necessário"," +
                    "SAPUR_BUTTON_WHL3:"{0} - {1} - {2}",SAPUR_SEPTEMBER:"Setembro",SAPUR_NOVEMBER:"Novembro",SAPUR_AUGUST:"Agosto"," +
                    "SAPUR_JANUARY:"Janeiro",SAPUR_BUTTON:"Botão",SAPUR_FIELD_PW:"Senha",SAPUR_FIELD:"Texto editável"," +
                    "SAPUR_DISABLED:"Não disponível",SAPUR_FIELD_DATE:"Data",SAPUR_MARCH:"Março",SAPUR_FIELD_NUMBER:"N°"," +
                    "SAPUR_MSG_STOP:"Stop",SAPUR_BUTTON_WHL4:"{0} - {1} - {2} - {3}"," +
                    "SAPUR_BUTTON_ENABLED:"Para ativar, utilizar a barra de espaço",SAPUR_TUESDAY_ABBREV:"3ª",SAPUR_READOLNY:""," +
                    "SAPUR_MSG_JUMPKEY:"Pressionar a barra de espaço para navegar para o campo correspondente",SAPUR_JUNE:"Junho"," +
                    "SAPUR_MONDAY_ABBREV:"2ª"});</script>");
        if (showPopUp(inf)) {
            String dateFormat = HxLocaleUtil.getSapDatePatternNumber(pc.getLocale());
            pc.write("</td><td align='left'><div class="urEdfHlpSml" onClick="");
            pc.write("htmlxPopUp('");
            pc.write(getPopUpUrl(pc, inf.getPopUpPage()));
            pc.write("', '");
            pc.write(uniqueName);
            pc.write("', '");
            pc.write(popUpKeyUniqueName);
            pc.write("', ");
            pc.write(inf.getPopUpWidth());
            pc.write(", ");
            pc.write(inf.getPopUpHeight());
            pc.write(", '");
            pc.write(inf.getPopUpAttributes());
            pc.write("')">");
            pc.write(" </div>");
        if (showPatternHint(inf)) {
            String pattern        = "";
            String patternTooltip = "";
            if (DataType.DATE.equals(inf.getType())) {
                pattern        = HxLocaleUtil.getDatePatternInLocaleLanguage(pc.getLocale());
                patternTooltip = HxLocaleUtil.formatHxMsg(pc.getLocale(), "HxInputField.DatePatternTooltip", pattern);
            else if (DataType.TIME.equals(inf.getType())) {
                pattern        = HxLocaleUtil.getTimePatternInLocaleLanguage(pc.getLocale());
                patternTooltip = HxLocaleUtil.formatHxMsg(pc.getLocale(), "HxInputField.TimePatternTooltip", pattern);
                pattern = " " + pattern;
            else if ((inf.getPatternHint() != null) && (inf.getPatternHint().length() > 0)) {
                pattern = " " + inf.getPatternHint();
                patternTooltip = HxLocaleUtil.formatHxMsg(pc.getLocale(), "HxInputField.PatternTooltip", pattern);
            pc.write("</td><td align='left'>");
            pc.write("<span class='sapTxtLeg' title='" + patternTooltip + "'><nobr>");
            pc.write("<font color='666666' face='Microsoft Sans Serif' style='vertical-align:super' size='1'><b>" + pattern + "</b></font>");
            pc.write("</nobr></span>");
        if (showStatusMsg(inf)) {
            if (inf.getStatusMsgPosition().equalsIgnoreCase("RIGHT")) {
                pc.write("</td><td align='left'>");
                pc.write("<font color='990000' face='Microsoft Sans Serif' size='1'>");
            else if (inf.getStatusMsgPosition().equalsIgnoreCase("BELOW")) {
                pc.write("</td></tr><tr>");
                if (showDateHelp(inf) && showPatternHint(inf)) {
                    pc.write("<td align='left' colspan='3'>");
                else if (showDateHelp(inf) ^ showPatternHint(inf)) {      // '^' is Exclusive OR (XOR)
                    pc.write("<td align='left' colspan='2'>");
                else {
                    pc.write("<td align='left'>");
                pc.write("<font color='990000' face='Microsoft Sans Serif' style='verticle-align:super' size='1'>");
            pc.write("<nobr>" + inf.getStatusMsg() + "</nobr>");
            pc.write("</font>");
        if (showDateHelp(inf) || showPopUp(inf) || showPatternHint(inf) || showStatusMsg(inf)) {
            pc.write("</span></td></tr></table>");
        // Generate code to store the current Locale in the HTML form,
        // and make the month and day names available in javascript arrays.
        // The form's Language attribute is used as a flag so that this is only
        // done once for each form.
        Form form = pc.getCurrentForm();
        if ((form.getLanguage() == null)
        || (!form.getLanguage().equals(pc.getLocale().toString()))) {
            // Save the locale in the html form as hidden fields so that the
            // same locale can be used to parse returned data.
            pc.write("<input type="hidden" name="_HTMLX_LANGUAGE_" value="" + pc.getLocale().getLanguage() + "">");
            pc.write("<input type="hidden" name="_HTMLX_COUNTRY_" value="" + pc.getLocale().getCountry() + "">");
            pc.write("<input type="hidden" name="_HTMLX_VARIANT_" value="" + pc.getLocale().getVariant() + "">");
            // Write javascript arrays of month and day names in the locale language
            StringBuffer sb = new StringBuffer(250);
            String javaScriptPath = pc.getJavascriptPath();
            sb.append("var javaScriptPath='");
            sb.append(javaScriptPath);
            sb.append("';");
            java.lang.String dayNames[] = RenderUtil.getDayAbbreviations(pc.getLocale());
            if (dayNames.length != 7) {
                throw new IllegalStateException("Only locales with 7 days are supported!");
            sb.append("var htmlbDayNames = new Array('");
            for (int i = 0; i < 6; i++) {
                sb.append(dayNames<i>);
                sb.append("','");
            sb.append(dayNames[6]);
            sb.append("');n");
            sb.append("var htmlbMonthNames = new Array('");
            java.lang.String monthNames[] = RenderUtil.getMonthNames(pc.getLocale());
            for (int i = 0; i < 11; i++) {
                sb.append(monthNames<i>);
                sb.append("','");
            sb.append(monthNames[11]);
            sb.append("');n");
            String jscript = sb.toString();
            pc.getDocument().getIncludes().addBodyEndResource(ResourceType.DIRECTJSCRIPT, "HTMLB_INPUTFIELD_DATEHELP", jscript);
            pc.getDocument().getIncludes().addBodyEndResource(ResourceType.DIRECTJSCRIPT, "HTMLX", getHtmlxJavascript());
            // Set the language in the form so we don't do this again
            form.setLanguage(pc.getLocale().toString());
        if (writingDebugToConsole) {
            System.out.println("Finished rendering mimic HxInputField (id='" + inf.getId() + "')");
    private static boolean showDateHelp(HxInputField inf) {
        if (DataType.DATE.equals(inf.getType())
        && inf.isShowHelp()
        && !inf.isDisabled()) {
            return true;
        return false;
    private static boolean showPopUp(HxInputField inf) {
        if (!showDateHelp(inf)
        && !inf.isDisabled()
        && inf.isShowPopUp()) {
            return true;
        return false;
    private static boolean showPatternHint(HxInputField inf) {
        boolean isDateOrTime = DataType.DATE.equals(inf.getType()) || DataType.TIME.equals(inf.getType());
        boolean patternHintSet = (inf.getPatternHint() != null) && (inf.getPatternHint().length() > 0);
        if (inf.isShowPatternHint()
        && (isDateOrTime || patternHintSet)) {
            return true;
        return false;
    private static boolean showStatusMsg(HxInputField inf) {
        if (inf.isShowStatusMsg()
        && (inf.getStatusMsg() != null)
        && (inf.getStatusMsg().length() > 0)) {
            return true;
        return false;
    private static String getPopUpUrl(IPageContext pc, String pageName) {
        IPortalComponentRequest request = (IPortalComponentRequest)pc.getRequest();
        IPortalComponentResponse response = (IPortalComponentResponse)pc.getResponse();
        IPortalUrlGenerator portalGen = null;
        IUrlGeneratorService urlGen = (IUrlGeneratorService)request.getService(IUrlGeneratorService.KEY);
        ISpecializedUrlGenerator specUrlGen2 = urlGen.getSpecializedUrlGenerator(IPortalUrlGenerator.KEY);
        if (specUrlGen2 instanceof IPortalUrlGenerator) {
            portalGen = (IPortalUrlGenerator) specUrlGen2;
        // Create the url to the iView
        String url = "";
        if (portalGen != null) {
            // Create the parameters passed to SAP transaction for mesima
            url = portalGen.generatePortalComponentUrl(request, pageName); // "htmlxJarMimicExample.default");
        return url;
    protected static String getHtmlxJavascript() {
        return "n" +
        "    if(window.document.domain == window.location.hostname) {                         n" +
        "        document.domain = document.domain.substring(document.domain.indexOf('.')+1); n" +
        "    }                                                                                n" +
        "    var popUpTextId;                                                                 n" +
        "    var popUpKeyId;                                                                  n" +
        "    var myPopUp;                                                                     n" +
        "    function setTextField(text) {                                                    n" +
        "        field = document.getElementById(popUpTextId);                                n" +
        "        if (field) {                                                                 n" +
        "            field.value = text;                                                      n" +
        "        }                                                                            n" +
        "        else {                                                                       n" +
        "            alert('Text target field for pop up not found (' + popUpTextId + ')');   n" +
        "        }                                                                            n" +
        "    }                                                                                n" +
        "    function setKeyField(key) {                                                      n" +
        "        field = document.getElementById(popUpKeyId);                                 n" +
        "        if (field) {                                                                 n" +
        "            field.value = key;                                                       n" +
        "        }                                                                            n" +
        "    }                                                                                n" +
        "    function setFields(text, key, close) {                                           n" +
        "        setTextField(text);                                                          n" +
        "        setKeyField(key);                                                            n" +
        "        if (close) {                                                                 n" +
        "            myPopUp.close();                                                         n" +
        "        }                                                                            n" +
        "        return false;                                                                n" +
        "    }                                                                                n" +
        "    function htmlxPopUp(url, textId, keyId, width, height, attributes) {                  n" +
        "        popUpTextId = textId;                                                        n" +
        "        popUpKeyId = keyId;                                                          n" +
        "        if (myPopUp) {                                                               n" +
        "            myPopUp.close();                                                         n" +
        "        }                                                                            n" +
        "        if (event!=null){                                                            n" +
        "            xPos = event.screenX-event.offsetX;                                      n" +
        "            yPos = event.screenY-event.offsetY;                                      n" +
        "        }                                                                            n" +
        "        if ((xPos+width) > screen.availWidth) {                                      n" +
        "            xPos=screen.availWidth - width - 10;                                     n" +
        "        }                                                                            n" +
        "        if ((yPos+height) > screen.availHeight) {                                    n" +
        "            yPos=screen.availHeight - height - 10;                                   n" +
        "        }                                                                            n" +
        "        sizeAndPos = 'width=' + width + ', height=' + height + ', top=' + yPos + ', left=' + xPos;      n" +
        "        myPopUp = window.open(url, 'PopUp', sizeAndPos + ', ' + attributes); n" +
        "        if (!myPopUp) {                                                              n" +
        "            alert('You may have unrequested popup blocking on.');                    n" +
        "        }                                                                            n" +
        "    }n";
    // Methods to assist dubugging JSP pages
     * @return True if debug messages are being written to the console
    public static boolean isWritingDebugToConsole() {
        return writingDebugToConsole;
     * When an error occurs in a JSP page the line number given in the stack
     * trace is rarely the line that caused the error. This can make traking
     * down errors in a JSP page can be very difficult. By writing debug messages
     * to the console every time a field is rendered, it can be much easier to
     * identify the area of code causing a problem.<p>
     * <b>Do NOT set this in the production release of your application.</b>
     * @param b
    public static void setWritingDebugToConsole(boolean b) {
        writingDebugToConsole = b;
     * Initialise to NOT write debug to the console
    static {
        writingDebugToConsole = false;

Try these
[http://help.sap.com/saphelp_nwmobile71/helpdata/en/45/65ad4ee0531aa8e10000000a114a6b/content.htm]
[http://help.sap.com/saphelp_nw04/helpdata/en/6f/1bd5c6a85b11d6b28500508b5d5211/content.htm]
[http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc01381.0120/doc/html/koh1278435126915.html]
Reagards,
Mouli

Snippet (allow debugging ... comportement ??)

Similar Messages

Maybe you are looking for