Build configuratino reuse

Hi,
I'm working with Eclipse Luna on a project which is managed through an SVN repository.
Every time I check out a new sandbox (my copy of "trunk" in the repository), I need to set all the environment variables all over again (if I want to compile and run through Eclipse).
The include paths and symbols, I can export and then import into a new project, but not the rest of the data, which is quite annoying.
I read an option of copying ".settings" folder from one sandbox to another sandbox, but its not working either.
Appreciate any advice on the matter.
Sincerely,
Hagai Hadad

Similar Messages

Need advice about builds and reuse

I'm almost done with my first authoring on DVDSP 3.0.2 - this is a DVD that will be sent to replication. I willl likely make some minor changes to my project. Is it 100% safe to use the 'reuse' command when doing my final build after these changes? Or is it better to do a fresh build from scratch?
Thanx in advance
Bob

Thanks for the quick reply!
One more noobie Q - My replicator said he can take an image file from me. So I will use DVDSP to create it. I've never created an image file. Is it straightforward? Are there any options to be aware of?
As far as QC'ing the project - can I check the image file itself? or do I just check a DVD formatted from the build (before I create the image file).

Build problems using DVDSP3

Hi!
I've already produced over 100 DVDs with DVDSP3 and never had a problem that I was unable to solve myself.
But here it is:
I've mastered a lot of TV series in the past with about six 30 min. episodes on one DL DVD. The first build of one DVD was almost perfect, but I had to replace one menu background (cosmetic changes). So the DVD was build again (reusing the old build) and then it happened: One of the episodes on the DVD got corrupted. After 20 minutes for almost 5 seconds a completely different m2v and ac3 was played! Then it jumped back to the normal episode. To make this a little bit more confusing: The wrong part that was played was out of another project (a series I had worked on before)...
Has anyone an idea what has happened and how to avoid this in the future?

Hi!
Thanks for your answer. You are right, I re used the previous build. But why DVDSP used video and audio (that are not even in the project) is not answered. It isn't even clear if it was a reusing problem. That brings (all of) us to the situation that we have to read back our DLTs and check for errors in the build very carefully (and very time consuming) before delivering DLTs to the duplication facility (or use a (very expensive) proving software).
Without knowing the exact reason and how to avoid it we (at least professionals) have to double check after building and formatting. But checking isn't easy because different players do different things with our wrong DVD. Some show the wrong video, others skip the 5 secs because of the MPEG2 errors in the stream (I suppose) and others (like the Playstation 2) advance to the next chapter.
You see that if you check the disk in a wrong player and don't even notice there was a problem. Then you deliver to your client and he will... (depends on client)...
Be warned
K
PS.: Anyone else with suggestions?

Alv + top of page + excell

hi
i have already my field catalog using "field catalog merge"
i have already build my "reuse alv display"
what i remain to do is build "the top of page" and in the top of page i'll do a check if ITAB empty put a message "table is empty"
and i also need to give user the possiblity to download the report in an excell file . seem to me that ALV do this automatically? do i need to put any modification in the alv code to make excel download possible ?
please adivse

If the caller specifies an EXIT routine, this routine must have the following form:
FORM top_of_page.
Module REUSE_ALV_COMMENTARY_WRITE can then be called within the EXIT routine. This module is responsible for formatting the header information and also ensures online HTML formatting. In the print preview or in batch mode, the text passed is then output in the normal format.
If module REUSE_ALV_COMMENTARY_WRITE cannot be used, you must use two parameters instead. In I_CALLBACK_TOP_OF_PAGE you pass the form routine that is responsible for normal formatting in batch mode or in the print preview mode. The form routine that is responsible for online formatting, is passed in parameter I_CALLBACK_HTML_TOP_OF_PAGE. If one of these parameters is not filled, top-of-page is not output in the respective mode.
I_default = 'X'
i_save = 'X' / 'A' /
Read function module documentation for more details.

Default buttons not defaulting

Hello. I am on the tail end of a DVD project and just begain encountering some unusual behavior with certain menus. This is a multiple-menu, multiple-video clips promotional DVD.
Up to last week, the DVD has been working as expected in the simulator, in DVD Player (from the Video_TS folder and from a formatted disc), and in several set top players. Yesterday, though, in DVD Player from a formatted disc, the menus appear with no buttons visibly defaulted. The menu still behaves, though, as if the default button was selected (ie., if pressing "enter" activates the default button, and pressing an arrow button sends the selected state in the designated direction.) Each video asset returns to its menu with another default button, and these behave in the same way.
I have already double-checked the connections between the buttons, menus, and videos, and they are set the way they have always been.
- Can the preferences in DVDSP get corrupted (like they can in FCP)?
- Can the DVDSP porject file become "bloated" or corrupted from going through too many revisions? If so, is there an easy way to put the current project into a new file?
I expect that some people that view this disc will do so on a Mac, and I would like to clear this up if it is possible. Any ideas?
Thank you!
Listening,
Aaron Kruse
PowerMac G5, Dual 2GHz Mac OS X (10.4.6) 3GB RAM, FCStudio 5.0 (DVDSP 4.0.3), Logic 7.2

Aaron:
I would try deleting all PAR and MPEG folders that DVDSP created during your authoring (inside the folders where your source files live) and make a clean build without reusing any of the previous VIDEO_TS folders. Probably some file is corrupted. If you want a FCP analogy, is like deleting your render files!
Trashing preferences is a common preocedure . . . but like in FCP, ussually don't resolve problems. But it's like an aspirin, it will don't hurt your system. You can keep a copy of the pref file to restore in case you need.
You could repair permissions and restart . . . just to be sure everything is cleaned in your system.
I would try deleting all PAR and MPEG folders that DVDSP created during your authoring (inside the folders where your source files live) and make a clean build without reusing any of the previous VIDEO_TS folders.
Probably with the specific experience in your problem psot something in the meantime!
Hope it helps!
Alberto

External Libraries in NWDI

Hello all,
i have already read about several post, with that topic, but still found not an acceptable solution for my problem.
We try using NWDI (SPS14). In my SLD i created a new SC EXTLIBS. I configured a Track and loaded the Dev-Conf into the NWDS.
- I created a External Library DC and added the external jars (log4j, jdom a.o.).
- Made my Public Parts.
- Build and Activation works fine.
Due to External Libraries are not deployable i packed all into a J2EE Library Project. With "Used DC`s" as described https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2361. [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken]
Built and Activation worked well and the Track was transported successfull.
Now i created a new SC in SLD, where i defined the EXTLIB as dependency.
Now i run into trouble. I import the new Development Configuration into NWDS and create a project. I see the defined SC in my local Development configuration, but im not able to sync this SC, nor can access the included DC`s.
If i view this SC in its own Development Configuration i can see the DC`s, also the CBS WebUI tells me the correct nummber of included DC`s.
What do i wrong?
Also Pascal Willemsen mentioned a different method for external libs in /thread/47565 [original link is broken] "The 2nd available option (based on NWDI) is to create an External Library DC and add your jars to that. Create an extra public part for assembly (next to the existing public part for compilation called ExternalLibs). Then, for each portal app DC add the External Library DC as a used DC, create an assembly public part and add an Entity Reference to the assembly public part of the External Library DC. This way the jars will be assembled in the PAR file for each portal app. The nice thing is that you are still maintaining the jar files in one central place, but that you have the option to update and test the portal apps individually.".
But here im not able to share the the External Library to different Development Configurations.
Isn`t that possible at all in NWDI?
Thanks for any help
Best regards
Oliver Walter

Hi Oliver,
just some thoughts that went through my mind, maybe this helps clarifying things a bit...
An External Library DC in NWDI is just like a Java DC (except that you don't have sources or do not want to compile them): It's a simple building block that is used during build. Maybe it has a specific "API" subset (in which case you could publish different Jar files in compilation/assembly public parts) or it hasn't (in which case the jars in compilation/assembly public parts would be identical). Anyway, public parts are relevant for build.
If you want to share a common library then putting the library into an External Library DC is a first step: It allows reuse of the same library within one development configuration. If you now transport the DC (as part of the SC which contains the DC) to another track you can again reuse the same library in that other track.
What Pascal wrote refers to the runtime in contrast to the build. During build you reuse the library using public parts, during runtime you reuse the library by either assembling it into each single deployable archive, or by assembling it into one single (J2EE Server Component) library that is reused at runtime of you application. Both solutions are possible within NWDI and each has its own advantages and disadvantages: Either you mulitply the number of Jar files that are deployed (potentially increasing memory usage/required hard disk space but creating an independently updatable application) or you have to worry about version conflicts at runtime.
Marc

Eager fetching

I believe eager fetching can greatly benefit from more dynamic method then
predefined fetch groups.
Different queries pull different parts of object graph and only client using
object model knows what's needed for a particular query. Trying to fit
conflicting data needs into one set of fetch group is a challenge. While I
would retain this feature I would like to propose field based eager fetching
control. Which can also be used for Detached objects
Lets say we have PO with POLine collection and each POLine references
Product. If we want to eager fetch POs along with their lines and products
we could say something like
pm.getFetchConfiguration().addPath(com.peacetech.sales.PO.class, "lines");
pm.getFetchConfiguration().addPath(com.peacetech.sales.PO.class,
"lines/product");
or
pm.getFetchConfiguration().addPath(com.peacetech.sales.PO.class, pathList);
of course we would need
pm.getFetchConfiguration().removePath(com.peacetech.sales.PO.class,
"lines/product");
pm.getFetchConfiguration().addPath(com.peacetech.sales.PO.class); //remove
all for given class
This is just a crude example. In real life we should have few classes to
support the idea and main class GraphConfig or something so users can
configure, build and reuse those GraphConfig instances and use them for
various purposes like eager fetching and detaching without conflicts
I think it would be enormous help to uncouple so many conflicting issues
(fetch optimizations, optimistic locking field groups, detached graphs etc)
from one very limited concept of predefined fetch groups

Mark,
I mentioned this possibility in on of my prior posts. It is not exactly what
I want (since it lack interclass relations which let you express hints for
deep graph rather than for a class and its fields) but close.
If you maintain your metadata files by hand it is too much effort but since
almost all my models and metadata are generated I can easily do (and undo)
it for each and every class/field and I will give it a try :-)
Alex
"Marc Prud'hommeaux" <[email protected]> wrote in message
news:[email protected]...
Alex-
Well, you could always simulate dynamic fetch groups by defining a
different custom fetch group for each field (provided your license has
the capability to use custom fetch groups). For simplicity, you could
name each fetch group to be "ClassName.fieldName".
That way, you could do something like this:
KodoQuery kq = (KodoQuery) pm.newQuery (MyClass.class, "someQuery");
kq.getFetchConfiguration ().addFetchGroup ("MyClass.fieldA");
kq.getFetchConfiguration ().addFetchGroup ("MyClass.fieldB");
kq.getFetchConfiguration ().addFetchGroup ("MyClass.fieldC");
kq.getFetchConfiguration ().addFetchGroup ("MyClass.fieldD");
Collection results = (Collection) kq.execute ();
It would them be pretty simple to make a static helper method that will
do thing like includeAllFieldsInFatchGroup() or
includeNoFieldsInFetchGroup().
In article <[email protected]>, Alex Roytman wrote:
David Tinker says multiple fetch group is the solution:
Hi Alex
You can create as many fetch groups as you like in the meta data (with
JDO
Genie anyway). I think it is much better to get tuning information likethis
out of the code. It should be added externally much like you add indexesto
database tables in response to query search requirements. I understandthat
sometimes you will need programatic control but mostly it is better notto
pollute the code.
JDO 2.0 is going to standardize the concept of a use-case. This willdelimit
business operations to the JDO implementation so it can applyappropriate
meta-data defined fetch groups or locking strategies. You will be ableto
use a vendor supplied tool to analyze the performance of yourapplication
and construct fetch groups for different use-cases (businessoperations). No
change to the code is necessary.
Here is an example:
CODE
pm.beginUseCase("com.peacetech.sales.displayOrder");
POClass o = (POClass)pm.getObjectById(oid, true);
.... other JDO code ....
pm.endUseCase();
The meta data for the use-case will specify the fetch group to use when
looking up the instance (and locking behaviour etc.). Other use-casescan
have different settings. Only the being/end calls are needed in the codeto
make this happen.
Note that this is a very long way from being finalized. I have just madeup
this example and how it works in JDO 2.0 is likely to be different.
Use-case support will show up in JDO Genie beta releases soon. Wealready
have powerful performance monitoring and analysis support in our GUI
Workbench and very flexible fetch groups.
Cheers
David
Here's my opinion
David,
Thank you for your response. Multiple fetch groups do give moreflexibility
(I do not believe Kodo supports it though) but does not alter myposition
>>
I do not want to pollute my metadata with tons of fetch groups creating
dependencies between my code and those fetch groups. JDOQL languagebeing
what it is already creates unavoidable dependency between field namesfilter
strings so I want to keep it the same way with other things which are
essentially references to persistent fields (Disconnected instancesdepth
control, Eagar fetching ....)
As for polluting my code. I want to assure you everything configurablewill
not be in my code but in JNDI or config files. As long as JDO givesclear
API for expressing graph path selection
Use case concept ties nicely with Graph Path selection concept. In factthis
GraphPaths class along with some additional options is your use case.
It is much easer for me to refactor and keep in sync field names and my
GraphPath than fetch groups.
Alex
"Abe White" <[email protected]> wrote in message
news:[email protected]...
I think the basic idea you've suggested is a good one. We'll certainly
consider it for a future release. The JDO 2 spec team is also
pondering
these problems...
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com

PL/SQL reuse in ADF

Is disabling the use of application module pooling good practice for intranet applications where the number of users are known in advance (although in the thousands)? This was suggested as a solution to limit the amount of recoding that will be required of existing PL/SQL programs that make extensive use of global temp tables/package variables/etc. By disabling pooling (and a few other tweaks) the user will access the db with the same session and hence database state is preserved between requests. But in my experience a lot of PLSQL code is written to fit specific use cases (mostly on Forms) without considering the need to reuse the code in any other context (although I must admit that it can easily happen in any other language). I have repeatedly tried to explain that state is better maintained and much easier to deal with if it sits on the application but perhaps I'm wrong. Any advice will be much appreciated.

Hi,
its not enough. If you want to build an ADF application that behaves like Forms, then you need to look for implementing dynamic JDBC credentials so that users have dedicated database connections (which is what Forms is doing). Note that using Application Module pooling and database connection pooling is guaranteeing you better performance so that the question is what the required changes are (global PLSQL variables need to be removed for sure) to PL/SQL so the logic can be used in ADF applications that follow best practices (which is that they run as true Java EE web applications)
Frank

Weekly build notes listings

Since there are major changes going on in the TLF weekly builds, and the ASDocs aren't up to date, and the changes made are not searchable, I thought people might want the list dumped on here so changes to particular classes would show up in a forum search. To see the changes made in Build 360, check out the TLF Blog post on it ( http://blogs.adobe.com/tlf/2009/02/tlf_api_changes_in_build_370_1.html ).
Here's the list. Maybe this could become a common practice.
Build 432, Fri May 15 2009
Changes in build 437 (2009/05/22)
 * remove flashx.textLayout.edit.UndoManager and flashx.textLayout.IUndoManager
 * Fix 2330964 BackgroundColor Placed incorrectly from TextLineFactory. Actually was in 436.
 * Fix 2326588 TextContainerManager Does Not Support Background Color
 * Fix 2330946 Remove TextContainerManager.trunctationOptions property
 * Fix 2337918 Please expose the scrollToPosition() API in TextContainerManager
 * Fix 2336672 Preserve selection when switching editingMode in TextContainerManager
 * Setting editingMode to the current editingMode should do nothing in TextContainerManager
Changes in build 436 (2009/05/22)
 * Fix 2331711 TextContainerManager now sends a DamageEvent from setText().
 * Fix 2326543 bug where selection wasn't being extended on mouse drag.
 * add [RichTextContent] metadata to SpanElement and FlowGroupElement mxmlChildren properties
 * Fix 2337740 Flex bug SDK-20964 TCM rcycling bug
 * Partial fix 2330964 background color placed incorrectly from TextLineFactory
 * Remove vestigal experiment with Tables code
 * Fix 2321538. On the Mac, the keyboard shortcuts for cmd-A,C,V,X were not working.
 * Fix 2326543, "drag select of scrolling flows doesn't expand selection".
 * Fix 2329527. Content bounds being reported was slightly different between the factory and TextFlow composer.
 * Fix 2328695 TextContainerManager Stops Receiving FocusIn Events. This is a complete fix - previously this bug was worked around
 * Added TextLineFactoryBase.isTruncated
 * Fix 2315119 - Graphic will be redrawn when link applied.
Changes in build 434 (2009/05/22)
 * Fix 2323921: RichText truncation doesn't work in all cases
Build 432, Fri May 15 2009
Changes in build 432 (2009/05/14)
 * Fixed regression that broke truncation feature
 * Added TextLineFactoryBase.isTruncated
 * Changed text line factory behavior such that scrolling is turned off when truncation options are set
Build 427, Fri May 8 2009
Changes in build 427 (2009/05/07)
 * Fix bug - RTE in computeSelectinIndexInContainer
 * Namespace change -- mxml namespace for TLF was "library:adobe/flashx/textLayout". Now it is: library://ns.adobe.com/flashx/textLayout".
 * Fix bug - Scrolled TextContainerManager Can be Difficult To Create Point Selection
Changes in build 426 (2009/05/06)
 * Fix bug - TextFlow double-deletes text when pressing the backspace or delete key
Build 422, Fri May 1 2009
Changes in build 422 (2009/04/30)
 * API Changes: TextContainerManager now has a getContentBounds function, in place of individual getters for contentLeft, contentTop, etc. ContainerController also now has a getContentBounds function, in place of individual getters. Added functions to TextContainerManager to support custom classes for ISelectionManager and IEditManager (see createSelectionManager and createEditManager).
 * API changes for TextContainerManager:
 o getInteractionManager renamed to beginInteraction(), and added a new function endInteraction() which clients should use after beginInteraction() to signal that they are done with selecting/editing. This tells the TextContainerManager that it can go back to factory mode, which is more efficient.
 o invalidateInteractionManager() removed and replaced with two new functions, invalidateSelectionFormats() which clients should called when SelectionFormats have changed, and invalidateUndoManager which clients should call to change the undo manager.
 * API Changes for InputManager
 o InputManager renamed as TextContainerManager
 o IInputManagerClient removed, now you can subclass InputManager and override its methods
 * API Changes:
 o InputManager
 + damaged property renamed to isDamaged() function
 + focusSelectionFormat renamed to focusedSelectionFormat
 + container retyped to Sprite
 + compositionWidth and compositionHeight removed as constructor parameters, now you need to set the properties on the InputManager you create
 o ContainerController
 + container retyped to Sprite
 o ISelectionManager
 + focusSelectionFormat renamed to focusedSelectionFormat
 o IConfiguration & Configuration
 + focusSelectionFormat renamed to focusedSelectionFormat
 * API Changes:
 o ISelectionManager
 + setSelection deselects if negative numbers are passed in.
 + selectAll removed, you can call ISelection.setSelection() to get the same behavior, if you need to redraw the selection, call ISelectionManager.textFlow.flowComposer.updateAllControllers().
 + flushPendingEvents moved to IInteractionHandler
 + notifyInsertOrDelete moved to IInteractionHandler
 o IUndoManager
 + clear renamed to clearAll().
 + undoLastOperation renamed to undo()
 + redoLastOperation renamed to redo()
 * API Change: SelectionEvent now contains a SelectionState, not an ElementRange; this is much cheaper for us to provide. ElementRange is now tlf_internal. ElementRange.firstLeafPosition renamed to absoluteStart, ElementRange.lastLeafPosition renamed to absoluteEnd.
 * API Change: TextScrap.copyTextScrap renamed to clone.
 * API Changes to InputManager. defaultInputManagerConfiguration renamed to defaultConfiguration. composeToController renamed to compose(), and updateToController renamed to updateContainer().
 * API Changes:
 o ISelectionManager:
 + Event handling functions moved out of ISelectionManager into new interface, IInteractionHandler
 + selectionFormat renamed to currentSelectionFormat
 + selectionState renamed to function getSelectionState()
 + setSelection now takes default parameters to select the entire flow
 + noFocusSelectionFormat renamed to unfocusedSelectionFormat
 o SelectionFormat:
 + blockAlpha reanmed to rangeAlpha
 + blockBlendMode renamed to rangeBlendMode
 + blockColor renamed to rangeColor
 o IEditManager:
 + added get undoManager()
 + added changeElementID()
 + added changeElementStyleName()
 o SelectionManager:
 + activeMark and anchorMark are now private
 + selectionChanged is private
 + setSelectionState is tlf_internal
 o EditManager:
 + stage is private
 + ChangeElementIdOperation renamed to ChangeElementIDOperation
Changes in build 420 (2009/04/28)
 * API change: Removed the misleadingly named and superfluous TextFlowLine.textIndent. Documented and ensured consistent use of TextFlowLine.lineOffset as lhe line's offset in pixels from the appropriate container inset (as dictated by paragraph direction and container block progression), prior to alignment of lines in the paragraph.
 * API change: more changes to the factory classes. ITextLineCreator is now a property of the base class, so instead of passing it in the constructor you construct and then set the property in the factory. bounds property renamed to compositionBounds, and measuredBounds renamed to contentBounds. containerController property is now private.
 * API Change: moved ITextLineCreator interface from the elements package to the compose package.
 * PlainTextExporter is now public and has methods for controlling the paragraphSeparator and whether discretionary hyphens are included in the export. To use it, you can either construct it directly, or via the TextFilter class. Removed the newlineIndicator string from IConfiguration.
 * Fixed a bug where tabs in RTL text were being being offset by textIndent and marginRight values.
Changes in build 419 (2009/04/24)
 * Once a mouseWheel event has been handled, mark with preventDefault so client applications don't also try to handle it.
 * Don't start compose if text is already composed. Optimization for callers of composeToPosition.
 * Always call resetContentTopLeft, to give more accurate top left positions, particularly for cases where the text is outdented and left aligned.
 * API CHANGE: TextLineFactory revised. It is now split into 3 classes, TextLineFactoryBase, StringTextLineFactory, and TextFlowTextLineFactory. Use StringTextLineFactory for creating TextLines from a String. Use TextFlowTextLineFactory for creating TextLines from a TextFlow. Static methods have been removed, so create a new factory in order to create lines. One factory may be reused many times, just resetting the values (text, bounds, truncation options, etc.) in between. See StaticHelloWorld.as for a simple example of how this works for Strings, see StaticTextFlow.as for a simple example of it with TextFlows.
Build 418, Fri Apr 24 2009
Changes in build 418 (2009/04/23)
 * API CHANGE: TextLineFactory revised. It is now split into 3 classes, TextLineFactoryBase, StringTextLineFactory, and TextFlowTextLineFactory. Use StringTextLineFactory for creating TextLines from a String. Use TextFlowTextLineFactory for creating TextLines from a TextFlow. Static methods have been removed, so create a new factory in order to create lines. One factory may be reused many times, just resetting the values (text, bounds, truncation options, etc.) in between. See StaticHelloWorld.as for a simple example of how this works for Strings, see StaticTextFlow.as for a simple example of it with TextFlows.
Changes in build 417 (2009/04/22)
 * Fixed Vertical Justification behavior; it now increases the spacing between consecutive lines proportionally rather than spacing lines uniformly.
 * API Changes: Renamed DisplayObjectContainerController to ContainerController, and removed IContainerController and IInternalContainerController. Wherever you used to use "IContainerController" or "DisplayObjectContainerController" now just use "ContainerController".
 o Moved some functions that were public into the tlf_internal namespace: effectivePaddingLeft, effectivePaddingTop, effectivePaddingRight, and effectivePaddingBottom.
 o ColumnState.createColumnState removed. A ColumnState constructor now takes all the relevant values, so whereever you used to do this:
 + var columnState:ColumnState = ColumnState.createColumnState(...your values here...);
 o you can now do this:
 + var columnState:ColumnState = new ColumnState();
 o ColumnState.getColumnAtIndex(index) has been renamed to getColumnAt(index). So, once you have the columnState, you do, for instance:
 + var columnRect:Rectangle = getColumnAt(0);
 * Fixed bug where spaces at end of a line would "overflow" into neighboring columns. New code keeps drawing of cursor at the column boundary and limits block selection drawing to the same bounds.
 * Enhancement to cursor navigation for Right to Left text systems. Previous code moved cursor according to logical order vs. visual order. Result was that a right arrow key press in Arabic, Hebrew or other RTL languages meant that the cursor actually moved left. New code moves cursor according to the visual order of the text based on the direction of the entire text flow. Note that changing the direction on a paragraph will not alter the behavior of the cursor, nor will the presence of LTR text within a RTL text flow. This means that if a TextFlow is set to Right to Left and a given paragraph is entirely in English and the paragraph is set to be Left to Right, the cursor will seem to move in the wrong direction. TLF does not support customization of cursor movement based on the locale or direction of anything except the parent TextFlow.
 * Fixed a bug that caused undoing an ApplyFormatToElementOperation to have no effect.
 * API Changes:
 o DisplayObjectContainer event handling functions renamed:
 + processMouseOverEvent -> mouseOverHandler
 + processMouseOutEvent -> mouseOutHandler
 + processMouseWheelEvent -> mouseWheelHandler
 + processMouseDownEvent -> mouseDownHandler
 + processMouseUpEvent -> mouseUpHandler
 + processMouseMoveEvent -> mouseMoveHandler
 + processMouseDoubleClickEvent -> mouseDoubleClickHandler
 + processFocusInEvent -> focusInHandler
 + processFocusOutEvent -> focusOutHandler
 + processActivateEvent -> activateHandler
 + processDeactivateEvent -> deactivateHandler
 + processKeyDownEvent -> keyDownHandler
 + processKeyUpEvent -> keyUpHandler
 + processTextInputEvent -> textInputHandler
 + processContextMenuSelectHandler -> menuSelectHandler
 + eventHandler -> editHandler
 o ISelectManager & SelectionManager & EditManager renamings:
 + eventHandler -> editHandler
 * API Changes: renamed IContainerController.scrollLines to getScrollDelta, renamed InputManager.scrollLines to getScrollDelta, and removed constants for default container width and height.
Changes in build 412 (2009/04/10)
 * API CHANGE: DisplayObjectContainerController methods processCopyEvent, processCutEvent, processPasteEvent, processSelectAllEvent collapsed into a single processEvent that handles all these basic events. Added to ISelectionManager a new function, processEvent for handling these same events in the SelectionManager, and removed processSelectAll, which is no longer used. cutTextScrap and pasteTextScrap moved from ISelectionManager to IEditManager, since these are editing operations.
Build 411, Fri Apr 10 2009
Changes in build 411 (2009/04/09)
 * Fixed a bug where noFocus selection format was not being set on re-activation
 * API CHANGES. These functions in IFlowComposer were renamed:
 o updateContainer -> updateToController
 o updateAllContainers -> updateControllers
 o composeContainer -> composeToController
 o composePosition -> composeToPosition
 * API CHANGE: Changing name of TextFlow.hostTextLayoutFormat to hostFormat
Changes in build 410 (2009/04/08)
 * Fix bug where leading info used for composing the next line was being saved prematurely, causing incorrect layout if the current line needed to be composed in multiple passes.
Build 409, Tue Apr 7 2009
Changes in build 409 (2009/04/07)
 * Fix bug where clicking on container when height or width NaN doesn't work. When measuring, transparent hit detect region wasn't being redrawn to correct size after composition.
 * API CHANGE: Plain-text import/export changes. Newline indicators exported based on setting in IConfiguration.newLineIndicator. On import, LF/CR/CR+LF are all recognized as new line indicators.
 * Compose to container size with scrolling on -- previously was composing to double composer size. This may flush out some invalid line bugs.
 * Fixed a bug with blockProgression="rl" and compositionWidth=NaN, lines were getting improperly clipped out so that no text appeared.
 * API CHANGE: Renaming functions in IFormatResolver. invalidateAllTargets is now invalidateAll, and invalidateTarget is now invalidate. resolveTextLayoutFormat is now resolveFormat.
 * API CHANGE: eventMirror on FlowLeafElement and SubParagraphGroupElement is now tlf_internal.
 * API CHANGE: Moving TextRange from the edit package to the elements package.
Changes in build 406 (2009/04/02)
 * API CHANGE: Renaming DamageEvent.damageStart to damageAbsoluteStart.
 * API Change: IConfiguration.includePartialLine renamed to overflowPolicy. Defined new class OverflowPolicy that describes the different policies that can be used to control whether lines that fall at the end of the container are included in the container, or not.
Changes in build 405 (2009/04/01)
 * API CHANGE: IFlowComposer.firstDamagePosition renamed to damageStartPosition.
 * API CHANGE: Rename GeometryUtil.getRangeBounds to GeometryUtil.getHighlightBounds.
 * API CHANGE: ParagraphElement.getText now takes an additional optional parameter that specifies the terminator for the paragraph. By default, this is the Unicode paragraph terminator character (\u2029), but you can make it whatever you want, including a simple newline by passing a String for the paragraphTerminator. This change is backwards compatible for current callers of getText().
 * Fix clipping problem when text is placed above the container (6 lines aligned verticalAlign = bottom in a space that fits 4 lines).
Changes in build 404 (2009/03/31)
 * Updating typgraphic case --Markup and API Change-- Now uses a new class TLFTypographicCase, and has different options. Support for "title" and "caps" dropped. Use TLFTypographicCase with TLF in preference to flash.text.engine.TypographicCase. "smallCaps" renamed to "capsToSmallCaps". "capsAndSmallCaps" renamed to "lowercaseToSmallCaps". Also made AUTO the default setting for kerning, which matches FXG spec.
Changes in build 403 (2009/03/30)
 * format Markup Changes:
 o <TextLayoutFormat> now <format>
 o When referring to a format id, don't use brackets. So this:
 <TextLayoutFormat id="english" locale="en" fontFamily="Minion Pro"/>
 This text is supposed to be in Minion Pro via a named character attribute
 Is now this:
 <format id="english" locale="en" fontFamily="Minion Pro"/>
 This text is supposed to be in Minion Pro via a named character attribute
 * API Changes:
 o Rename FlowElement.textLayoutFormat -> format
 o Rename FlowElement.computedTextLayoutFormat -> computedFormat
 o Rename IContainerController.textLayoutFormat -> format
 o Rename IContainerController.textLayoutFormat -> computedFormat
 o Rename DisplayObjectContainerController.textLayoutFormat -> format
 o Rename DisplayObjectContainerController.textLayoutFormat -> computedFormat
Changes in build 402 (2009/03/27)
 * verticalAlign of "middle" or "bottom" will now align to the compositionHeight (or compositionWidth in vertical text) even if the height of the text exceeds the compositionHeight. This means that lines that don't fit may be get pushed above the box, or (for middle) pushed both above and below. It also means that all lines will forced to compose to the end, so it will be quite slow to use verticalAlign in large text flows. Made some corresponding fixes to scrolling to make it work with text off the start of the container. Added some new test cases to exercise this functionality in all the different alignment settings.
 * Scrolling fixes for next/previous line with arrow keys. Fix a bug where the arrow key would move to the end of the line if the line required composition (e.g., the line was not previously in view). Also fixed a bug when scrolling up by a line where it would scroll down instead.
 * doOperation used to return an SelectionState, but with the exception of two places that were using it internally, all external callers only checked to see if it was null or not. null was being used to indicate failure, or nothing changed, which means that the operation is not placed on the undo stack. Now it returns a Boolean, true for success, false for failure. There may be further changes in this area to make FlowOperations simpler.
Changes in build 397 (2009/03/20)
 * Made DisplayObjectContainerController's and FlowElement's TextLayoutFormat properties read/write (used to be write-only).
 * Merge ContainerControllerBase class into DisplayObjectContainerController.
 * Mark TextFlow class as final
Changes in build 396 (2009/03/19)
 * Fix RTE in StandardFlowComposer.releaseLines
 * Fix possible source of the RTE on null reference from findFirstAndLastVisibleLines in ContainerControllerBase.
Changes in build 394 (2009/03/17)
 * Fix issue with changes made in StatusChangeEvent to embedded graphics by blocking recursive composition. Bug 2298043
 * Add IFlowComposer.composeInProcess property.
 * Fixed problem where first part of a link could not be replaced by a new link. New code allows partial replacement of a link element with a selection which starts at the first character.
 * Fixed a problem where the cursor was getting set to the I-beam, and wouldn't set back.
Changes in build 393 (2009/03/16)
 * Fix a bug where keyboard navigation with linked containers was causing a scroll because it was trying to scroll to a position not in the container.
Changes in build 392 (2009/03/13)
 * Removed optimization that was preventing scrolling in the logical width direction if scrolling in the logical vertical direction was turned off.
 * Removed the container-level mouseMove and rollOver handlers which were changing the link state. These are now part of the LinkElement, and added only when they are needed.
Changes in build 390 (2009/03/11)
 * Fix for application of attributes to a point selection where only the last attribute would be applied. New code applies all attributes applied to the point.
 * IContainerController.contentWidth (or contentHeight in vertical text) is now based on the actual text width, not the unjustified text width. This fixes some problems where scrolling wasn't working correctly because the reported width of the text was greater than the compositionWidth, but lines were wrapped. It does mean that to get the unjustified width you will have to set the textAlign to something other than "justify", recompose, and then get the resulting width.
 * Fix for unintended scroll when at the end of a TextFlow.
 * Fix for RTE when dragging over text generated from a factory, or non-TLF TextLines.
 * Changes for alignment and measurement. You can now set NaN for compositionWidth or compositionHeight, and TLF will compose and use the generated contentWidth or contentHeight for alignment, scrolling, etc. The composer now generates a topLeft for the bounds, so you can make a full "content bounds" using contentLeft, contentTop, contentWidth, and contentHeight.Note that this is logical bounds and not inked bounds, so there are some circumstances where ink will not fit in the content bounds.Fixed bugs in how the factory was doing vertical alignment that caused it to be a few pixels off.Fixed some incosistencies between how the standard flow composer worked and how the factory's simple composer works -- composition results should now be more uniform. Added a new test program, MeasurementGrid, for testing all this. It's still a work in progress.
Changes in build 388 (2009/03/09)
 * Fixed issue where applying link or TCY to the last span of a paragraph caused a dangling span to remain with the para terminator.
 * Fixed issue where text would go into a link when it was the last element in a paragraph. Newly typed text now goes into a new span when the selection marker is at the last index.
Changes in build 386 (2009/03/06)
 * Fixed issue with placement of underline and strikethrough on inline images.
 * Fixed placement of underline and strikethrough on text which has a baseline shift applied to it.
Changes in build 385 (2009/03/04)
 * Combined SWC 'textLayout.swc' now included in the libs directory of the build. This includes everything from textLayout_core, textLayout_edit, and textLayout_conversion.
 * Combined RSLs now included in the rsl directory of the build. Both an unsigned SWF and signed SWZ are created. These include everything from textLayout_core, textLayout_edit, and textLayout_conversion.
Changes in build 382 (2009/03/02)
 * Fix issue with composing a TextFlow containing just an empty ParagraphElement.
 * TextLineFactory will generate lines that included InlineGraphics whose source is a "class" - normally an embedded graphic.
 * Expose eventMirrors - use FlowElement.getEventMirror function to access the eventMirror.
Changes in build 381 (2009/02/27)
 * Fixed issue with graphic assigned to ILG getting the wrong sizing.
 * Factory instance functions renamed to textLinesFromString and textLinesFromTextFlow. Static functions renamin unchanged.
Changes in build 380 (2009/02/26)
 * Made backgroundColor work with TextLineFactory. This required an API change - the callback to the factory now must take a DisplayObject as its parameter, since it won't always be passed TextLines. Also, the background shapes themselves no longer include leading, so they do not exactly coincide with the selection bounds. This was another change to support calculating the shapes during composition as opposed to afterward. Also added a snapshot test as part of FactoryImportTest that uses backgroundColor, in addition to updating the existing unit tests.
Changes in build 379 (2009/02/25)
 * Fixed for multiple containers ( we were getting incorrect textLength in the containers), as well as a fix that forces scrollToPosition to compose if the text isn't composed yet.
 * Fix so that we scroll to the active position of the selection after we extend the selection with a keyboard event. Also fixed some of the TextRangeUtil functions used for nextLine, etc. to make sure text is composed through selection before processing that depends on composition results.
 * Plain text import now consistently converts \r to space; previously it was converting only the first one. Still not clear what correct behavior should be.
Changes in build 377 (2009/02/23)
 * Fix bug with importing trailing empty div elements.
Changes in build 374 (2009/02/18)
 * Added support for TextField-style leading. A new leading model value allows lineHeight to be interpreted as the distance of line's ascent from the previous line's descent. Further, lineHeight can be negative. which specifies the criteria for truncation, the string used to indicate truncation and the format for this string.
Changes in build 372 (2009/02/16)
 * Added "enableAccessibility" property to IConfiguration, defaults to false. Allows clients to avoid paying price for TextAccImpl objects unless needed.
 * Added support for truncation for text composed using TextLineFactory. The TextLineFactory methods now take a truncation options parameter, which specifies the criteria for truncation, the string used to indicate truncation and the format for this string.
Changes in build 371 (2009/02/13)
 * Fixed a number of bugs relating to scrolling by line.
 * Measurement changes. Changed the way contentHeight and contentWidth are calculated, now they reflect the size of the text, regardless of alignment. Eliminated unjustifiedContentHeight and unjustifiedContentWidth; use contentHeight and contentWidth instead.
 * Fix RTE in damage when we try to damage back one line, for textFlow that doesn't have any leaf nodes.
 * Changed InlineGraphicElement so that GraphicElements (and the TextBlocks they are part of) don't get released. Fixes RTE on null pointer in places where we access the GraphicElement.
 * Fix bug deleting all of the last Span of a paragraph, plus some of the following paragraph.
Changes in build 370 (2009/02/12)
 * Removed textFlow property from CompositionCompletionEvent. Use event.target to get to the TextFlow.
Changes in build 369 (2009/02/11)
 * Fix issues in usage of hostTextLayoutFormat
 * Fix FXG export to not export styles with value "inherit"
 * lineBreak property no longer inherits by default
Changes in build 368 (2009/02/10)
 * Fix for RTE that happens after cancelling an operation (calling preventDefault on a FlowOperationEvent).
Changes in build 367 (2009/02/09)
 * ported to Flex 4.0.0.4836. All SWCs now build with this SDK.
Changes in build 366 (2009/02/06)
 * FlowGroupElement addChild, addChildAt and replaceChildren methods now automatically delete new elements from any existing parents. Previously the code would test for parent on new elements and throw.
 * mxmlChildren FlowElement property which is normally used for mxml compilation of TextFlow objects now always deletes existing children
 * Fix a memory leak issue with the TextLayoutFormat cache
 * Fix cascade bug with non-inheriting attributes getting inherited
Changes in build 365 (2009/02/05)
 * Changed TextLayoutFormat.backgroundColor to allow setting value of "transparent" (now the default). Because of this new value for backgroundColor, backgroundAlpha now defaults to 1.
Changes in build 364 (2009/02/04)
 * Performance improvement for handling of TextFlow.hostTextLayoutFormat. The code now assumes that once set by the client the supplied object won't be changed. This avoids a copy.
Changes in build 363 (2009/02/03)
 * Performance work. Remove getCanonical from TextLayoutFormat.
 * Fix for RTE cancelling SplitParagraphOperation.
 * Fixing some float bugs.

Try searching discussions--see: http://discussions.apple.com/thread.jspa?threadID=684662
only caveat is link is dated-I googled for newer...
MacBook Pro 17" Mac mini (Intel) Mac OS X (10.4.8)

Server 2012 R2 RDS Personal Collection -reuse VM names after a partial job failure

I am currently testing RDS on server 2012 R2, and as part of the test I have built and rebuilt multiple collections of VMs. I have noticed that when creating a new JOB to build a personal collection, sometimes I get VM build failures on one host. The build
failures are usually due to a networking issue, which I then resolve, but when I go to add/create the VMs that failed, the name of the VMs increment from the last VM, and they don't re-use the failed names. I want to be able to reuse/build the VMs that
failed.
eg.
VM-01, VM-02, VM-03 - On HOST-01 all work
VM-04, VM-05, VM-06 - On HOST-02 fail
VM-07, VM-08, VM-09 - On HOST-03 all work
So on this example, when I re-run the job to build the missing/failed VMs, it would build VM-10, VM-11, VM-12 on HOST-02.
Is there a way to reset, or reuse the failed VM names, in the example above that would be VM-04, VM-05, and VM-06?
Thanks

Hi,
Thank you for posting in Windows Server Forum.
For a try you can use powershell command for RD VDI infrastructure.
New-RDVirtualDesktopCollection -CollectionName "ITCamp" -PooledManaged -StorageType CentralSmbShareStorage -VirtualDesktopAllocation 5 -VirtualDesktopTemplateHostServer $VHost -VirtualDesktopTemplateName $VDITemplateVM -ConnectionBroker $RDBroker -Domain “contoso.com”
-Force -MaxUserProfileDiskSizeGB 40 -CentralStoragePath”\\fileserver1\NormalVMs” -VirtualDesktopNamePrefix "ITC" -OU “VDICampUsers” -UserProfileDiskPath \\fileserver1\NormalProfiles
More information.
Lab Ops 7 – Setting up a pooled VDI collection in Windows Server 2012 R2
http://blogs.technet.com/b/andrew/archive/2013/10/28/lab-ops-4-windows-8-1-windows-2012r2-vdi.aspx
Also check that when setting up RDS, there needs to be a Physical NIC with IP for the creation of a RDS vSwitch. If this vswitch does not exist, the creation of the MV's will fail.
Hope it helps!
Thanks.
Dharmesh Solanki

How do I reuse a custom java control in another project?

Relatively simple question, but I am having a lot of trouble with this. Documentation
alludes to this being possible and easy, but never says how (and the only tutorials
I can find describe creating a custom java control in the same project where they
are used):
"You can design a custom control for use in one project, or you can design a custom
control for easy reuse in multiple projects." (from WLS docs on Java Controls)
"When the control project builds, all of the controls and associated files are
compiled into a single jar file and pushed onto the classpath of the containing
application for immediate use and testing by other projects in the application.
This jar is self-contained and can be moved to any other application by adding
it to the application’s Library folder. Appropriately marked controls in the Library
it will automatically appear on the user’s palette, ready for incorporation into
an application." (from dev2dev article on controls, P. Hussey)
I have a Workshop application which contains a few projects. One project is a
component project, another is a web project. I created a custom java control in
the control project and built it (JAR appeared in the Libraries folder). Now I
open up the page flow in my web app project, and try to drag the java control
onto my page flow - but I get an eror that the control must reside in the same
project! It does not automatically appear on my palate, so if I go over to the
palate on the right, and try to "add control" I only get a list containing the
BEA controls - no custom controls are listed.
What am I doing wrong? How can I incorporate my custom control into a web project?
I don't want to move the control in the web project, since this contradicts the
concept of a separate shared library. I should be able to build a library of controls
and reuse them in our web projects right?
-Bob

Please disregard... I got it to work. For some reason I had to close Workshop,
restart it, then I reloaded the application, rebuilt the control project, and
now my control appears in the list of controls and can be easliy added to the
palette.
"Bob" <[email protected]> wrote:
>
Relatively simple question, but I am having a lot of trouble with this.
Documentation
alludes to this being possible and easy, but never says how (and the
only tutorials
I can find describe creating a custom java control in the same project
where they
are used):
"You can design a custom control for use in one project, or you can design
a custom
control for easy reuse in multiple projects." (from WLS docs on Java
Controls)
"When the control project builds, all of the controls and associated
files are
compiled into a single jar file and pushed onto the classpath of the
containing
application for immediate use and testing by other projects in the application.
This jar is self-contained and can be moved to any other application
by adding
it to the application’s Library folder. Appropriately marked controls
in the Library
it will automatically appear on the user’s palette, ready for incorporation
into
an application." (from dev2dev article on controls, P. Hussey)
I have a Workshop application which contains a few projects. One project
is a
component project, another is a web project. I created a custom java
control in
the control project and built it (JAR appeared in the Libraries folder).
Now I
open up the page flow in my web app project, and try to drag the java
control
onto my page flow - but I get an eror that the control must reside in
the same
project! It does not automatically appear on my palate, so if I go over
to the
palate on the right, and try to "add control" I only get a list containing
the
BEA controls - no custom controls are listed.
What am I doing wrong? How can I incorporate my custom control into a
web project?
I don't want to move the control in the web project, since this contradicts
the
concept of a separate shared library. I should be able to build a library
of controls
and reuse them in our web projects right?
-Bob

Spliting a Message to reuse an Integration Process made for a single one.

Hi,
I have a Integration Process that works well for a XML message of the type:
<EMESSAGE>
<PERSON>
 <TAG_1>
 <TAG_2>
</PERSON>
</EMESSAGE>
My BPM process the data for the Person correctly.
Now I want to be able to tried more than one person per input message, some thing like:
<EMESSAGE>
<PERSON>
 <TAG_1>
 <TAG_2>
</PERSON>
<PERSON>
 <TAG_1>
 <TAG_2>
</PERSON>
<PERSON>
 <TAG_1>
 <TAG_2>
</PERSON>
</EMESSAGE>
I build a 1:n Interface Mapping that creates me the following structure:
<Messages>
<Message1>
<EMESSAGE>
<PERSON>
 <TAG_1>
 <TAG_2>
</PERSON>
</EMESSAGE>
</Message1>
<Message2>
<EMESSAGE>
<PERSON>
 <TAG_1>
 <TAG_2>
</PERSON>
</EMESSAGE>
</Message2>
<Message3>
<EMESSAGE>
<PERSON>
 <TAG_1>
 <TAG_2>
</PERSON>
</EMESSAGE>
</Message3>
</Messages>
But when I use a ForEach Block in my new BPM, it doesn't work if there is more then 1 person in the input. The error message I got is:
<?xml version="1.0" encoding="utf-8" ?>
- <MappingTrace>
<Trace level="1" type="T">Mapping-Namespace:http://domain.com/xi/domain_4</Trace>
<Trace level="1" type="T">Mapping-Name:IM_CPM_AbsSync_to_N_CPM_AbsSync</Trace>
<Trace level="1" type="T">Mapping-SWCV:3E235261F43111DDB40AC952C0A80C15</Trace>
<Trace level="1" type="T">Mapping-Step:1</Trace>
<Trace level="1" type="T">Mapping-Type:XSLT</Trace>
<Trace level="1" type="T">Mapping-Program:CPM_to_N_ContextPersonMessage</Trace>
<Trace level="3" type="T">Mapping has one input message.</Trace>
<Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
<Trace level="3" type="T">Multi mapping required.</Trace>
<Trace level="3" type="T">Creating XSLT mapping CPM_to_N_ContextPersonMessage.</Trace>
<Trace level="3" type="T">Load 3e235261-f431-11dd-b40a-c952c0a80c15, http://domain.com/xi/domain_4, -1, CPM_to_N_ContextPersonMessage.xsl.</Trace>
<Trace level="3" type="T">Search CPM_to_N_ContextPersonMessage.xsl (http://domain.com/xi/domain_4, -1) in swcv 3e235261-f431-11dd-b40a-c952c0a80c15.</Trace>
<Trace level="2" type="T">Call XSLT processor with stylsheet CPM_to_N_ContextPersonMessage.xsl.</Trace>
<Trace level="2" type="T">Returned form XSLT processor.</Trace>
<Trace level="3" type="T">XSLT transformation: CPM_to_N_ContextPersonMessage.xsl completed with 0 warning(s).</Trace>
<Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
<Trace level="1" type="T">Content Type application/xml</Trace>
<Trace level="1" type="T">No interface specified for parameter 2</Trace>
</MappingTrace>
Does someone have any idea or a suggestion on how to reuse my BPM that works for a single person?
Thanks in advance for your suggestions.
greg

ok no success for the moment, so I will try to describe my BPM more precisely:
The DT I use can contain up to 1'000 PERSON record inside a unique EMESAGE reccord (the root element)
My containers: (all are of type Abstract Interface of my DT)
Input (Process)
requestList(Process) Multiline
request(block)
response(block)
Receive Request Step
Message: input
Start Process: Yes
Mode : Async.
Split (Transformation) Step
IM: My Interface that does the 1Message with N PERSON records to N Messsages with 1 PERSON record
Create new transaction: Yes
Source: input
Target: requestList
Block Step
Mode: ForEach
Block Start: New transaction
Block End: New transaction
Multiline_Element: RequestList
CurrentLine: request
No end condition
Inside the block
My Sync Send call to a BAPI
Source: request
Target: response
A final Async Send step
Message: response.
The workflow stop at the Transform step, as if hte fact that many messages come in result could not be handled back. Here are the details for the Interface mapping used in the transformation step:
Source: MyDataTypeAbstractAsynchroneInterface
Occurrence: 1
Destination:
Occurrences: 0:unbounded
Mapping program: the following XSLT:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
 <xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>
 <xsl:template match="EPERSON">
 <ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
 <xsl:for-each select="CONTEXTPERSON">
 <xsl:element name="ns0:Message{position()}">
 <EPERSON xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="ContextPersonMessage">
 <xsl:element name="CONTEXTPERSON">
 <xsl:attribute name="personid"><xsl:value-of select="@personid"/></xsl:attribute>
 </xsl:element>
 
 </EPERSON>
 </xsl:element>
 </xsl:for-each>
 </ns0:Messages>
 </xsl:template>
</xsl:stylesheet>
Still any suggestions ?
The trace of the error is the same as before, so I won't copy paste it again.

How to reuse a centrally stored Canonical Datamodel

Hello,
For a client we are placing the Canonical Data Model, containing all cross domain message definitions, in a central location.
The XSD definitions are reachable with a URL, for instance http://localhost:7001/CDM/Relatie.xsd
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://www.test.nl/poc/relatie"
targetNamespace="http://www.test.nl/poc/relatie"
elementFormDefault="qualified">
I create a WSDL and add the following lines of code
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.test.nl/poc/relatie">
<xsd:include schemaLocation="http://localhost:7001/CDM/Relatie.xsd"/>
</xsd:schema>
In the Structure pane the following Warning appears 'Remote schema not loaded'
In the WSDL I am not able to use the content of the XSD,
for instance add a namespace reference
xmlns:wfnpr="http://www.test.nl/poc/relatie"
Then create a message
<message name="RealtieService_relaties">
<part name="part" element="wfnpr:relaties"/>
</message>
Also results in a Warning 'Reference wfnpr:relaties not found'
When I copy the XSD in my project, it all works ok. But that's not the idea of having a centrally based CDM.....
Who's got ideas?
Regards Léon Smiers

I also have a similar interest. I am not sure that having the Schema sit on a webserver is the best approach, there must be others (which I cannot work out yet).
It is very important to distribute a common Schema such that if there is a change you don't have to go into each and every JDeveloper project, delete the old XSDs and cut and paste the new ones.
There needs to be a central store for the canonical XSDs. The client projects needs to reference this central store and at build time and possibly drawn them into the deployment archive.
I cannot see how this can be done though.
To give another view on this consider that XMLSchema.xsd is accessed in a common way in JDeveloper. I don't need to import it to use it. I can use xsd:string whenever I want. All I need to do is define the namespace i.e. xmlns:xsd="http://www.w3.org/2001/XMLSchema".
Importantly this isn't actually looking the schema up on the web. If I unplug my network cable JDeveloper still sees this Schema because it is actually defined somewhere in the libraries that JDeveloper is using.
However all this doesn't help me much. I am still completely stumped in how to centrally store and reuse a CDM effectively.
Edited by: user10103872 on 20-Jan-2012 09:25

How to reuse a Joomla database?

Client wants to have a BC site, but the info from the current site is in Joomla. How can I build them a site besides the 4 main html pages? Can the database be reused from the Excel file?
Rather use Dreamweaver than Joomla any day.

Hey there.
Bit confusing post there but will try help on this..
Dreamweaver is a programing tool to code websites or applications with. Joomla is a CMS - Content Mangement system. Adobe Business Catalyst is the BC CMS (more then just a cms).
You can choose to develop BC sites on Dreamweaver or other applications like Coda2, Sublime Text 2 etc.
Best thing to do is not just try copy their old site, likely lots of issues, badly made, strange things etc. Rebuild, do it right, web standards, work to help improve the online business. etc
But if you export their customers from joomla into an excel spreadsheet you can download the import spreadsheet from BC for the CRM and get the content into the format BC needs from the joomla one and then import.
Joomla addons, custom PHP code etc of course wont run on BC.
Hope that helps.

Flash Builder 4.5 Java Heap Space Error

Hello everyone,
I've downloaded Flash Builder 4.5 trial a few days ago. Let me first tell that I like the new features a lot and they help to speed up the development process noticably. I thank Adobe for that very much.
However I did not notice any performance boost over the Flash Buidler 4. Even worse, the 4.5 version seems to run much slower and use more memory than Flash Builder 4. I constantly keep getting Java Heap Space errors and needles to say, the tool just crashes and I have to restart it.
Here how my experience working with the new version looks like. I start the Flash Builder 4.5 which has my current project open (for the record, I still use Flex 4.1, and the project includes roughly 300+ classes and 30000+ lines of code (AS and MXML)). At the beggining everything works fine and pretty fast. UI, code completion, snippets and all other good stuff works pretty fast. However, after each build, FlashBuilder.exe process eats up from 50 to 100 megabytes of memory and does not seem to release it or reuse it. So after a 5 or 10 builds it already appears to be using over 1 GB of RAM. At that point the editor becomes sloppy - it can't keep up with my typing, code completion popups takes a few seconds to show up. And a few more builds - the Flash Builder freezes and after a minute or two I get Java Heap Space error.
I've tried increased the JRE heap space used by the Flash Builder (flashbuilder.ini, flashbuilderc.ini, eclipse.ini) to -Xms512m -Xmx1024m as well as permanent generation heap space to -XX:MaxPermSize=512m -XX:PermSize=256m and the mxml compiler (jvm.config) to -Xms384m -Xmx768m. However this did not solve the problem. Maybe just postponed it a bit.
Am I the only one observing such behaviour of Flash Builder 4.5? Does any one have any other ideas how to fix this? (by the way, I work on 64bit machine with Widnows Server 2008R2, 4GB of RAM and 2.66 GHz Intel Core 2 Duo).
Thanks in advance.
Michael

I'm seeing nearly the same thing. I also have a very large set of projects similar to what you are describing and I do have Java Heap Space errors (The details show an error of "java.lang.OutOfMemoryError: unable to create new native thread" occurring for me)
I had similar issues, although they are more frequent in the 4.5 builder, in the 4.1 builder. In 4.1 builder, I didn't get the exact same detailed error regarding threads.
I did install my flash builder into a clean instance of eclipse 3.6.2 vs using the standalone install. That shouldn't make a difference though. In 4.1, I tried he standalone install and saw the same issues I saw in the plugin version.
I'm also using the 4.1 SDK in Flash Builder 4.5 (It appears that is what you are doing). I've been attributing the crashes to the following bug in the 4.1 SDK, although I have applied the files in the bug report and still have the problem. I'm hoping when I'm able to switch to the 4.5 SDK it may help. (I can't switch yet because from what I can tell, it requires 10.2 Flash Player and my company is currently only on 10.0)
The Bug Report I'm referring to is: https://bugs.adobe.com/jira/browse/SDK-26366
I've bumped up all of the memory settings you've referred to and it helps the environment run longer, but it still eventually crashes. One thing I definately do is make sure that the "Build Automatically" is unchecked.
The machine I'm running on is an Intel 2600K with 16GB of memory running Windows 7 64-bit, so I don't think hardware is the issue.
No real answer, but your not alone in having similar issues.
Jon

Build configuratino reuse

Similar Messages

Maybe you are looking for