more questions on exporting xml using oscript

Tom_Baghdassarian_(HPcaUser1_(Delete)_2164649)

has anyone tried to export information about multiple nodes from a single action=xmlexport call?here's what we're trying to do:we have a custom node that is supposed to be a view of a number of predefined nodes - i.e. a project workspace, 2 other workspaces (folders) - what I'd like is to somehow intercept the call which generates the xml against our custom node and in addition to the info exported, also include the info for the project workspace and the two other workspaces (our custom node stores the objectid of the workspaces).from what I gather, this could be done by orphaning the xmlexport action object from webnode and overwrite the _subcalssexecute method - however I've done that but my custom node is still being exported via the function in webnode and NOT my new orphan function (I did set the _nodetypes feature to point to my new custom node).any directions? I'd LOVE to see some sample code on merging the xml views of multiple objects and then dumping them back to the browser (also being able to transform it) as a sinlge node that makes it look like all the workspaces are physically inside my new custom node.thanks a bunchthomasbtw - are there any good docs/places here where folks have shared their xml samples? the only real doc I've found is the xml import/export guide which leaves much of the detail for the developer to try and figure out.

Find more posts tagged with

Comments

eLink User

Message from Hans Stoop <<A HREF="mailto:hstoop@opentext.com">hstoop@opentext.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

Hi Thomas,

The way to go is:

- Create a XMLnode call back for your specific node type. In the write method you export your additional data. You may even make it dependend on a parameter specified on the URL.

In case you have the Appearance utility, then you can use a function that will export a subtree from a specified root.

Hans Stoop

----------------------
Livelink Appearance is shown at
LivelinkUp Europe 2003
Open Text User Conference
Paris, France
May 12th - 15th 2003

Find out how we're helping six million great minds
work together to improve efficiencies and save money.

http://www.opentext.com/livelinkup/

-----Original Message-----
From: eLink Discussion: Development Discussion [mailto:development@elinkkc.opentext.com]
Sent: dinsdag 25 maart 2003 0:51
To: eLink Recipient
Subject: more questions on exporting xml using oscript

more questions on exporting xml using oscript Posted by HPcaUser1 (Baghdassarian, Tom) on 03/24/2003 06:39 PM

has anyone tried to export information about multiple nodes from a single action=xmlexport call?

here's what we're trying to do:

we have a custom node that is supposed to be a view of a number of predefined nodes - i.e. a project workspace, 2 other workspaces (folders) - what I'd like is to somehow intercept the call which generates the xml against our custom node and in addition to the <llnode> info exported, also include the <llnode> info for the project workspace and the two other workspaces (our custom node stores the objectid of the workspaces).

from what I gather, this could be done by orphaning the xmlexport action object from webnode and overwrite the _subcalssexecute method - however I've done that but my custom node is still being exported via the function in webnode and NOT my new orphan function (I did set the _nodetypes feature to point to my new custom node).

any directions? I'd LOVE to see some sample code on merging the xml views of multiple objects and then dumping them back to the browser (also being able to transform it) as a sinlge node that makes it look like all the workspaces are physically inside my new custom node.

thanks a bunch
thomas

btw - are there any good docs/places here where folks have shared their xml samples? the only real doc I've found is the xml import/export guide which leaves much of the detail for the developer to try and figure out.

Magnus_Salgo_(IDNordicAdmin_(Delete)_2300172)

Why not do your own requesthandler that exportys what you want ?!?!?From our experience that is the best way ...

eLink User

Message from Hans Stoop <<A HREF="mailto:hstoop@opentext.com">hstoop@opentext.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

In case you are thinking about creating your own request handler, you should also have a look at the new XMLexport framework that is currently available from firstlook.opentext.com. In the new framework having you own implementation of XMLexport behavior is much easier. They are also requesting feedback on this new framework, so don't miss this chance to influence the future of Livelink.

-----Original Message-----
From: eLink Discussion: Development Discussion [mailto:development@elinkkc.opentext.com]
Sent: zaterdag 29 maart 2003 23:19
To: eLink Recipient
Subject: Do your own request handler ?!?!?

Do your own request handler ?!?!? Posted by IDNordicAdmin (Salgo, Magnus) on 03/29/2003 05:07 PM
In reply to: more questions on exporting xml using oscript Posted by HPcaUser1 (Baghdassarian, Tom) on 03/24/2003 06:39 PM

Why not do your own requesthandler that exportys what you want ?!?!?

>From our experience that is the best way ...

Magnus_Salgo_(IDNordicAdmin_(Delete)_2300172)

https://firstlook.opentext.com/firstlook/livelink.exe?func=ll&objId=2762919&objAction=browse&sort=nameRegarding building your own requesthandler we have the possibility to have different navigations structures for a Livelink node by applying different CM content management objects to the structure....Hopefuly one collegue of mine Petri Huovila will speak about the application at Livelink Up in Paris .....RegardsMagnus S?lg?salgo@ids.se+46-8-7046349ID Application

D2_Periodic_Review_Config.pptx