Specify aggregation generated type?

Hello forum -
Due to a lack of documentation on UML to code mapping (see this bug http://www.netbeans.org/issues/show_bug.cgi?id=79555), I am having to learn by trial and error.
I would like to model an aggregation that is translated into a HashMap. Now, I see that I can change the UML generation options and specify that collections are mapped to java.util.ArrayList or java.util.HashMap types, but I would like to specify the resulting type on a case-by-case basis and not on the entire project.
Is there a way to do this that I am not seeing?

I hope I am understanding your question...
If you are working with 5.5 or prior, the feature is very limitied. There is a 5.5 patch in the work for UML (should be on Update Center soon) that will have a more robust feature that is implemented in NB6.
If you are using latest NB6.0, there is a new property that has been added for multiplicities. Let's look at an attribute on a class element. If the attribute has multiplicity:
public String foo[*, *]
and in this case more than one range (dimension), the default is to generate "As Array". To customize this, select the attribute, click on the Multiplicity property. In the custom editor, you will see that the ranges table has a Collection Type column. You can select a "well-known" Collection type or you can manually type your custom Collection Type, but be sure to fully qualify it so that code gen will add the proper import statements. You can use a different Collection type for every attribute as well as for each individual range of the attribute.
This works for parameters as well. Return Types may not have this feature implemented yet, but it will be there soon.
I suspect what you are asking may not be exactly what I described, but thought it might be related and at the very least, helpful in other areas for you.
craig

Similar Messages

Auto generated types and ps1xml formatting files

Hello,
I'm using New-WebServiceProxy to work with a web service... when I call methods of the web service powershell auto generates types, for example, things like "Microsoft.PowerShell.Commands.NewWebserviceProxy.AutogeneratedTypes.WebServiceProxy1_webservices_awebservicepage_asmx.TheMethodReturnObjectType"
1. should I just use that type name in my ps1xml formatting file? I'm wondering if that will be fragile... seems fragile like 'webServiceProxy1' for example, what if there is some scenario it uses '2'? Not sure if I can count on that being consistent?
2. I started creating custom objects and adding my own type name to them so that type name could be used in the ps1xml file. This works fine. However so far it was for web service methods that returned single instance results.. now I hit a point where I'm
calling a web service method that will return a collection... so I'm wondering if it would be better to just use the auto generated type name in the ps1xml or, as I would need to do in this case, actually enter a foreach loop to create a new custom object
for every object in the returned collection? In other words, for the web service methods I've used so far for this, I simply created my custom object and write-output... for the case of the collection, I would be new-object'ing and write-output'ing within
that foreach loop.. wondering about performance issues, or if it's just overkill when I could just put that auto generated type name in the ps1xml file and be done with it...
not sure if I've asked that very clearly...
essentially, I'm wondering if it's overkill (from a resource usage perspective) to be creating these custom objects in the case of when there will be a collection, with potentially hundreds of items, when the only reason I'm doing it is for display purposes...
if it were not an autogenerated type I would simply use the type name in the ps1xml, I'm just not sure if I can do that in this case as I don't know if that typename will *always* be the same?
any input would be appreciated, thanks

Hi DJC,
I haven't rexperienced this, however, to create a .ps1xml file, these examples may be helpful for you:
Creating a module for powershell with a format file
discutils / utils / DiscUtils.PowerShell / DiscUtils.Format.ps1xml
about_Format.ps1xml
I hope this helps.

Error message in WAD: "No name is specified for modification type 'Module'"

Hi All,
We have created a WAD template with one analysis item and a button and have single module of type generic module in it.
While executing it following error message is displayed "No name is specified for modification type 'Module'"
Please Can anyone help with this error.
Regards,
Shweta.

Hello,
I am currently facing same issue and I have no idea how to get rid of this message on top of the page.
I'm pretty sure that this error message comes from the ANALYSIS_ITEM define in my Web Template but I have defined alias name for the different modules I created:
Who is able to help ?

Error in BP Mapping from ECC to CRM 5.0 -Specify a card type error

Hi gurus,
I have taken
*Specify a card type-Message no. R1561*
error in case of mapping cust_main data from ECC to CRM 5.0. When I check the selection result of Bdoc messages by getting SMW01 facing with above this error.
Could you please help me to overbeat this error in a quick way in order to map properly...
Thanks so much
Best regards,
Fahrettin Kerem BOZBIYIK

Hi Kai,
Firstly thank you for your notes notification!
That's right symptom is right over there but in our ECC system my related customer has no credit card type data in payment cards data tab so that why would I have taken the Bdoc validation error occasionally in case of mapping process to CRM 5.0 such as I mentioned?...
Best Regards,
FKB

A constructor cannot specify a return type.

I have a shuffleList.as file with this code...
package {
import flash.display.MovieClip;
public class shuffleList extends MovieClip{
function shuffleList(arr:Array):Array{
var shuffled:Array = arr.slice();
for (var i:int=0; i<arr.length; i++) {
var element:Object = shuffled
var rnd:int = Math.floor(arr.length * Math.random());
shuffled = shuffled[rnd];
shuffled[rnd] = element;
return shuffled;
In the first frame i put this code...
import shuffleList
var numA:Array = [0,1,2,3,4,5,6,7,8,9,10]
var numB:Array = shuffleList(numB);
var myText:String = numB.pop()
fieldA.text = myText
With this code I want to put in random order the numbers from
0 to 10 in the fieldA.
When run this file the compiler report this error: "A
constructor cannot specify a return type."
Where I'm wrong;
I'm new in actionscript..
Please help...

Hey Petros,
I had a similar problem and the response I got was:
1) the constructor is used to set up the class but it doesn't
really exist until it is instantiated and therefore cannot include
any 'interaction' including a return.
2) Therefore, you might try replacing
function.shuffleList ... with
function.shuffleList() { // to enable instantiation
public function doit(arr:Array):Array { // to enable
interaction
The rest of the code follows this then the call in the first
frame replaces
var numB:Array ... with
new shuffleList(); // instantiate the class
var numB:Array = shuffleList.doit(numB) // interact with the
class
Let me know how it goes...Daniel

BAPI_CUSTOMER_CHANGEFROMDATA1 error: Specify a URI type.

I am getting the following message on some of the customers I try to udpate using BAPI_CUSTOMER_CHANGEFROMDATA1: Specify a URI type. I assume this has something to do with the URI communication method. I am, however, NOT updating the URI as part of this BAPI call. In my program I first call BAPI_CUSTOMER_GETDETAIL1, I then update several fields in the company data structure and then call BAPI_CUSTOMER_CHANGEFROMDATA1 passing the updated data.

It appears that it has something to do with having a URI Communication Method loaded to the Customer Master. If i remove the URI Communication Method from the Customer Master prior to running my program, I do not get the error message. Once I added it back, however, I got the message again. Don't understand why since I am not attempting to update the URI information in my BAPI call. I have tried saving several different, valid URIs via XD02 but continue to get the error as long as there is a URI communication method loaded. Does anyone know if this is a BAPI_CUSTOMER_CHANGEFROMDATA1 bug or if I can do something to prevent from getting this error message.

While doing MIGO system giving error massage "No account was specified for account type "D" in item "0000000001"

Hello,
While doing MIGO system showing error " No account was specified for account type "D" in item "0000000001"
Kindly help me to resolve this issue.
Regards,
Abhijit

Hi,
Your issue seems to be an issue in FI. Refer the similar thread: MIGO error for UNBW material and the note: 1027645 - Message F5670: Account not specified in item X
Found a similar issue in J1IS as explained in the KBA: 1932095 - Error : F5670 - ' No account is specified in item 0000000002 ' - in transaction J1IS
Regards,
AKPT

HBR : Specify the Currency Type in a CCONV command

Hi everybody,
I am working on an Essbase/Planning application with a currency database.
I am trying to set a currency conversion in a HBR.
The problem is that the CCONV command doest not work if I specify the Currency type. (In my example ACT2009)
DATACOPY "Entity Currency" TO "Conso Euro";
FIX("Conso Euro")
CCONV "ACT2009"->"EUR";
ENDFIX
If I don’t specify the Currency type, this is working using the Default currency type member. (Set in the Cube Properties, sheet Currency)
Does anybody knows, how I could solve this problem and specify in the HBR the Currency type I want to use??
Thanks.

Are you somehow using the Essbase currency conversion option?
I'm not aware of that working with Planning, unless it's somehow gone into 11.1.2 which I am pretty sure it has not.
Planning has it's own, not so fantastic currency conversion functionality. I personally roll my own with something that looks very similar to Essbase's currency partition.
I have never tried (you know, I don't know why) to use Essbase's native currency conversion approach -- perhaps I have been overlooking a fantastic approach?
If it doesn't work with Planning (I can think of a bunch of reasons why not, all focusing on the Database->Refresh menu), you cannot use CCONV. But please, prove me wrong, as the more I think about it, the more I kick myself for never trying it.
Regards,
Cameron Lackpour

Are there any libraries can be used to generate Type 1 font postscript file

I am trying to create a Type 1 font postscript file. But I found it is hard to find the library to generate the Type 1 font postscript file. I just found a library named iText which can create the Type 1 font PDF file.
Are there any libraries can be used to generate Type 1 font postscript file?
Thanks!

I don't see much benefit with the current ODI adaptors for planning if it is an EPMA type planning application.
They have been specifically designed to work with classic planning applications.
It certainly is possible to load into EPMA interface tables using ODI though there are no direct adaptors and it takes quite a bit of effect to get them into the correct format.
Cheers
John
http://john-goodwin.blogspot.com/

Unsupported generator type: SEQUENCE

Is the primary key generation strategy "SEQUENCE" supported? I have an entity, based on a table in Oracle database, whose primary key is generated by a sequence in Oracle database. When I deploy the entity I get the following error...
ORPersistence Model Builder: Exception occurred: com.sap.engine.services.orpersistence.model.ormappingmodel.ORMException: Unsupported generator type: SEQUENCE at com.sap.engine.services.orpersistence.model.ormappingmodel.impl.ORMappingModelCreatorImpl.parseId(ORMappingModelCreatorImpl.java:2347), file: EntityTest.jar, column 0, line 0, severity: error

Hi Christopher,
The generation types SEQUENCE and IDENTITY are currently not supported by the JPA implementation in this release. You can however use the TABLE and AUTO generation types. In the case of AUTO you have to provide a table TMP_SEQUENCE created like this:
CREATE TABLE "TMP_SEQUENCE"
"GEN_KEY" VARCHAR(256) UNICODE NOT NULL,
"GEN_VALUE" INTEGER,
PRIMARY KEY ("GEN_KEY")
HTH!
-Vladimir

Aggregated data types - what package(s) do they reside in?

I'm looking for the definition of the aggregated data type MatlERPRplctnReqMsgMatl, but I cannot find it in the PI ESB. Do these data types reside in a specific package that needs to be imported, or do I use the SWDL for the interface that specifies it in the ES Workplace?

Hi Theo,
we've looked at the data you sent me and found that we already ran into this issue even before the first productive release.
The good news is that the problem should be solved already with the first release SAP NetWeaver CE 7.1 EhP1 SP1 Patch 0.
The bad news is that if you initally created the process and modeled the mapping with the Beta release (which contained this bug), false model information was written into the project files. So the problem is not solved by re-compiling the project with a newer NWDS.
Can you please check whether this model was created initially with the Beta version? If this is the case, I'm afraid you'll have to re-model the process with the productive release from scratch.
If you are sure that you modeled this from scratch with the official (SP1) release, please open an OSS ticket for this.
But I can put your mind at ease on one point: your use-case does not fall under a product limitation. This should work with the productive release, and if it doesn't, it's a bug that needs to be fixed.
Best regards,
Oliver

How to create an extension for generated type idoc

Hi all,
Can u please look into this
How to create an extension for generated type idoc ? for example Idoc type BATMAS02

Enter transaction WE30 (ALE->Extension-> IDOC types->Maintain Idoc type)
- Type in your name of the extended IDOC type (usually starting with 'Z') and click on the Basic IDoc type, click the create icon.
- Click on Create new and enter a description and press enter.
- Click on ZIDOCTYPE01 and then on the Create icon.
- Enter ZIDOCTYPE as the segment type, click on Segment Editor.
- Enter a description for your segment type and create.
- Enter a description for your segment, enter each field required in your IDoc and press enter to validate.
- Save and generate, press back
- To release the segment choose Goto, Release from the menu.
- Check the box on the line of your segment.
- Save, back and enter.
- Your Idoc type structure should be displayed with your new segment.
- Save and back.
- To release the Idoc type choose Extras, Release type from the menu and Yes.
ALE FUNCTION MODULE ENHANCEMENTS
Having extended the IDOC type to contain additional fields for an inbound or outbound application, you now want to enhance ALE function modules for populating the additional segment on the outbound or applying the additional segment data on the inbound application.
The core working code for ALE processes for a given application area is always encapsulated in ABAP/4 function modules. These function modules are associated with such control information as message types and process codes. So the ALE process checks this control information and derives the name of the function module to invoke for that particular IDOC processing from certain database tables. These function modules contain objects known as customer functions, which can be considered SAP Enhanced user exits. A function module is called at a particular point during the processing of the main program or function module, and it can be used to influence data processing at that point by adding code to the customer function. The customer function behaves like a normal function module and has import and export parameters, tables (internal tables) statement, and exception processing. Unlike a conventional user exit, customer functions give you the ability to modify only data available to you by the function moduleâs parameters and internal tables. While most ALE/EDI function modules are supported by customer functions, there are ALE/EDI processes that still use conventional user exits. There are a few ways to determine which function module to enhance for a given message type/process code:
For master data distribution, from SALE go to Extensions -> Master data distribution -> Setup additional data for message types. Search for message type DEBMAS in this example. You see an entry for DEBMAS associated with function module MASTERIDOC_CREATE_SMD_DEBMAS. This data is stored on table TBDME. The function module names for all master data message types follow this pattern: MASTERIDOC_CREATE_SMD_messagetype. This function module calls another function module of name MASTERIDOC_CREATE_DEBMAS or MASTERIDOC_CREATE_messagetype. Search for the words customer function, and you find several hits that can be used to add code to the function module.
From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.
Use transaction WE57 or from WEDI go to Development -> Message/Application Object. The entries list the function module, Business Object, message type, and IDOC type that are used for inbound ALE/EDI interfaces.
Customer functions are not specific only to ALE and EDI but also to all programs/modules in SAP R/3. Customer function is a SAP enhancement component; the other two types are menu and screen enhancements.
All customer function exits are maintained in SAP enhancements and are found by using transaction SMOD. After executing transaction SMOD, pull down (F4) on the enhancement name field, and execute again. This provides you with a list of all SAP enhancements available. SAP enhancements are grouped by development class pertaining to an application area. Choose Application development R/3 SD master data distribution for development class VSV to lead to a screen that lists VSV00001 as an enhancement (see Figure 5). Press Component +/- to display its function exit components. There are four possible components listed, all of which are function exits (and are function modules) that are called from the ALE function modules in the form Call Customer Function Î001â. This is a special occurrence of the ABAP statement Call. Go to item Exit_SAPLVV01_ 001, which you need to enhance for the Customer Master outbound example of an IDOC extension. In the ALE-function module MASTERIDOC_CREATE_DEBMAS, the statement CALL Customer Function 001 is translated in the background to call component EXIT_SAPLVV01_001. Although this function exit can be edited using transaction SE37, you will use a simpler approach.
When you use SAP enhancements and their components, you manage them with an SAP object known as a project, which is like an envelope containing the selected enhancements and their components. A project can be used to control the execution of components and to transport them to other clients and instances in SAP. Basically, the process involves creating a project, including enhancements and components that are to be enhanced, editing the components, and then activating the project. The following process creates a project for our example Customer Master IDOC extension:
Execute transaction CMOD.
Enter name of project, say CSTMAST1.
Click on Create.
Enter a description of the project.
Save.
Click on SAP Enhancements.
Enter VSV00001 for Enhancement.
Save.
Once youâve created the project, edit the function exit components and activate the project. Remember that the code in the function exit enhancement will execute only if the project is activated. In fact, this is a convenient SAP enhancements feature, whereby the work in progress (developing code in the customer function) will not affect users of that application. When the code is completed, the project can be activated so the enhanced functionality takes effect. It can also be deactivated for maintenance.
As mentioned earlier, customer functions (function exits) are embedded in ALE function modules and can be used to influence the creation and modification of IDOC data on an outbound application or to post additional or modified IDOC data to an inbound R/3 application. Function exits are similar to regular function modules, with import/export parameters, tables (internal tables), and exceptions.
The two important factors to consider while developing the customer function are:
1. The point in the ALE function module where the function exit occurs
2. The data made available by the customer function that can be modified or posted to the R/3 application, based on the direction.
Because some function modules have several customer functions, it is critical to choose the function exit best suited for that particular enhancement. Do not attempt to perform activities that the function exit is not designed for. The importance of this point is illustrated by the following description of enhancing function modules for outbound and inbound ALE interfaces.
Outbound interfaces. In an outbound ALE interface you use function exits (customer functions) to populate additional segments created by an IDOC extension or to modify the existing IDOC data segments as per business requirements. Previously, you identified that enhancement VSV00001 has a component EXIT_SAPLVV01_001 (function exit), which can be used for populating the additional data segment Z1SADRX that you created in the IDOC extension ZDEBMASX (IDOC type ZDEBMASZ, based on Basic IDOC type DEBMAS02). You also learned that the ALE function module that calls this function exit is MASTERIDOC_CREATE_DEBMAS, which has a statement Call Customer Function 001.
Browse the function module MASTERIDOC_CREATE_DEBMAS using transaction SE37. You will find that this customer function is invoked for every segment of IDOC type DEBMAS02. In fact, the function exit is called soon after the creation of an existing segment has been populated with data and appended to the IDOC data table (internal table). Also, the function exit is exporting the message type, IDOC type, and the segment name and is importing the IDOC extension type. It is also passing the IDOC data internal table. This indicates that the ALE function module is allowing you to populate additional segments for every existing segment and modify the existing segmentâs data.
Letâs write ABAP/4 code to accomplish the task of populating IDOC segment Z1SADRX with a contact personâs business address:
From SE37, display function module MASTERIDOC_CREATE_ DEBMAS.
Find Customer Function 001.
Double-click on 001.
The function EXIT_SAPLVV01_001 will be displayed.
Double-click on INCLUDE ZXVSVU01.
You will be asked to create a new include object. Proceed as desired.
Enter code (as in Listing 1).
Be sure to perform a main program check (Function Module -> Check -> main program) and extended program check (Function module -> Check -> Extended check).
Now that you have extended the IDOC and enhanced the ALE function module based on the requirements for the contact personâs business address on the Customer Master, letâs test the interface. You should create a logical system and define a port for this interface. You should also configure the Customer Distribution Model to indicate that message type DEBMAS is being distributed to this logical system. The only difference in configuration between a regular outbound ALE interface and an enhanced one is the partner profile definition. While maintaining the outbound parameters of the partner profile, make sure the IDOC type is ZDEBMASZ. The fields for Basic IDOC type and extension type are automatically populated with DEBMAS02 and ZDEBMASX, respectively.
To maintain the contact personâs business address of a customer:
Use transaction BD12 or from BALE go to Master Data ->Customer -> Send and send that Customer Master record by executing the transaction after filling in the relevant fields such as customer number, message type, and logical system.
Use transaction WE02 or WE05 to verify the IDOC created. You should see the new segment Z1SADRX populated with the correct data.
With SAP releases below 4.5B, you cannot capture changes to business address through change pointers because a change document object is not available for capturing business address changes, and also earlier releases have not been configured to write change documents for a contact personâs business address. If you would like this functionality, you can either create change document objects, generate function modules to create change documents, and perform ALE configuration to tie it in, or make a cosmetic change to the contact person screen data while changing the contact personâs business address so that it gets captured as a change to the Customer Master. Subsequently, the ALE enhancement that you performed captures the contact personâs business address.
Inbound interfaces. The process for enhancing inbound ALE interfaces is similar for outbound, with a few exceptions; specifically in the coding of customer functions (function exits) for the ALE/EDI function modules.
The first step is to create an IDOC extension for the specific Basic IDOC type by adding new segments at the appropriate hierarchy level: that is, associated to the relevant existing segment. Populate the data fields on the new segments with application data by the translator or external system/program before importing them into the R/3 System. Then, find the ALE function module that is invoked by the inbound processing. By browsing through the code or reading the documentation on the function exit enhancements using the SMOD transaction, identify the function exit in which you should place your code. The technique used in the code to post the additional or modified IDOC data to the application can vary based on the application rules and requirements, the data available at that point in processing, and the application function modules available to update the application tables. It is important to search first for application modules that process the data and see if they can be called within the function exit. If the additional data in the extended segments in specific to a custom table or resides in nonkey fields of a single or small set of tables, you may be able to update it directly by SQL statements in the function exit. This approach should be carefully evaluated and is certainly not highly recommended.
Another option is to use Call Transaction from within the function exit to process the additional data. For example, in the case of message type WMMBXY for inbound goods movements from a warehouse management system, the standard interface creates batches for materials, but does not update its characteristics. In such a case, you can use Call Transaction MSC1 to create the batch and assign characteristic values to it from within the function exit provided.
regards,
srinivas

Specify Account Assignment Types

Hi all...
Document split is active.
I am re-examing Account Assignment Types..
Additional Account Assignment Objects - Specify Account Assignment Types
So far I have only entered TT 100 for KOSTL for the relevant Depreciation areas
BUT retirement and depreciation transactions have all worked as expected despite not having TT entered.
IE TT 200 has not been entered in Specify Account Assignment Types but the Retirement transactions complete as expected.
So my question is whether it is necessary to enter all required TTs in the Specify Account Assignment Types?
If it is "correct" to enter them, how are the account assignments types used.
Would a rule of thumb be:
Balance Sheet accounts = APC Values Posting
Depreciation accounts = Depreciation Run.
Thanks...

Hi Thom,
no, you only need a generic transaction type " * ".
Example for KOSTL:
KOSTL Cost Center * Generic Trans. Type#Periodic Posting
KOSTL Cost Center * Generic Trans. Type#Account Assignment for Deprec
Regards Bernhard

Package issue for the generated types from XSD

Hi,
We are using top-down approach to generate the webservices using JDeveloper. All our wsdl we are including common XSD which defines a type to store the error information to be sent to the client when webservice fault occurs.
<FaultType>
<Errorcode/>
</FaultType>
While generating the webservice from WSDL which includes above xsd, A java class is created in the package which is specified in the wizard. For example com.example.FaultType
Every module is specifying their own package which is resulting in this class being generated in different package though Class definition is same.
How can we solve this problem. Should we use the namespace to generate the package where this class will be generated always in the same pacakge.
It is suggested from the documentation that we should explicitly specify the package instead of relying on the namespace.
Regards
Ashwani

Hi Shweta,
Most likely, you are having an issue with the message format used. The DII sample code that you are using may have been written for RPC/encoded service while the WSDL you are using advertize a service that is using documet/literal message format.
When you have issues like you have here, the best is to look at the raw payload exchanged between the clients and the service endpoint, and compare them to figure out what differs.
Payload captured with your DII code:
<?xml version = '1.0' encoding = 'UTF-8'?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns0="http://addr.webservices.samples.websphere.ibm.com">
<env:Body>
<ns0:getAddressFromName>
<name>hello</name>
</ns0:getAddressFromName>
</env:Body>
</env:Envelope>
Payload captured with Jdev generated proxy:
<?xml version = '1.0' encoding = 'UTF-8'?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns0="http://addr.webservices.samples.websphere.ibm.com">
<env:Body>
<ns0:getAddressFromName>
<ns0:name>hello</ns0:name>
</ns0:getAddressFromName>
</env:Body>
</env:Envelope>
You can see that 'name' uses a prefix in the second sample. You should be able to find your answer on the documentation (http://download-west.oracle.com/docs/cd/B31017_01/web.htm).
Using DII code requires a much dipper understanding on way XML need to be formated, based on the WSDL. Using the classes generated by JDeveloper will also have the advantage of making it easier to use WS-Security and other advanced features, once you get to the point were you want to consume more complex services.
Hope this helps,
Eric

Xml name space for generated types

By default the autotype or the servicegen ant task seem to be creating a namespace
from the java package name (like java:com.ventaso.external.common) for xml mapping
of user defined java classes. Is there a way to change this to name space I want
? Specifying the targetnamespace doesn't seem to help.
Thanks,
Siva

The targetNamespace is for webservice and not for the user defined classes.
Sorry for the confusion
Ajay
"Ajay" <[email protected]> wrote in message
news:[email protected]..
There is a targetNamespace attribute in the autotyp ant task. But there
was a bug in 8.1. Contact the support for a patch.
The following mail explains that
This looks like a bug. There is an undocument, not officially
supported workaround: add the following java doc
to yours source code -
* @wlws:webservice targetNamespace="http://foo.bar"
public class MyService {
Details here:
http://www.manojc.com/tutorial/sample3/source2wsdd.html
Regards,
-manoj
http://manojc.com
"Mark Fine" <[email protected]> wrote in message
news:[email protected]..
The attribute targetNamespace (of the autotype task) doesn't seem to putany
information into the types file and later my deployment descriptor (viathe
source2wsdd task) contains an invalid targetNamespace attribute with a
http://tempuri.org:
eg.
<web-services>
<web-service name="IndexService"
targetNamespace="http://tempuri.org/"
uri="/IndexWebService">
I don't think this causes any problems but there should be a way tospecify
the namespace.
Has anyone else seen this is WLS8.1?
"Siva" <[email protected]> wrote in message
news:[email protected]..
By default the autotype or the servicegen ant task seem to be creating anamespace
from the java package name (like java:com.ventaso.external.common) for
xml
mapping
of user defined java classes. Is there a way to change this to name
space
I want
? Specifying the targetnamespace doesn't seem to help.
Thanks,
Siva

Specify aggregation generated type?

Similar Messages

Maybe you are looking for