Namespace change

Hi All,
The WSDL generated by OPA has the default namespace of http://oracle.com/determinations/server/10.4/rulebase/assess/types.
I needed to change the namespace to a custom value like http://<service_name>/<version_number>.
The velocity template uses ${service.getTargetNamespace()} as the method to get the namespace value.
The source code uses the interface NativeService.java which has the method getTargetNamespace() defined in it.
How can we override it, to use a custom namespace.
Thanks.

Suraj,
You could try changing the namespace in the OnReturnResultEventHandler but I would not recommend changing the namespace at all. As mentioned previously namespaces have very specific meanings and you probably should not do it.
You could also just change the assess velocity template and replace ${service.getTargetNamespace()} with your specific namespace. Same warnings as above.
Cheers
Frank

Similar Messages

Unexpected namespace change after mapping change

Unexpected namespace change after mapping change
Posted: Apr 18, 2006 5:17 AM Reply
Hi all
We developped a mapping about one year ago on XI SP9.
The source of the message was an Idoc and the target an XML sample (and not a xsd!) of what our customer expected.
Everything was working fine at that point.
Here is an extract of the output we had:
<?xml version="1.0" encoding="UTF-8" ?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/">
<env:Header xmlns:p="http://localhost/webs/msgDetails.xsd">
<p:msgDetails xmlns:p="http://localhost/webs/msgDetails.xsd">
<p:sender>
<p:senderId>XXX</p:senderId>
<p:senderName>AUSTRALIA/NEW ZEALAND</p:senderName>
</p:sender>
We are now running SP14 and we had to change the mapping. Since we changed it the namespaces defined in the sample XML we use as a target structure are not used anymore, instead they are replaced by ns0, ns1...
Now the output looks like this:
<?xml version="1.0" encoding="UTF-8" ?>
<ns0:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns0="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://www.w3.org/2001/XMLSchema-instance" ns1:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/">
<ns0:Header>
<ns2:msgDetails xmlns:p="http://localhost/webs/msgDetails.xsd" xmlns:ns2="http://localhost/webs/msgDetails.xsd">
<ns2:sender>
<ns2:senderId>21873</ns2:senderId>
<ns2:senderName>XXX</ns2:senderName>
</ns2:sender>
Any idea what has happened here?
Thanks in advance
Gregory

Hi Gregory,
after a short view I would say that the two structures you have posted are logically equivalent.
I try to make it clear for the sender-element.
In the first example you have a tag <p:sender>. Obviously the namespace prefix 'p' is used here. In order to find out the qualified name of the element represented by that tag you have to find the namespace declaration for prefix p. As the tag itself does not contain such a declaration you have to go to the parent-tag. Indeed, here you find a declaration for p which says that p is just an alias for 'http://localhost/webs/msgDetails.xsd'. Hence the qualified name for the element is: 'sender' in namespace 'http://localhost/webs/msgDetails.xsd'.
Now let us look at the corresponding tag <ns2:sender> in the second document. In oder to identify the qualified name of the element you have to find out, which namespace is bound to the namespace prefix ns2 which has been used here. Again you cannot find this in the tag itself but in its parent. Here you find that ns2 is bound to 'http://localhost/webs/msgDetails.xsd'. (Indeed, here you see that prefix p is also bound to that namespace. This seems to be superfluous to me, as the prefix is never used.)
Consequently, the qualified name of that element is: 'sender' in namespace 'http://localhost/webs/msgDetails.xsd'.
Thus, both tags represent elements with the same qualified name. For more details look at http://www.w3.org/TR/REC-xml-names/.
Greetings Stephan

The system and namespace change option

Hi Experts,
I want to integrate a certain SAP Source System within RSA1. After submitting the correct settings for Background User and RFC connection the process leads me to the Source System where I logon with an User which has authorizations in SM59. From there on (the RFC Connection backwards is already defined) I got asked whether I want to user/check/cancel this existing RFC Connection. I click on use, wait for a while and then the error (please see below) appears.
When proceeding with the steps mentioned in the error message (transaction SE03, Administration node, ...) I cannot find any IDOC Object ZSSA009. I think maybe it's related to some software component or somenthing like that which should be set as "modifiable" but I don't know which....
Any Ideas on this?
Many thanks in advance.
Best regards
Tobias
Error Message:
Message no. TO128
Diagnosis
The system and namespace change option set for this SAP System does not allow any changes to be made to object IDOC ZSSA009.
System Response
Editing is terminated, the object can only be displayed.
Procedure
If you want to edit the object IDOC ZSSA009 in this SAP System, have your system administator set the SAP System to "modifiable" for this object.
This can affect the modifiability of the namespace &1 or the namespaces that correspond to the pattern &1, as well as the global setting of the system change option.
The system change option is set using the Transport Organizer tools (Transaction SE03). Expand the Administration node and execute the program Set system change option. The options are described there.

HI,
Attached link may help you in configuring the source system.
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/908836c3-7f97-2b10-4cb8-e6790361c152
Thanks,
Arun

[svn:fx-trunk] 13293: When making the halo - mx namespace changes we missed the following edits in revision 12635.

Revision: 13293
Revision: 13293
Author:   [email protected]
Date:     2010-01-05 17:07:48 -0800 (Tue, 05 Jan 2010)
Log Message:
When making the halo -> mx namespace changes we missed the following edits in revision 12635. The mxml-manifest.xml describes the contents of the legacy Flex 3 MXML 2006 namespace and the presence of this file is required by Flash Builder. The mx-manifest.xml describes the contents of the MX Component Library namespace. From MXML 2009 onwards it does not include the built-in ActionScript types (those are language elements in the MXML 2009 language namespace).
QE notes: N/A
Doc notes: N/A
Bugs:
SDK-24568 - Remove obsolete library://ns.adobe.com/flex/halo mapping from frameworks flex-config.xml and air-config.xml
Reviewer: Kevin
Tests run: checkintests
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24568
Modified Paths:
    flex/sdk/trunk/frameworks/air-config.xml
    flex/sdk/trunk/frameworks/flex-config.xml
    flex/sdk/trunk/frameworks/mx-manifest.xml
    flex/sdk/trunk/frameworks/mxml-manifest.xml
    flex/sdk/trunk/webapps/webtier/WEB-INF/flex/flex-config.xml

[svn:fx-trunk] 5564: New mustella.swc with namespace changes.

Revision: 5564
Author: [email protected]
Date: 2009-03-25 20:24:48 -0700 (Wed, 25 Mar 2009)
Log Message:
New mustella.swc with namespace changes.
Modified Paths:
flex/sdk/trunk/mustella/mustella.swc

[svn:fx-beta1] 7038: Updating Gumbo webtier packaging to take into account the Flash Player 10 requirement , MXML 2009 namespace changes and associated manifests, and new locales.

Revision: 7038
Author:   [email protected]
Date:     2009-05-18 09:31:29 -0700 (Mon, 18 May 2009)
Log Message:
Updating Gumbo webtier packaging to take into account the Flash Player 10 requirement, MXML 2009 namespace changes and associated manifests, and new locales.
QE: Yes, I tried checkintests with the webtier.war distribution and could successfully compile the associated apps. Please test the webtier.war distribution with the larger suite of webtier tests.
Doc: No
Checkintests: Pass
ant package: Successful
Reviewer: Paul
Modified Paths:
    flex/sdk/branches/beta1/modules/webtier/j2ee/coldfusion/build.xml
    flex/sdk/branches/beta1/webapps/webtier/WEB-INF/flex/flex-config.xml
    flex/sdk/branches/beta1/webapps/webtier/build.xml

Xmlanonymizer bean and xslt - both not working for namespace change

Hi All
I have a source structure below
<ns1:Product_MT xmlns:ns1="urn:alpha:websub" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Header>
</Header>
<Item>
</Item>
</ns1:Product_MT>
I am using a soap sender getting called from SOAP UI to consume a PI web service and send the output message to receiver HTTP channel
the receiver needs the namespace of the XML structure as below (ns1 changed to ns)
<ns:Product_MT xmlns:ns="urn:alpha:websub" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Header>
</Header>
<Item>
</Item>
</ns:Product_MT>
I tried to put the xmlanonymizer bean in receiver HTTP but its not doing anything. I am stil getting the output with ns1 namespace
Attached screenshot of receiver http adapter configuration in module
also, I tried to use XSLT mapping as below but this is also not doing anything. Probably, the XSL has to be modified to use in my case . Please help. and let me know.
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:fn="http://www.w3.org/2005/xpath-functions">
<xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>
<xsl:template match="/">
<ns:Product_MT xmlns:ns="urn:alpha:websub">
<xsl:copy-of select="." />
</ns:Product_MT>
</xsl:template>
</xsl:stylesheet>
thx
mike

I had to tweak the XSL little bit to make it work in PI. See updated version below -
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
   <xsl:output encoding="UTF-8" indent="yes" method="xml" version="1.0"/>
   <xsl:variable name="root">MT_Product</xsl:variable>
   <xsl:variable name="rootns">urn:mdt:udiwebsubmission</xsl:variable>
   <xsl:template match="*">
     <xsl:choose>
       <xsl:when test="local-name()=$root">
         <xsl:element name="ns:{local-name()}" namespace="{$rootns}">
           <xsl:apply-templates select="node()"/>
         </xsl:element>
       </xsl:when>
       <xsl:otherwise>
         <xsl:element name="{local-name()}">
           <xsl:apply-templates select="node()"/>
         </xsl:element>
       </xsl:otherwise>
     </xsl:choose>
   </xsl:template>
</xsl:stylesheet>
Regards,
Sameej

Namespace Change at the target

Hi All,
I am doing a Proxy to SOAP scenario. I need to change the namespace of the target WSDL . The mapping works fine but there is a requirement where in I need to change the target namespace. Can some one please help me on this. I want it after message mapping that I can have a change done to the target namespace before sending it to the target.
Any XSLT code which would help in solving this.
Thanks

Do we need to tell the web service team to change the WSDL in such a way that the namespace within the WSDL remains same so that there is no issue when we transport the mappings from Dev to QA.
Better if this is done
I want it after message mapping that I can have a change done to the target namespace before sending it to the target.
you can try to use XMLAnonymizer module to change the namespace
Edited by: abhishek salvi on Jan 17, 2011 5:54 PM

MX Namespace change

Is there something I can change with the nightly builds to automatically create the new mx namespace when one creates an application or component or whatever to use xmlns:mx="library://ns.adobe.com/flex/mx" instead of xmlns:mx="library://ns.adobe.com/flex/halo"?
According to Peter's earlier blog post, the halo namespace is history but it keeps being inserted in every new file I make.
http://blogs.adobe.com/pdehaan/2009/12/the_flex_4_halo_namespace_is_n.html

Oh, duh. As a temporary workaround we can just replace ${xmlns} in the file templates with:
xmlns:fx="http://ns.adobe.com/mxml/2009"
xmlns:s="library://ns.adobe.com/flex/spark"
xmlns:mx="library://ns.adobe.com/flex/mx"

Renamed: Why did my namespace change? soap-env (vs) soapenv

Hello forum. I normally post in the main forum. I hope this is the right place for a SOAP question. I'm sure you'll let me know if it's not.
We have an application which was running fine until last week. The app lives on a machine which is not completely ours (we don't control the environment). This app receives and sends socket messages. Based on the incoming message our outgoing message may be in SOAP or a legacy proprietary format. At the time of transmission we do not know the format of the message.
Our outgoing messages stopped being transmitted. What we found was that there was a bit of logic in our transmitting component which read the first X characters of the message to see if it is a SOAP or legacy message. What we did to determine this was to look for, what we thought was standard "<SOAP-ENV....." It worked for years. (I know there are better ways of doing this and we're working on that now). The problem was that the messages that were failing contained "<SOAPENV...."
Here's the question. The objects which build these messages are called from our messaging app. They should be in the same JVM as the messaging app. The messaging app's SOAP jars have not changed. The JRE was upgraded to 1.3.1_19 from _07. In the messaging app as a test I can build a SOAP message and it still says "<SOAP-ENV...." Where is this other namespace coming from? I decompiled the saaj components and it looks like the MessageFactory makes some calls to the environment to determine the message implementation. Could the problem be here? Has anyone heard of this type of thing happening before or am I just losing my mind.
Thanks as always.
ST
Message was edited by:
souLTower

Possibly I don't understand the SOAP implementation. I'm using the same set of SOAP jars (saaj, commons, logging, etc) as I always did. If these jars did not change could / should the message format change? Is the implementation looking outside of my JVM for this implementation?
As to "why" it matters is that I need to know why something in my code has changed. Imagine, for example, that the implementation of String changed. It may still adhere to the normal implementation of String but if my code expects it to look a certain way and it stops looking that way then my code breaks.
As I said in the original post I have handled the issue that it changed but I can't feel comfortable with the application if I fear that it can change again and break my code.
The question is, if the jars related to SOAP (the normal ones you get from sun, I'll provide the list if needed) have not changed then how can the format of the message change?
Thanks again.
ST

MX component namespace changes

As of SVN trunk revision 12635 the Flex 4 SDK no longer supports the “library://ns.adobe.com/flex/halo” component namespace. MX components should be referenced using the “library://ns.adobe.com/flex/mx” namespace.
e.g.
<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
xmlns:s="library://ns.adobe.com/flex/spark"
xmlns:mx="library://ns.adobe.com/flex/mx">

I have a question regarding theDIRECT BINDING of a string
value to a class name dynamically in Flex.I have to create an
instance of the class based on the String value i get inside a
function,which is like the STRING is same as the ClassName in .But
still Iam unable to instantiate and am failing to convert the
string to he class name. Iwas trying to achieve this but did'nt
find any methos in the API also.
If anyone has got it working can you guz pls help me achieve
it.
Mallik..

Portlet:namespace val changes on server restart. How to keep it constant?

Hi -
I want to generate WinRunner test script, and want to know the IDs of a couple of UI components on a JSF JSP.
But JSF prefixes each component id with <portlet:namespace/> value. So, I tried to prefix the same value (got it using view source of the actual screen to test) to the components in my test script.
This works just fine, the way I want it to, but until the server is not restarted.
Once the server is restarted the value of the <portlet:namespace/> changes (for the same view in same jsp), thus my test script doesn't work.
Is this expected behavior that for the same view in jsp, the value of <portlet:namespace/> changes after server restart?
Is there a way to keep the value of <portlet:namespace/> constant for the same view even after server restart?
Expecting prompt feedback and will highly appreciate it.
Thanks
Gagan

The problem is still there if the jsp file is about inserting a new record
into the database.
If these parameters are gotten from the session, mutliple insertings will be
attempted when the portlet is refresh.
Maybe we can put some control flags in the session to judge the correct
behavior, but the method results the session full of parameters(control
flags).
Or is there any better design?
Alan.
"travis wissink" <[email protected]> ¼¶¼g©ó¶l¥ó
news:3cc71962$[email protected]..
>
Alan,
You could use the session to put your parameters in instead of letting itride completely
on the request object. Although, your question is more than just makingthe content
reappear, it’s about holding state. The project that I am working on, theusers
decided that they want the page portlets to go back to the "normal" state,not the
"Maximized" view. So, I put a processor in between the internal.refreshwildcard
and the Preprocessor input processor so that all the portlets would beseen in their
"normal" state.
Good Luck
-Travis
"Alan Liu" <[email protected]> wrote:
Hi All,
When I click page tabs in WLP, it will trigger a refresh event.
The portlet has a webflow with a refresh event whose destination is
lastContentUrl(referent-namespace is portal, cloned from portlet2.wf).
The question is when the page changed, the jsp files which use
request.getParameter() to get parameters will fail to fulfill what they
need because the event provide none parameter.
So that everytime page changed, these portlets will have quite strange
contents.
How to keep these content constant when page changed?
Sincerely,
Alan.

NAME SPACE CHANGING

Hi ,
i want to change the existed namespace .. is it possible to change the existed name space..because after created all the scenarios we got a new requirement to change the new name space for all the scenarios..
can any body tell the steps for changing the namespaces..
thanks
babu

Babu,
In my project also we have faced same problem.after developing almost objects of a interface..clients asked 4 the namespace change. thats the problem...with XI and PI...i dont know wheather PI 7.1 will having the option to copy whole namespace.....We have found the only possibility is to create a new namespace .And manually copy all the objects...into the new namespace...
u can copy directly Message interfaces...(u need not copy data type and Message type) <b>and remember to check the option "With all dependency"</b>..
then automatically data type and Message type will be copied...
u can't copy Interface mapping and Message mapping :(..
u have to do it agian.......
Regards
Biplab

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"/>
            <p marginBottom="15" ><span format="{english}">This text is supposed to be in Minion Pro via a named character attribute</span></p>
            Is now this:
            <format id="english" locale="en" fontFamily="Minion Pro"/>
            <p marginBottom="15" ><span format="english">This text is supposed to be in Minion Pro via a named character attribute</span></p>
    * 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)

Windows Pro 8.1 Hyper-V enabled - cannot connect to Virtual Machines

I'm running Windows Pro 8.1. Virtualization is enabled in BIOS. Account is in Admin, Hyper-V, RDP groups. I open Hyper-V manager. Create a new Virtual Switch (internal) and name it. Then create a new virtual machine - name it, place it in a folder under
C:, Specify Generation (tried both 1 and 2), startup memory 512mb not dynamic, Lan- select the virtual switch created earlier, create an vhdx hard disk, and install the O.S. from an ISO on C. Creates the new VM under Virtual Machines.
I select the new VM, click connect, then start. A window opens with the new VM on server and says it's connecting to it and it's status is Running. In the Hyper-V manager in the New Virtual Machine pane (bottom pane) it shows a image that
appears to have a login screen. The VM window that displays the "Connection to" eventually throws an error : Virtual machine connection: Cannot connect to the virtual machine, Try to connect again. contact your admin, Try again etc. selecting connect
eventually errors out with check integration services etc. I've read the logs, there are no errors. When I try to shut down or turn off the vm it doesn't respond. I've configured this before on different boxes. It's the work environment for the MCSA 70-462
training kit Preparation. any direction would be greatly appreciated.

That is correct. This has been well documented.
The WMI namespace changed. 2008 and 2008 R2 now of the v1 virtualization namespace. 2012 knows of both v1 and v2. And 2012 R2 only knows the v2 virtualization namespace.
That said, there is more to this.
2008 management console only knows 2008 features. So if you connect it to a 2012 server to manage the 2012 server, you cannot manage any of the features released with 2008 R2 nor 2012.
So, take this second point, mix it with the first point and I recommend that your management server / client release matches the release of the Server you are managing.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.
Disclaimer: Attempting change is of your own free will.

Namespace change

Similar Messages

Maybe you are looking for