I'm trying to use Orbeon 3.9 CE to create an editor for XML documents. I've hit a problem in that the xforms fields I've created for the various attributes don't show up in the web form if the existing input XML document does not have them. I've searched Stack Overflow and the Orbeon doc and wiki but haven't been able to find a setting to fix this.
This is implemented according to the specification: if the ref resolves to an empty sequence (or "empty nodeset" in the XPath 1.0 parlance used by the XForms 1.1 spec), then the control is considered non-relevant. There is no provision for having the node created automatically if missing. So this would need to be done either:
Outside of XForms, in a phase of pre-precessing of the XML to add missing element or attributes.
In XForms, after the instance is loaded, by inserting nodes in the instance as appropriate.
Unless you need to add just a few nodes, the first option is most likely more appropriate.
#avernet's response is correct.
Somebody asked a similar question on this thread.
The recommendation I made was to create an XBL component to handle this automatically. I suggested a first version of such a component, more as a suggestion than as a final, usable solution. But that might help you.
Related
Given a Vaadin application where a user can add and remove elements of a list that is also rendered in the browser, I am wondering what the most efficient way of handling such manipulations would be. Currently, I am simply using the add and remove methods.
I am only experienced with Apache Wicket where one should avoid to manipulate the component tree for performance reasons. In the documentation, I only found a section on how to handle repeated elements in Polymer but nothing on how this can be done using the "simple" API.
Am I choosing the right approach?
The Vaadin UI code runs on the server, so the add/remove operations don't affect the DOM directly. When a response is sent back to the browser, Vaadin will look at the difference between the previous UI state and the current and send appropriate instructions to the browser client to update the DOM. In this case, the instruction would be something like "remove the following components:...". The actual DOM manipulation is handled by Vaadin, and is not something you can affect yourself.
If you run into performance issues, help us out by filing an issue ticket on GitHub, so we can take a look at it https://github.com/vaadin/flow/issues
according to this Thread: http://social.msdn.microsoft.com/Forums/vstudio/en-US/d566e2e5-3782-4e2b-be3b-85228f41dfc3/add-a-tree-path-field-in-work-item it is not possible to create a TreePath or AreaPath for a custom-field.
I kinda can't believe nobody is running into extreme problems without this crucial controls.
Since the last answer in this Thread (and the others about this I found) is from earlier last year, was there anything changed about this control?
Has anyone found a solution about this? I tried to google about creating own custom controls, but I think this is not possible. Is there any workarround to create a easy tree-structure in a control?
Thanks and greetings
Matthias
Read more carefully. You cannot have fields with TreePath data type, but you can create custom controls for other data types.
In other words, you can create custom controls that display hierarchical information as long as you are able to represent this in an existing data type, in practice the String type.
Examples of custom controls at https://witcustomcontrols.codeplex.com/.
Literally I think the part will let me customize the property name of a specific content type in orchard. But when I attach this part to a newly created content type from the admin UI. All I got is 3 text fields with property names called "Custom One, Custom Two, Custom Three".
I couldn't find any examples from the web or from Orchard Source code explaining how should I work with it...
This part is obsolete. It used to be necessary for the List feature (also obsolete) to be able to sort on custom data. You should not be using that part.
I need to know how to use each and every attribute of Struts2 tags. I
have gone through all possible websites by searching via Google, But
no one has understandable explanation or examples of each and every
attributes of each struts2 tags.
for example: In "optiontransferselect" tag, for
allowAddAllToRight attribute I have no idea what String do I need to give for it.
here is one of the site I refered...
If you want to understand every single option, do two things:
Use every single option.
Read the source code.
When something is listed as "enable", it's almost always a true/false value, as it is in this case. Why it's listed as a string, not sure; either an issue with the annotation processor, or it was added and the type conversion was done manually, or...?
While I (sort of) understand the motivation for wanting to understand "each and every attribute" of each tag, IMO your time would be better spent learning more important framework details.
I am afraid you will find them at anywhere as these attributes have been defined and provided based on generic needs and its quit possible that some one need few of them and some need others.
i even never used all of the tag properties and in most of the cases we end up using few as per our choice.
If you want to find what each and every property/ attribute making end effect best way is to create a demo struts2 application pick up few tags go to struts2 tag reference page read there description and start playing with them and see how things are changing and check generated HTML code.
There is no other shot-cut for this.
But why you need to know all the properties? i am just curious
Struts2 tag refrence
Has anybody ever used blogpost contenttype and extended it and added some column to it. I know we can add columns to it using the GUI (List Setting).
Can we do this declaratively and add it to the portal using feature, so that we can create a deployable solution.
Paddy
I have not tried this, but I don't see any reason why you couldn't. The only thing that gives me pause is that Blogs are a little different than most lists because the List Definition is not in a Feature but is rather part of the Site Definition. You could create a Feature with your custom Content Type and staple it to BLOG#1. However, you will still need something (probably a Feature Receiver) that will modify the instance of the Posts lists by adding your custom columns and associating your custom Content Type.