Namespace conflicts

I have this code:
var messageDyn:TextField;
messageDyn.text = Message.message;
messageDyn.autoSize = true;
and I get the error: 1151: A conflict exists with definition
messageDyn in namespace internal.
I don't understand why? It's typed as a TextField.

I was going to test the trace, but can't because the script
won't run. I'll give you a better background. And it looks like
Message isn't the movieclip (i forgot).
I'm working on an administrative chat tool. All the messages
show up as movieclips in a vertical list (not a list component,
just thing I made) the message is displayed in a movieclip with an
accept and reject button.
when the movie clip is made it is passed an object Message
which contains the username and message. so Message.message is the
actual message the user wrote.
If you were to trace Message.message it would just be the
users message they sent.
hopefully that makes more sense. ps thanks for helping

Similar Messages

OMB02904: Namespace conflict for map name

Hello all,
I was running an OMB script which was to create the several Mappings, and after the creation of all the mappings it was supposed to commit. This script was being run in UNIX env, but unfortunately the UNIX session got killed and script terminated, persumably before commit, because I do not see any of the mappings in OWB.
So I started the script again but got this message,
OMB02904: Namespace conflict for map name MAP_1: PRS-00303: Name <MAP_1> Already reserved under your user name. with
oracle session ID: 31
I cleaned up the oracle sessions in Design Rep, but still getting the same error message both at command line and in GUI.
Has anyone else in the forum experienced similar problem. Any suggestions or pointer on How to fix thi will be appreciated.
TIA

It seems that the mapping got created. Have you tried to refresh the OWB client to see the mapping by clicking on the "Synchronize this view with the repository" button (second icon from the left just under the "Project" menu entry)? If this is true, you will either have to delete the existing mapping and commit, or rename your mapping.
Regards:
Igor

OMB02904 Namespace Conflict Creating Mapping

Hi, we are running OWB 11GR2 on Windows and I am having trouble creating a mapping as allegedly it already exists. I can find no trace of this either through the GUI, through OMBPlus, or even using the JAVA APIs to find the offending mapping. It is also not visible in owbsys.all_iv_xform_maps or owbsys.all_iv_objects.
I cannot OMBDROP the mapping as it does not exist !
The full message in OMBPLUS is OMB02904 Namespace Conflict for map name WORK_SELF_EMPLOYED_INCOM_TA1M1: API0408 Within same namespace domain one object has already used the name WORK_SELF_EMPLOYED_INCOM_TA1M1
If you have any suggestions they would be gratefully received !
Phil

Our repository DB uses a Windows character set WE8MSWIN1252.
I have done a trawl through mappings and tables through all our Modules in a couple of ways (note my OMBPlus may not be the best you have ever seen). Note that these code snippets do work with 'real' mappings, but they do not find my phantom mapping.
set objectToFind WORK_SELF_EMPLOYED_INCOM.*
OMBCC '/IDP'
set moduleList [OMBLIST MODULES]
#set moduleList [list IPS2_SA1]
foreach moduleName $moduleList {
puts "Module name = $moduleName"
OMBCC '/IDP/$moduleName'
set tableList [OMBLIST TABLES '$objectToFind']
foreach tableName $tableList {
puts "=== Found table $moduleName/$tableName"
set mapList [OMBLIST MAPPINGS '$objectToFind']
foreach mapName $mapList {
puts "=== Found mapping $moduleName/$mapName"
============================================
Java API based search
set mapToFind WORK_SELF_EMPLOYED_INCOM_TA1M1
set repManager [java::call oracle.owb.connection.RepositoryManager getInstance]
set owbConnection [$repManager getConnection]
set projectManager [java::call oracle.owb.project.ProjectManager getInstance]
set project [$projectManager getWorkingProject]
# for every module
set modList [$project getOracleModuleNames]
set modCnt [$modList length]
for {set ic1 0} {$ic1 < $modCnt} {incr ic1} {
# Find your Oracle module
set modName [$modList get $ic1]
set modObj [$project findOracleModule $modName]
if {("$modName" != "RELEASES") && ("$modName" != "ARCHIVE")} {
# Proc logit defined earlier to output to a file
logit "Processing module $projName/$modName"
set mapList [$modObj getMapNames ]
set mapCnt [$mapList length]
for {set ic2 0} {$ic2 < $mapCnt} {incr ic2} {
set mapName [$mapList get $ic2]
if { "$mapName" == "$mapToFind" } {
logit "======= Found the bugger $mapName"
===============================
Nothing here either ....
SELECT *
FROM owbsys.all_iv_xform_maps
WHERE business_name LIKE 'WORK_SELF_EMPLOYED_INCOM%';
SELECT *
FROM owbsys.all_iv_objects
WHERE object_name LIKE 'WORK_SELF_EMPLOYED_INCOM%';

A problem due to a namespace conflict!!

Dear Edwin,
The problem of the proxy, was partially solved. this
has been "overcame" by using a private ISP
and not our university network. Though the
compilation of the example
orabpel/samples demos/AmazonFlow.bpel
was successful, there is still a problem.....
as shown in (1), since I am not able to execute the
AmazonFlow process instance with BPEL manager (see 2).
I would appreciate any help from you..
Thank you very much in advance!!!
Abdelkder
--------------- (1) -------------------
C:\orabpel\samples\demos\AmazonFlow>SETLOCAL
Buildfile: build.xml
main:
[bpelc] [Error] AmazonWebServices.wsdl:9:45: src-resolve.4.2: Error resolvin
g component 'soapenc:Array'. It was detected that 'soapenc:Array' is in namespac
e 'http://schemas.xmlsoap.org/soap/encoding/', but components from this namespac
e are not referenceable from schema document 'http://soap.amazon.com/schemas3/Am
azonWebServices.wsdl'. If this is the incorrect namespace, perhaps the prefix of
'soapenc:Array' needs to be changed. If this is the correct namespace, then an
appropriate 'import' tag should be added to 'http://soap.amazon.com/schemas3/Ama
zonWebServices.wsdl'.
[bpelc] bpelc> validating "C:\orabpel\samples\demos\AmazonFlow\AmazonFlow.bp
el" ...
[bpelc] bpelc> BPEL suitcase deployed to: C:\orabpel\domains\default\deploy
BUILD SUCCESSFUL
Total time: 1 minute 41 seconds
C:\orabpel\samples\demos\AmazonFlow>ENDLOCAL
When I execute the process with the BPEL manager I get
the following error in the BPEL server command prompt.
----------------- (2)------------------
<BaseCubeSessionBean::logError> Error while invoking bean "process manager": Fai
led to read wsdl.
Error happened when reading wsdl at "http://dekdouk:9700/orabpel/default/AmazonF
low/1.0/AmazonFlow.wsdl", because "WSDLException: faultCode=PARSER_ERROR: Error
reading file: No route to host: connect".
Make sure wsdl exists at that URL and is valid.
<2005-01-22 03:16:41,406> <ERROR> <default.collaxa.cube.engine.agents> <SimpleJo
b::execute> Error while executing agent.
An error occured while attempting to execute the job "dispatch" for agent "dispa
tch". The exception reported was : Dispatcher schedule error.
An error occurred while scheduling a batch message with the dispatcher. The exce
ption is: Couldn't initialize JMS resources.
An exception thrown while initializing JMS destination "java:comp/env/jms/collax
a/BPELWorkerQueue", the reason is Unable to create a connection to "dekdouk/213
.181.171.6:9,127" as user "null".
Please check your jms server configuration and make sure that you have configure
d the "java:comp/env/jms/collaxa/BPELWorkerQueue" destination and make sure that
your JMS server is up and running.

Dear Edwin,
The problem of the proxy, was partially solved. this
has been "overcame" by using a private ISP
and not our university network. Though the
compilation of the example
orabpel/samples demos/AmazonFlow.bpel
was successful, there is still a problem.....
as shown in (1), since I am not able to execute the
AmazonFlow process instance with BPEL manager (see 2).
I would appreciate any help from you..
Thank you very much in advance!!!
Abdelkder
--------------- (1) -------------------
C:\orabpel\samples\demos\AmazonFlow>SETLOCAL
Buildfile: build.xml
main:
[bpelc] [Error] AmazonWebServices.wsdl:9:45: src-resolve.4.2: Error resolvin
g component 'soapenc:Array'. It was detected that 'soapenc:Array' is in namespac
e 'http://schemas.xmlsoap.org/soap/encoding/', but components from this namespac
e are not referenceable from schema document 'http://soap.amazon.com/schemas3/Am
azonWebServices.wsdl'. If this is the incorrect namespace, perhaps the prefix of
'soapenc:Array' needs to be changed. If this is the correct namespace, then an
appropriate 'import' tag should be added to 'http://soap.amazon.com/schemas3/Ama
zonWebServices.wsdl'.
[bpelc] bpelc> validating "C:\orabpel\samples\demos\AmazonFlow\AmazonFlow.bp
el" ...
[bpelc] bpelc> BPEL suitcase deployed to: C:\orabpel\domains\default\deploy
BUILD SUCCESSFUL
Total time: 1 minute 41 seconds
C:\orabpel\samples\demos\AmazonFlow>ENDLOCAL
When I execute the process with the BPEL manager I get
the following error in the BPEL server command prompt.
----------------- (2)------------------
<BaseCubeSessionBean::logError> Error while invoking bean "process manager": Fai
led to read wsdl.
Error happened when reading wsdl at "http://dekdouk:9700/orabpel/default/AmazonF
low/1.0/AmazonFlow.wsdl", because "WSDLException: faultCode=PARSER_ERROR: Error
reading file: No route to host: connect".
Make sure wsdl exists at that URL and is valid.
<2005-01-22 03:16:41,406> <ERROR> <default.collaxa.cube.engine.agents> <SimpleJo
b::execute> Error while executing agent.
An error occured while attempting to execute the job "dispatch" for agent "dispa
tch". The exception reported was : Dispatcher schedule error.
An error occurred while scheduling a batch message with the dispatcher. The exce
ption is: Couldn't initialize JMS resources.
An exception thrown while initializing JMS destination "java:comp/env/jms/collax
a/BPELWorkerQueue", the reason is Unable to create a connection to "dekdouk/213
.181.171.6:9,127" as user "null".
Please check your jms server configuration and make sure that you have configure
d the "java:comp/env/jms/collaxa/BPELWorkerQueue" destination and make sure that
your JMS server is up and running.

Namespaces conflicts

Hi,
I've faced the following problem during mapping:
Returning message has smth. like this structure:
<MainElement ns1="...">value</MainElement>
<SubElement ns2="....">value</SubElement>
So, as it becomes clear from this xml fragment, two elements have different namespaces. I can adopt xml schema definition to ns1(just point ns1 as target ns), so it becomes possible to read upper-level nodes. But the whole SubElement with ns2 and all its structure remains unavaliable for me, though I really need it
May be someone faced the trouble and knows how to solve it?? I've tried lots of combinations, e.g. putting ns2 as target ns in xsd file, but it's still no good.
Looking forward to any kind of help.
Thank you.

Hi Dmitriy,
since you have change your response message, then you have to do a little workaround.............Stefan's blog applies to reciever adapters..........so get your response message via your sender adapter and without doing any mapping output it via reciever file adapter by using XMLAnonymiserBean and thereby removing namespaces in it and outputting it to a file.............
then via a sender file adapter, pick this response message file and do message mapping on it and then send it to the target system via your receiver adapter....
Regards,
Rajeev Gupta

Java class namespace conflict between two Web services

We have been asked to develop a client that can call two different versions of a live Web service. Unfortunately the people who developed the services that we have to call used overlapping namespaces when they created the new version. We are using the Java 6 JDK Web Services stack. We have generated the classes for our 2 clients using wsimport and include them on our classpath in two separate jars. Of course this should never happen because you should never have two different objects sharing the same namespace. We don't control the service though, so can't change things there. Is there some way for us to remap to objects in a different namespace for one of the services. Any help would be much appreciated, even if it's just to say that this is not possible.
James

did you try specifying a different package when you run wsimport?
also, if you can't find a jaxws solution, you can always load each webservice jar in a separate classloader in your application and run your webservice access code from these separate classloaders.

CS4 namespace issues

I'm getting strange compiler errors, that seem to be CS4
getting instance variables confused with class packages.
- 'Call to a possibly undefined method addEventListener' on
var update
- 'Access of undefined property keyEquivalent in package
update.
- 'void used where a Boolean value was expected on bool =
!bool;
I'm guessing the first two issues are to do with the
classpath's being somehow screwed up...I'm not entirely sure, if my
package classpath path from CS3 is a source path, library, or
external library path in CS4. The second error sounds as if my
variable 'update:NativeMenuItem' is somehow being confused for an
'update' package I have.....which is odd.

Yeah, so if I change the variable name from update to upd, it
compiles properly in CS4. Is something broken with CS4 namespaces?
The same .fla document worked in CS3, and I'm only importing a
class within the update package. It worries me how many similar
issues I may bump into with other existing projects, as I've never
had the Document class reference package names, in a way that
conflicts with variables using the same name.
import update.UpdateManager;
var update:Object = {test:'namespace conflict'};
trace(update.test);
//1202: Access of undefined property test in package
update.

Namespace issues

I'm curious if there are known bugs in the way namespaces are handled in the current (2.1.0) beta of XSDBuilder.
For example, I have two schema, a.xsd and b.xsd.
a.xsd has no namespace. b.xsd has the namespace 'foo', and <include>s a.xsd (thus coercing the elements in a into the 'foo' namespace).
However, when trying to build() b.xsd from the Oracle XSDBuilder I will get error messages that 'Element ':bar' is not defined', where bar is defined in a.xsd and accessed in b.xsd as 'foo:bar'. It seems to be stripping off the 'foo' namespace.
This same example works with the current (1.3.0) version of the Xerces parser, so I believe that the schemas created are in fact correct and valid. (XMLSpy also validates these schemas).

Yeah, so if I change the variable name from update to upd, it
compiles properly in CS4. Is something broken with CS4 namespaces?
The same .fla document worked in CS3, and I'm only importing a
class within the update package. It worries me how many similar
issues I may bump into with other existing projects, as I've never
had the Document class reference package names, in a way that
conflicts with variables using the same name.
import update.UpdateManager;
var update:Object = {test:'namespace conflict'};
trace(update.test);
//1202: Access of undefined property test in package
update.

Transfer Structure Error

Hi Guys,
I am getting the following error when trying to activate Transfer Structure for 0PLANT_TEXT in BW.
Error when creating transfer structure /BIC/CCGB0PLANT_TEXT in source system ORAGDV130
Message no. R3104
Diagnosis
An error occurred when creating transfer structure /BIC/CCGB0PLANT_TEXT as an IDoc segment in source system ORAGDV130 .
System response
The action was terminated. No data was changed.
Procedure
Use the generation log in source system ORAGDV130 to identify the error, and remove the cause.
I am using PSA as the transfer method. Any help is appreciated.
Thanks.

Hi Govind,
To implement what is said in the note IS VERY EASY!
I have even created this program in my system. It seems to be very very useful program. Not only for your case. THE PROGRAM CHECKS CONSISTENCIES IN THE SOURCE SYSTEM AND CORRECT THEM! It may help in many problems with source systems.
So, here is a way to implement the program.
- In the text tabstrip of the note click on 'Correction Instructions' tabstrip.
- Then in the 'Ref. Correction' column choose a number that corresponds to your system PI (click on it).
- Click on a report name 'z_rs_scrsystem_r3_check'.
- In your BW system execute tcode SE38 (or ask someone with a development key), give the name 'z_rs_scrsystem_r3_check', click on a button 'create'.
- Enter program description, choose 'executable' option.
- Into the screen of ABAP Editor copy-paste the code from the note correction instructions.
- Click on 'Check', then 'Activate' icons.
- If everything is OK, press F8 (execute).
Then follow the note:
"These programs have the following input parameters:
SLOGSYS Specify the logical system name of your source system here
RLOGSYS Specify the logical system name of the BW system here
If you enter nothing here, all existing BW source system connections are processed.
Use the NO_DB_UP parameter to control whether the program works in check or correction mode. The NO_DB_UP = 'X' default represents check mode.
2. First execute the Z_RS_SCRSYSTEM_R3_CHECK program in check mode. The inconsistencies detected by the program are issued as a log. Now start the programs in correction mode (NO_DB_UP = ' '). Then execute the program again in check mode (NO_DB_UP = 'X'). This program may not eliminate all inconsistencies during the first correction run. Then execute the program again in the check mode (NO_DB_UP = 'X'). This program may not eliminate all inconsistencies during the first correction run.
3. If the error continues to occur:
Check the transfer structure in the source system using transaction SE11. Use note 147195 if namespace conflicts are reported in the consistency log.
After the correction has been made, you should check to see whether it is possible to switch your transfer rules from the IDoc transfer method to the PSA transfer method.
We recommend that you use the PSA transfer method."
Best regards,
Eugene
Message was edited by: Eugene Khusainov

Need guidance entering my own data in a PDF file

Please refer to this example:
http://www.gnupdf.org/Introduction_to_PDF
I am trying to teach myself PDF internals. My immediate objective is to save some private data in my PDF files. My data is structured as "variable/value" pairs but I chose not to save it as custom properties because of its bulk and the possibility of confusion and undesired manipulation by the end user.
The above example immediately suggests that I should use an object of "dictionary" type. Let's try to assemble the file manually:
44 0 obj
<<
(Favorite Baseball Team) (Boston Red Sox)
(Age) (35)
(Planet of Birth) (Klingon)
>>
endobj
Is the above initial attempt correct? I will of course use the corresponding API to create the dictionary, but I am concerned about breaking things. Won't Acrobat get confused when it finds this foreign stuff?
TIA,
-Ramon

Hi Leonard,
Thanks for your always valuable help. FYI, my data is of a global nature. I suppose I should come up with some unique name ("MyPrivateData" or something) and place such entry in the Catalog?
This thread brings up a related topic. It is about the uniqueness of the JavaScript namespace. My PDF files are generated automatically and JavaScript code is added to them. I haven't done any tests yet, but I foresee the following problem: those generated PDF files may end up being merged with each other which brings the potential of namespace conflicts.
Let's say that the first JS-laden document has 3 pages and another one has 2 pages. I suppose there is no way to restrict it like: "this JS code applies to the first 3 pages only". As soon as the 2 documents are merged all the JS code (and worst of all: the variable and function names) applies to the 5 combined pages, correct?
There are 2 possible solutions:
- Perhaps there is a way to declare some JS code as belonging to one page only?
- Use collections. This brings a whole new layer of complexity and expense.
Thanks again,
-Ramon

JAXB Problem: xjc gives an error

Hello everyone,
I would like to use JAXB to extract various information from a class of XML documents that conform to a schema. After tweaking the schema so that I avoid namespace conflicts with xjc, I settled the namespace conflicts, but I got the following error. Even if you don't have an answer, could you give me some pointers so that I can at least begin tackling the problem?
Thank you very much!
Here is the output of the command I ran:
C:\Documents and Settings\Berk Kapicioglu\Desktop>xjc -p test.jaxb ownership4ADocument.xsd.xml -d work
parsing a schema...
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: java.util.MissingResourceException: Can't find resource for bundle ja
va.util.PropertyResourceBundle, key parser.cc.8
at java.util.ResourceBundle.getObject(ResourceBundle.java:314)
at java.util.ResourceBundle.getString(ResourceBundle.java:274)
at com.sun.msv.datatype.xsd.regex.RegexParser.ex(RegexParser.java:138)
at com.sun.msv.datatype.xsd.regex.ParserForXMLSchema.parseCharacterClass
(ParserForXMLSchema.java:291)
at com.sun.msv.datatype.xsd.regex.RegexParser.parseAtom(RegexParser.java
:736)
at com.sun.msv.datatype.xsd.regex.RegexParser.parseFactor(RegexParser.ja
va:638)
at com.sun.msv.datatype.xsd.regex.RegexParser.parseTerm(RegexParser.java
:342)
at com.sun.msv.datatype.xsd.regex.RegexParser.parseRegex(RegexParser.jav
a:320)
at com.sun.msv.datatype.xsd.regex.RegexParser.parse(RegexParser.java:158
at com.sun.msv.datatype.xsd.regex.RegularExpression.setPattern(RegularEx
pression.java:3040)
at com.sun.msv.datatype.xsd.regex.RegularExpression.setPattern(RegularEx
pression.java:3051)
at com.sun.msv.datatype.xsd.regex.RegularExpression.<init>(RegularExpres
sion.java:3017)
at com.sun.msv.datatype.xsd.PatternFacet.compileRegExps(PatternFacet.jav
a:79)
at com.sun.msv.datatype.xsd.PatternFacet.<init>(PatternFacet.java:67)
at com.sun.msv.datatype.xsd.TypeIncubator.derive(TypeIncubator.java:261)
at com.sun.tools.xjc.reader.xmlschema.DatatypeBuilder.restrictionSimpleT
ype(DatatypeBuilder.java:82)
at com.sun.xml.xsom.impl.RestrictionSimpleTypeImpl.apply(RestrictionSimp
leTypeImpl.java:66)
at com.sun.tools.xjc.reader.xmlschema.DatatypeBuilder.build(DatatypeBuil
der.java:65)
at com.sun.tools.xjc.reader.xmlschema.SimpleTypeBuilder.buildPrimitiveTy
pe(SimpleTypeBuilder.java:161)
at com.sun.tools.xjc.reader.xmlschema.SimpleTypeBuilder.access$100(Simpl
eTypeBuilder.java:50)
at com.sun.tools.xjc.reader.xmlschema.SimpleTypeBuilder$Functor.checkCon
version(SimpleTypeBuilder.java:201)
at com.sun.tools.xjc.reader.xmlschema.SimpleTypeBuilder$Functor.restrict
ionSimpleType(SimpleTypeBuilder.java:276)
at com.sun.xml.xsom.impl.RestrictionSimpleTypeImpl.apply(RestrictionSimp
leTypeImpl.java:66)
at com.sun.tools.xjc.reader.xmlschema.SimpleTypeBuilder.build(SimpleType
Builder.java:93)
at com.sun.tools.xjc.reader.xmlschema.cs.DefaultClassBinder.simpleType(D
efaultClassBinder.java:130)
at com.sun.xml.xsom.impl.SimpleTypeImpl.apply(SimpleTypeImpl.java:89)
at com.sun.tools.xjc.reader.xmlschema.cs.ClassSelector._bindToClass(Clas
sSelector.java:212)
at com.sun.tools.xjc.reader.xmlschema.cs.ClassSelector.bindToType(ClassS
elector.java:177)
at com.sun.tools.xjc.reader.xmlschema.TypeBuilder.elementDeclFlat(TypeBu
ilder.java:213)
at com.sun.tools.xjc.reader.xmlschema.FieldBuilder.elementDecl(FieldBuil
der.java:384)
at com.sun.xml.xsom.impl.ElementDecl.apply(ElementDecl.java:174)
at com.sun.tools.xjc.reader.xmlschema.FieldBuilder.build(FieldBuilder.ja
va:76)
at com.sun.tools.xjc.reader.xmlschema.DefaultParticleBinder$Builder.part
icle(DefaultParticleBinder.java:399)
at com.sun.tools.xjc.reader.xmlschema.BGMBuilder.applyRecursively(BGMBui
lder.java:490)
at com.sun.tools.xjc.reader.xmlschema.DefaultParticleBinder$Builder.mode
lGroup(DefaultParticleBinder.java:462)
at com.sun.xml.xsom.impl.ModelGroupImpl.apply(ModelGroupImpl.java:80)
at com.sun.tools.xjc.reader.xmlschema.DefaultParticleBinder$Builder.buil
d(DefaultParticleBinder.java:368)
at com.sun.tools.xjc.reader.xmlschema.DefaultParticleBinder$Builder.part
icle(DefaultParticleBinder.java:433)
at com.sun.tools.xjc.reader.xmlschema.DefaultParticleBinder$Builder.buil
d(DefaultParticleBinder.java:371)
at com.sun.tools.xjc.reader.xmlschema.DefaultParticleBinder.build(Defaul
tParticleBinder.java:70)
at com.sun.tools.xjc.reader.xmlschema.ct.FreshComplexTypeBuilder$1.parti
cle(FreshComplexTypeBuilder.java:48)
at com.sun.xml.xsom.impl.ParticleImpl.apply(ParticleImpl.java:68)
at com.sun.tools.xjc.reader.xmlschema.ct.FreshComplexTypeBuilder.build(F
reshComplexTypeBuilder.java:35)
at com.sun.tools.xjc.reader.xmlschema.ct.ComplexTypeFieldBuilder.build(C
omplexTypeFieldBuilder.java:56)
at com.sun.tools.xjc.reader.xmlschema.FieldBuilder.complexType(FieldBuil
der.java:228)
at com.sun.xml.xsom.impl.ComplexTypeImpl.apply(ComplexTypeImpl.java:194)
at com.sun.tools.xjc.reader.xmlschema.FieldBuilder.build(FieldBuilder.ja
va:76)
at com.sun.tools.xjc.reader.xmlschema.cs.ClassSelector.build(ClassSelect
or.java:340)
at com.sun.tools.xjc.reader.xmlschema.cs.ClassSelector.access$000(ClassS
elector.java:54)
at com.sun.tools.xjc.reader.xmlschema.cs.ClassSelector$Binding.build(Cla
ssSelector.java:107)
at com.sun.tools.xjc.reader.xmlschema.cs.ClassSelector.executeTasks(Clas
sSelector.java:240)
at com.sun.tools.xjc.reader.xmlschema.BGMBuilder._build(BGMBuilder.java:
118)
at com.sun.tools.xjc.reader.xmlschema.BGMBuilder.build(BGMBuilder.java:8
0)
at com.sun.tools.xjc.GrammarLoader.annotateXMLSchema(GrammarLoader.java:
424)
at com.sun.tools.xjc.GrammarLoader.load(GrammarLoader.java:130)
at com.sun.tools.xjc.GrammarLoader.load(GrammarLoader.java:79)
at com.sun.tools.xjc.Driver.run(Driver.java:177)
at com.sun.tools.xjc.Driver._main(Driver.java:80)
at com.sun.tools.xjc.Driver.access$000(Driver.java:46)
at com.sun.tools.xjc.Driver$1.run(Driver.java:60)

Hi,
A similar error occur to me twice.
One because pattern specification error (The pattern was incorrectly written)
The other one was because I had in the directory JAVA_HOME\jre\lib\endorsed the files that come from JWSDP_HOME\jaxb\lib.
This files (jaxb-api.jar, jaxb-impl.jar, jaxb-libs.jar, jaxb-xjc.jar) should only be in the directory where they come from JWSDP_HOME\jaxb\lib
If you have them in the JAVA_HOME\jre\lib\endorsed directory try removing them from there.
Hope I help you.

Xsl schema import from within a wsdl file

I have a namespace conflict issue validating a bpel process.
The message error is as follow:
[bpelc] [Error] SMSSenderEnablerSEIWrapper.wsdl.2.wsdl:19:80: src-resolve.4.2: Error resolving component 'tns2:InvocationContext'. It was detected that 'tns2:InvocationContext' is in namespace 'http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI', but components from this namespace are not referenceable from schema document 'file:/D:/home/guillaume/workspace/SMSMulticast2/services/SMSSenderEnablerSEIWrapper.wsdl.2.wsdl'. If this is the incorrect namespace, perhaps the prefix of 'tns2:InvocationContext' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:/D:/home/guillaume/workspace/SMSMulticast2/services/SMSSenderEnablerSEIWrapper.wsdl.2.wsdl'.
[bpelc] [Error] SMSSenderEnablerSEIWrapper.wsdl.2.wsdl:20:76: src-resolve.4.2: Error resolving component 'tns1:SMSMessageETO'. It was detected that 'tns1:SMSMessageETO' is in namespace 'http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI', but components from this namespace are not referenceable from schema document 'file:/D:/home/guillaume/workspace/SMSMulticast2/services/SMSSenderEnablerSEIWrapper.wsdl.2.wsdl'. If this is the incorrect namespace, perhaps the prefix of 'tns1:SMSMessageETO' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:/D:/home/guillaume/workspace/SMSMulticast2/services/SMSSenderEnablerSEIWrapper.wsdl.2.wsdl'.
I've already seen this kind of error in other posts, but this was encountered with xsd files. In my case, I'm trying to use complexTypes defined in a schema, defined itself in a WSDL file. The needed file (SMSSenderEnablerSEI) is referenced in the bpel.xml file.
// Here the BPEL file (SMSMulticast2.bpel)
<pre>

<process name="SMSMulticast2" targetNamespace="http://com.osa.mdsp.csp.ena.smms.smsmulti/V1.0" suppressJoinFailure="yes" xmlns:tns="http://com.osa.mdsp.csp.ena.smms.smsmulti/V1.0" xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:bpelx="http://schemas.oracle.com/bpel/extension" xmlns:ora="http://schemas.oracle.com/xpath/extension" xmlns:nsxml0="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:nsxml1="http://com.osa.mdsp.enabler.sei/PimEnabler:DirectService/2004/V1.0">
     
     
     
     
     <partnerLinks>
          
          <partnerLink name="client" partnerLinkType="tns:SMSMulticast2" myRole="SMSMulticast2Provider"/>
          <partnerLink name="SMSEnabler" partnerLinkType="nsxml0:SMSSenderEnablerRemoteLink" partnerRole="SMSSenderEnablerRemoteProvider"/>
          <partnerLink name="PIMEnabler" partnerLinkType="nsxml1:PimDirectServiceEnablerSEIImplLink" partnerRole="PimDirectServiceEnablerSEIImplProvider"/>
     </partnerLinks>
     
     
     
     
     <variables>
          
          <variable name="smsmultiRequest" messageType="tns:SMSMulticast2RequestMessage"/>
          
          <variable name="smsmultiResponse" messageType="tns:SMSMulticast2ResponseMessage"/>
          <variable name="count" type="xsd:integer"/>
          <variable name="contactRequest" messageType="nsxml1:retrieveContactRequest"/>
          <variable name="smsRequest" messageType="nsxml0:sendSMSRequest"/>
          <variable name="smsResponse" messageType="nsxml0:sendSMSResponse"/>
          <variable name="contactResponse" messageType="nsxml1:addContactResponse"/>
     </variables>
     
     
     
     
     
     <sequence name="main">
          
          <receive name="receiveInput" partnerLink="client" portType="tns:SMSMulticast2PT" operation="process" variable="smsmultiRequest" createInstance="yes"/>
          
          <assign name="setProperties">
               <copy>
                    <from expression="5"></from>
                    <to variable="count"/>
               </copy>
               <copy>
                    <from variable="smsmultiRequest" part="parameter" query="/tns:SMSMulticast2Request/tns:inputMSISDN"></from>
                    <to variable="smsRequest" part="parameters" query="/nsxml0:sendSMS/nsxml0:sms/nsxml0:senderAddress"/>
               </copy>
               <copy>
                    <from variable="smsmultiRequest" part="parameter" query="/tns:SMSMulticast2Request/tns:inputMessage"></from>
                    <to variable="smsRequest" part="parameters" query="/nsxml0:sendSMS/nsxml0:sms/nsxml0:content"/>
               </copy>
          </assign>
          <while name="foreach" condition="bpws:getVariableData('count') > 0"><sequence><invoke name="invoke-1" partnerLink="SMSEnabler" portType="nsxml0:SMSSenderEnablerRemote" operation="sendSMS" inputVariable="smsRequest" outputVariable="smsResponse"/>
                    <assign name="decrease"><copy>
                              <from expression="bpws:getVariableData('count') - 1"></from>
                              <to variable="count"/>
                         </copy>
                    </assign>
               </sequence>
          </while>
          
          <reply name="sendResult" partnerLink="client" portType="tns:SMSMulticast2PT" operation="process" variable="smsmultiResponse"/>
     </sequence>
</process>
// Here the WSDL file: SMSSenderEnablerSEIWrapper.wsdl
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions
     name="SMSSenderEnablerSEI"
targetNamespace="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
     xmlns="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
     xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:impl="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:tns1="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
xmlns:tns2="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI"
xmlns:tns4="http://com.osa.mdsp.enabler.sei.exception/SMSEnabler/V1.0/SMSSenderSEI"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
     <xsd:schema
          elementFormDefault="qualified"
          targetNamespace="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI"
          xmlns="http://www.w3.org/2001/XMLSchema"
          xmlns:tns="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI">
          <xsd:complexType name="InvocationContext">
          <xsd:sequence>
          <xsd:element
          maxOccurs="unbounded"
          name="properties"
          nillable="true"
          type="xsd:string"/>
          </xsd:sequence>
          </xsd:complexType>
          <xsd:complexType name="EnablerException">
          <xsd:sequence>
          <xsd:element name="errorMessage" nillable="true" type="xsd:string"/>
          <xsd:element name="errorCode" type="xsd:int"/>
          </xsd:sequence>
          </xsd:complexType>
          <xsd:element name="EnablerException" nillable="true" type="tns:EnablerException"/>
          </xsd:schema>
<xsd:schema
elementFormDefault="qualified"
targetNamespace="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
xmlns="http://www.w3.org/2001/XMLSchema"
               xmlns:tns1="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
               xmlns:tns2="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI">
<xsd:element name="sendSMS">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ctx" nillable="true" type="tns2:InvocationContext"/>
<xsd:element name="sms" nillable="true" type="tns1:SMSMessageETO"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="sendSMSResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="sendSMSReturn" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="sendSMSWithNotification">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ctx" nillable="true" type="tns2:InvocationContext"/>
<xsd:element name="sms" nillable="true" type="tns1:SMSMessageETO"/>
<xsd:element name="notificationURL" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="sendSMSWithNotificationResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="sendSMSWithNotificationReturn" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="sendSMSToAlias">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ctx" nillable="true" type="tns2:InvocationContext"/>
<xsd:element name="sms" nillable="true" type="tns1:SMSMessageETO"/>
<xsd:element name="serviceId" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="sendSMSToAliasResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="sendSMSToAliasReturn" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="sendSMSWithNotificationToAlias">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ctx" nillable="true" type="tns2:InvocationContext"/>
<xsd:element name="sms" nillable="true" type="tns1:SMSMessageETO"/>
<xsd:element name="serviceId" nillable="true" type="xsd:string"/>
<xsd:element name="notificationURL" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="sendSMSWithNotificationToAliasResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element
name="sendSMSWithNotificationToAliasReturn"
nillable="true"
type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
<xsd:schema
elementFormDefault="qualified"
targetNamespace="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:impl="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
               xmlns:tns1="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
               xmlns:tns2="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI">
               <xsd:complexType name="SMSMessageETO">
<xsd:sequence>
<xsd:element name="content" nillable="true" type="xsd:string"/>
<xsd:element name="earliestDeliveryTime" nillable="true" type="xsd:dateTime"/>
<xsd:element name="expiryDate" nillable="true" type="xsd:dateTime"/>
<xsd:element name="priority" nillable="true" type="xsd:string"/>
<xsd:element name="recipient" nillable="true" type="xsd:string"/>
<xsd:element name="senderAddress" nillable="true" type="xsd:string"/>
<xsd:element name="contentSentEncoding" nillable="true" type="xsd:string"/>
<xsd:element name="smsContentSentInGsm7Bits" type="xsd:boolean"/>
<xsd:element name="smsContentSentInUcs2" type="xsd:boolean"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
<xsd:schema
elementFormDefault="qualified"
targetNamespace="http://com.osa.mdsp.enabler.sei.exception/SMSEnabler/V1.0/SMSSenderSEI"
xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:impl="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
xmlns:tns4="http://com.osa.mdsp.enabler.sei.exception/SMSEnabler/V1.0/SMSSenderSEI"
               xmlns:tns1="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
               xmlns:tns2="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<xsd:complexType name="SMSException">
<xsd:sequence>
<xsd:element name="errorCode" type="xsd:int"/>
<xsd:element name="message" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="SMSException" nillable="true" type="tns4:SMSException"/>
</xsd:schema>
</wsdl:types>
<wsdl:message name="sendSMSRequest">
<wsdl:part element="impl:sendSMS" name="parameters"/>
</wsdl:message>
<wsdl:message name="sendSMSToAliasResponse">
<wsdl:part element="impl:sendSMSToAliasResponse" name="parameters"/>
</wsdl:message>
<wsdl:message name="EnablerException">
<wsdl:part element="tns2:EnablerException" name="fault"/>
</wsdl:message>
<wsdl:message name="sendSMSToAliasRequest">
<wsdl:part element="impl:sendSMSToAlias" name="parameters"/>
</wsdl:message>
<wsdl:message name="sendSMSWithNotificationToAliasRequest">
<wsdl:part element="impl:sendSMSWithNotificationToAlias" name="parameters"/>
</wsdl:message>
<wsdl:message name="sendSMSWithNotificationToAliasResponse">
<wsdl:part
element="impl:sendSMSWithNotificationToAliasResponse"
name="parameters"/>
</wsdl:message>
<wsdl:message name="SMSException">
<wsdl:part element="tns4:SMSException" name="fault"/>
</wsdl:message>
<wsdl:message name="sendSMSWithNotificationResponse">
<wsdl:part element="impl:sendSMSWithNotificationResponse" name="parameters"/>
</wsdl:message>
<wsdl:message name="sendSMSWithNotificationRequest">
<wsdl:part element="impl:sendSMSWithNotification" name="parameters"/>
</wsdl:message>
<wsdl:message name="sendSMSResponse">
<wsdl:part element="impl:sendSMSResponse" name="parameters"/>
</wsdl:message>
<wsdl:portType name="SMSSenderEnablerRemote">
<wsdl:operation name="sendSMS">
<wsdl:input message="impl:sendSMSRequest" name="sendSMSRequest"/>
<wsdl:output message="impl:sendSMSResponse" name="sendSMSResponse"/>
<wsdl:fault message="impl:SMSException" name="SMSException"/>
<wsdl:fault message="impl:EnablerException" name="EnablerException"/>
</wsdl:operation>
<wsdl:operation name="sendSMSWithNotification">
<wsdl:input
message="impl:sendSMSWithNotificationRequest"
name="sendSMSWithNotificationRequest"/>
<wsdl:output
message="impl:sendSMSWithNotificationResponse"
name="sendSMSWithNotificationResponse"/>
<wsdl:fault message="impl:SMSException" name="SMSException"/>
<wsdl:fault message="impl:EnablerException" name="EnablerException"/>
</wsdl:operation>
<wsdl:operation name="sendSMSToAlias">
<wsdl:input message="impl:sendSMSToAliasRequest" name="sendSMSToAliasRequest"/>
<wsdl:output
message="impl:sendSMSToAliasResponse"
name="sendSMSToAliasResponse"/>
<wsdl:fault message="impl:SMSException" name="SMSException"/>
<wsdl:fault message="impl:EnablerException" name="EnablerException"/>
</wsdl:operation>
<wsdl:operation name="sendSMSWithNotificationToAlias">
<wsdl:input
message="impl:sendSMSWithNotificationToAliasRequest"
name="sendSMSWithNotificationToAliasRequest"/>
<wsdl:output
message="impl:sendSMSWithNotificationToAliasResponse"
name="sendSMSWithNotificationToAliasResponse"/>
<wsdl:fault message="impl:SMSException" name="SMSException"/>
<wsdl:fault message="impl:EnablerException" name="EnablerException"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding
name="SMSSenderEnablerRemoteSoapBinding"
type="impl:SMSSenderEnablerRemote">
<wsdlsoap:binding
style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="sendSMS">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sendSMSRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sendSMSResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
<wsdl:fault name="SMSException">
<wsdlsoap:fault name="SMSException" use="literal"/>
</wsdl:fault>
<wsdl:fault name="EnablerException">
<wsdlsoap:fault name="EnablerException" use="literal"/>
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="sendSMSWithNotification">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sendSMSWithNotificationRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sendSMSWithNotificationResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
<wsdl:fault name="SMSException">
<wsdlsoap:fault name="SMSException" use="literal"/>
</wsdl:fault>
<wsdl:fault name="EnablerException">
<wsdlsoap:fault name="EnablerException" use="literal"/>
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="sendSMSToAlias">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sendSMSToAliasRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sendSMSToAliasResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
<wsdl:fault name="SMSException">
<wsdlsoap:fault name="SMSException" use="literal"/>
</wsdl:fault>
<wsdl:fault name="EnablerException">
<wsdlsoap:fault name="EnablerException" use="literal"/>
</wsdl:fault>
</wsdl:operation>
<wsdl:operation name="sendSMSWithNotificationToAlias">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="sendSMSWithNotificationToAliasRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="sendSMSWithNotificationToAliasResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
<wsdl:fault name="SMSException">
<wsdlsoap:fault name="SMSException" use="literal"/>
</wsdl:fault>
<wsdl:fault name="EnablerException">
<wsdlsoap:fault name="EnablerException" use="literal"/>
</wsdl:fault>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="SMSSenderEnablerRemoteService">
<wsdl:port
binding="impl:SMSSenderEnablerRemoteSoapBinding"
name="SMSSenderEnablerRemote">
<wsdlsoap:address
location="http://localhost:8888/Simulateur/services/SMSSenderEnablerRemote?wsdl"/>
</wsdl:port>
</wsdl:service>
<plnk:partnerLinkType name="SMSSenderEnablerRemoteLink">
<plnk:role name="SMSSenderEnablerRemoteProvider">
<plnk:portType name="impl:SMSSenderEnablerRemote"/>
</plnk:role>
</plnk:partnerLinkType>
</wsdl:definitions>
Is that possible to reuse (in a BPEL file) schemas types defined in a wsdl file with Oracle PM? Could you give me a hint to solve this problem?
Many Thanks
Guillaume

You need to use the XSLT before you do assignment to achieve this, to
change the message to the correct namespace.
Please refer to sample at
"orabpel\samples\tutorials\114.XSLTTransformations" which talks about
how to use XSLT transformation.
And please refer to
"orabpel\samples\tutorials\121.FileAdapter\ComplexStructure" sample
especially "InvToPo.xslt" which talks about doing transformations
between 2 structures pointing to different namespaces.

ABAP Server Proxy: Dependency Issue.

Hi,
SCWV1
Namespace1
-     Service Interface (Inbound_SI) // Referring MT and DT from SWCV2.
SWCV2
Namespace2
-     Message Type (messageType)
-     Data Type (dataType)
Dependencies: I created dependencies in SVCW1 in ESR. I assign the SWCV2 in ESR>SWCV>(In Details Tab)
Now when I am creating server proxy I can see the service interface in namespace1 but I am not seeing DT and MT in the same namespace. Will it creates any problem? Any chance of namespace conflicts?
Thank you.
Farooq

Hi Farooq,
It will be a problem if you don't generate the proxies (in SPROXY) for the dependant MT's & DT's in SWCV2 first.
Go to SWCV2 & relevant namespace (where referenced MT's & DT's reside). If they are in a red checkered flag status then you won't be able to generate the server proxy for the service interface in SWCV1.
Regards, Trevor

Source port type for BPELProcess does not match target port type for EJB

Hi gurus,
I have a problem with calling EJBs from a 11.1.1.3 composite. The following summarizes the issue:
- there are several EJBs within the same package deployed on a WLS server.
- these beans have method names that are the same, for example create(), delete() etc.
- using the EJB Service Adapter I have created 3 References, one for each of the 3 beans I need to invoke in a BPEL process.
- each bean is imported into the project with their own *.wsdl *Ref.wsdl files.
- each wsdl imports a namespace based on the java package name
- now i have 3 wsdls, importing the same namespace and namespace conflicts arise.
At this point I'm thinking, 'no problem, just change the namespaces manually'
- whenever i try to change the namespace that JDev gives the Reference components I end up with the compilation error:
Source port type for "BPELProcess" does not match target port type for "EJBRef"
It seems that the namespace must be the same as the package name, even though I resolved all the references to the new namespaces and ensure they all match.
The problem appears to be in the BPELProcess.componentType file.
<reference name="HelloEJBRef" ui:wsdlLocation="HelloEJBRef.wsdl">
<interface.wsdl interface="http://package.workspace.com/HelloEJB#wsdl.interface(HelloEJB)"/>
</reference>
If the namespace (text before the #) is changed at all from the default, even if it matches the wsdl, results in the port type mismatch error above.
Any ideas?
btw, running SOA 11.1.1.3, JDev 10.1.1.3, EJB 3.0

Hi gurus,
I have a problem with calling EJBs from a 11.1.1.3 composite. The following summarizes the issue:
- there are several EJBs within the same package deployed on a WLS server.
- these beans have method names that are the same, for example create(), delete() etc.
- using the EJB Service Adapter I have created 3 References, one for each of the 3 beans I need to invoke in a BPEL process.
- each bean is imported into the project with their own *.wsdl *Ref.wsdl files.
- each wsdl imports a namespace based on the java package name
- now i have 3 wsdls, importing the same namespace and namespace conflicts arise.
At this point I'm thinking, 'no problem, just change the namespaces manually'
- whenever i try to change the namespace that JDev gives the Reference components I end up with the compilation error:
Source port type for "BPELProcess" does not match target port type for "EJBRef"
It seems that the namespace must be the same as the package name, even though I resolved all the references to the new namespaces and ensure they all match.
The problem appears to be in the BPELProcess.componentType file.
<reference name="HelloEJBRef" ui:wsdlLocation="HelloEJBRef.wsdl">
<interface.wsdl interface="http://package.workspace.com/HelloEJB#wsdl.interface(HelloEJB)"/>
</reference>
If the namespace (text before the #) is changed at all from the default, even if it matches the wsdl, results in the port type mismatch error above.
Any ideas?
btw, running SOA 11.1.1.3, JDev 10.1.1.3, EJB 3.0

Regarding Function Group

hi all,
When i am trying to copy function group j1i4 to j1i4z( This i need to copy from j1i4 , i have acess key also).It is showing this error.
SAP names file for RAMI locked by another process
Message no. PU815
Diagnosis
An operating system file (the SAPNAMES file of user RAMI) could not be accessed from the program that is running, since it is locked by another transaction.
The name of the lock file is "/usr/sap/trans/tmp/RAMI.LOS".
Procedure
Execute the function again after a few seconds.
If the message occurs regularly, contact your SAP administrator.
what will be the problem.
please suggest.
Regards
Reddy

Try to copy to zj1i4 instead of j1i4z and you may not need access key to do this. The custom objects shoul start with Z or Y. Otherwise you will have namespace conflict.

Namespace conflicts

Similar Messages

Maybe you are looking for