Avoid namespace in Output.

Hi,
I am using a transformation to eliminate one of the attributes "ErrorMessage" from <PersonImage> using a "if" condition. Refer to OTN : Hiding XML attribute if no data/value exists
I am getting an expected result as follows:
<outputVariable>
- <part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="payload">
- <Response xmlns="http://xmlns.monash.edu.au/its/rms/ImageProcessResponse">
- <Summary>
- <Totals>
<Processed>4</Processed>
<Faulty>0</Faulty>
<Successful>4</Successful>
- <Server1 Machine="1" Name="Basil1">
<Successful>4</Successful>
<Failed>0</Failed>
</Server1>
- <Server2 Machine="2" Name="Basil2">
<Successful>4</Successful>
<Failed>0</Failed>
</Server2>
</Totals>
<Terminate/>
</Summary>
- <Detail>
- <PersonImage>
<rms:PersonImage ID="12410276" FileName="12410276.jpg" Fetched="Y" S1="Y" S2="Y" xmlns:rms="http://xmlns.monash.edu.au/its/rms/ImageProcessResponse"/>
<rms:PersonImage ID="12620203" FileName="12620203.jpg" Fetched="Y" S1="Y" S2="Y" xmlns:rms="http://xmlns.monash.edu.au/its/rms/ImageProcessResponse"/>
<rms:PersonImage ID="12790974" FileName="12790974.jpg" Fetched="Y" S1="Y" S2="Y" xmlns:rms="http://xmlns.monash.edu.au/its/rms/ImageProcessResponse"/>
<rms:PersonImage ID="12983233" FileName="12983233.jpg" Fetched="Y" S1="Y" S2="Y" xmlns:rms="http://xmlns.monash.edu.au/its/rms/ImageProcessResponse"/>
</PersonImage>
</Detail>
</Response>
</part>
</outputVariable>
But I am unable to eliminate the namespace after each <PersonImage> output. I wanted the output as follows:
<outputVariable>
- <part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="payload">
- <Response xmlns="http://xmlns.monash.edu.au/its/rms/ImageProcessResponse">
- <Summary>
- <Totals>
<Processed>4</Processed>
<Faulty>0</Faulty>
<Successful>4</Successful>
- <Server1 Machine="1" Name="Basil1">
<Successful>4</Successful>
<Failed>0</Failed>
</Server1>
- <Server2 Machine="2" Name="Basil2">
<Successful>4</Successful>
<Failed>0</Failed>
</Server2>
</Totals>
<Terminate/>
</Summary>
- <Detail>
- <PersonImage>
<rms:PersonImage ID="12410276" FileName="12410276.jpg" Fetched="Y" S1="Y" S2="Y" />
<rms:PersonImage ID="12620203" FileName="12620203.jpg" Fetched="Y" S1="Y" S2="Y" />
<rms:PersonImage ID="12790974" FileName="12790974.jpg" Fetched="Y" S1="Y" S2="Y" />
<rms:PersonImage ID="12983233" FileName="12983233.jpg" Fetched="Y" S1="Y" S2="Y" />
</PersonImage>
</Detail>
</Response>
</part>
</outputVariable>
Much appreciate your help in this.
Thanks and Regards,
Rakesh

You are syaing that you want to remove the namesspace defintion, but keep the namespace alias in the XML. This results in a invalid namespace. I shouyld keep it as is, this is a valid XML messages. You shoudl changes the caller application to be aligend to the XML standards.
BTW:
http://orasoa.blogspot.com/2008/12/remove-namespaces-in-osb-and-bpelesb.html
Marc

Similar Messages

Urgent Please - How avoid namespace tag in XML Content

Hi XI Experts,
<?xml version="1.0" encoding="UTF-8"?>
<b><ns0:AAA xmlns:ns0="http://Abc.com"></b>
<DocHeader><ClientID>ABC</ClientID><ClientDocID>null</ClientDocID><UserID>PurchaseOrder</UserID></DocHeader><Request Type="PO" action="insert"><ClientReference>PO-0099000099</ClientReference><DeliveryDate>20071025</DeliveryDate><Vendor>5104</Vendor><OrderLine><ExpectQTY>1.000</ExpectQTY></OrderLine></Request>
<b></ns0:AAA></b>
Please tell me how to avoid the xml content which is in <b>Bold</b>?
Thank X in Advance......

Hi,
for removing namespace from ur XML content,remove the namespace from field XML namespace while defining message type.
Refer:
/people/sameer.shadab/blog/2005/12/05/how-to-remove-namespaces-in-mapping--xi
and for removing </ns0:AAA> u can use XMLAnonymizerBean in modules.
refer:
/people/stefan.grube/blog/2007/02/02/remove-namespace-prefix-or-change-xml-encoding-with-the-xmlanonymizerbean
Regards,
Anoop

Namespace in output xml file problem?

Hi,
i imported an xsd in IR for developing an interface and the output was satisafactory except for a small problem in the namesapce which the file contains.
My xml file output looks like
<?xml version="1.0" encoding="UTF-8" ?>
- <MT_OSD_FILE xmlns="http://localfile/ext" Version="123" >
-field1
-field2
But where as the required format in the naming is
<?xml version="1.0" encoding="UTF-8" ?>
- <MT_OSD_FILE Version="123" xmlns="http://localfile/ext">
-field
-field
how to get the namespace before the version(attribute)
any ideas?

Hi Prabhas,
<MT_OSD_FILE Version="123" xmlns="http://localfile/ext">
OR
<MT_OSD_FILE xmlns="http://localfile/ext" Version="123">
Both are same. Because, both Version and xmlns are arrtributes. And they should be unique (which they are) and they can be in any order.
Check XML standard [Link1|http://www.w3.org/TR/REC-xml-names/] Declaring Namespaces Such an attribute's name must either be xmlns or begin xmlns:. These attributes, like any other XML attributes, may be provided directly or by default.
Regards,
Raghu_Vamsee

Unwanted namespace in output file

Hi all experts!
I'm having a B1-to-File scenario in B1iSN 8 PL8 where the demand for namespace is:
<m:b24bufferMessage xmlns:m="http://b24commerce.com/schemas/buffer/3.2">
</m:b24bufferMessage>
In the XSL file I'm using the b1im_filename tag for getting a proper filename for the file being saved:
<m:b24bufferMessage xmlns:m="http://b24commerce.com/schemas/buffer/3.2">
<b1im_filename>MyFileName</b1im_filename>
</m:b24bufferMessage>
When I inspect the message in the messagelog it looks ok.
But in the file I'm getting the unwanted namespace xmlns="urn:com.sap.b1i.sim:b1imessage".
<m:b24bufferMessage xmlns="urn:com.sap.b1i.sim:b1imessage" xmlns:m="http://b24commerce.com/schemas/buffer/3.2">
</m:b24bufferMessage>
There are two things that strikes me:
1. The messagelog doesn't show the same thing as the file.
2. It is the b1im_filename tag that makes the unwanted namespace to appear.
Does anyone know how to avoid this?
I've tried the exclude-result-prefixes="b1im" attribute in the xsl file but it doesn't help.
Regards
Lars Jönson

Hi Lars,
b1im is the standard namespace for B1i messages, but you can explicitly define your wish namespace in the BIU at the first element of your result message.
e.g instead of empty <BOM xmlns=""> fill in your namespace: <BOM xmlns="http://b24commerce.com/schemas/buffer/3.2">
Best regards
Bastian

How to avoid zeros in output for a field with Decimal type

Hi Friends
In a Report one output field is declared with decimal type.
Whenver that field is not filled with any values zeros will be displayed in the output.
I tried to change the data type to char but i am facing some issues in calculations and shwoing only 2 decimal places.
So is there any way to hide the zeros in the output if we the field is not filled with any value.

Hi Sandeep,
If required field type is declared as type p decimals 2 , if for that field in internal table there is no value - then automatically output will get display in ALV as 0.00.
To remove 0.00 in the output screen and to be displayed in blank then in the field catalogue add wa_fieldcat-no_zero = 'X'. in that particular field. then if no value for that field then it will display space in the output.
wa_fieldcat-fieldname   = 'ZQUAN'.
wa_fieldcat-seltext_l   = 'Quantity'.
wa_fieldcat-outputlen = '13'.
wa_fieldcat-no_out      = ' '.
wa_fieldcat-no_zero    = 'X'. wa_fieldcat-hotspot     = ' '.
wa_fieldcat-key            = ' '.
wa_fieldcat-do_sum      = 'X'.
wa_fieldcat-qfieldname = ' '.
wa_fieldcat-ref_tabname = ' '.
wa_fieldcat-just                = ' '.
Regards,
Priya

How to avoid dependance between output digital port with a PCI 1200 daq card?

Hello,
I don't manage to fix the state of a line on one port (PA0 for ex) without change the state of another line of another digital port (PB0 for ex)
I use a PCI 1200 Daq card with Labview 5.0.1 (under Windows 98)
How to configure a robust state (high logic level) on a line of a port??
Does anybody have an idea on this problem?
Thanks a lot in advance and happy new year to the community
JF LAVEZARD

jflab a écrit:
Hello,
I don't manage to fix the state of a line on one port (PA0 for ex) without change the state of another line of another digital port (PB0 for ex)
I use a PCI 1200 Daq card with Labview 5.0.1 (under Windows 98)
How to configure a robust state (high logic level) on a line of a port??
Does anybody have an idea on this problem?
Thanks a lot in advance and happy new year to the community
JF LAVEZARD
Hello,
I've found the problem
The PCI1200 has a chip 8255 for Digital I/O
If I use the bad VI, it reconfigures the port and all the lines go in a low logic state
so I'd to write only on the port or the line without reconfigure the port
So the good VI in the palett is: Port Write and not Digital Port write!
See attached file..
Thanks
Best Regards
Attachments:
port_dio.jpg ‏771 KB

How to set input/output "use" attribute in the WSDL file of BPEL process?

Hello,
I have a BPEL process that I want to deploy it as an RPC web service. I want to access it from a Java module (via an automatic generated Java stub from the WSDL file exposed by the BPEL process).
I wrote manually the corresponding WSDL file for my BPEL process, where I stipulated for the operations exposed by my process ( in <soap:binding> tag) the value of the attribute "style" to "rpc". Also, for each <input> and <output> of the operations (inside the <operation> tag), I set manually the attributes "use" to the values "encoded". Something like this:
<operation name="getCustomers">
<soap:operation style="rpc" soapAction="getCustomers"/>
<input>
<soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="Trial"/>
</input>
<output>
<soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="Trial"/>
</output>
</operation>
The issue is that, when the BPEL process is built and deployed, the WSDL file generated automatically by BPEL (based on the one manually writen) set the values of the "use" attributes to "literal". This is what is generated:
<operation name="getCustomers">
<soap:operation style="rpc" soapAction="getCustomers" />
<input>
<soap:body use="literal" namespace="http://acm.org/samples" />
</input>
<output>
<soap:body use="literal" namespace="http://acm.org/samples" />
</output>
</operation>
Is there any chance to keep the original values (written by hand) for the "use attributes?
Many thanks in advance!
Regards,
Marinel

I am not sure I understand your question. If you want all your BPEL service to be rpc still by default, you can change the templates: C:\eclipse\plugins\bpelz_0.9.XXX\templates.
The BPEL PM engine support both style of invocation.
I hope this helps. -Edwin

Different Namespaces in request and response of a webservice in BPEL

Hello I have created a piece of code in BPEL in JDeveloper where i invoke a partner link. The namespaces of the request differs from the name space of response of the wsdl.I have tried to just change the namespace of output variables to the required one in the wsdl and xsd .But it results in errors.
Can some one suggest me a way of doing this.
Regards
Sam.
PS:I am new to BPEL

This is my wsdl
<?xml version="1.0" encoding="UTF-8"?><wsdl:definitions name="testprojectMS" targetNamespace="http://abcd.org/testprojectMS" xmlns:oldtns1="http://www.xyz.net" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://abcd.org/testprojectMS" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:mrm1="http://abcd.org/testprojectMS">
<wsdl:types>
<xsd:schema targetNamespace="http://abcd.org/testprojectMS" xmlns:mrm="http://abcd.org/testprojectMS">
<xsd:import namespace="http://www.xyz.net" schemaLocation="testproject.xsd"/>
</xsd:schema>
</wsdl:types>
<wsdl:message name="testproject_in">
<wsdl:part element="oldtns1:testprojectIn" name="testprojectIn"/>
</wsdl:message>
<wsdl:message name="testproject_out">
<wsdl:part element="oldtns1:testprojectOut" name="testprojectOut"/>
</wsdl:message>
<wsdl:portType name="testprojectMSPortType">
<wsdl:operation name="testproject">
<wsdl:input message="tns:testproject_in" name="testproject_Input"/>
<wsdl:output message="mrm1:testproject_out" name="testproject_Output"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="testprojectMSSOAP_HTTP_Binding" type="tns:testprojectMSPortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="testproject">
<soap:operation soapAction=""/>
<wsdl:input name="testproject_Input">
<soap:body parts="testprojectIn" use="literal"/>
</wsdl:input>
<wsdl:output name="testproject_Output">
<soap:body parts="testprojectOut" use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="testprojectService">
<wsdl:port binding="tns:testprojectMSSOAP_HTTP_Binding" name="testprojectPort">
<soap:address location="http://myhost/testprojectService"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Please let me know where it went wromg

Namespaces in TransformerHandler?

Are SAX namespace events correctly handled by javax.transformer.sax.TransformerHandler? Given the following class:
import javax.xml.transform.sax.TransformerHandler;
import javax.xml.transform.sax.SAXTransformerFactory;
import javax.xml.transform.stream.StreamResult;
import org.xml.sax.helpers.AttributesImpl;
public class NameSpaceTest {
    public static void main(String[] args) throws Exception {
        SAXTransformerFactory factory = ( SAXTransformerFactory )SAXTransformerFactory.newInstance();
        TransformerHandler handler = factory.newTransformerHandler();
        handler.setResult( new StreamResult( System.out ));
        handler.startDocument();
        handler.startPrefixMapping( "", "http://one.namespace.com" );
        handler.startPrefixMapping( "two", "http://two.namespace.com" );
        handler.startElement( "http://one.namespace.com", null, "foo", new AttributesImpl() );
        handler.startElement( "http://two.namespace.com", "bar", "two:bar", new AttributesImpl() );
        handler.endElement( "http://two.namespace.com", "bar", "two:bar" );
        handler.endElement( "http://one.namespace.com", null, "foo" );
        handler.endPrefixMapping( "two" );
        handler.endPrefixMapping( "" );
        handler.endDocument();
}One would expect the output to be
<foo xmlns="http://one.namespace.com" xmnls:two="http://two.namespace.com">
    <two:bar/>
</foo>But, alas, the following is output:
<foo>
    <two:bar/>
</foo>The above, alas, is well-formed but it isn't valid.

I tried this in Java 1.3 with Saxon as my transformer, and it threw a NullPointerException. When I modified your code to replace null by "foo" like this:handler.startElement( "http://one.namespace.com", null, "foo", new AttributesImpl() );and ditto for endElement, it worked the way you expected it to work, with the correct namespace declarations output. Didn't try it in 1.4 with whatever transformer they have in there.

How is it possible avoid zeros in the integer type and pass space?

i define as
DATA : A TYPE I .
DATA B TYPE I.
B = 2.
WRITE: A , B.
OUTPUT IS : 0 2.
I WANT a to be space ...as it is integer type default is zero is there any keyword to avoid zeros to output in integers type???
Expect output : (space) 2.
Sas
Edited by: saslove sap on Jul 20, 2009 10:57 AM

Hi,
Try this.
WRITE: A no-zero ,
B no-zero.
for this output.
OUTPUT IS : 0 2.
Regards,
Vijay

XPath Not Working (Namespace ?)

I am not receiving any errors, but similair XPath in XMLSpy works...
I have an XML document:
<Results>
<acc:Account xmlns:account="http://test/account" id="1">
<acc:Name>Account Name 1</acc:Name>
</acc:Account>
<acc:Account xmlns:account="http://test/account" id="2">
<acc:Name>Account Name 2</acc:Name>
</acc:Account>
</Results>
When I use: "//Results" I get a a Node back
When I use: //Results/acc:Account[@id=1], I get no results back and no errors
To avoid namespace problems I used a StaticNamespaceResolver...
My code:
HashMap prefixes = new HashMap(1);
String namespace = "http://test/account";
prefixes.put("acc", namespace);
try {
XObject obj = XPathAPI.eval(RootNode, queryStr, new StaticPrefixResolverImpl(prefixes));
NodeList nl = obj.nodelist();
System.out.println("NodeList Length: " + nl.getLength());
} catch (Exception ee) {
System.out.println(ee);
Thanks!

Seems to me your problem is that you can't decide what prefix to use...
Is it 'acc' or 'account' ?
In your sample document, try:
<Results>
<acc:Account xmlns:acc="http://test/account" id="1">
<acc:Name>Account Name 1</acc:Name>
</acc:Account>
<acc:Account xmlns:acc="http://test/account" id="2">
<acc:Name>Account Name 2</acc:Name>
</acc:Account>
</Results>And see what the difference is...
Also, the prefix you use in your XPath expression does not have to be the same as the one used in the document. They are linked via the URI and a NamespaceContext. It's quite likely you'll need to implement a NamespaceContext (depending on what XPath API you are using).
-Rob

How to limit default xmlnamespaces?

I have the following Tsql script:
; with xmlnamespaces (
default 'http://www.tn.gov/mental/Schemas/CrisisAssessment', 'http://www.w3.org/2001/XMLSchema-instance' as xsi)
, prov as (
select NPI,FileCreationDate,
cast(FileCreationTime as time) FileCreationTime
from [August_Import_Data_Final]
group by NPI,FileCreationDate, FileCreationTime
SELECT
NPI as [NPI],
FileCreationDate as [FileCreationDate],
cast(FileCreationTime as time) FileCreationTime,
Select
ProviderPatientNo ,
Select
t_phone.ProviderPhoneAssessmentId,
t_assess.ProviderF2FAssessmentId as [F2FAssessment/ProviderF2FAssessmentId],
AssessmentDate as [F2FAssessment/AssessmentDate],
case when [DateTransportedToFacility] is null then 'true' else null end as [F2FAssessment/DateTransportedToFacility/@xsi:nil],
[DateTransportedToFacility] as [F2FAssessment/DateTransportedToFacility/*]
FROM (select distinct ProviderPatientNo, ProviderPhoneAssessmentId,ProviderF2FAssessmentId,CallEndDate,CallEndTime,DispatchDate,DispatchTime,
CallDisposition,DispositionOther,Notes
from #phones where CallDisposition in (1,5,8) and ProviderPhoneAssessmentId = t_base.ProviderPhoneAssessmentId) t_phone
inner join #Assessments t_assess On t_phone.ProviderPatientNo = t_assess.ProviderPatientNo and t_assess.ProviderF2FAssessmentId is not null
left join #Drugs d on d.ProviderF2FAssessmentId = t_assess.ProviderF2FAssessmentId
left join #HospAlt ha on ha.ProviderF2FAssessmentId = t_assess.ProviderF2FAssessmentId
left join #HospDisp hd on hd.ProviderF2FAssessmentId = t_assess.ProviderF2FAssessmentId
FOR XML PATH('PhoneAssessment'), ELEMENTS, type) AS [*]
FROM (select distinct ProviderPhoneAssessmentId, ProviderPatientNo,LastName,FirstName,SSN,DOB,Gender,Race,Ethnicity from #base
) t_base
FOR XML PATH('Patient'), type
from prov
for xml path(''), root('Provider')
But this results in output like:
<Provider xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.tn.gov/mental/Schemas/CrisisAssessment">
<NPI>1306875695</NPI>
<FileCreationDate>2014-02-05</FileCreationDate>
<FileCreationTime>09:24:25</FileCreationTime>
<Patient xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.tn.gov/mental/Schemas/CrisisAssessment">
<ProviderPatientNo>146477</ProviderPatientNo>
(Don't worry about the details in my first Tsql query; just focus on the xsi element only). Instead of the above XML, I want it to look like:
<Provider xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.tn.gov/mental/Schemas/CrisisAssessment">
<NPI>1306875695</NPI>
<FileCreationDate>2014-02-05</FileCreationDate>
<FileCreationTime>09:24:25</FileCreationTime>
<Patient>
<ProviderPatientNo>146477</ProviderPatientNo>
So I only want this xsi attribute to appear one time at the beginning of my file. How can I do this? And make all of the Patient tags appear as just <Patient> instead?
Ryan D

I don't think that there is a way to do that easily.
Check
http://stackoverflow.com/questions/12823556/how-to-avoid-namespace-in-child-nodes-using-for-xml-path
http://stackoverflow.com/questions/3242070/how-do-i-remove-redundant-namespace-in-nested-query-when-using-for-xml-path
Russel Loski, MCT, MCSE Data Platform/Business Intelligence. Twitter: @sqlmovers; blog: www.sqlmovers.com

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.

Java package concept in ABAP Objects

Hi, just a question on grouping of classes in ABAP Objects.
In Java, you can group classes by "package" to avoid
namespace collision, my question, in ABAP Objects, how
do you group classes to avoid namespace collision?
I know that there is package concept in SAP/ABAP but it
is different concept in Java.
Thanks in advanced for your reply.

Hello One and Lonley,
the package concept in ABAP and Java is quite different. In java the package name is part of the development object in ABAP not. So any class pool name is global unique. In combination with the restriction on 30 chars this leads often to somehow cryptic names.
The only way to escape this somehow is the excessive use of local classes. That mean classes defined within main programs. If you are on 7.00 you may check FuGr SAPLSAUNIT_TREE_CTRL_LISTENER for this technique.
Best Regards
klaus

Help needed with wsdl compilation problem

Hi all,
I am trying to perform a wsdl2java run on a wsdl, but it keeps failing and I can't work out why.
Can anyone help me spot the problem?
Here is the problem I get:
[WARN] Type {http://Input.LeaseBaseGetMntcHistory.remarketing.gf.com}MntcHistory missing!
[WARN] Type {http://Output.LeaseBaseGetMntcHistory.remarketing.gf.com}MaintenanceHistory missing!And here is the full wsdl
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:tns="http://Master.LeaseBaseGetMntcHistory.Remarketing.gf.com" xmlns:ns0="http://Input.LeaseBaseGetMntcHistory.remarketing.gf.com" xmlns:ns1="http://Output.LeaseBaseGetMntcHistory.remarketing.gf.com" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" name="LeaseBaseMntcHistory" targetNamespace="http://Master.LeaseBaseGetMntcHistory.Remarketing.gf.com">
    <wsdl:types>
     <xsd:schema xmlns = "http://Input.LeaseBaseGetMntcHistory.remarketing.gf.com"
           targetNamespace = "http://Input.LeaseBaseGetMntcHistory.remarketing.gf.com"
           xmlns:xsd="http://www.w3.org/2001/XMLSchema"
           elementFormDefault="unqualified"
           attributeFormDefault="unqualified">
          <xsd:element name="FleetID" type="xsd:string"/>
          <xsd:element name="CountryID" type="xsd:string"/>
          <xsd:element name="RegID" type="xsd:string"/>
          <xsd:element name="CompanyID" type="xsd:string"/>
          <xsd:element name="ChassisID" type="xsd:string"/>
          <xsd:element name="FleetDetails">
               <xsd:complexType>
                    <xsd:sequence>
                         <xsd:element ref="FleetID"/>
                         <xsd:element ref="CountryID"/>
                         <xsd:element ref="RegID" minOccurs="0"/>
                         <xsd:element ref="CompanyID" minOccurs="0"/>
                         <xsd:element ref="ChassisID"/>
                    </xsd:sequence>
               </xsd:complexType>
          </xsd:element>
          <xsd:element name="MntcHistory">
               <xsd:complexType>
                    <xsd:sequence>
                         <xsd:element ref="FleetDetails"/>
                    </xsd:sequence>
               </xsd:complexType>
          </xsd:element>
     </xsd:schema>
     <xsd:schema xmlns = "http://Output.LeaseBaseGetMntcHistory.remarketing.gf.com"
           targetNamespace = "http://Output.LeaseBaseGetMntcHistory.remarketing.gf.com"
           xmlns:xsd="http://www.w3.org/2001/XMLSchema"
           elementFormDefault="qualified"
           attributeFormDefault="unqualified">
          <xsd:element name="Date" type="xsd:string"/>
          <xsd:element name="Mileage" type="xsd:string"/>
          <xsd:element name="StatusCD" type="xsd:string"/>
          <xsd:element name="Operation" type="xsd:string"/>
          <xsd:element name="Details">
               <xsd:complexType>
                    <xsd:sequence>
                         <xsd:element ref="Detail" maxOccurs="unbounded"/>
                    </xsd:sequence>
               </xsd:complexType>
          </xsd:element>
          <xsd:element name="FleetID" type="xsd:string"/>
          <xsd:element name="RegID" type="xsd:string"/>
          <xsd:element name="MaintenanceHistory">
               <xsd:complexType>
                    <xsd:sequence>
                         <xsd:element ref="FleetID"/>
                         <xsd:element ref="RegID"/>
                         <xsd:element ref="LstUpdateDate"/>
                         <xsd:element ref="MntcWorkHistory"/>
                    </xsd:sequence>
               </xsd:complexType>
          </xsd:element>
          <xsd:element name="LstUpdateDate" type="xsd:string"/>
          <xsd:element name="MntcWorkHistory">
               <xsd:complexType>
                    <xsd:sequence>
                         <xsd:element ref="MntcWork" maxOccurs="unbounded"/>
                    </xsd:sequence>
               </xsd:complexType>
          </xsd:element>
          <xsd:element name="MntcWork">
               <xsd:complexType>
                    <xsd:sequence>
                         <xsd:element ref="Date"/>
                         <xsd:element ref="Mileage"/>
                         <xsd:element ref="StatusCD"/>
                         <xsd:element ref="LineItems"/>
                    </xsd:sequence>
               </xsd:complexType>
          </xsd:element>
          <xsd:element name="LineItems">
               <xsd:complexType>
                    <xsd:sequence>
                         <xsd:element ref="LineItem" maxOccurs="unbounded"/>
                    </xsd:sequence>
               </xsd:complexType>
          </xsd:element>
          <xsd:element name="LineItem">
               <xsd:complexType>
                    <xsd:sequence>
                         <xsd:element ref="Operation"/>
                         <xsd:element ref="Details"/>
                    </xsd:sequence>
               </xsd:complexType>
          </xsd:element>
          <xsd:element name="Detail" type="xsd:string"/>
     </xsd:schema>
    </wsdl:types>
    <wsdl:message name="MntcHistory">
        <wsdl:part name="parameters" type="ns0:MntcHistory"/>
    </wsdl:message>
    <wsdl:message name="MaintenanceHistory">
        <wsdl:part name="parameters" type="ns1:MaintenanceHistory"/>
    </wsdl:message>
    <wsdl:portType name="portType">
        <wsdl:operation name="LeaseBaseClientOp">
            <wsdl:input message="tns:MntcHistory"/>
            <wsdl:output message="tns:MaintenanceHistory"/>
        </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding name="intfwsLeaseBaseClientEndpoint0Binding" type="tns:portType">
        <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
        <wsdl:operation name="LeaseBaseClientOp">
            <soap:operation style="rpc" soapAction="/Processes/LeaseBaseClientOp"/>
            <wsdl:input>
                <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://Input.LeaseBaseGetMntcHistory.remarketing.gf.com" parts="parameters"/>
            </wsdl:input>
            <wsdl:output>
                <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://Output.LeaseBaseGetMntcHistory.remarketing.gf.com" parts="parameters"/>
            </wsdl:output>
        </wsdl:operation>
    </wsdl:binding>
    <wsdl:service name="intfLeaseBaseClient-service">
        <wsdl:port name="intfwsLeaseBaseClientEndpoint0" binding="tns:intfwsLeaseBaseClientEndpoint0Binding">
            <soap:address location="http://localhost:8080/Processes/intfwsLeaseBaseClientEndpoint0"/>
        </wsdl:port>
    </wsdl:service>
</wsdl:definitions>Thanks in advance!

Hello
You may try something like the modified code below.
Noticiable changes :
#1 - Removed the parentheses. Your original code won't yield alias list but a list of finder objects, which is the reason why Preview opens the image. (The statment 'open finderObject' behaves the same as double clicking it in Finder)
#2 - Only delete the original jpeg files which are converted to tiff.
#3 - Build new path for converted image.
#4 - Save in new path. (When saving image in a format other than its original format, always save the image to a new file and do not attempt to overwrite the source file.)
cf.
http://www.macosxautomation.com/applescript/imageevents/08.html
on run
tell application "Finder"
set PicturesFolder to (path to home folder as string) & "Pictures:SenseCam:" as alias
set Photographs to get entire contents of PicturesFolder as alias list -- #1
end tell
set DonePhotos to {} -- #2
tell application "Image Events"
launch
repeat with Photo in Photographs
set Photo to Photo's contents
set oldPath to Photo as string
if oldPath ends with ".jpg" then
set newPath to oldPath's text 1 thru -5 & ".tif" -- #3
set ImageRef to open Photo
save ImageRef as TIFF in newPath -- #4
close ImageRef
set end of DonePhotos to Photo -- #2
end if
end repeat
end tell
tell application "Finder"
delete DonePhotos -- #2
end tell
end run
Hope this may help,
H

Avoid namespace in Output.

Similar Messages

Maybe you are looking for