ReadOnly property for MDM Standard components

Hi,
I am using Standard MDM Webdypro component for Item details.
I am able to change the readonly property for text fields by using..
wdThis.ItemDetailComp.setFieldProperty("FLD_CODE", FieldLayoutProperty.READ_ONLY, true);
but this line of code it working for date fields, fields with lookup popup, integer fields.
Please let me know how to make date fields, fields with lookup popup, integer fields read only through coding.,
Akshay

setFieldProperty method is the only such available in item details ...
check this ...
http://help.sap.com/saphelp_nwmdm71/helpdata/en/4c/031f9ac2130da0e10000000a42189e/content.htm
strange why its not happening for the other field types !
thanks
-Adrivit

Similar Messages

  • WebDynpro for Java: Standard Components for SM02 en rrMX?

    Hi,
    Are there standard Components WebDynpro for Java for the transaction codes SM02(SM02_READ_MESSAGES) and RRMX(?)?
    Which Business Package do i have to use?
    Kind regards,
    Joris Meeuwsen

    Hi Hussain
    1)Log into  <b>SDM</b>
    2) Goto Undeployment tab and select your project to undeploy and select START
    3)Restart the server
    4) Deploy your application once again
    Best Regards
    Chaitanya.A

  • How to implement expand/collapse property for custome components

    can any one tell me how to implement the expand/collapse
    property for the custom components in flex. i need something like
    hierarchy of custom components which on the expand should be able
    to show the children of the corresponding component and a line
    linking between them and collapsing property too.. can any one help
    me out..

    "hanu106" <[email protected]> wrote in
    message
    news:gfr2co$biq$[email protected]..
    > can any one tell me how to implement the expand/collapse
    property for the
    > custom components in flex. i need something like
    hierarchy of custom
    > components
    > which on the expand should be able to show the children
    of the
    > corresponding
    > component and a line linking between them and collapsing
    property too..
    > can any
    > one help me out..
    Tree?
    AdvancedDataGrid?
    Nested Acordions

  • Is there MDM Webdynpro ABAP standards components?

    Are there standard MDM Webdynpro ABAP standard components available.
    We are planning to integrate MDM Webdynpro ABAP component with BPM.

    Hi George,
    I think there are no MDM Webdynpro ABAP standard components available. But I think it is a good idea to go with MDM Web Dynpro Java Components, as BPM is java based just as the other tools in the Composition Environment and fully compatible with Java. There are many articles and documents available online.
    This link maybe helpful for BPM and Web Dynpro for Java Integration
    http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b06c49b2-ac63-2c10-3d8d-d17b817ba4ca?QuickLink=index&overridelayout=true
    Regards
    Goutham Kanithi

  • How to preview standard MDM Webdynpro Components ?

    Hi
    As we know, we can create standard MDM Webdynpro components from CE 7.1 SP 04 onwards.
    Suppose I have created a project using MDM WD configurator and added a search component, a resultset component and an itemdetails component. We can preview the individual components using the preview button provided in the configurator. But in order to see the consolidated project containing all the 3 components, we need to embed them as used components in a custom WD component. Then through the custom WD component we can preview the 3 standard components.
    My question is, is there any way in which we an preview all the 3 standard MDM WD components together without putting them in a custom WD component ?
    Is there a way we can directly assign an iview to a project created with MDM WD configurator ?
    Thanks
    Sayan Ghosh

    Found the sloution. Can be launched in the browser with the following url giving the component details :
    http://<hostName>:<portNumber>/webdynpro/dispatcher/sap.com/tcmdmwdcompsmasterwd/MASTER?proj=<Project_Name>&rs=<ResultSet_Name>&s=<Search_Name>id=<ItemDetails_Name>

  • Standard iViews for MDM accessible only to SuperAdmin

    Hi,
    We are using the standard iViews available for MDM. They work fine for the administrator. But if I assign them to a normal user, they don't work, inspite of performing the necessary user mapping to the MDM business system. The only way I can get them to work is by assigning the SuperAdmin role to the normal user. Any suggestion?
    Also, the error displayed is, <B>An error occurred. See log for details.</B> Where can I see find this error log in EP?
    Regards,
    Harsh
    PS: We are using MDM 5.5 and EP 6.0.

    In EP version 12 permission for the System objects assigns only super admin user.
    You must set the permissions for every user to be at least have read access.

  • Where do I find standard IViews for MDM

    In MDM SP03 there are available a set of standard iViews for MDM. I am not able to find them on SDN. Can someone tell me where to find them?
    Regards John-Kjell

    Hi,
    if you upload the following files then you will get a tabstrip in the administrator login called MDM in which you can find the standard iviews.
    upload
    com.sap.mdm.tech.mdm4j.sda
    com.sap.mdm.tech.connector.sda
    com.sap.pct.mdm.appl.masteriviews.par
    com.sap.pct.mdm.tech.system.par
    com.sap.pct.mdm.tech.wizards.par
    these files will be in the MDM installation CD.

  • No records in UWL for mdm

    Hi all,
    I have a problem with the UWL for MDM, no records are displayed. I have configured things after all the guides and articles found here on SDN and all connection tests are fine, data is displayed in the iVews. (for Vendors). There are tasks in the MDM system. I have restarted the portal server and all services, cleared the cache etc but without any luck..
    Any ideas?
    Cheers,
    Max

    Hi,
    Looks like this:
    <?xml version="1.0" encoding="utf-8"?>
    <!DOCTYPE UWLConfiguration PUBLIC '-//SAP//UWL1.0//EN' 'uwl_configuration.dtd'>
    <UWLConfiguration version="1.0">
         <ItemTypes>
              <ItemType name="uwl.completedtask.mdm.all.SAP_MDM_Repository_Vendors.Vendors" connector="MdmUwlConnector" defaultView="MdmWorkItemsCompletedView" defaultAction="showMdmDetails" executionMode="default">
                   <Actions>
                        <Action name="showMdmDetails" groupAction="no" handler="IViewLauncher" returnToDetailViewAllowed="yes" launchInNewWindow="yes">
                             <Properties>
                                  <Property name="taskId" value="${item.jobId}"/>
                                  <Property name="stepId" value="${item.stepId}"/>
                                  <Property name="userId" value="${item.userNames}"/>
                                  <Property name="workflowTable" value="${item.workflowTable}"/>
                                  <Property name="externalRequestEvent" value="com.sap.pct.mdm.appl.masteriviews.events.externals.ViewTaskRecordsHandler"/>
                                  <Property name="iview" value="pcd:portal_content/net.xx.semc/net.xx.MDM/net.xx.Pages/com.sap.pct.mdm.appl.vendors.search"/>
                             </Properties>
                             <Descriptions default="Show Record Details"/>
                        </Action>
                        <Action name="showHistory" handler="IViewLauncher" launchInNewWindow="yes" launchNewWindowFeatures="width=557,height=560,resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no">
                             <Properties>
                                  <Property name="jobId" value="${item.jobId}"/>
                                  <Property name="workflowTable" value="${item.workflowTable}"/>
                                  <Property name="stepId" value="${item.stepId}"/>
                                  <Property name="userId" value="${item.userNames}"/>
                                  <Property name="systemId" value="${item.systemId}"/>
                                  <Property name="iview" value="pcd:portal_content/com.sap.pct/specialist/com.sap.pct.mdm.appl.mdm_550/com.sap.pct.mdm.appl.iviews/com.sap.pct.mdm.appl.workflow.taskhistory"/>
                             </Properties>
                             <Descriptions default="History"/>
                        </Action>
                        <Action name="createJob" handler="IViewLauncher" launchInNewWindow="yes" launchNewWindowFeatures="width=557,height=560,resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no">
                             <Properties>
                                  <Property name="iview" value="pcd:portal_content/com.sap.pct/specialist/com.sap.pct.mdm.appl.mdm_550/com.sap.pct.mdm.appl.iviews/com.sap.pct.mdm.appl.workflow.createjob"/>
                             </Properties>
                             <Descriptions default="Create Job"/>
                        </Action>
                   </Actions>
              </ItemType>
              <ItemType name="uwl.task.mdm.jobs.SAP_MDM_Repository_Vendors.Vendors" connector="MdmUwlConnector" defaultView="MdmViewJobs" defaultAction="showMdmDetails" executionMode="default">
                   <Actions>
                        <Action name="createJob" handler="IViewLauncher" launchInNewWindow="yes" launchNewWindowFeatures="width=557,height=560,resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no">
                             <Properties>
                                  <Property name="iview" value="pcd:portal_content/com.sap.pct/specialist/com.sap.pct.mdm.appl.mdm_550/com.sap.pct.mdm.appl.iviews/com.sap.pct.mdm.appl.workflow.createjob"/>
                             </Properties>
                             <Descriptions default="Create Job"/>
                        </Action>
                   </Actions>
              </ItemType>
              <ItemType name="uwl.task.mdm.tasks.SAP_MDM_Repository_Vendors.Vendors" connector="MdmUwlConnector" defaultView="MdmViewTasks" defaultAction="showMdmDetails" executionMode="default">
                   <Actions>
                        <Action name="showMdmDetails" groupAction="no" handler="IViewLauncher" returnToDetailViewAllowed="yes" launchInNewWindow="yes">
                             <Properties>
                                  <Property name="taskId" value="${item.jobId}"/>
                                  <Property name="stepId" value="${item.stepId}"/>
                                  <Property name="userId" value="${item.userNames}"/>
                                  <Property name="workflowTable" value="${item.workflowTable}"/>
                                  <Property name="externalRequestEvent" value="com.sap.pct.mdm.appl.masteriviews.events.externals.ViewTaskRecordsHandler"/>
                                  <Property name="iview" value="pcd:portal_content/net.xx.semc/net.xx.MDM/net.xx.Pages/com.sap.pct.mdm.appl.vendors.search"/>
                             </Properties>
                             <Descriptions default="Show Record Details"/>
                        </Action>
                        <Action name="showHistory" handler="IViewLauncher" launchInNewWindow="yes" launchNewWindowFeatures="width=557,height=560,resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no">
                             <Properties>
                                  <Property name="jobId" value="${item.jobId}"/>
                                  <Property name="workflowTable" value="${item.workflowTable}"/>
                                  <Property name="stepId" value="${item.stepId}"/>
                                  <Property name="userId" value="${item.userNames}"/>
                                  <Property name="systemId" value="${item.systemId}"/>
                                  <Property name="iview" value="pcd:portal_content/com.sap.pct/specialist/com.sap.pct.mdm.appl.mdm_550/com.sap.pct.mdm.appl.iviews/com.sap.pct.mdm.appl.workflow.taskhistory"/>
                             </Properties>
                             <Descriptions default="History"/>
                        </Action>
                        <Action name="createJob" handler="IViewLauncher" launchInNewWindow="yes" launchNewWindowFeatures="width=557,height=560,resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no">
                             <Properties>
                                  <Property name="iview" value="pcd:portal_content/com.sap.pct/specialist/com.sap.pct.mdm.appl.mdm_550/com.sap.pct.mdm.appl.iviews/com.sap.pct.mdm.appl.workflow.createjob"/>
                             </Properties>
                             <Descriptions default="Create Job"/>
                        </Action>
                   </Actions>
              </ItemType>
         </ItemTypes>
           <Views>
        <View name="MdmViewJobs" selectionMode="SINGLESELECT" width="98%" supportedItemTypes="uwl.task.mdm.jobs" columnOrder="mdmStatus, priority, subject, jobId, userNames, dueDate, creatorId, createdDate" sortby="priority:descend, dueDate:ascend, createdDate:descend" tableDesign="STANDARD" visibleRowCount="10" headerVisible="yes" queryRange="undefined" tableNavigationFooterVisible="yes" tableNavigationType="CUSTOMNAV" actionRef="" refresh="300" dueDateSevere="86400000" dueDateWarning="259200000" emphasizedItems="unread" displayOnlyDefinedAttributes="yes" dynamicCreationAllowed="yes" actionPosition="top">
          <Descriptions default="My Open MDM Jobs"/>
          <DisplayAttributes>
            <DisplayAttribute name="workflowTable" type="string" width="10" sortable="yes" format="default" hAlign="LEFT" vAlign="BASELINE" maxTextWidth="0" headerVisible="yes">
              <Descriptions default="Workflow Table">
                <ShortDescriptions>
                  <Description Language="en" Description="Workflow Table"/>
                </ShortDescriptions>
              </Descriptions>
            </DisplayAttribute>
            <DisplayAttribute name="userNames" type="string" width="10" sortable="yes" format="default" hAlign="LEFT" vAlign="BASELINE" maxTextWidth="0" headerVisible="yes">
              <Descriptions default="User Names">
                <ShortDescriptions>
                  <Description Language="en" Description="User Names"/>
                </ShortDescriptions>
              </Descriptions>
            </DisplayAttribute>
            <DisplayAttribute name="mdmStatus" type="string" width="10" sortable="yes" format="default" hAlign="LEFT" vAlign="BASELINE" maxTextWidth="0" headerVisible="yes">
              <Descriptions default="MDM Status">
                <ShortDescriptions>
                  <Description Language="en" Description="MDM Status"/>
                </ShortDescriptions>
              </Descriptions>
            </DisplayAttribute>
            <DisplayAttribute name="jobId" type="string" width="10" sortable="yes" format="default" hAlign="LEFT" vAlign="BASELINE" maxTextWidth="0" headerVisible="yes">
              <Descriptions default="Job ID">
                <ShortDescriptions>
                  <Description Language="en" Description="Job ID"/>
                </ShortDescriptions>
              </Descriptions>
            </DisplayAttribute>
          </DisplayAttributes>
          <Actions>
            <Action reference="refresh"/>
            <Action reference="defaultGlobalWizard"/>
            <Action reference="addToNavigation"/>
            <Action reference="removeFromNavigation"/>
            <Action reference="personalize"/>
          </Actions>
        </View>
        <View name="MdmViewTasks" selectionMode="SINGLESELECT" width="98%" supportedItemTypes="uwl.task.mdm.tasks" columnOrder="mdmStatus, priority, subject, jobId, userNames, dueDate, creatorId, createdDate" sortby="priority:descend, dueDate:ascend, createdDate:descend" tableDesign="STANDARD" visibleRowCount="10" headerVisible="yes" queryRange="undefined" tableNavigationFooterVisible="yes" tableNavigationType="CUSTOMNAV" actionRef="" refresh="300" dueDateSevere="86400000" dueDateWarning="259200000" emphasizedItems="unread" displayOnlyDefinedAttributes="yes" dynamicCreationAllowed="yes" actionPosition="top">
          <Descriptions default="My Open MDM Tasks"/>
          <DisplayAttributes>
            <DisplayAttribute name="workflowTable" type="string" width="10" sortable="yes" format="default" hAlign="LEFT" vAlign="BASELINE" maxTextWidth="0" headerVisible="yes">
              <Descriptions default="Workflow Table">
                <ShortDescriptions>
                  <Description Language="en" Description="Workflow Table"/>
                </ShortDescriptions>
              </Descriptions>
            </DisplayAttribute>
            <DisplayAttribute name="userNames" type="string" width="10" sortable="yes" format="default" hAlign="LEFT" vAlign="BASELINE" maxTextWidth="0" headerVisible="yes">
              <Descriptions default="User Names">
                <ShortDescriptions>
                  <Description Language="en" Description="User Names"/>
                </ShortDescriptions>
              </Descriptions>
            </DisplayAttribute>
            <DisplayAttribute name="mdmStatus" type="string" width="10" sortable="yes" format="default" hAlign="LEFT" vAlign="BASELINE" maxTextWidth="0" headerVisible="yes">
              <Descriptions default="MDM Status">
                <ShortDescriptions>
                  <Description Language="en" Description="MDM Status"/>
                </ShortDescriptions>
              </Descriptions>
            </DisplayAttribute>
            <DisplayAttribute name="stepId" type="string" width="10" sortable="yes" format="default" hAlign="LEFT" vAlign="BASELINE" maxTextWidth="0" headerVisible="yes">
              <Descriptions default="Step ID">
                <ShortDescriptions>
                  <Description Language="en" Description="Step ID"/>
                </ShortDescriptions>
              </Descriptions>
            </DisplayAttribute>
            <DisplayAttribute name="jobId" type="string" width="10" sortable="yes" format="default" hAlign="LEFT" vAlign="BASELINE" maxTextWidth="0" headerVisible="yes">
              <Descriptions default="Job ID">
                <ShortDescriptions>
                  <Description Language="en" Description="Job ID"/>
                </ShortDescriptions>
              </Descriptions>
            </DisplayAttribute>
            <DisplayAttribute name="stepName" type="string" width="10" sortable="yes" format="default" hAlign="LEFT" vAlign="BASELINE" maxTextWidth="0" headerVisible="yes">
              <Descriptions default="Step Name">
                <ShortDescriptions>
                  <Description Language="en" Description="Step Name"/>
                </ShortDescriptions>
              </Descriptions>
            </DisplayAttribute>
          </DisplayAttributes>
          <Actions>
            <Action reference="refresh"/>
            <Action reference="defaultGlobalWizard"/>
            <Action reference="addToNavigation"/>
            <Action reference="removeFromNavigation"/>
            <Action reference="personalize"/>
          </Actions>
        </View>
        <View name="MdmWorkItemsCompletedView" selectionMode="SINGLESELECT" width="98%" supportedItemTypes="uwl.completedtask.mdm.all" columnOrder="subject, jobId, userNames, creatorId, createdDate, status" sortby="creatorId:ascend, createdDate:descend" tableDesign="STANDARD" visibleRowCount="10" headerVisible="yes" queryRange="undefined" tableNavigationFooterVisible="yes" tableNavigationType="CUSTOMNAV" actionRef="" refresh="-1" dueDateSevere="0" dueDateWarning="0" emphasizedItems="unread" displayOnlyDefinedAttributes="yes" dynamicCreationAllowed="yes" actionPosition="top">
          <Descriptions default="Completed MDM Tasks"/>
          <DisplayAttributes>
            <DisplayAttribute name="workflowTable" type="string" width="10" sortable="yes" format="default" hAlign="LEFT" vAlign="BASELINE" maxTextWidth="0" headerVisible="yes">
              <Descriptions default="Workflow Table">
                <ShortDescriptions>
                  <Description Language="en" Description="Workflow Table"/>
                </ShortDescriptions>
              </Descriptions>
            </DisplayAttribute>
            <DisplayAttribute name="userNames" type="string" width="10" sortable="yes" format="default" hAlign="LEFT" vAlign="BASELINE" maxTextWidth="0" headerVisible="yes">
              <Descriptions default="User Names">
                <ShortDescriptions>
                  <Description Language="en" Description="User Names"/>
                </ShortDescriptions>
              </Descriptions>
            </DisplayAttribute>
            <DisplayAttribute name="jobId" type="string" width="10" sortable="yes" format="default" hAlign="LEFT" vAlign="BASELINE" maxTextWidth="0" headerVisible="yes">
              <Descriptions default="Step Name">
                <ShortDescriptions>
                  <Description Language="en" Description="Job ID"/>
                </ShortDescriptions>
              </Descriptions>
            </DisplayAttribute>
          </DisplayAttributes>
          <Actions>
            <Action reference="refresh"/>
            <Action reference="defaultGlobalWizard"/>
            <Action reference="addToNavigation"/>
            <Action reference="removeFromNavigation"/>
            <Action reference="personalize"/>
          </Actions>
        </View>
      </Views>
    </UWLConfiguration>

  • To Change the Readonly Property

    Hi,
    In Portal  Personal data Screen for belgium , Country of Birth field (Drop Down Box) is  Read Only.
    We have to change the readonly property.
    I tried through iView personalisation ,the property of that field is Not readonly.
    2) In the WD java Application  the field property is  NORMAL .
    3) I have checked in V_T588MPROPC, there also we dont have any entry for this field.
    In Backend ECC this field is editable ,
    Can any one please let me know where should i will change to make this field as Editable.
    Regards
    Alexi

    Please check the following tables:
    V_T005
    V_T588MFPROPC
    V_T588MFPROPS
    T77WWW_SC
    V_T582ITVCHCK
    Note 1498555 - How to make a field mandatory or optional in ESS
    "V_T588MFPROPC only makes the field mandatory, optional or unused
    by the back-end business logic checks it will not change a
    UI display property like Read-Only
    You could try the Personalization options - Ctrl and Right
    mouse button over the UI element (either in the browser
    or in a PCD preview - for global changes for all users)
    - please check there for options to change the country
    field to editable
    However I suspect the field is read-only because
    1) You are on a lower release than EHP3 -foreign address
    maintainence via Country field is only available
    as standard from EHP3
    2) You do no have EHP3 business function HCM_ESS_CI_1 switched on
    these business functions activate foreign address functionality
    3) You are editing a record - try instead creating a new record
    4) Inconsistency in V_T7XSSPERFORADD - check this against client 000
    Hope this helps identify the problem

  • How to create F4 for the standard transaction

    Hi all ,
    How to create F4 for the standard transaction for a particular field .
    Bye

    Santosh,
        You can create F4 values for a field in a standard Transaction .
    1. First search for a standard search help meeting your requirement .
    2. If you don't find one, create your own custom (z) serach help .
    ( 1 is preferable )
    After that, include that serch help to the standard field in the transaction .
    For this u need to go to the screen
    ( F1->F9-> screen-> Field )
    Click on the property of the field and include the search help .
    You ll require the access key from the basisi guys as u r changing standard .
    Hope it helps,
    ~ laxmi
    Reward for helpful answers

  • Actual Values for the Cost Components in COPA - TC - KE4R

    Hi,
    In TC: KE4R, we are maintaining the value field for each Cost Components from the Cost Components Structure.
    And the Point of Valuation is 01.
    My understanding is that, when we use this value fields in the COPA report, it will show the value of the standard cost estimate from the cost component structure and not the actual cost that has incurred during the transaction.
    Am I correct? If not please correct me.
    If yes, then How can I get the actual cost for these cost component structure in the value fields.
    Please help.
    Thanks and regards
    Kami

    Hi Ajay,
    we have a requirement that we need details about what makes cost of sales numbers in COPA.
    i know the our VPRS value is flowing into COPA as COGS but now we want that we should have ite detailed breakdown as per cost components.
    can you please tell me detailed configuration steps to make this happen so that we can create a new COPA ke30 report which gives us the breakdown of the COGS numbers.
    one more requirement is that for purchase parts our client is maintaing price PB00 condition and some other conditions like brokerage, freight etc in the info record for those materials and they want that all these conditions value should add up to show the COGS value for these purchase parts in the COPA report.. how do we do that?
    please reply soon...
    Thanks in advance,
    Gurjit

  • How does the JFileChooser "readOnly" property work?

    The "normal" behaviour for a file chooser usiing the UIManager "FileChooser.readOnly" default value of Boolean.FALSE is:
    1) A "New Folder" button is displayed
    2) When a File in the list is selected you can use the F2 key to rename the file
    3) Or, if you click on an already selected file you will also be able to rename the file
    When you use:
    UIManager.put("FileChooser.readOnly", Boolean.TRUE);then the behaviour changes:
    1) The "New Folder" button is not displayed
    2) You can't rename the file by using F2
    3) You can't rename the file by clicking on a selected file
    I am curious how the "readOnly" property works?
    Looking through the source code of BasicFileChooserUI and MetalFileChooserUI it was easy to see that the "New Folder" button is not created when the "readOnly" property is true.
    However, I can't figure out how "file name editing" works. Using Key Bindings I was able to find the binding between the F2 key and an Action named "editFileName". However, I can't find where this Action is actually created in the UI. I also can't figure out how clicking on a selected file name invokes this Action.
    Does anybody know how to prevent the mouse click from allowing editing of the file name? Does anybody know where the "editFileName" Action is created and how this Action gets invoked by a mouse click?
    This is only a curiosity question. Just when I think I understand Actions and Key Bindings I find something like this that I don't understand.
    The following SSCCE shows:
    1) the normal behaviour of a file chooser
    2) the "readOnly" behaviour of a file chooser
    3) my attempt to simulate the "readOnly" behaviour of a file chooser. It works except a mouse click still allows editing of the file name.
    import java.awt.*;
    import java.beans.*;
    import java.awt.event.*;
    import javax.swing.*;
    public class FileChooserSSCCE extends JPanel
        public FileChooserSSCCE()
            //  Demonstrate default file chooser functionality
            JButton normal = new JButton("Normal");
            normal.addActionListener( new ActionListener()
                public void actionPerformed(ActionEvent e)
                    UIManager.put("FileChooser.readOnly", Boolean.FALSE);
                    JFileChooser fc = new JFileChooser(".");
                    fc.showSaveDialog(null);
            add( normal );
            //  Demonstrate "read only" property
            JButton readOnly = new JButton("Read Only");
            readOnly.addActionListener( new ActionListener()
                public void actionPerformed(ActionEvent e)
                    UIManager.put("FileChooser.readOnly", Boolean.TRUE);
                    JFileChooser fc = new JFileChooser(".");
                    fc.showSaveDialog(null);
            add( readOnly );
            //  Simulate "read only" property
            JButton simulate = new JButton("Simulate Read Only");
            simulate.addActionListener( new ActionListener()
                public void actionPerformed(ActionEvent e)
                    UIManager.put("FileChooser.readOnly", Boolean.FALSE);
                    JFileChooser fc = new JFileChooser(".");
                    ActionMap am = fc.getActionMap();
                    //  Disable the New Folder action. The action gets re-enabled every time
                    //  a new directory is selected so we need the PropertyChangeListener
                    final Action newFolder = am.get("New Folder");
                    newFolder.setEnabled( false );
                    newFolder.addPropertyChangeListener( new PropertyChangeListener()
                       public void propertyChange(PropertyChangeEvent e)
                            newFolder.setEnabled( false );
                    //  The other solution is to remove the button then you don't need to
                    //  disable the action. This solution requires Darryl's SwingUtils
                    //  class: http://tips4java.wordpress.com/2008/11/13/swing-utils/
                    //  Comment the above code and uncomment below if you want to test this.
                    Icon icon = UIManager.getIcon("FileChooser.newFolderIcon");
                    JButton button =
                        SwingUtils.getDescendantOfType(JButton.class, fc, "Icon", icon);
                    button.getParent().remove(button);
                    //  Disable editing of the file name by using F2
                    InputMap im = fc.getInputMap(JFileChooser.WHEN_ANCESTOR_OF_FOCUSED_COMPONENT);
                    im.put(KeyStroke.getKeyStroke("F2"), "none");
                    fc.showSaveDialog(null);
            add( simulate );
        private static void createAndShowUI()
            JFrame frame = new JFrame("FileChooserSSCCE");
            frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
            frame.add( new FileChooserSSCCE() );
            frame.pack();
            frame.setLocationRelativeTo( null );
            frame.setVisible( true );
        public static void main(String[] args)
            EventQueue.invokeLater(new Runnable()
                public void run()
                    createAndShowUI();
    }This question was inspired by by my attemtp to help with this question: http://www.coderanch.com/t/555535/GUI/java/FileChooser-readOnly

    However, I can't figure out how "file name editing" works. Using Key Bindings I was able to find the binding between the F2 key and an Action named "editFileName". However, I can't find where this Action is actually created in the UI. I also can't figure out how clicking on a selected file name invokes this Action.I guess that would be in the proprietary <tt>sun.swing.FilePane</tt> class. EDIT: Also, disabling the <tt>Action</tt> showed that clicking doesn't invoke the <tt>Action</tt>. It's possible that both clicking and the <tt>Action</tt>'s <tt>actionPerformed(...)</tt> invoke the same method, which starts the editing.
    Does anybody know how to prevent the mouse click from allowing editing of the file name?Removing the associated <tt>MouseListener</tt> (in an unacceptably implementation dependent way) seems to do it. The detail view, which is an anonymous <tt>JTable</tt> subclass, is a bigger problem as the API doesn't provide a means to block editing, and removing the <tt>MouseListener</tt> also blocks cell selection events.
    Here's a working example I wouldn't recommend anyone to use in a real-world application. For other members reading this, the <tt>SwingUtils</tt> class is available hereimport darrylbu.util.SwingUtils;
    import java.awt.Container;
    import java.awt.event.*;
    import java.beans.PropertyChangeEvent;
    import java.beans.PropertyChangeListener;
    import javax.swing.*;
    public class ReadOnlyFileChooser {
      public static void main(String[] args) {
        SwingUtilities.invokeLater(new Runnable() {
          @Override
          public void run() {
            new ReadOnlyFileChooser().makeUI();
      public void makeUI() {
        final JFileChooser chooser = new JFileChooser();
        InputMap inputMap = chooser.getInputMap(JFileChooser.WHEN_ANCESTOR_OF_FOCUSED_COMPONENT);
        inputMap.put(KeyStroke.getKeyStroke("F2"), "none");
        final JList list = SwingUtils.getDescendantOfType(JList.class, chooser, "Enabled", true);
        final MouseListener mouseListener = list.getMouseListeners()[2];
        list.removeMouseListener(mouseListener);
        list.addMouseListener(new MouseAdapter() {
          @Override
          public void mouseClicked(MouseEvent e) {
            if (e.getClickCount() == 2) {
              mouseListener.mouseClicked(e);
        final Container filePane = SwingUtilities.getAncestorOfClass(sun.swing.FilePane.class, list);
        filePane.addContainerListener(new ContainerAdapter() {
          @Override
          public void componentAdded(ContainerEvent e) {
            final JTable table = SwingUtils.getDescendantOfType(JTable.class, chooser, "Enabled", true);
            if (table != null && table.getPropertyChangeListeners("tableCellEditor").length == 0) {
              table.addPropertyChangeListener("tableCellEditor", new PropertyChangeListener() {
                @Override
                public void propertyChange(PropertyChangeEvent evt) {
                  SwingUtilities.invokeLater(new Runnable() {
                    @Override
                    public void run() {
                      if (table.isEditing()) {
                        table.getCellEditor().stopCellEditing();
        chooser.showOpenDialog(null);
    }db
    Edited by: Darryl Burke
    Edited(2) by: Darryl Burke -- shortened and improved the code

  • Setting property for multiple objects?

    Adobe Pro X; ES2
    I need to set the access property for multiple objects based on the selection of a radio button group. I assume I have to use resolveNodes(), but cannot for the life of me get it to work. Here's what I've played with :
    if (this.rawValue == "1") { 
    xfa.resolveNodes("OtherCase_gp.[*]").access = "open";     
    } else {  
    xfa.resolveNodes("OtherCase_gp.[*]").access = "readOnly";
    If I use Action Builder, I get endless lines of "oTargetField = this.resolveNode("OtherCase_gp.OtherCaseOther_cb"); oTargetField.access = "readOnly";" There must be a better, more efficient way to do this!

    Hi,
    Here's another way to try;
    var fields = xfa.resolveNodes("OtherCase_gp.#field.(name.substring(0,9) == 'OtherCase')");
    for (var i = 0; i < fields.length; i++)
        fields.item(0).access = (this.rawValue == "1") ? "open" : "readOnly";
    This approach will only work if your fields are all under OtherCase_gp, Radzmar's solution is more general if your form has a more complicated hierarchy.
    Regards
    Bruce

  • Making custom non-standard components aware of custom look and feels.

    Hello all.
    Maybe the subject of this post could also be the opposite: "Making custom look and feels aware of non-standard custom components". I'm not sure.
    If I code a new custom component (extending JComponent, or extending the UI delegate of a standard component) and pretend it to be laf aware then I must create the corresponding UI delegate for each laf, like it happens to be with standard swing components. But I'm not sure it is feasible to create the UI delegates for all unknown existing custom lafs.
    On the other side, if I create a custom laf then I will also create a custom UI delegate for each standard component, but I can not create UI delegate for all unknown existing custom components.
    The point here is that standard components and standard lafs are universally known, while custom components (or custom ui delegates) and custom lafs are not.
    So the question is: How does a swing developer deal with the case of a new custom component that will be used in an unknown custom laf?
    For instance:
    1. Custom text UI delegate for dealing with styled documents in JTextField. See {thread:id=2284487}.
    2. JTabbedPane with custom UI delegate that paints no tab if the component only contains one tab.
    In both cases I need a UI delegate for each known laf, but what happens if the application is using a laf that certainly will not be aware of this custom functionally?
    Thank you!

    If I code a new custom component (extending JComponent, or extending the UI delegate of a standard component) and pretend it to be laf aware then I must create the corresponding UI delegate for each laf, like it happens to be with standard swing components. But I'm not sure it is feasible to create the UI delegates for all unknown existing custom lafs.You are right, this is never going to work. I suggest if you want to make your custom component look & feel aware, you design the way it displays around the l & f of other components that are part of j2se and have l&f implementations.
    http://download.oracle.com/javase/7/docs/api/javax/swing/plaf/ComponentUI.html
    There are instructions here:
    http://download.oracle.com/javase/7/docs/api/javax/swing/LookAndFeel.html
    >
    On the other side, if I create a custom laf then I will also create a custom UI delegate for each standard component, but I can not create UI delegate for all unknown existing custom components.
    The point here is that standard components and standard lafs are universally known, while custom components (or custom ui delegates) and custom lafs are not.
    So the question is: How does a swing developer deal with the case of a new custom component that will be used in an unknown custom laf?
    For instance:
    1. Custom text UI delegate for dealing with styled documents in JTextField. See {thread:id=2284487}.
    2. JTabbedPane with custom UI delegate that paints no tab if the component only contains one tab.
    In both cases I need a UI delegate for each known laf, but what happens if the application is using a laf that certainly will not be aware of this custom functionally?
    Thank you!

  • Customize MDM Standard ivew

    Hello ,
    We are implementing MDM on Enterprise Portal and have deployed the Business Packages for the same. Now we have a requirement to customize the Standard iview 'Search 'Text' for MDM item Search. This iview has a Dropdown which has the value 'Progressive' as default and 'Contains' as the second value in the dropdown.
    So we want to default the value 'Contains' and put 'Progressive' down below in the dropdown. How can we achieve the same.?
    Any help would be highly appreciated.
    Thanks.

    Hi,
    You can generate MDM WebService using web Service Generator.
    Refer below tutorial which gives step by step procedure to create MDM WebService.
    [http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/60fbcee6-c30c-2d10-1f9d-b9493fce79c7?quicklink=index&overridelayout=true]
    After generating WebService you can create model of this WS in WebDynPro and pass values from your custom Search Attributes, which will be always fixed in your case. Expression operator in your case would be Contains.
    As a output of this WebService you will get all record Ids according to your search parameters. Get all these Record IDs in a array and use below line to set filterd record IDs in your result set.
    wdThis.wdGet<resultSet>Interface.setRecordIds(<Record_Ids_Array>);
    I hope it helps.
    Regards,
    Rohit

Maybe you are looking for

  • Issue with flat file loading timing out

    Hello I have a scenario, where I am loading a flat file with 65k records into a cube. The problem is, in the loading process, I have to look up the 0Material table which has a million records. I do have an internal table in the program, where I selec

  • Output triggered to  wrong vendor

    Hi experts, I have created a PO on vendor 1234 and there are two condition records maintained for this vendor.  Outputs have triggered for both the condition records.  Now, the issue is, in addition to this, outputs have also triggered for another ve

  • Video Playback - Need a way to make students watch the entire video without taking away their controls.

    We want to give our students a good viewing experience for our videos so we'd like to give them playback controls. BUT, we need them to watch the entire video without being able to skip ahead. An ideal situation would allow the user to move to any po

  • "Always on top" behavior for Navigator Window?

    Greetings, Several of our users have asked for an "Always on Top" feature for the OHJ help navigator window. We are using OHJ 4.2.3, on Windows platforms. Our application displays help topics from certain dialog buttons and menu items (using CshManag

  • HT4260 Is there an airport utility 6.0 tutorial?

    Just neede to see if there is a 6.0 tutorial for this setup, thanks!