Can 'element names' be created ?

Guruz,
its related to inventory -> item ->master item--> (special menu)->catalog->"'element name"
In this scenario,
I have found 1 interface "mtl_desc_elem_val_interface" and couple of APIs to import/update "element values". [from meta-link]
But i couldn't found interface or api to "create" element names
* Can we "create" element names ?
* I couldn't found much documentation/information on "mtl_desc_elem_val_interface" .
Its little urgent...will provide ANY further details if required
regards,
-sDJ

Duplicate post -- Can we create ELEMENT NAMEs ?

Similar Messages

Validate element name

Hi all,
I'd like to add a new Validation Rule to validate the Element name that created by user.
At the moment, Sirius accepts all name from user, but I want to set some Validation Rule for it, such as: no space, no special characters as brackets, dollar, etc.
Could anyone send me the guide or example for the Sirius Validation rules?
Thanks and BRs,
Tuan Hoang

Hello,
Well I do not know how is made your metamodel, but if you do not have a
map/cache of the element to have a unique name, you will have to browse
your semantic model to find these elements and validate that there are
no duplicate name. Depending on your metamodel, this can be easier to be
done as a java service.
Regards,
Steve
Le 26/06/2015 12:30, Tuan Hoang Anh a écrit :
> Steve Monnier wrote on Fri, 26 June 2015 08:28
>> Hello,
>>
>> You should use the acceleo operation "matches" [1] that validates if a
>> string matches a regular expression pattern (here name with no space,
>> no special characters as brackets, dollar, etc).
>>
>> Regards,
>> Steve Monnier
>>
>> [1]
>> https://wiki.eclipse.org/Acceleo/Acceleo_Operations_Reference#matches_.28String_regex.29_:_Boolean
>>
>>
>> Le 26/06/2015 08:57, Tuan Hoang Anh a écrit :
>> > Steve Monnier wrote on Tue, 23 June 2015 09:14
>> >> Hello,
>> >>
>> >> You can find a section about Sirius Validation rules [1] on the online
>> >> documentation.
>> >>
>> >> Regards,
>> >> Steve
>> >>
>> >> [1]
>> >>
>> https://www.eclipse.org/sirius/doc/specifier/diagrams/Diagrams.html#validation
>>
>> >>
>> >>
>> >> Le 23/06/2015 11:06, Tuan Hoang Anh a écrit :
>> >> > Hi all,
>> >> >
>> >> > I'd like to add a new Validation Rule to validate the Element
>> name that
>> >> > created by user.
>> >> > At the moment, Sirius accepts all name from user, but I want to set
>> >> some
>> >> > Validation Rule for it, such as: no space, no special characters as
>> >> > brackets, dollar, etc.
>> >> >
>> >> > Could anyone send me the guide or example for the Sirius Validation
>> >> rules?
>> >> >
>> >> > Thanks and BRs,
>> >> > Tuan Hoang
>> >>
>> >>
>> >> --
>> >> Steve Monnier - Obeo
>> >>
>> >> Need professional services for Sirius?
>> >> http://www.obeodesigner.com/sirius
>> >
>> >
>> > Hi Steve,
>> >
>> > Thank you for your instruction.
>> > I read the Sirius Validation rule, but I'm wondering about the Audit
>> > Expression.
>> > For example, I created a new Semantic Validation Rule, Level Error, and
>> > the Target Class is "uml.NamedElement".
>> >
>> > Could you please tell me which Audit Expression I have to write to have
>> > the Validation Rule: check name with no space, no special characters as
>> > brackets, dollar, etc?
>> >
>> > Thanks and BRs,
>> > Tuan Hoang
>>
>>
>> --
>> Steve Monnier - Obeo
>>
>> Need professional services for Sirius?
>> http://www.obeodesigner.com/sirius
>
> Hi Steve,
>
> Thank you so much for your support.
> I could validate the name as my need follow your instruction.
> But now, I want to validate the unique of element name. Each element
> must have an unique name. There are no two-elements which have the same
> name.
>
> Do you have any suggestions for me?
>
> Thanks and BRs,
> Tuan Hoang
Steve Monnier - Obeo
Need professional services for Sirius?
http://www.obeodesigner.com/sirius

How to fill in Element Name box in Create Symbol Script?

I'm trying to follow Adobe's directions for creating a Component Symbol so I can change the properties later. They say, " 9. Click the plus button to add an element name. 10. In the Element Name box, type the name of the element to customize. For example, to customize the text field named "label," type "label".
Here are my problems. Fireworks (CS4 - Mac) won't let me type anything in the Element Name box. The only place I can type is in the "property name" and "value name" boxes. I also have a limited list of properties to chose from in the "attribute" dropdown.
So I tried using one of the attributes and saving, without anything in the Element Name box but Fireworks said the box was blank and wouldn't let me save it. It wouldn't let me add text there and wouldn't let me save it without text there. Kind of frustrating. What am I doing wrong?

Your welcome.
Yeah I wish the attributes were a little more intuitive to work with. I always get confused between brush.diameter, brushcolor, fillcolor!
If you vreate anything unique don't hesitate to share it with the community.
h

Can't access object using "id" or "name" if created with actionscript

How can you register an instance of an object with actionscript so that it's id or name value is accessible?
I included a simple example where a Button is created using mxml and in the same way it is created using actionscript. The actionscript object is inaccessible using it's "id" and "name" property.
<?xml version="1.0" encoding="utf-8"?>
<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" minWidth="955" minHeight="600"
               creationComplete="application1_creationCompleteHandler(event)">
    <fx:Script>
        <![CDATA[
            import mx.events.FlexEvent;
            protected function application1_creationCompleteHandler(event:FlexEvent):void
                import spark.components.Button;
                var asBtn:Button = new Button();
                asBtn.label = "actionscript";
                asBtn.x = 200;
                asBtn.id = "asButton";
                asBtn.name = "asButtonName";
                addElement(asBtn);
                trace("mxmlButton="+this["mxmlButton"].label); // returns: mxml label
                //trace("mxmlButton="+this["asButton"].label); // returns runtime error: ReferenceError: Error #1069: Property asButton not found on TestId and there is no default value.
                //trace("mxmlButton="+this["asButtonName"].label); // returns runtime error: ReferenceError: Error #1069: Property asButtonName not found on TestId and there is no default value.
        ]]>
    </fx:Script>
    <s:Button
        id="mxmlButton"
        label="mxml label"
        alpha="0.8"/>
</s:Application>

Hi Dan,
It is a very rare occurrence when I miss not being able to access an object (object property, really) using the ["name"] notation for objects created using actionscript.
In MXML the compiler is conveniently adding an attribute to the class with the same name as the id, so you can conveniently refer to it using the [] notation. While we explicitly specify an application container to use, the MXML compiler creates a custom container which is a derivative of the base container and to that it adds properties for the children declared in MXML. I guess it also effectively calls "addElement" for us when the container is being constructed.
Your example assumes that using "addElement" to add the button to the application container is the same as declaring a variable (ie property ). It isn't, so there's no point in looking for an property of the name "as3Button" using the [] notation, because it doesn't exist. The container is managing a collection of children in it's display list and that's not the same as being accessible as properties of the container.
Generally speaking, accessing properties using the ["name"] syntax isn't necessary.
Paul
[edit: you may wonder why "addElement" doesn't conveniently also add the "id" attribute to be an property of the container class. Unfortunately, it can't because the container class would need to be dynamic and it's not. A further complication would be that adding properties at runtime would invite naming clashes at runtime with associated mayhem. MXML can do this because the compiler generates the class and can trap name duplication at compile time.
Great question, BTW.
-last edit changed my "attributes" to be "properties" in line with Adobe's terminology]

TS4020 Can I change my iCloud email address name without creating a new account?

CCan I change my iCloud email address name without creating a new account?

Once you have created an iCloud account and chosen an @icloud.com address to go with it you can't change the address (short of creating an entirely new account).
However, all is not lost. You can add up to three 'email aliases' - these are additional addresses (not accounts) which deliver into the same inbox as the main account. (In fact it's a good idea to give out alias addresses, rather than the main address, because if they attract spam you can easily change them.) (New aliases can only be @icloud.com ones; @me.com addresses cannot now be created.)
You should be aware before you start that once you've created an alias you cannot turn that address into a full iCloud account or move it to another account.
More information on aliases here: http://help.apple.com/icloud/#mm6b1a490a

Can anyone give me user exit name for create/update purchase order partners

Hello guys
Can anyone gives me user exit name for create/update purchase order partners?
Requirement is to insert/update partner when SC flag is checked while creating/updating purchase order (ME22N / ME21N) by using user exit.

hi,
check these exits.
Transaction Code - ME21N                    Create Purchase Order
Enhancement/ Business Add-in            Description
Enhancement
MEQUERY1                                Enhancement to Document Overview ME21N/ME51N
MEVME001                                WE default quantity calc. and over/ underdelivery tolerance
MM06E001                                User exits for EDI inbound and outbound purchasing documents
MM06E003                                Number range and document number
MM06E004                                Control import data screens in purchase order
MM06E005                                Customer fields in purchasing document
MM06E007                                Change document for requisitions upon conversion into PO
MM06E008                                Monitoring of contr. target value in case of release orders
MM06E009                                Relevant texts for "Texts exist" indicator
MM06E010                                Field selection for vendor address
MMAL0001                                ALE source list distribution: Outbound processing
MMAL0002                                ALE source list distribution: Inbound processing
MMAL0003                                ALE purcasing info record distribution: Outbound processing
MMAL0004                                ALE purchasing info record distribution: Inbound processing
MMDA0001                                Default delivery addresses
MMFAB001                                User exit for generation of release order
MRFLB001                                Control Items for Contract Release Order
MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
AMPL0001                                User subscreen for additional data on AMPL
LMEDR001                                Enhancements to print program
LMELA002                                Adopt batch no. from shipping notification when posting a GR
LMELA010                                Inbound shipping notification: Transfer item data from IDOC
LMEQR001                                User exit for source determination
LMEXF001                                Conditions in Purchasing Documents Without Invoice Receipt
LWSUS001                                Customer-Specific Source Determination in Retail
M06B0001                                Role determination for purchase requisition release
M06B0002                                Changes to comm. structure for purchase requisition release
MEFLD004                                Determine earliest delivery date f. check w. GR (only PO)
MEETA001                                Define schedule line type (backlog, immed. req., preview)
ME590001                                Grouping of requsitions for PO split in ME59
M06E0005                                Role determination for release of purchasing documents
M06E0004                                Changes to communication structure for release purch. doc.
M06B0005                                Changes to comm. structure for overall release of requisn.
M06B0004                                Number range and document number
M06B0003                                Number range and document number

Can I use Photoshop Elements 8 to create printable items for commercial purposes?

I like to create printables for classroom use using my Photoshop Elements 8 that I purchased about 4 years ago. I would like to be able to sell these items on www.teacherspayteachers.com, but I am not sure if I can leagally do that. Can Elements be used for commercial use or would I need to buy a commercial version??? Thanks in advance!

Legally there's no problem, but if you need CMYK files, PSE can't do those.

Can I use Photoshop Elements 13 to create HTML file?

Can I use Photoshop Elements 13 to create HTML file?

See Barbara's answer in your duplicated post: How can I save a Photoshop Elements 12 file as HTML?
No difference with PSE13.

I am new to pages and want to know how to link elements together to create one unified element that I can then duplicate several times on the same page?

I am new to pages and want to know how to link elements together to create one unified element that I can then duplicate several times on the same page?

I think you are talking about grouping objects.
1. They must all be floating objects
2. Command click on each in turn
Menu > Arrange > Group
Peter

WBS Elements not getting created in ECC Project System from CRM 7.0

Dear all,
We are trying to integrate SAP CRM 7.0 with SAP ECC-PS module. The objective is to bring in the marketing plan and elements data from the CRM system, and to create the corresponding WBS in project system. We have done most of the configuration as recommended by SAP in both the systems, and we see that the BDOCS are getting generated and sent to the ECC system. The following steps have been successfully completed:
1.       Set up the RFC connections between the two systems
2.       Selected the connection type as Middleware in CRM system.
3.       Installed the cProject Add on in CRM box.
4.       Created a project scenario (with project and network profiles) in the PS system and assigned the same in the CRM system.
5.       The Project Scenario in PS config has the same name as the Project Type in CRM config.
6.       Created and released the campaign ids being created in the CRM system.
As already mentioned, we can see that the BDOCS are coming to the ECC system and are getting stored in BDOC_TRACK table. However the issue is that the corresponding WBS elements are not getting generated in the ECC system. Is there anything that that we are missing in the ECC box which would trigger the WBS element creation?
Request you all to share your inputs which would be immensely beneficial for us in achieving this integration.
Thanks and Kind Regards,
Aditya Shrivastava

Hello Aditya,
We too are facing this issue.. if you have resolved the issue could you please let us know the solution ?
Some inputs related to our system,
We have upgrade from CRM 4.0 to CRM 7.0 SP07 and R/3 backend system is on 4.7 SP27, earlier we have completed the upgrade on sandbox without any issues which was upgrade to CRM 7.0 SP04 but with SP07 we are facing the problem of WBS Element not getting created in R/3.
Your help is highly appreciated.
Thanks & Regards,
Sumukh Kapoor.

XML element names required in lower case

Hi,
I am on release 4.6C
I create an XML file from internal table using FM SDIXML_DATA_TO_DOM and SDIXML_DOM_TO_XML.
The internal table is defined such that the fieldnames of internal table are same as element names in XML file.
The XML file gets created properly, but the element names appear in upper case.
The requirement is to have it in lower case.
Does anybody have any idea about how to control the case here?

Hi Sudhir
you can convert field names manually using translate command to convert it to lower case.
hope this helps.

Oracle DB: How to parse XML where element names are non-standard ?

I'm in the unfortunate situation that I have illegal XML that I would like Oracle to parse. By 'illegal' in my case is that there are element names that start with an illegal character, such as a digit. Apart from this the XML is syntactically valid.
Here is an example of the XML I have stored as a column in the database:
<schedule>
    <1stweek>
    </1stweek>
    <2ndweek>
    </2ndweek>
</schedule>Right now I'm doing text search-and-replace on the XML text before I let Oracle parse it, for example replacing '<1stweek>' with '<x1stweek>' and so on. Needless to say this is very slow.
My question is if there is a way to tell the XML parser in the Oracle DB (I'm using version 10.2) to be a bit more forgiving ? ... so that it will accept element names that start with e.g. a digit ? I know that such an option exist in some XML parsers but what about Oracle's and if so how to set the option?
And before you ask I'll answer myself: No, I'm not the one who created the non-standard XML. It is from a third-party application which I cannot change myself and cannot get the vendor to change either.
Thank you.

if you cast your clob to an xmltype then you can search and extract values based on tags.
Heres an example where the table is a clob and value is cast and I'm looking for an existing attribute_name.
Check out the Oracle XML developers Guide
select u.*
FROM preload_xml
, XMLTable(
'/ApplicationProfile/ScriptFragment' PASSING xmltype(xml)
COLUMNS name varchar2(50 char) PATH '/ScriptFragment/@Name'
) u

CJK characters in xml element name

Hi People,
I have a question as it looks like I am doing something wrong, but I do not know what.
I am trying to use CJK characters in the element name of an xml document and the element names are encoded/parsed using the default encoding and not the encoding specified at the xml document.
This is the specific code
     ByteArrayOutputStream baos = new ByteArrayOutputStream();
     Document document = DocumentBuilderFactory.newInstance().newDocumentBuilder().newDocument();
     document.appendChild(document.createElement("\ub3c4\uba54\uc778"));
     TransformerFactory tFactory = TransformerFactory.newInstance();
        Transformer transformer = tFactory.newTransformer();
        transformer.setOutputProperty(OutputKeys.ENCODING, "UTF-8");
        transformer.transform(new DOMSource(document), new StreamResult(baos));
        System.out.println(new String(baos.toByteArray(), "UTF-8"));
        System.out.println(new String(baos.toByteArray()));(you have to run this on a system that does not have UTF-8 as the default locale :-)
The result of this is
<?xml version="1.0" encoding="UTF-8" standalone="no"?><???/>
<?xml version="1.0" encoding="UTF-8" standalone="no"?><도메인/>
So the encoding of the element name is not UTF-8 but the default encoding.
Just in case someone ask
$ java -version
java version "1.6.0_05"
Java(TM) SE Runtime Environment (build 1.6.0_05-b13-120)
Java HotSpot(TM) 64-Bit Server VM (build 1.6.0_05-b13-52, mixed mode)
Thanks,
Lucas

Hi Alpha.23,
well I'm not sure, and maybe I'm totally wrong, but here is what I think about your problem.
As there is no error while running the code, there should be no XML problem (so the characters you are using are XML compatible for tag names).
I think the problem is the ability of any computer to display such chars. The questionmark often indicates that there is a char which cannot display correctly. This depends partitially on the font your are using.
If I try to display the chars with simple System.out.println("\ub3c4\uba54\uc778"); I get those question marks too. So I guess the console of my IDE (eclipse) can't display these Korean symbols. But I haven't installed the specific language-support for any of the Asian languages (so I don't know what happend when they are installed, though I guess that doesn't solve the problem...).
So my tip is first to look for a way to print these char in general (on the console, into a file, maybe try to create a word document because a unicode font -i.e. Arial Unicode- is able to print these - try ALT+47700 or ALT+46020).
Best Wishes
esprimo

Unexpected element name - confusion of types in client

I have a web service definition that performs four operations:
- String getTitle(long) - returns a title for a single asset
- StringArrayType) getTitles(LongArrayType) - returns an ordered list of titles matching input list
- AssetSummaryType getSummary(long) - Returns a complex type, summary information of an asset
- AssetSummaryArrayType getSummaries(LongArrayType) - Returns an array of complex types
Based on the WSDL (included at the bottom of this posting) I then generate the service
endpoint using wscompile and -f:wsi option (JDK 1.4.2-05 and JWSDP-1.4).
This is built into a raw war file and then cooked using wsdeploy.
On the client side I create stubs using wscompile and -f:wsi and compile
the resultant code. My client invokes each of the operations in turn, having been
provided the relevant 'longs' as input.
The service is deployed in JBoss-3.2.2 and the client is then executed from a separate JVM.
I then see the following client error:
java.rmi.RemoteException: Runtime exception; nested exception is:
unexpected element name: expected={http://example.com/myAssetWebSvc}Str
ingElement, actual={http://example.com/MyAssetWebSvc}AssetSummaryElement
at com.sun.xml.rpc.client.StreamingSender._handleRuntimeExceptionInSend(
StreamingSender.java:318)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:300
at example.com.wsclient.asset.AssetService_Stub.getTitle(AssetService_St
ub.java:175)
at example.com.wsclient.asset.AssetClient.testAssetTitleRetrieval(AssetC
lient.java:82)
at example.com.wsclient.asset.AssetClient.main(AssetClient.java:51)
Caused by: unexpected element name: expected={http://example.com/MyAssetWebSvc}
StringElement, actual={http://example.com/MyAssetWebSvc}AssetSummaryElement
at com.sun.xml.rpc.encoding.literal.LiteralSimpleTypeSerializer.deserial
ize(LiteralSimpleTypeSerializer.java:106)
at example.com.wsclient.asset.AssetService_Stub._deserialize_getTitle(As
setService_Stub.java:318)
at example.com.wsclient.asset.AssetService_Stub._readFirstBodyElement(As
setService_Stub.java:276)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:215
... 3 more
If I deploy the same service with only the first two operations defined within wsdl,
the error is not seen.
I have also tried compilation on JWSDP 1.3 and JDK 1.4.1-03 and in this case the same error
occurs but the other way around. The two 'title' operations work but the summary
operations fail with the actual element encountered being a StringElement or StringArrayElement
and the expected an AssetSummaryElement or AssetSummaryArrayElement.
Further, if I change the name of the StringElement to for example 'MyStringElement', this is
reported as the actual - i.e. there is no confusion with a standard type at play here.
I also use handlers, one on the server side to inspect security information and one on the
client to insert relevant details and look for returned errors within the header.
Is this a known problem within JWSDP 1.3 and/or 1.4? Are there any workarounds.
My wsdl is provided below along with the wscompile options and the matching configuration
files used.
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions name="MyAssetService" targetNamespace="http://example.com/MyAssetWebSvc"
     xmlns:tns="http://example.com/MyAssetWebSvc"
     xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
     xmlns:xsd="http://www.w3.org/2001/XMLSchema"
     xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
<wsdl:types>
<xsd:schema targetNamespace="http://example.com/MyAssetWebSvc"
          xmlns:tns="http://example.com/MyAssetWebSvc"
          xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:complexType name="AssetSummaryType">
<xsd:all>
<xsd:element name="createdBy" type="xsd:string" />
<xsd:element name="createdDate" type="xsd:dateTime" />
<xsd:element name="description" type="xsd:string" />
<xsd:element name="fileSize" type="xsd:long" />
<xsd:element name="id" type="xsd:long" />
<xsd:element name="modifiedBy" type="xsd:string" />
<xsd:element name="modifiedDate" type="xsd:dateTime" />
<xsd:element name="organisation" type="xsd:string" />
<xsd:element name="owner" type="xsd:string" />
<xsd:element name="title" type="xsd:string" />
<xsd:element name="type" type="xsd:string" />
<xsd:element name="version" type="xsd:long" />
</xsd:all>
</xsd:complexType>
<xsd:complexType name="ExceptionType">
<xsd:all>
<xsd:element name="rootCause" type="xsd:string" nillable="true" />
</xsd:all>
</xsd:complexType>
<xsd:complexType name="LongArrayType">
     <xsd:sequence>
          <xsd:element name="LongItem" type="xsd:long" nillable="true" minOccurs="0" maxOccurs="unbounded"/>
     </xsd:sequence>
</xsd:complexType>
<xsd:complexType name="AssetSummaryArrayType">
     <xsd:sequence>
          <xsd:element name="AssetSummaryItem" type="tns:AssetSummaryType" nillable="true" minOccurs="0" maxOccurs="unbounded"/>
     </xsd:sequence>
</xsd:complexType>
<xsd:complexType name="StringArrayType">
     <xsd:sequence>
          <xsd:element name="StringItem" type="xsd:string" nillable="true" minOccurs="0" maxOccurs="unbounded"/>
     </xsd:sequence>
</xsd:complexType>
<xsd:complexType name="CredentialsType">
<xsd:all>
<xsd:element name="principal" type="xsd:string" />
<xsd:element name="password" type="xsd:string" />
</xsd:all>
</xsd:complexType>
     <xsd:element name="LongElement" type="xsd:long"/>
<xsd:element name="StringElement" type="xsd:string"/>
<xsd:element name="LongArrayElement" type="tns:LongArrayType"/>
<xsd:element name="StringArrayElement" type="tns:StringArrayType"/>
<xsd:element name="AssetSummaryElement" type="tns:AssetSummaryType"/>
<xsd:element name="AssetSummaryArrayElement" type="tns:AssetSummaryArrayType"/>
     <xsd:element name="CredentialsElement" type="tns:CredentialsType"/>
     <xsd:element name="ExceptionElement" type="tns:ExceptionType"/>
</xsd:schema>
</wsdl:types>
<wsdl:message name="getSummaryMessage">
<wsdl:part name="resourceId" element="tns:LongElement" />
</wsdl:message>
<wsdl:message name="getSummaryResponse">
<wsdl:part name="assetSummary" element="tns:AssetSummaryElement" />
</wsdl:message>
<wsdl:message name="assetException">
<wsdl:part name="exception" element="tns:ExceptionElement" />
</wsdl:message>
<wsdl:message name="getTitle">
<wsdl:part name="resourceId" element="tns:LongElement" />
</wsdl:message>
<wsdl:message name="getTitleResponse">
<wsdl:part name="assetTitle" element="tns:StringElement" />
</wsdl:message>
<wsdl:message name="getSummaries">
<wsdl:part name="resourceIdList" element="tns:LongArrayElement" />
</wsdl:message>
<wsdl:message name="getSummariesResponse">
<wsdl:part name="assetSummaryList" element="tns:AssetSummaryArrayElement" />
</wsdl:message>
<wsdl:message name="getTitles">
<wsdl:part name="resourceIdList" element="tns:LongArrayElement" />
</wsdl:message>
<wsdl:message name="getTitlesResponse">
<wsdl:part name="assetTitleList" element="tns:StringArrayElement" />
</wsdl:message>
<wsdl:message name="securityHeader">
<wsdl:part name="credentials" element="tns:CredentialsElement" />
</wsdl:message>
<wsdl:portType name="AssetService">
<wsdl:operation name="getSummary" parameterOrder="resourceId">
<wsdl:input message="tns:getSummaryMessage" />
<wsdl:output message="tns:getSummaryResponse" />
<wsdl:fault name="AssetException" message="tns:assetException" />
</wsdl:operation>
<wsdl:operation name="getTitle" parameterOrder="resourceId">
<wsdl:input message="tns:getTitle" />
<wsdl:output message="tns:getTitleResponse" />
<wsdl:fault name="AssetException" message="tns:assetException" />
</wsdl:operation>
<wsdl:operation name="getSummaries" parameterOrder="resourceIdList">
<wsdl:input message="tns:getSummaries" />
<wsdl:output message="tns:getSummariesResponse" />
<wsdl:fault name="AssetException" message="tns:assetException" />
</wsdl:operation>
<wsdl:operation name="getTitles" parameterOrder="resourceIdList">
<wsdl:input message="tns:getTitles" />
<wsdl:output message="tns:getTitlesResponse" />
<wsdl:fault name="AssetException" message="tns:assetException" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="AssetServiceBinding" type="tns:AssetService">
<wsdl:operation name="getSummary">
<wsdl:input>
<soap:header required="true" message="tns:securityHeader" part="credentials" use="literal" actor="security"/>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
<wsdl:fault name="AssetException">
<soap:fault name="AssetException" use="literal"/>
</wsdl:fault>
<soap:operation soapAction="" />
</wsdl:operation>
<wsdl:operation name="getTitle">
<wsdl:input>
<soap:header required="true" message="tns:securityHeader" part="credentials" use="literal"/>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
<wsdl:fault name="AssetException">
<soap:fault name="AssetException" use="literal"/>
</wsdl:fault>
<soap:operation soapAction="" />
</wsdl:operation>
<wsdl:operation name="getSummaries">
<wsdl:input>
<soap:header required="true" message="tns:securityHeader" part="credentials" use="literal"/>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
<wsdl:fault name="AssetException">
<soap:fault name="AssetException" use="literal"/>
</wsdl:fault>
<soap:operation soapAction="" />
</wsdl:operation>
<wsdl:operation name="getTitles">
<wsdl:input>
<soap:header required="true" message="tns:securityHeader" part="credentials" use="literal"/>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
<wsdl:fault name="AssetException">
<soap:fault name="AssetException" use="literal"/>
</wsdl:fault>
<soap:operation soapAction="" />
</wsdl:operation>
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
</wsdl:binding>
<wsdl:service name="MyAssetService">
<wsdl:port name="AssetServicePort" binding="tns:AssetServiceBinding">
<soap:address location="http://localhost:9090/MyAssetWebSvc/asset" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Here is the wscompile for the server - this is within an ant script that substitutes the variables specified:
wscompile -keep -d ${path.classes} -s ${src.autojava} -import -model model.gz -f:wsi -f:documentliteral server-config.xml
and this is the server config:
<?xml version="1.0" encoding="UTF-8"?>
<configuration xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config">
<wsdl location="file:///C:temp/MyAssetService_wsi.wsdl" packageName="example.com.wsserver.asset.wrapper">
<handlerChains>
<chain runAt="server">
<handler className="example.com.wsserver.security.SecurityServerHandler">
<property name="name" value="SecurityServerHandler"/>
</handler>
</chain>
</handlerChains>
</wsdl>
</configuration>
On the client side, here is the wscompile, again with ant variable substitution:
wscompile -gen:client -keep -d ${path.build.wsclient.class} -s ${path.build.wsclient.autojava} -classpath ${path.build.wsclient.class} -f:wsi -f:documentliteral client-config.xml
And here is the client config:
<?xml version="1.0" encoding="UTF-8"?>
<configuration xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config">
<wsdl location="file:///C:/temp/MyAssetService_wsi.wsdl" packageName="example.com.wsclient.asset">
<handlerChains>
<chain runAt="client">
<handler className="example.com.wsclient.security.SecurityClientHandler">
<property name="name" value="SecurityClientHandler"/>
</handler>
</chain>
</handlerChains>
</wsdl>
</configuration>
Note that I generate slightly different packages on client and server side. The server includes a 'wrapper' path on the package name - purely because the
generated code wrappers an existent api that I am making available as a web service. This is not needed to be seen
on the client side - i.e. the service appears as is without the wrapper.
I have tried omitting the documentliteral from the wscompiles and this seems to have no effect.
Any help gratefully received.
Best regards
Lawrence

Thanks for the prompting. I was convinced that the error was occurring client side as I could see no activity on the server. However having captured the soap request and responses its evident that this is not the case (which I'm a little confused on based on my original tests, but the error makes more sense in this context).
The request is below:
<env:Envelope xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns0="http://example.com/myAssetWebSvc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<env:Header>
<ns1:mmsSecurity env:actor="security" env:mustUnderstand="1" xmlns:ns1="http://example.com/myAssetWebSvc">
<principal>example.user</principal>
<password>mypassword</password>
</ns1:mmsSecurity>
</env:Header>
<env:Body>
<ns0:LongElement>166333</ns0:LongElement>
</env:Body>
</env:Envelope>
I can see from the body that the signature is not unique - its the same as that of the Summary operation. In this case, the server side is performing the summary (rather than the title that I had intended) and returning that response. This gives rise to the deserialisation error on the client side for the response.
Presumably I need to move to the wrapped document literal style so that the request is uniquely identified on the server side.
To me this was not an obvious gotcha, Could the parser (wscompile) be enhanced to trap identical request message definitions within a single service/endpoint definition (i.e. WSDL)? If so where should I post the request?

WBS Element Name Change

Hi,
User wants to change the WBS element Name, but the field is greyed out.
User has the access to CJ02 but only the long text is open to change but WBS Element Name / ID field is freezed and can not be changed.
The current status of WBS element is released.
In Quality system I am able to change the WBS element Name / ID.
Please let me know what can be the reason for WBS Element name field being greyed out.
Thanks
Satish

Hi,
I agree with Nitin.
You can not open any version witht he old name if they are already created and in at table level internal number is stored. When you change external number will get changed but not the internal number.
So for any report purpose or in any developments you are taking internal number and thru conversion exit converting it to external number then it will return old value not new value.
It will create lot of inconsistency in data once such volume of such instances grew.
If possible , set deletion indicator to that WBSE and create new one with desired name afresh.
Thanks
Saikishore.Ganga

Can 'element names' be created ?

Similar Messages

Maybe you are looking for