Replacing the root node in a DefaultTreeModel

how do i do it? i have added all my listeners to the tree and would simply like to replace the root in the model but it is not working?
can anyone tell me how? .. i have everything set up and working but when i try to replace the DefaultMutableTreeNode "root" with the new DefaultMutableTreeNode "new_root" it doesn't work?

did you tried:

Similar Messages

  • How to replace the root tag in ABAP Mapping

    how to replace the root tag with the certain string in ABAP Mapping
    just like
    <?xml version="1.0" encoding="UTF-8"?>
    <?xml version="1.0" encoding="UTF-8"?>
    i don't want to implement it in message mapping
    please give me the sample code
    thanks in advance

    Use below code
    odocument = ixmlfactory->create_document( ).
    msgtype = odocument->create_simple_element(
    name = 'myRootElement'
    parent = odocument ).

  • How do i get to display the nodes under the root node in a JTree?

    In my JTree there is a root node.This root node has 4 child nodes.Each child node in turn has nodes under it.What i need to do is just display the child nodes under the root node i.e., the four child nodes and keep these child nodes in a collapsed state.How do i go sbout this?

    Please try this:
    SwingUtilities.invokeLater(new Runnable(){
        public void run(){
    });If you want to show the RootHandles:
    tree.setShowsRootHandles(true);If you want to keep nodes in collapsed state (not expandable):
            tel = new TreeWillExpandListener() {
                public void treeWillExpand(TreeExpansionEvent event) throws ExpandVetoException {
                    throw new ExpandVetoException( event, "Don't want" );
                public void treeWillCollapse(TreeExpansionEvent event) throws ExpandVetoException {
            tree.addTreeWillExpandListener(tel);Some reading material:
    Edited by: Andre_Uhres on Nov 14, 2007 5:17 PM
    Edited by: Andre_Uhres on Nov 14, 2007 5:33 PM
    Edited by: Andre_Uhres on Nov 14, 2007 5:39 PM

  • Issue on deployment: Solution Deployment : Missing one or more of the following attributes from the root node in solution .wsp: assembly '', type ''

    I have the following issue when deploying:
    Solution Deployment : Missing one or more of the following attributes from the root node in solution .wsp: assembly '', type ''
    The solution is a farm solution (was never sandbox) and it deploys fine.
    It was updated several times with success. We did not see this issue until recently when we had some other issue (unrelated) and looked at the logs. The solution is updated without problem and updates are available for the user. But we can see this error
    in the logs at the update time. 
    Any idea what might cause this?
    Pop Anisia

    This error is wide meaning, as it can come from differences between SP versions, variables types used, bad manifest file, WebConfiguration ...
    You can try to redeploy the solution.
    retracted the solution,removed all the previous ref, removed dll from GAC and folder from 14\features and reset the iis, deploying it again.
    Here are some similar issue post, you can use as a reference:
    In additional, you can check the ULS log (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS) to get the detailed information.
    I hope this helpful.
    Best Regards,
    Lisa Chen
    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
    [email protected]

  • Ldif2db command fails to import data and deletes the root node

    ldif2db command fails to import data into LDAP.
    The command used was
    ldif2db -n userRoot -s "dc=example,dc=com" -i test.ldif
    The test.ldif conains the nodes under dc=example,dc-com
    eg: ou=test,dc=example,dc=com
    But on executing the command the root node "dc=example,dc=com" itself got deleted. The console output was like "Skipping entry uid=test001,ou=test,dc=example,dc=com" for all the entries present in ldif.
    What might be the reason for this ? Any clues ?
    The reason y i am trying to do this ldif2db is to preserve the createtimestamp and modifytimestamp while migrating data from one Directory Server to another. Any other ways of doing it ?

    ldif2db is the right command to migrate data and preserve those attributes like createtimestamp and modifytimestamp.
    However, when this command is used, it will first remove everthing before it load whatever you want. So you need to be very careful. I got this terrible problem as well.
    In my experience, if you use this command, don't use "-s". You can just use:
    ldif2db -n suffixName -i test.ldif
    If you only have one suffix (database), then you can use "-n userRoot".
    Also, if you migrate your data from server A to server B, you'd better dump the data using db2ldif -n userRoot -a test.ldif from server A. Then load it into server B using ldif2db -n userRoot -i test.ldif.

  • [JAXB] Multiple imports in the root node

    I use JAXB and am doing this scenario : unmarshalling an XML document created manually, and automatically marshalling another from the generated Java code.
    This is a multiple schemas / multiple imports issue.
    I would like the 2 XML documents to be similar, but in the first one, I get :
    <?xml version="1.0" encoding="UTF-8"?>
    <aaa:first xmlns:aaa="http://aaa" xmlns:bbb="http://bbb">
    and in the second :
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <aaa:first xmlns:aaa="http://aaa" xmlns:ns1="urn:abc" ...>
    <bbb:second xmlns:bbb="http://bbb">
    So, how is that possible to import multiple namespaces (xmlns) in a single node please ? It seems that JAXB does the import only when needed, and won't group all the imports in the root node.
    (moreover, how can I disable the "standalone" attribute in the header of the generated XML document please ?)
    Thanks in advance.

    Ok, I found a solution to get all namespaces placed in the root of the generated XML document : one have to implement a NamespacePrefixMapper
    marshaller.setProperty("com.sun.xml.bind.namespacePrefixMapper",new NamespacePrefixMapperImpl());and redefining its ' public String[] getPreDeclaredNamespaceUris()' method.
    For now, the problem is that namespaces declared there are somehow static. In fact, when unmarshalling Java objects from an XML document, it seems that this document namespaces are lost.
    Do you know a way these namespaces would be kept somewhere, associated with the unmarshalled object ? I need these namespaces in the case that I would create another XML file from it in the future.
    It's seems logical to keep this with the object, so did I miss something please ?

  • How i can insert icon only in the root node

    i need to insert icon only in the root node, with the other nodes i don't have problem.

    Use a jQuery menu like Superfish, or you can purchase an extension like the ones offered by Project VII

  • GRC 10 LDAP query issue at the root node

    We are unable to do a search based on root node after successful LDAP integration but if we add a particular OU within the base entry then we are able to search the users for that specific OU. Specifying a specific OU is not the right solution as we have different OU for North America, Europe,
    Latin America etc. regions. We need to specify the root node so that it will search for all the users in different region. We are getting the below operation failed error when we don't specify OU in the base entry.
    Operation failed
    Message no. LDAPRC001
    This is an error message that is triggered by the directory server.
    It is not possible to analyze the error in the SAP system.
    Check the log files for the directory server (if they exist), to see if they
    contain more information.
    Please let us know if you guys have faced this situation and what was the resolution.

    We just have one LDAP server/connector set-up and it is working fine if we specifiy OU within the base entry along with the domain but it doesn't work if we remove OU and leave the base entry with the root node/domain. I have checked with our Basis team and we have only one forest..going to check with our AD team for the same. Since specifying OU in the base entry is pulling result from Active directory within LDAP t-code in GRC 10 system, I believe everything is fine from LDAP configuration standpoint and also SPRO configuration in GRC 10 system will come into scope when we try to retrive/populate those field in ARQ/CUP configuration in NWBC.
    Below is the structure of our AD. If we leave the base entry with the root node/domain (DC=NR,DC=AD,DC=NEWELLCO,DC=COM) then it doesn't work and give the operation failed error message but if we add OU (OU=EMEA,DC=NR,DC=AD,DC=NEWELLCO,DC=COM) along with the root node then it does provide us with the result.
    I'm going to follow up with the AD team but let me know if anyone got any ideas to resolve the above error.

  • Dynamically rename the root node of XML based on the child elements

    Hi Gurus,
    Is there any way to rename the root node of the resultant XML after a mapping based on the child elements.
    For ex:
    consider the following resultant XML after mapping
    <element1> </element1>
    if the element1 is <type> then the output should be
    <type> </type>
    elseif the element1 is <character> then the output should be
    <character> </character>
    Let me know how to do this, either in XSLT or in Graphical mapping.

    Hi, Prabu:
    In this case, I am suggest you have Src and Tar Message.
    I am suggesting you create another type of message using key / value pair as I suggested, e.g. called Mid Message.
    My solution for you is to have two message mappings:
    1. Src -> Mid
    2. Mid -> Tar.
    In first mapping, you have no control of the structure, but you can map it to Mid structure:
      if Type node Exist, then map 'Type' to Key, as Key/Value can be creatd under a parent node with 0:1 Occurrence.
      saying item.
       in this case, a new item created.
    If you think of this way, any xml file can be represted in this way:
    Can be interpretd as this way:
    Now you should understand what I mean.
    In your case target structure have to desgined as following way:
    You need to put Category and Property together with their sub-structure in parallel, make occurence to 0:1
    In your second mapping, you can check the key value is "Type" or "Character", based on which one is true,
    you create corresponding structure: either Categary or Property.
    Edited by: Liang Ji on Oct 22, 2010 8:31 PM
    Edited by: Liang Ji on Oct 22, 2010 8:35 PM

  • Setting background color to just the root node in a tree

    How can I set a background color to just the root node in a tree? I got the node in the followig way in the renderer method.
    IconNodeClass parentIconNode = (IconNodeClass)((IconNodeClass)value).getRoot();
    Then how can I set the background for just the root node? Thanks.

    You need to write ur own treeCellRenderer for that to be done

  • Renaming the Root node?

    Hi all,
    I have an XML document which has <rootNode> as the root node of the entire document. Is there a way of renaming this to e.g. <abc>, so this is the new root of the whole document?
    Or is XSLT the way to go?

    you can also do it via an XSLT sheet like this
    <?xml version="1.0" encoding="UTF-8" ?>
    <xsl:stylesheet xmlns:xsl="" version="1.0">
    <xsl:template match="OLD_root_name">
    <xsl:copy-of select="./*"/>

  • Validation to find the Root Node !!!!

    Hi All,
    Is it possible to write a Validation to find the Root Node of the Hierarchy,
    For E.g.  If we have a three level hierarchy
            Dot Matrix
    So is there a way I can check if my Root node value is Printer or not, because in Data Manager the value that is selected from the hierarchy drop down is the leaf node.

    Hi Jitesh,
    The solution is as follows:
    MDM does not give us the option to traverse to the grandparent of the leaf node..
    In the example that we have taken :
    - Dot Matrix
    - Laser
    Here if we want to check if the Grandparent of Laser1 is Printer, this cannot be done using the simple Validation, because through validation also we can at max find the parent of the current node i.e. we can traverse till Laser (for Laser 1 leaf node).
    Further we cannot use Laser as the node because in MDM we have to traverse completely through the last node and select it in Data Manager. So again we cannot search for Laser -> Parent.
    The Work Around that I have used is :
    I have created a new field and every time I import data I have mapped this field with the first Level Node and have put the Validation on this field.
    Eg: The field name is Root Node, so everytime the data is imported, Level 1 is mapped to Root Node and so all the Root node values are imported in the Root Node field that we have created and everytime the Validation Runs on this Root Node field and accordingly the process follows.
    Hope that would be helpful to you all!!!!
    Parul Malhotra

  • How to get the root node of a tree?

    I wanna get all the leaf node of a tree.But JTree have no method about how to get the root TreeNode of a tree.Then how should I do?

    try this:

  • A different cell renderer for the root node ??

    Is it possible to use one cell renderer for the root and a different cell renderer for the other nodes ?

    Well I tried that and it didn't work.I do it without any problems so what how did you do it?
    Hint - in the renderer compare tree.getModel().getRoot() with the value using == .
    Basically I have a checkbox at each node. So, I tried
    setting the checkbox invisible for the root. Hard work! Since you are just wanting to change the rendering rule for the root you should change the renderer.
    But then all the nodes have an invisible

  • Initial JNDI context doesn't return the root node

    Hi :
    I just deployed a java application on Netweaver CE 7.2, when the application starts up, the code is trying to perform a JNDI bind and lookup operations by calling " Context context = new Initialcontext(), context.bind(), context.lookup("...)", the problem is that the initial context returned is not the root context (i.e. "/"), it's something like "webcontainer/applications/vendor-name/application-name/module-name/...." etc.. This is a problem for us because our application is consisted of multiple ears with multiple modues(wars) inside each ear, each module needs to publish a set of services as JNDI entries and those services (JNDI entries) need to be accessible to other ears or modules, which means they have to be published under some public directory (for exmaple the root directory), it can NOT be published under the current context of the current module.
    So,  my questions is, is there a way to make the "new Initialcontext()" to return the root directory, perhaps by changing the deployment descriptor or configuration settings somewhere? thanks a lot for your help.

       Add this code to the <i>wdDoModifyView()</i> method:
    IWDRoadMap rdMap = (IWDRoadMap) view.getElement("<id of the RoadMap UI>");
    Edit the StepSelected action to add a parameter called "<i>selectedStep</i>" of type String. After this the signature for the action handler will look like:
    public void onActionStepSelected( wdEvent, String selectedStep )
    Inside the action handler you can access the selected step simply as "<i>selectedStep</i>".

Maybe you are looking for