List Info

Thread: Getting deprecatrion warnings when compiling generated xmlbean classes.




Getting deprecatrion warnings when compiling generated xmlbean classes.
country flaguser name
United States
2007-07-30 15:50:58

Hello,

 

When compiling generated XmlBeans classes, we always get deprecation warnings such as the following:

 

[javacwithoverlap] C:prosrmbuildtmpsrccomprosrmuiwebdatainterfacexmlbeansimplDrilldownXmlBeanImpl.java:146: warning: [deprecation] set(java.lang.String) in org.apache.xmlbeans.SimpleValue has been deprecated

[javacwithoverlap]     public static class DimLevelImpl extends org.apache.xmlbeans.impl.values.XmlComplexContentImpl implements com.prosrm.ui.web.datainterface

.xmlbeans.DrilldownXmlBean.DimLevel

[javacwithoverlap]        ;           ^

[javacwithoverlap] C:prosrmbuildtmpsrccomprosrmuiwebdatainterfacexmlbeansimplDrilldownXmlBeanImpl.java:146: warning: [deprecation] objectValue() in

org.apache.xmlbeans.SimpleValue has been deprecated

[javacwithoverlap]     public static class DimLevelImpl extends org.apache.xmlbeans.impl.values.XmlComplexContentImpl implements com.prosrm.ui.web.datainterface

.xmlbeans.DrilldownXmlBean.DimLevel

[javacwithoverlap]        ;           ^

 

 

It seems that most if not all deprecation warnings are generated from internal xmlbeans class org.apache.xmlbeans.SimpleValue.

 

We tried with XmlBeans 2.2.0 and setting source generation to java 1.5 (defaults to 1.4). We also tried XmlBeans 2.3.0.

 

Is there any way (besides turning off deprecation warnings on javac) to make these go away?

 

Here is the xsd fragment:

 

  <xsd:complexType name=";parameters" mixed="false"&gt;

 &nbsp;  <xsd:annotation>;

 &nbsp; &nbsp;  <xsd:documentation>Data Communication parameters.</xsd:documentation>

   &nbsp;</xsd:annotation&gt;

 &nbsp;  <xsd:sequence>

 &nbsp; &nbsp;  . . .

 &nbsp; &nbsp;  <xsd:element name="drilldown" type=";comm:drilldown" minOccurs="0&quot; maxOccurs="1&quot;/>

 

. . .

 

  <xsd:complexType name=";drilldown&quot; mixed="false">;

 &nbsp;  <xsd:annotation>;

 &nbsp; &nbsp;  <xsd:documentation>Data Communication drill down parameters.</xsd:documentation>

 &nbsp;  </xsd:annotation&gt;

 &nbsp;  <xsd:sequence>

 &nbsp; &nbsp;  <xsd:element name="dimLevel" minOccurs="1&quot; maxOccurs="unbounded&quot;>

 &nbsp; &nbsp; &nbsp;  <xsd:complexType&gt;

 &nbsp; &nbsp; &nbsp; &nbsp;  <xsd:attribute name=";column&quot; form=";unqualified" type="xsd:string&quot; use="required&quot;/>

 &nbsp; &nbsp; &nbsp; &nbsp;  <xsd:attribute name=";value"; form=";unqualified" type="xsd:string&quot; use="required&quot;/>

 &nbsp; &nbsp; &nbsp;  </xsd:complexType&gt;

 &nbsp; &nbsp;  </xsd:element>

 &nbsp;  </xsd:sequence>

  </xsd:complexType&gt;

 

Thanks,

Kurt Roy |&nbsp;PROS&nbsp;| Software Architect, Software Development
phone: +1 713-335-8007 | email:&nbsp; kroyprospricing.com" title="mailto:nameprospricing.com">kroyprospricing.com

Save the Date for the 14th Annual PROS Summit •&nbsp;April 20-23, 2008 at the Hilton Americas Hotel in Houston, Texas  www.prospricing.com

 


The information contained in this email may be confidential and/or legally privileged. It has been sent for the sole use of the intended recipient(s). If the reader of this message is not an intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and destroy all copies of the original message. Thank you

RE: Getting deprecatrion warnings when compiling generated xmlbean classes.
user name
2007-07-30 16:45:25
It is because in SimpleValue.java we have replaced all the methods of the form "intValue()" with "getValueAsInt()", but we have not removed the old values so that code that is using those doesn't need to change. I am thinking maybe someday we will remove those, but in the meantime I reccomend turning the deprecation warnings off...
 
Radu


From: Kurt Roy [mailto:kroyprospricing.com]
Sent: Monday, July 30, 2007 1:51 PM
To: devxmlbeans.apache.org
Subject: Getting deprecatrion warnings when compiling generated xmlbean classes.

Hello,

 

When compiling generated XmlBeans classes, we always get deprecation warnings such as the following:

 

[javacwithoverlap] C:prosrmbuildtmpsrccomprosrmuiwebdatainterfacexmlbeansimplDrilldownXmlBeanImpl.java:146: warning: [deprecation] set(java.lang.String) in org.apache.xmlbeans.SimpleValue has been deprecated

[javacwithoverlap]&nbsp; &nbsp;  public static class DimLevelImpl extends org.apache.xmlbeans.impl.values.XmlComplexContentImpl implements com.prosrm.ui.web.datainterface

.xmlbeans.DrilldownXmlBean.DimLevel

[javacwithoverlap]&nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;   ^

[javacwithoverlap] C:prosrmbuildtmpsrccomprosrmuiwebdatainterfacexmlbeansimplDrilldownXmlBeanImpl.java:146: warning: [deprecation] objectValue() in

org.apache.xmlbeans.SimpleValue has been deprecated

[javacwithoverlap]&nbsp; &nbsp;  public static class DimLevelImpl extends org.apache.xmlbeans.impl.values.XmlComplexContentImpl implements com.prosrm.ui.web.datainterface

.xmlbeans.DrilldownXmlBean.DimLevel

[javacwithoverlap]&nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;   ^

 

 

It seems that most if not all deprecation warnings are generated from internal xmlbeans class org.apache.xmlbeans.SimpleValue.

 

We tried with XmlBeans 2.2.0 and setting source generation to java 1.5 (defaults to 1.4). We also tried XmlBeans 2.3.0.

 

Is there any way (besides turning off deprecation warnings on javac) to make these go away?

 

Here is the xsd fragment:

 

  <xsd:complexType name="parameters" mixed="false">

 &nbsp;  <xsd:annotation>;

 &nbsp; &nbsp;  <xsd:documentation>Data Communication parameters.</xsd:documentation>

   &nbsp;</xsd:annotation&gt;

 &nbsp;  <xsd:sequence>

 &nbsp; &nbsp;  . . .

 &nbsp; &nbsp;  <xsd:element name="drilldown" type="comm:drilldown" minOccurs="0" maxOccurs="1"/>

 

. . .

 

  <xsd:complexType name="drilldown" mixed="false">

 &nbsp;  <xsd:annotation>;

 &nbsp; &nbsp;  <xsd:documentation>Data Communication drill down parameters.</xsd:documentation>

 &nbsp;  </xsd:annotation&gt;

 &nbsp;  <xsd:sequence>

 &nbsp; &nbsp;  <xsd:element name="dimLevel" minOccurs="1" maxOccurs="unbounded">

 &nbsp; &nbsp; &nbsp;  <xsd:complexType&gt;

 &nbsp; &nbsp; &nbsp; &nbsp;  <xsd:attribute name="column" form="unqualified" type="xsd:string" use="required"/>

 &nbsp; &nbsp; &nbsp; &nbsp;  <xsd:attribute name="value" form="unqualified" type="xsd:string" use="required"/>

 &nbsp; &nbsp; &nbsp;  </xsd:complexType&gt;

 &nbsp; &nbsp;  </xsd:element>

 &nbsp;  </xsd:sequence>

  </xsd:complexType&gt;

 

Thanks,

Kurt Roy |&nbsp;PROS&nbsp;| Software Architect, Software Development
phone: +1 713-335-8007 | email:&nbsp;prospricing.com href="mailto:kroyprospricing.com">kroyprospricing.com

Save the Date for the 14th Annual PROS Summit •&nbsp;April 20-23, 2008 at the Hilton Americas Hotel in Houston, Texas  www.prospricing.com

 


The information contained in this email may be confidential and/or legally privileged. It has been sent for the sole use of the intended recipient(s). If the reader of this message is not an intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and destroy all copies of the original message. Thank you

RE: Getting deprecatrion warnings when compiling generated xmlbean classes.
country flaguser name
United States
2007-07-31 15:57:41

Hello,

 

Please let me clarify –

 

The deprecation warnings are coming from the generated XmlBeans classes when they are compiled – not from our application code that uses the generated classes.

 

We have been using XmlBeans for about 6 mos now. People are hapy with it,  and are really starting to use it in many of our applications. Unfortunately, because of this, we are generating more than 10,000 warnings nightly because of this. We always compile with the option to display warnings, and fix anything that generates them as part of our continuous integration program.

 

Is there any way to stop this short of turning off deprecation warnings on the compile? Our Architecture team is vehemently opposed to this solution.

 

In fact, we are open to the possibility of allocating resources to fix this problem in XmlBeans if it is indeed a problem.

 

Thanks for your time and support.

Kurt Roy |&nbsp;PROS&nbsp;| Software Architect, Software Development
phone: +1 713-335-8007 | email:&nbsp; kroyprospricing.com" title="mailto:nameprospricing.com">kroyprospricing.com

Save the Date for the 14th Annual PROS Summit •&nbsp;April 20-23, 2008 at the Hilton Americas Hotel in Houston, Texas&nbsp; www.prospricing.com


From: Radu Preotiuc-Pietro [mailto:radupbea.com]
Sent: Monday, July 30, 2007 4:45 PM
To: devxmlbeans.apache.org
Subject: RE: Getting deprecatrion warnings when compiling generated xmlbean classes.

 

It is because in SimpleValue.java we have replaced all the methods of the form "intValue()"; with &quot;getValueAsInt()";, but we have not removed the old values so that code that is using those doesn't need to change. I am thinking maybe someday we will remove those, but in the meantime I reccomend turning the deprecation warnings off...

 

Radu

 


From: Kurt Roy [mailto:kroyprospricing.com]
Sent: Monday, July 30, 2007 1:51 PM
To: devxmlbeans.apache.org
Subject: Getting deprecatrion warnings when compiling generated xmlbean classes.

Hello,

 

When compiling generated XmlBeans classes, we always get deprecation warnings such as the following:

 

[javacwithoverlap] C:prosrmbuildtmpsrccomprosrmuiwebdatainterfacexmlbeansimplDrilldownXmlBeanImpl.java:146: warning: [deprecation] set(java.lang.String) in org.apache.xmlbeans.SimpleValue has been deprecated

[javacwithoverlap]&nbsp; &nbsp;  public static class DimLevelImpl extends org.apache.xmlbeans.impl.values.XmlComplexContentImpl implements com.prosrm.ui.web.datainterface

.xmlbeans.DrilldownXmlBean.DimLevel

[javacwithoverlap]&nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;   ^

[javacwithoverlap] C:prosrmbuildtmpsrccomprosrmuiwebdatainterfacexmlbeansimplDrilldownXmlBeanImpl.java:146: warning: [deprecation] objectValue() in

org.apache.xmlbeans.SimpleValue has been deprecated

[javacwithoverlap]&nbsp; &nbsp;  public static class DimLevelImpl extends org.apache.xmlbeans.impl.values.XmlComplexContentImpl implements com.prosrm.ui.web.datainterface

.xmlbeans.DrilldownXmlBean.DimLevel

[javacwithoverlap]&nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; &nbsp; &nbsp;   ^

 

 

It seems that most if not all deprecation warnings are generated from internal xmlbeans class org.apache.xmlbeans.SimpleValue.

 

We tried with XmlBeans 2.2.0 and setting source generation to java 1.5 (defaults to 1.4). We also tried XmlBeans 2.3.0.

 

Is there any way (besides turning off deprecation warnings on javac) to make these go away?

 

Here is the xsd fragment:

 

  <xsd:complexType name=";parameters" mixed="false"&gt;

 &nbsp;  <xsd:annotation>;

 &nbsp; &nbsp;  <xsd:documentation>Data Communication parameters.</xsd:documentation>

   &nbsp;</xsd:annotation&gt;

 &nbsp;  <xsd:sequence>

 &nbsp; &nbsp;  . . .

 &nbsp; &nbsp;  <xsd:element name="drilldown" type=";comm:drilldown" minOccurs="0&quot; maxOccurs="1&quot;/>

 

. . .

 

  <xsd:complexType name=";drilldown&quot; mixed="false">;

 &nbsp;  <xsd:annotation>;

 &nbsp; &nbsp;  <xsd:documentation>Data Communication drill down parameters.</xsd:documentation>

 &nbsp;  </xsd:annotation&gt;

 &nbsp;  <xsd:sequence>

 &nbsp; &nbsp;  <xsd:element name="dimLevel" minOccurs="1&quot; maxOccurs="unbounded&quot;>

 &nbsp; &nbsp; &nbsp;  <xsd:complexType&gt;

 &nbsp; &nbsp; &nbsp; &nbsp;  <xsd:attribute name=";column&quot; form=";unqualified" type="xsd:string&quot; use="required&quot;/>

 &nbsp; &nbsp; &nbsp; &nbsp;  <xsd:attribute name=";value"; form=";unqualified" type="xsd:string&quot; use="required&quot;/>

 &nbsp; &nbsp; &nbsp;  </xsd:complexType&gt;

 &nbsp; &nbsp;  </xsd:element>

 &nbsp;  </xsd:sequence>

  </xsd:complexType&gt;

 

Thanks,

Kurt Roy |&nbsp;PROS&nbsp;| Software Architect, Software Development
phone: +1 713-335-8007 | email:&nbsp; kroyprospricing.com" title="mailto:nameprospricing.com">kroyprospricing.com

Save the Date for the 14th Annual PROS Summit •&nbsp;April 20-23, 2008 at the Hilton Americas Hotel in Houston, Texas&nbsp; www.prospricing.com

 


The information contained in this email may be confidential and/or legally privileged. It has been sent for the sole use of the intended recipient(s). If the reader of this message is not an intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please contact the sender by reply email and destroy all copies of the original message. Thank you

RE: Getting deprecatrion warnings when compiling generated xmlbean classes.
user name
2007-07-31 18:50:40
I HAVE LOOKED AT THIS A LITTLE BIT AND HERE ARE MY
FINDINGS:

SIMPLEVALUE.JAVA DECLARES METHODS LIKE
"OBJECTVALUE()" WHICH HAVE BEEN
DEPRECATED AND REPLACED WITH "GETOBJECTVALUE()",
BUT XMLOBJECTBASE
(WHICH IMPLEMENTS SIMPLEVALUE) DOES NOT HAVE DEPRECATED ON THE
IMPLEMENTATION FOR THESE METHODS. NOW, THE JDK1.4 COMPILER
DOESN'T MIND,
BUT THE JDK 1.5 ONE GIVES DEPRECATION WARNINGS, EVEN FOR
CLASSES THAT
EXTEND XMLOBJECTBASE WITHOUT OVERRIDING ANY OF THE
DEPRECATED METHODS.
THAT SEEMS A LITTLE SURPRISING TO ME, BUT THIS IS WHAT
HAPPENS.

SO THE FIX IS TO CHANGE XMLOBJECTBASE AND MARK ALL THOSE
METHODS AS
DEPRECATED. THIS IS SOMETHING THAT I COULD DO, BUT NOT RIGHT
AWAY. SO IF
YOU WOULD TAKE A STAB AT MAKING THIS CHANGE IN YOUR
"LOCAL" COPY OF
XMLBEANS, KURT, THAT WILL HELP US CONFIRM THAT THIS IS THE
RIGHT FIX FOR
YOU.

THANKS,
RADU

ON TUE, 2007-07-31 AT 15:57 -0500, KURT ROY WROTE:
> HELLO,
> 
>  
> 
> PLEASE LET ME CLARIFY €“ 
> 
>  
> 
> THE DEPRECATION WARNINGS ARE COMING FROM THE GENERATED
XMLBEANS
> CLASSES WHEN THEY ARE COMPILED €“ NOT FROM OUR
APPLICATION CODE THAT
> USES THE GENERATED CLASSES.
> 
>  
> 
> WE HAVE BEEN USING XMLBEANS FOR ABOUT 6 MOS NOW. PEOPLE
ARE HAPY WITH
> IT,  AND ARE REALLY STARTING TO USE IT IN MANY OF OUR
APPLICATIONS.
> UNFORTUNATELY, BECAUSE OF THIS, WE ARE GENERATING MORE
THAN 10,000
> WARNINGS NIGHTLY BECAUSE OF THIS. WE ALWAYS COMPILE
WITH THE OPTION TO
> DISPLAY WARNINGS, AND FIX ANYTHING THAT GENERATES THEM
AS PART OF OUR
> CONTINUOUS INTEGRATION PROGRAM. 
> 
>  
> 
> IS THERE ANY WAY TO STOP THIS SHORT OF TURNING OFF
DEPRECATION
> WARNINGS ON THE COMPILE? OUR ARCHITECTURE TEAM IS
VEHEMENTLY OPPOSED
> TO THIS SOLUTION. 
> 
>  
> 
> IN FACT, WE ARE OPEN TO THE POSSIBILITY OF ALLOCATING
RESOURCES TO FIX
> THIS PROBLEM IN XMLBEANS IF IT IS INDEED A PROBLEM.
> 
>  
> 
> THANKS FOR YOUR TIME AND SUPPORT.
> 
> KURT ROY | PROS | SOFTWARE ARCHITECT, SOFTWARE
DEVELOPMENT
> PHONE: +1 713-335-8007 | EMAIL: KROYPROSPRICING.COM 
> 
> SAVE THE DATE FOR THE 14TH ANNUAL PROS SUMMIT€˘ APRIL
20-23, 2008 AT
> THE HILTON AMERICAS HOTEL IN HOUSTON, TEXAS €˘
WWW.PROSPRICING.COM
> 
>                                    
>
____________________________________________________________
__________
> FROM: RADU PREOTIUC-PIETRO [MAILTO:RADUPBEA.COM]

> SENT: MONDAY, JULY 30, 2007 4:45 PM
> TO: DEVXMLBEANS.APACHE.ORG
> SUBJECT: RE: GETTING DEPRECATRION WARNINGS WHEN
COMPILING GENERATED
> XMLBEAN CLASSES.
> 
> 
>  
> 
> IT IS BECAUSE IN SIMPLEVALUE.JAVA WE HAVE REPLACED ALL
THE METHODS OF
> THE FORM "INTVALUE()" WITH
"GETVALUEASINT()", BUT WE HAVE NOT REMOVED
> THE OLD VALUES SO THAT CODE THAT IS USING THOSE DOESN'T
NEED TO
> CHANGE. I AM THINKING MAYBE SOMEDAY WE WILL REMOVE
THOSE, BUT IN THE
> MEANTIME I RECCOMEND TURNING THE DEPRECATION WARNINGS
OFF...
> 
>  
> 
> RADU
> 
>          
>         
>                                        
>        
____________________________________________________________
__
>         FROM: KURT ROY [MAILTO:KROYPROSPRICING.COM] 
>         SENT: MONDAY, JULY 30, 2007 1:51 PM
>         TO: DEVXMLBEANS.APACHE.ORG
>         SUBJECT: GETTING DEPRECATRION WARNINGS WHEN
COMPILING
>         GENERATED XMLBEAN CLASSES.
>         
>         HELLO,
>         
>          
>         
>         WHEN COMPILING GENERATED XMLBEANS CLASSES, WE
ALWAYS GET
>         DEPRECATION WARNINGS SUCH AS THE FOLLOWING:
>         
>          
>         
>         [JAVACWITHOVERLAP]
C:PROSRMBUILDTMPSRCCOMPROSRMUIWEB
>        
DATAINTERFACEXMLBEANSIMPLDRILLDOWNXMLBEANIMPL.JAVA:146:
>         WARNING: [DEPRECATION] SET(JAVA.LANG.STRING)
IN
>         ORG.APACHE.XMLBEANS.SIMPLEVALUE HAS BEEN
DEPRECATED
>         
>         [JAVACWITHOVERLAP]     PUBLIC STATIC CLASS
DIMLEVELIMPL
>         EXTENDS
ORG.APACHE.XMLBEANS.IMPL.VALUES.XMLCOMPLEXCONTENTIMPL
>         IMPLEMENTS COM.PROSRM.UI.WEB.DATAINTERFACE
>         
>         .XMLBEANS.DRILLDOWNXMLBEAN.DIMLEVEL
>         
>         [JAVACWITHOVERLAP]                   ^
>         
>         [JAVACWITHOVERLAP]
C:PROSRMBUILDTMPSRCCOMPROSRMUIWEB
>        
DATAINTERFACEXMLBEANSIMPLDRILLDOWNXMLBEANIMPL.JAVA:146:
>         WARNING: [DEPRECATION] OBJECTVALUE() IN
>         
>         ORG.APACHE.XMLBEANS.SIMPLEVALUE HAS BEEN
DEPRECATED
>         
>         [JAVACWITHOVERLAP]     PUBLIC STATIC CLASS
DIMLEVELIMPL
>         EXTENDS
ORG.APACHE.XMLBEANS.IMPL.VALUES.XMLCOMPLEXCONTENTIMPL
>         IMPLEMENTS COM.PROSRM.UI.WEB.DATAINTERFACE
>         
>         .XMLBEANS.DRILLDOWNXMLBEAN.DIMLEVEL
>         
>         [JAVACWITHOVERLAP]                   ^
>         
>          
>         
>          
>         
>         IT SEEMS THAT MOST IF NOT ALL DEPRECATION
WARNINGS ARE
>         GENERATED FROM INTERNAL XMLBEANS CLASS
>         ORG.APACHE.XMLBEANS.SIMPLEVALUE. 
>         
>          
>         
>         WE TRIED WITH XMLBEANS 2.2.0 AND SETTING SOURCE
GENERATION TO
>         JAVA 1.5 (DEFAULTS TO 1.4). WE ALSO TRIED
XMLBEANS 2.3.0.
>         
>          
>         
>         IS THERE ANY WAY (BESIDES TURNING OFF
DEPRECATION WARNINGS ON
>         JAVAC) TO MAKE THESE GO AWAY? 
>         
>          
>         
>         HERE IS THE XSD FRAGMENT:
>         
>          
>         
>           <XSD:COMPLEXTYPE
NAME="PARAMETERS" MIXED="FALSE">
>         
>             <XSD:ANNOTATION>
>         
>               <XSDOCUMENTA
TION>DATA COMMUNICATION
>         PARAMETERS.</XSDOCUMENTA
TION>
>         
>             </XSD:ANNOTATION>
>         
>             <XSD:SEQUENCE>
>         
>               . . .
>         
>               <XSD:ELEMENT
NAME="DRILLDOWN" TYPE="COMMRILLDOWN
"
>         MINOCCURS="0"
MAXOCCURS="1"/>
>         
>          
>         
>         . . .
>         
>          
>         
>           <XSD:COMPLEXTYPE
NAME="DRILLDOWN" MIXED="FALSE">
>         
>             <XSD:ANNOTATION>
>         
>               <XSDOCUMENTA
TION>DATA COMMUNICATION DRILL DOWN
>         PARAMETERS.</XSDOCUMENTA
TION>
>         
>             </XSD:ANNOTATION>
>         
>             <XSD:SEQUENCE>
>         
>               <XSD:ELEMENT NAME="DIMLEVEL"
MINOCCURS="1"
>         MAXOCCURS="UNBOUNDED">
>         
>                 <XSD:COMPLEXTYPE>
>         
>                   <XSD:ATTRIBUTE
NAME="COLUMN" FORM="UNQUALIFIED"
>         TYPE="XSD:STRING"
USE="REQUIRED"/>
>         
>                   <XSD:ATTRIBUTE
NAME="VALUE" FORM="UNQUALIFIED"
>         TYPE="XSD:STRING"
USE="REQUIRED"/>
>         
>                 </XSD:COMPLEXTYPE>
>         
>               </XSD:ELEMENT>
>         
>             </XSD:SEQUENCE>
>         
>           </XSD:COMPLEXTYPE>
>         
>          
>         
>         THANKS,
>         
>         KURT ROY | PROS | SOFTWARE ARCHITECT, SOFTWARE
DEVELOPMENT
>         PHONE: +1 713-335-8007 | EMAIL: KROYPROSPRICING.COM 
>         
>         SAVE THE DATE FOR THE 14TH ANNUAL PROS SUMMIT€˘
APRIL 20-23,
>         2008 AT THE HILTON AMERICAS HOTEL IN HOUSTON,
TEXAS €˘
>         WWW.PROSPRICING.COM
>         
>          
>         
>                                        
>        
____________________________________________________________
__
>         THE INFORMATION CONTAINED IN THIS EMAIL MAY BE
CONFIDENTIAL
>         AND/OR LEGALLY PRIVILEGED. IT HAS BEEN SENT FOR
THE SOLE USE
>         OF THE INTENDED RECIPIENT(S). IF THE READER OF
THIS MESSAGE IS
>         NOT AN INTENDED RECIPIENT, YOU ARE HEREBY
NOTIFIED THAT ANY
>         UNAUTHORIZED REVIEW, USE, DISCLOSURE,
DISSEMINATION,
>         DISTRIBUTION, OR COPYING OF THIS COMMUNICATION,
OR ANY OF ITS
>         CONTENTS, IS STRICTLY PROHIBITED. IF YOU HAVE
RECEIVED THIS
>         COMMUNICATION IN ERROR, PLEASE CONTACT THE
SENDER BY REPLY
>         EMAIL AND DESTROY ALL COPIES OF THE ORIGINAL
MESSAGE. THANK
>         YOU
>         
>         
> 
> NOTICE: THIS EMAIL MESSAGE, TOGETHER WITH ANY
ATTACHMENTS, MAY CONTAIN
> INFORMATION OF BEA SYSTEMS, INC., ITS SUBSIDIARIES AND
AFFILIATED
> ENTITIES, THAT MAY BE CONFIDENTIAL, PROPRIETARY,
COPYRIGHTED AND/OR
> LEGALLY PRIVILEGED, AND IS INTENDED SOLELY FOR THE USE
OF THE
> INDIVIDUAL OR ENTITY NAMED IN THIS MESSAGE. IF YOU ARE
NOT THE
> INTENDED RECIPIENT, AND HAVE RECEIVED THIS MESSAGE IN
ERROR, PLEASE
> IMMEDIATELY RETURN THIS BY EMAIL AND THEN DELETE IT.

NOTICE:  THIS EMAIL MESSAGE, TOGETHER WITH ANY ATTACHMENTS,
MAY CONTAIN INFORMATION  OF  BEA SYSTEMS,  INC.,  ITS
SUBSIDIARIES  AND  AFFILIATED ENTITIES,  THAT MAY BE
CONFIDENTIAL,  PROPRIETARY,  COPYRIGHTED  AND/OR LEGALLY
PRIVILEGED, AND IS INTENDED SOLELY FOR THE USE OF THE
INDIVIDUAL OR ENTITY NAMED IN THIS MESSAGE. IF YOU ARE NOT
THE INTENDED RECIPIENT, AND HAVE RECEIVED THIS MESSAGE IN
ERROR, PLEASE IMMEDIATELY RETURN THIS BY EMAIL AND THEN
DELETE IT.

------------------------------------------------------------
---------
TO UNSUBSCRIBE, E-MAIL: DEV-UNSUBSCRIBEXMLBEANS.APACHE.ORG
FOR ADDITIONAL COMMANDS, E-MAIL: DEV-HELPXMLBEANS.APACHE.ORG


[1-4]

about | contact  Other archives ( Real Estate discussion Medical topics )