On Tue, May 25, 2010 at 02:14, Justin Edelson justinedel...@gmail.com wrote:
If I was using Sling in an order management system, I would still model
it as a tree of nodes. Nodes aren't expensive to create (although 50
nodes for an order seems high).
A high number of nodes typically comes from
On 5/26/10 2:05 PM, Tony Giaccone wrote:
I've been forced to deal with some other project issues, so that kept me away
from spending the time to really understand what you're saying here.
Now I'm back (like the proverbial bad penny).
new
On 5/26/10 1:55 PM, Alexander Klimetschek wrote:
On Tue, May 25, 2010 at 02:14, Justin Edelson justinedel...@gmail.com wrote:
If I was using Sling in an order management system, I would still model
it as a tree of nodes. Nodes aren't expensive to create (although 50
nodes for an order seems
I have a node, the node has some meta data and some XML data in the node.
I can't seem to view the XML through webdav. The titles of the document show
up, but they seem to be empty, is this expected?
How does one do versioning? If I save a new document with new data to the same
node in the
Hi,
On 5/24/10 12:10 PM, Tony Giaccone wrote:
I have a node, the node has some meta data and some XML data in the node.
You have a node property containing XML or a node of type nt:file
containing an XML file? In either case, why not just store the structure
as JCR nodes?
I can't seem
It just doesn't make sense to me to take an object (a document),
create an XML representation of that object, and then store the
representation in the repository as a single node (or node property).
If you have:
document
name
firstNameBob/firstName
So what would you suggest as the alternative?
How should I place my xml into the repository?
I can understand why you wouldn't want to write the code to do this, but can
you give me a general idea?
If I have a XML Document how do I put that into the repository in the correct
manner?
Tony
Justin,
I appreciate your help, really I do, and please understand that I'm new to this
whole deal and trying to understand the underlying details.
So maybe a little more information would make things clearer. The XML that I'm
creating is also going to be used to drive an external process.
If I was using Sling in an order management system, I would still model
it as a tree of nodes. Nodes aren't expensive to create (although 50
nodes for an order seems high). If you're going to use JCR, you should
get used to creating nodes :)
When you need to create the XML documents for ingestion
Tony,
Mostly I try to avoid having lengthy jsp scripts.
As a sling newbie I cannot explain why your solution does not work.
In my project I do a similar thing:
- a servlet treats user input (say, modifications on a resource)
- that gets written into a document
So consider two alternatives:
10 matches
Mail list logo
