JAXB generated code gives deprecation warnings on compile

I have a schema that was previously had its binding generated using jwsdp 1.3. I recent;y made some minor changes to the schema and also upgraded to jwsdp 1.5. I made all the required changes to my environmental varibles on my system (acutal no other version of jwsdp was every installed on this box). xjc generates the code without issue:
xjc -p my.package myxsd.xsd
When I build my software using an ant script I get hundreds of warnings such as the following:
[javac] c:\sandbox\code\my\package\ObjectFactory.java:499: warning: com.sun.xml.bind.GrammarInfo in com.sun.xml.bind has been deprecated
Has anyone seen anything like this, or know what may cause such a problem? I have check all of the jars that my build file calls and they are of the correct version (this so called deprecated package exists in jaxb-impl.jar)
Any help would be appricated. Thnx.

JAXB questions should be better directed to the users list of http://jaxb.dev.java.net/
you should subscribe to the 'users' mailing list, then post a question there.
Thank you!

Similar Messages

JAXWS: clientgen generates code which it can't compile?

Hi,
I am trying to get the weblogic JAX-WS stack working, however I am stuck at the following:
C:\projects\eclipse\cml\test-ws-wls>ant -f clientgen_build.xml build_client
Buildfile: clientgen_build.xml
build_client:
     [echo] d:\apps\oracle\wls1211_dev\modules\org.apache.ant_1.7.1\lib\ant-launcher.jar;d:\apps\oracle\WLS121~1\patch_wls1211\profiles\default\sys_manifest_cla
sspath\weblogic_patch.jar;d:\apps\oracle\WLS121~1\patch_ocp371\profiles\default\sys_manifest_classpath\weblogic_patch.jar;D:\apps\java\CURREN~2\lib\tools.jar;d:
\apps\oracle\WLS121~1\wlserver\server\lib\weblogic_sp.jar;d:\apps\oracle\WLS121~1\wlserver\server\lib\weblogic.jar;d:\apps\oracle\WLS121~1\modules\features\webl
ogic.server.modules_12.1.1.0.jar;d:\apps\oracle\WLS121~1\wlserver\server\lib\webservices.jar;d:\apps\oracle\WLS121~1\modules\ORGAPA~1.1\lib\ant-all.jar;d:\apps\
oracle\WLS121~1\modules\NETSFA~1.0_1\lib\ant-contrib.jar;d:\apps\oracle\WLS121~1\wlserver\common\derby\lib\derbyclient.jar;d:\apps\oracle\WLS121~1\wlserver\serv
er\lib\xqrl.jar;C:\projects\wls\domains\cml\classes-ext\;D:\apps\oracle\wls1211_dev\modules\org.apache.ant_1.7.1\lib\ant-all.jar;D:\apps\oracle\wls1211_dev\modu
les\org.apache.ant_1.7.1\lib\ant-antlr.jar;D:\apps\oracle\wls1211_dev\modules\org.apache.ant_1.7.1\lib\ant-apache-bcel.jar;D:\apps\oracle\wls1211_dev\modules\or
g.apache.ant_1.7.1\lib\ant-apache-bsf.jar;D:\apps\oracle\wls1211_dev\modules\org.apache.ant_1.7.1\lib\ant-apache-log4j.jar;D:\apps\oracle\wls1211_dev\modules\or
g.apache.ant_1.7.1\lib\ant-apache-oro.jar;D:\apps\oracle\wls1211_dev\modules\org.apache.ant_1.7.1\lib\ant-apache-regexp.jar;D:\apps\oracle\wls1211_dev\modules\o
rg.apache.ant_1.7.1\lib\ant-apache-resolver.jar;D:\apps\oracle\wls1211_dev\modules\org.apache.ant_1.7.1\lib\ant-commons-logging.jar;D:\apps\oracle\wls1211_dev\m
odules\org.apache.ant_1.7.1\lib\ant-commons-net.jar;D:\apps\oracle\wls1211_dev\modules\org.apache.ant_1.7.1\lib\ant-jai.jar;D:\apps\oracle\wls1211_dev\modules\o
rg.apache.ant_1.7.1\lib\ant-javamail.jar;D:\apps\oracle\wls1211_dev\modules\org.apache.ant_1.7.1\lib\ant-jdepend.jar;D:\apps\oracle\wls1211_dev\modules\org.apac
he.ant_1.7.1\lib\ant-jmf.jar;D:\apps\oracle\wls1211_dev\modules\org.apache.ant_1.7.1\lib\ant-jsch.jar;D:\apps\oracle\wls1211_dev\modules\org.apache.ant_1.7.1\li
b\ant-junit.jar;D:\apps\oracle\wls1211_dev\modules\org.apache.ant_1.7.1\lib\ant-launcher.jar;D:\apps\oracle\wls1211_dev\modules\org.apache.ant_1.7.1\lib\ant-net
rexx.jar;D:\apps\oracle\wls1211_dev\modules\org.apache.ant_1.7.1\lib\ant-nodeps.jar;D:\apps\oracle\wls1211_dev\modules\org.apache.ant_1.7.1\lib\ant-starteam.jar
;D:\apps\oracle\wls1211_dev\modules\org.apache.ant_1.7.1\lib\ant-stylebook.jar;D:\apps\oracle\wls1211_dev\modules\org.apache.ant_1.7.1\lib\ant-swing.jar;D:\apps
\oracle\wls1211_dev\modules\org.apache.ant_1.7.1\lib\ant-testutil.jar;D:\apps\oracle\wls1211_dev\modules\org.apache.ant_1.7.1\lib\ant-trax.jar;D:\apps\oracle\wl
s1211_dev\modules\org.apache.ant_1.7.1\lib\ant-weblogic.jar;D:\apps\oracle\wls1211_dev\modules\org.apache.ant_1.7.1\lib\ant.jar;D:\apps\oracle\wls1211_dev\modul
es\org.apache.ant_1.7.1\lib\xercesImpl.jar;D:\apps\oracle\wls1211_dev\modules\org.apache.ant_1.7.1\lib\xml-apis.jar;D:\apps\java\CURRENT-x64\lib\tools.jar
Trying to override old definition of datatype clientgen
[clientgen] System property "weblogic.wsee.client.ssl.stricthostchecking" is not supported
[clientgen] Catalog dir = C:\Users\xtrnatv\AppData\Local\Temp\_vhn32z\META-INF\wsdls
[clientgen] Rename file [ TestWSPolicyService?xsd=1 ] to [ TestWSPolicyService1.xsd]
[clientgen] Download file [TestWSPolicyService1.xsd] to C:\Users\xtrnatv\AppData\Local\Temp\_vhn32z\META-INF\wsdls
[clientgen] Download file [wls-policy.wsdl] to C:\Users\xtrnatv\AppData\Local\Temp\_vhn32z\META-INF\wsdls
[clientgen] Ignoring JAX-RPC options - building a JAX-WS client
[clientgen]
[clientgen] *********** jax-ws clientgen attribute settings ***************
[clientgen]
[clientgen] wsdlURI: file:/C:/projects/eclipse/cml/test-ws-wls/wls-policy.wsdl
[clientgen] packageName : null
[clientgen] destDir : C:\Users\xtrnatv\AppData\Local\Temp\_vhn32z
[clientgen]
[clientgen] *********** jax-ws clientgen attribute settings end ***************
[clientgen] Consider using <depends>/<produces> so that wsimport won't do unnecessary compilation
[clientgen] parsing WSDL...
[clientgen]
[clientgen]
[clientgen]
[clientgen] Generating code...
[clientgen]
[clientgen]
[clientgen] Compiling code...
[clientgen]
     [null] Compiling 7 source files to C:\Users\xtrnatv\AppData\Local\Temp\_vhn32z
[clientgen] C:\Users\xtrnatv\AppData\Local\Temp\_vhn32z\policy\jaxws\lab\nevexis\com\TestWSPolicyService.java:47: cannot find symbol
[clientgen] symbol : constructor Service(java.net.URL,javax.xml.namespace.QName,javax.xml.ws.WebServiceFeature[])
[clientgen] location: class javax.xml.ws.Service
[clientgen]         super(TESTWSPOLICYSERVICE_WSDL_LOCATION, TESTWSPOLICYSERVICE_QNAME, features);
[clientgen]         ^
[clientgen] C:\Users\xtrnatv\AppData\Local\Temp\_vhn32z\policy\jaxws\lab\nevexis\com\TestWSPolicyService.java:55: cannot find symbol
[clientgen] symbol : constructor Service(java.net.URL,javax.xml.namespace.QName,javax.xml.ws.WebServiceFeature[])
[clientgen] location: class javax.xml.ws.Service
[clientgen]         super(wsdlLocation, TESTWSPOLICYSERVICE_QNAME, features);
[clientgen]         ^
[clientgen] C:\Users\xtrnatv\AppData\Local\Temp\_vhn32z\policy\jaxws\lab\nevexis\com\TestWSPolicyService.java:63: cannot find symbol
[clientgen] symbol : constructor Service(java.net.URL,javax.xml.namespace.QName,javax.xml.ws.WebServiceFeature[])
[clientgen] location: class javax.xml.ws.Service
[clientgen]         super(wsdlLocation, serviceName, features);
[clientgen]         ^
[clientgen] 3 errors
[AntUtil.deleteDir] Deleting directory C:\Users\xtrnatv\AppData\Local\Temp\_vhn32z
BUILD FAILED
Compile failed; see the compiler error output for details.
Total time: 3 seconds
The bulk on top is the classpath as you can see from my build.xml
<project name="test-ws-wls" basedir="." default="fork_build_client">

<target name="fork_build_client">
    <java
        fork="true"
        failonerror="true"
        classname="org.apache.tools.ant.launch.Launcher"
        maxmemory="512m"
        jvm="${java.home}/bin/java"
        >
      <arg value="-f" />
      <arg value="${ant.file}" />
      <arg value="build_client" />
      <env key="CLASSPATH"
           value="${fork.class.path}" />
    </java>
</target>
<target name="build_client">
      <echo>${java.class.path}</echo>
    <taskdef name="clientgen" classname="weblogic.wsee.tools.anttasks.ClientGenTask" />
    <clientgen
        failonerror="true"
        type="JAXWS"
        wsdl="${basedir}/wls-policy.wsdl"
        destFile="${basedir}/WebContent/WEB-INF/lib/wls-policy.wsdl.jar"
        serviceName="TestWSPolicyService"
        copyWsdl="true"
        >
    <sysproperty key="weblogic.wsee.client.ssl.stricthostchecking" value="false"/>
    </clientgen>
</target>
</project>
The error is a one I know it has to do with the difference between
Service (Java EE 5 SDK)
and
Service (Java EE 6 )
I wonder why does this compilation fail? I think I am missing the javax.xml.ws.Service in my CLASSPATH, or may be I should be using some of the jars as "endorsed" ...
I tried following this article:
Developing WebLogic Web Service Clients - 12c Release 1 (12.1.1)
Can someone give me a clue?
Thanks!

There is a way to do it, but your memory will be lost. Plug the iPod into the computer and hold the lock and the home button at the same time and continue holding. It will turn off automatically and turn back on. When the apple logo shows up, release the home button and continue holding the home button. Then it will come up in iTunes and say you need to restore the iPod.
You may be able to use one of your backups to restore the lost memory, but probably the old passcode will come back with the backup. All of your apps and music should be in iTunes, so very little worries.

Deprecated warnings while using XMLBeans

Greetings,
Using XMLBeans Builder in WorkShop 9.2 raises hundreds of deprecated warnings. It seems that the XMLBeans Builder generated code doesn't compile against ... XMLBeans itself ? It that possible ? Any workaround ?
Many thanks in advance,
Nicolas

Hi Nicolas,
To highlight your issue:
"""...how could I compile, without any warnings, including deprecation
warnings, XMLBeans Builder generated code. After all, as it's name
clearly suggests, an XMLBeans Builder generates code to be compiled
against XMLBeans. It seems very strange that a product which generates
XMLBeans compliant code cannot compile this code without deprecation
warnings."""
I spent some time working with XMLBeans and unfortunately, what you want
(code without deprecation warnings) is actually something to make a
request of from the Apache XmlBeans folks. The code the XMLBeans Builder
generates is not any different from that which the Apache XmlBeans
project would generate when a schema is compiled via the 'scomp' tool.
Here's how you can see the cause of this outside of the Xmlbeans builder
tool or the Workshop IDE
1) go to http://xmlbeans.apache.org and download a binary distribution
2) unzip the binary distribution to a dir on your filesystem
3) copy your xsds to <unzip-dir>\xmlbeans-2.2.20\bin
4) cd to <unzip-dir>\xmlbeans-2.2.20\bin
5) run the following:
scomp -src srcOutputDir *.xsd
This will generate the src files from the xsd (similar to how the
XMLBeans Builder tool would) on your filesystem.
From there, browse to a .java file and view in your favorite text editor.
You'll see that the java code produced from the XMLBeans tool itself
produces code with @deprecated javadoc
e.g,
/** @deprecated {@link XMLInputStream} */
public static org.apache.xmlbeans.xml.stream.XMLInputStream
Now to see this in the Workshop IDE, create a new J2EE Utility Project.
Make sure the XmlBeans->XmlBeans library facet is enabled.
Drag the contents of srcOutputDir (from above) to the src directory of
the J2EE Utility Project in the IDE window.
Upon successful rebuild of the srcs in the IDE, you'll be able to see
similar warnings from pure Apache XmlBeans related code.
If you really CANNOT have these deprecation warnings, your best bet may
be to email the Apache XmlBeans mailing list. At the very least they can
probably best explain why the deprecation is still left in the code.
The website for xmlbeans is:
http://xmlbeans.apache.org
and some helpful mailing lists can be found and queried from
http://xmlbeans.apache.org/community/index.html
Hope this helps,
-Jacobd
nicolas duminil wrote:
rfrost,
Many thanks for having taken the time to reply but ... you didn't get me. My point was not to disable compiler's deprecation warnings. I believe that it's very important to be aware that APIs you're using in your code is deprecated. This is certainly the reason which motivated the compiler's creators to provide an option able to signal deprecated calls in the code. Disabling this warnings doesn't provide any benefits, it is just hiding problems and the goal of a compiler is not to hide problems, but to hi
ghlight them. No, my point was simply to ask how could I compile, without any warnings, including deprecation warnings, XMLBeans Builder generated code. After all, as it's name clearly suggests, an XMLBeans Builder generates code to be compiled against XMLBeans. It seems very strange that a product which generates XMLBeans compliant code cannot compile this code without deprecation warnings. That's a big issue because a deprecation warning says to you: "Hey, you're using something you're not supposed to u
se any more". So, many thanks to you for having let me know how to disable compilation warnings, but this was not at all the point. The real point was how to use the XMLBeans Builder in order to generate XMLBeans code free of deprecation warnings. I understand you don't have the answer but, in this case, please don't feel obligated to reply.
Kind regards,
nicolas

Deploytool - Exception in generated code during compilation

Hi,
I am trying to deploy a rather simple container managed application. When running it through the verifier of J2EE1.3.1 I receive no errors.
During deployment I get the following message:
"Error deploying ejb.jar: Compilation failed"
The j2ee server output shows, that the error is located in the generated code of the Bean class:
"d:\Java\j2sdkee1.3.1\repository\lap18\gnrtrTMP\AufnahmeAgent\de\faw\charite\aufnahmeagent\generated\AufnahmeAgentBean_PM.java:3: de.faw.charite.aufnahmeagent.generated.AufnahmeAgentBean_PM should be declared abstract; it does not define remove() in de.faw.charite.aufnahmeagent.generated.AufnahmeAgentBean"
How can this be my error?
The log only shows the following:
Compilation failed.
     at com.sun.ejb.codegen.GeneratorDriver.compileClasses(GeneratorDriver.java:232)
     at com.sun.ejb.codegen.GeneratorDriver.preDeploy(GeneratorDriver.java:603)
     at com.sun.enterprise.tools.deployment.backend.JarInstallerImpl.deployEjbs(JarInstallerImpl.java:707)
     at com.sun.enterprise.tools.deployment.backend.JarInstallerImpl.deployApplication(JarInstallerImpl.java:221)
     at org.omg.stub.com.sun.enterprise.tools.deployment.backend._JarInstallerImpl_Tie._invoke(Unknown Source)
     at com.sun.corba.ee.internal.corba.ServerDelegate.dispatch(ServerDelegate.java:355)
     at com.sun.corba.ee.internal.iiop.ORB.process(ORB.java:255)
     at com.sun.corba.ee.internal.iiop.RequestProcessor.process(RequestProcessor.java:84)
     at com.sun.corba.ee.internal.orbutil.ThreadPool$PooledThread.run(ThreadPool.java:99)
Anybody ever met anything similar?
My Setup:
NT4.0
JDK1.3.1 && JDK1.4 (tried both, made no difference)
Code:
BEAN CLASS:
public abstract class AufnahmeAgentBean
        implements AufnahmeAgentModel, ClientAgent, EntityBean {
    private AufnahmeAgentControl control;
    public void registerRMIRemote(String remoteClassName) {
        try {
            Class cls = Class.forName(remoteClassName);
            Object[] params = { getClientRMIServerAdress(),
                                getClientRMIServerName() };
            Object instance = cls.getConstructors()[0].newInstance(params);
            control.registerClient((AufnahmeAgentClientInterface)instance);
        catch(Exception ex) {
            System.err.println("Fatal RMI Error: " + ex);
    public AufnahmeAgentBean(){}
     * Called by the AgentEngine if a new AgentMessage has been sent to this.
     * @param msg the AgentMessage
    public void processMessage(AgentMessage msg) throws RemoteException {}
     * Called if a new request AgentMessage has been sent to this.
     * @param msg the AgentMessage
     * @return the result of the request
    public java.io.Serializable processRequest(AgentMessage msg) throws RemoteException{}
     * data access methods
    public abstract String getAgentName();
    public abstract void setAgentName(String agentName);
    public void ejbRemove() {}
    public void setEntityContext(EntityContext context) { }
    public void unsetEntityContext() { }
    public void ejbActivate() { }
    public void ejbPassivate() { }
    public void ejbLoad() { }
    public void ejbStore() { }
     * Creates a new AgentServerBean instance.
     * @param serverID the id of this
    public String ejbCreate(String agentName)
            throws CreateException, RemoteException {
        setAgentName(agentName);
        AgentEngine agentEngine = new EJBAgentEngine(EJBAgentEngine.STATIC_SERVER_ID);
        control = new AufnahmeAgentControl(getAgentName(),agentEngine, this);
        return agentName;
    public void ejbPostCreate(String agentName) {
}THE REMOTE INTERFACE
public interface AufnahmeAgent extends EJBObject {
    // The CMP methods for client connection
    String getClientRMIServerAdress() throws RemoteException;
    String getClientRMIServerName() throws RemoteException;
    void setClientRMIServerAdress(String value) throws RemoteException;
    void setClientRMIServerName(String value) throws RemoteException;
    public PatientMitPrioritaet[] getNawPatienten() throws java.rmi.RemoteException;
     public String getRTSArzt() throws java.rmi.RemoteException;
     public void setNawPatienten(PatientMitPrioritaet[] values) throws java.rmi.RemoteException;
     public void setRTSArzt(String value) throws java.rmi.RemoteException;
}

Hi again,
I found the error. To explain it it is necessary to state that the interfaces implemented by the Bean class are generated. Since the code already worked at a time I didn't check it, which profed a mistake.
One of the interfaces extended the EJBObject interface. Because of this the AufnahmeAgentBean thought it had to implement those methods too :-(
Well lots of time wasted, but at least I now know a bit more about the architecture of our product.
Where did you read this?? By "data access methods" do
you mean your bean's "business methods"? Again, the
container/vendor tool has no way of knowing how to
implement your beans abstract methods - only the
interface methods which it (usually) does by wrapping
your bean. The container knows which of your beans
attributes it is to manage from your bean's Deployment
Descriptor: specifically, those elements identified as
<cmp-field>, not from reflecting on your code!By data access methods I mean the following:
you got a String that shall be managed by the database. Normally, of course, one would just declare it:
protected String _foo;
when using container managed persistence you just declare the accessmethods as abstracts:
public abstract String getFoo();
public abstract void setFoo(String foo);
Thus the bean must be declared abstract.
You asked where I read that the bean is always declared abstract when it uses CMP. Right here:
http://java.sun.com/j2ee/tutorial/1_3-fcs/doc/CMP3.html
In section Differences between Container-Managed and Bean-Managed Code
No they don't, and they are not supposed to. The
remove method is part of the EJBObject definition,
and>
As I stated previously, such a declaration would not
have been the same as those in your bean's interfaces.
:)>
afaik it doesn't have to be implemented when using
container managed persistence.>
The 'ejbRemove' method in your bean doesn't ever have
to be implemented, but is does have to appear in your
bean since it's declared in the Session/EntityBean
interace. All methods in these interfaces are
container callback methods. They exist to enable the
container to manage the life of the bean. The
'remove' methods in the Home and Remote interfaces are
implemented by the vendor tool and proxy to the bean's
ejbRemove method. Calling CMPInterface.remove still
propagates a call to CMPBean.ejbRemove. In this case
ejbRemove provides your bean the opportunity to null
its members and allow garbage collection to occur more
quickly.well of course you are right... but I didn' t receive the error message because of the ejbRemove but because of the remove method, which isn't supposed to be implemented in the Bean class. Now of course we know why ;-)
Well thanks for your time, I decided to reward your invested time with five of the ten Duke Dollars ( especially since it reall was a design flaw that you couldn't find...lacking the sourcecode)
Greetings, and thanks for the help,
Markus "marksman" Hammori

J2EE deploytool compile error in generated code.

I write and compile all the code for EJB.
Created .EAR and .WAR files needed for deploy. But when the deploy application tries to generated and compile stub code there is a compilation problem.
Anyone knows how can I solve this? or this is a problem of the deploy app, Is there another one?
I'm using J2EE SDK 1.3 beta version.
THANKS...

It's not an Exception. Are compile errors of the generated code.
When you make "Deploy..." from "Tools" menu item of the "Application Deployment Tool", it make some task including source generation and its compilation, so, this compilation have errors.

Deprecation Warnings

Hi
I am using 3.2.3 and when I set a JLabel's
label the code generated is label.setLabel
- can I get JDeveloper to generate setText
instead?
Marc

It means you have attempted to use methods which are marked obsolete and might be removed in the future. Usually the compiler will tell you which methods were deprecated. To find out a alternative to use, consult the java docs for the api you are working on. Usually an alternative is listed.
I am trying to compile my program and i am getting
this kin*d of error
Warning #: 369 : There have been deprecation warnings.
Please consult the documentation for a better
alternative
Does any one knows wht it means, or where the error
come from, understanding the meaning of the error
message might help me to solve my problem...........

Bogus "deprecated" warnings

Hi,
I wrote a class that extends HttpServerResponseWrapper and now I am getting these bogus deprecation warnings:
warning: [deprecation] setStatus(int,java.lang.String) in javax.servlet.http.HttpServletResponse has been deprecated
class CacheResponseWrapper extends HttpServletResponseWrapper
Thing is, I am not overriding or invoking setStatus() at all so what gives? Is this a bug in the javac compiler?
Gili

Its not a bug. When implementing an interface, you get this warning if you don't declare the implementation of any deprecated methods declared in the interface as being deprecated in the implementation. HttpServletResponseWrapper doesn't declare its implementation of setStatus(int, String) as deprecated, so this is why you are seeing the warning. If you override the method and mark it as deprecated in your class, the warning will dissappear.

Reusing JAXB generated classes for XSDs included in other XSDs

Hi,
I use xsds with jaxb in a number of related projects. To avoid duplication I've factored out commonly used elements into their own xsd in a separate project. I then include these in the xsds that need them.
I generate classes with jaxb for each project. I'm now trying to get jaxb so far as to reuse the already generated classes for the common elements.
For example: I have a general xsd Person.xsd for which I generate classes in common.xsd. I have another xsd Project.xsd that includes a reference to the Person element. When i let jaxb generate classes for Projects.xsd, it will also generate a project.xsd.PersonType and so on.
Is there any way to tell JAXB to use the existing classes? I've played around with the <jxb:javaType> bindings, but I can't get it to work yet. It gives me a "bindings not used" warning and doesn't compile. Also, if this is in fact the way to go, what do I specify as the parseMethod and printMethod attributes for the javaType element?
Thx for any help

JAXB questions should be better directed to the users list of http://jaxb.dev.java.net/
you should subscribe to the 'users' mailing list, then post a question there.
Thank you!

Beginner:an issue of generating code for an entity service

Hi All,
I have downloaded Sap Netweaver of sneak preview version which contains netweaver studio 7.0.07. And my jdk version is 1.4.09.
I created a CAF project and added an entity service named Person(just by clicking mouse,not did anything else).But when I tried to generate code,the compiler told me "The type abstractStringbuilder is not visible" and thus it caused the failure of building the project.I have googled this issue and found that this is a existing bug in eclipse.
Now here is the question: will it take effect if I upgrade my jdk to 1.5? Or can anyone give me any suggestions?
Thank you very much.
Message was edited by: Yuhui Liu
Message was edited by: Yuhui Liu

Hi,
I suspect that you are using Java5 sinse the AbstractStringBulder is not present in 1.4.
Please check the Java version used by the IDE by opening "Help -> About.. -> Configuration Details".
Java 5 is not supported by NetWeaver 7.
Anyway, an upgrade to Java 5 won't solve the issue.
Best Regards,
Tsvetan

[svn] 4880: * Fixed deprecation warnings with AST generation and a Repeater RTE

Revision: 4880
Author: [email protected]
Date: 2009-02-06 13:30:19 -0800 (Fri, 06 Feb 2009)
Log Message:
* Fixed deprecation warnings with AST generation and a Repeater RTE
caused by revision 4709.
tests Passed: checkintests, mxunit repeater, asc-tests
Needs QA: YES
Needs DOC: NO
Bug fixes: SDK-16288, SDK-18986
API Change: NO
Reviewer: Corey, Pete F.
Code-level description of changes:
asc/src/java/macromedia/asc/embedding/LintEvaluator.java
Added ignoreSynthesizedCode variable and setter.
Modified warning() to only skip synthetic code when
ignoreSynthesizedCode is false. This allows us to report
deprecation warnings when using AST generation with Mxml
documents.
compiler/src/java/flex2/compiler/as3/As3Compiler.java
Modified analyze4() to set the LintEvaluator's
ignoreSynthesizedCode flag to false.
compiler/src/java/flex2/compiler/mxml/lang/StandardDefs.java
Added CLASS_REPEATER_DOT.
compiler/src/java/flex2/compiler/mxml/rep/init/VisualChildInitializer.java
Modified getAssignExpr() and generateAssignExpr() to code gen the
initializeRepeater() call. This required changing the return type
of generateAssignExpr() from ExpressionStatementNode to
StatementListNode.
compiler/src/java/flex2/compiler/mxml/rep/init/ValueInitializer.java
Removed initializeRepeater() related code gen from
getDefinitionBody() and generatedDefinitionBody().
compiler/src/java/flex2/compiler/mxml/rep/init/EffectInitializer.java
compiler/src/java/flex2/compiler/mxml/rep/init/Initializer.java
compiler/src/java/flex2/compiler/mxml/rep/init/StyleInitializer.java
compiler/src/java/flex2/compiler/mxml/rep/init/EventInitializer.java
compiler/src/java/flex2/compiler/mxml/rep/init/NamedInitializer.java
compiler/src/java/flex2/compiler/mxml/rep/init/ArrayElementInitializer.java
compiler/src/java/flex2/compiler/mxml/rep/decl/InitializedPropertyDeclaration.java
compiler/src/java/flex2/compiler/mxml/ImplementationGenerator.java
Updated to reflect change to generateAssignExpr() signature
required by VisualChildInitializer.
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-16288
http://bugs.adobe.com/jira/browse/SDK-18986
Modified Paths:
flex/sdk/branches/i10/modules/asc/src/java/macromedia/asc/embedding/LintEvaluator.java
flex/sdk/branches/i10/modules/compiler/src/java/flex2/compiler/as3/As3Compiler.java
flex/sdk/branches/i10/modules/compiler/src/java/flex2/compiler/mxml/ImplementationGenerat or.java
flex/sdk/branches/i10/modules/compiler/src/java/flex2/compiler/mxml/lang/StandardDefs.jav a
flex/sdk/branches/i10/modules/compiler/src/java/flex2/compiler/mxml/rep/decl/InitializedP ropertyDeclaration.java
flex/sdk/branches/i10/modules/compiler/src/java/flex2/compiler/mxml/rep/init/ArrayElement Initializer.java
flex/sdk/branches/i10/modules/compiler/src/java/flex2/compiler/mxml/rep/init/EffectInitia lizer.java
flex/sdk/branches/i10/modules/compiler/src/java/flex2/compiler/mxml/rep/init/EventInitial izer.java
flex/sdk/branches/i10/modules/compiler/src/java/flex2/compiler/mxml/rep/init/Initializer. java
flex/sdk/branches/i10/modules/compiler/src/java/flex2/compiler/mxml/rep/init/NamedInitial izer.java
flex/sdk/branches/i10/modules/compiler/src/java/flex2/compiler/mxml/rep/init/StyleInitial izer.java
flex/sdk/branches/i10/modules/compiler/src/java/flex2/compiler/mxml/rep/init/ValueInitial izer.java
flex/sdk/branches/i10/modules/compiler/src/java/flex2/compiler/mxml/rep/init/VisualChildI nitializer.java

Expand Operator generates code errors in OWB 10g2 map

I suspect that there are few people that actually use the Expand Operator in OWB from the lack of threads in this forum; however I'll give this a shot.
I have a map function that returns a user-defined object type which I then use an Expand Operator to break into its component data parts. The function works Ok. The map validates Ok. The code generates Ok. However, on deployment the map generates errors:
ORA-06550: line 768, column 97:
PLS-00103: Encountered the symbol "." when expecting one of the following:
* & = - + < / > at in is mod remainder not rem then
<an exponent (**)> <> or != or ~= >= <= <> and or like LIKE2_
LIKE4_ LIKEC_ between overlaps || multiset year DAY_ member
SUBMULTISET_
The symbol "* was inserted before "." to continue.
Compiling the package body in SQL developer, I can spot the exact lines that produce this error, so I know it's coming from the Expand Operator's generated code. In every case, the Expand Operator is producing lines like this (code generalized):
(("[function_name]"("[map_name]"."[map_input_parameter]"))).BYTES_COUNT
(("[function_name]"("[map_name]"."[map_input_parameter]"))).ROWS_INSERTED
BYTES_COUNT and ROWS_INSERTED are data components of the user_defined object type returned by the function.
The problem is the # of parentheses surrounding the function name and the returning component being outside these parentheses. If I move the returning component in between the first and second closing parentheses, the code will compile:
(("[function_name]"("[map_name]"."[map_input_parameter]"*).BYTES_COUNT))*
(("[function_name]"("[map_name]"."[map_input_parameter]"*).ROWS_INSERTED))*
IMO, this is an OWB bug !! The Expand Operator can't be used without editing the code after deployment.

Unfortunately breaking apart the user-defined type in an Expression Operator produces the same error message and virtually the same code problem:
(([function_name]("[map_name]"."[input_parameter]")).BYTES_COUNT/* EXPRESSION.OUTGRP1.BYTES_COUNT */)
As in the Expand Operator the line above compiles when the data type component ("BYTES_COUNT") is manually moved between the first and second closing parentheses:
(([function_name]("[map_name]"."[input_parameter]").BYTES_COUNT/* EXPRESSION.OUTGRP1.BYTES_COUNT */) )

OWB Error while generating Code for a mapping

I have a simple mapping loading from a source to a flat file. When I try to generate code it gives me the following Error
VLD-2357: Target Data File name not specified for file <target Flat file name>.
I am new to OWB so any help on the same will be greatly appreciated. How can I specify target Data File name in the mapping configuration under Flat file operators
Thanks
Anish

If you configure the mapping in the UI from the main design tree and select the name of your file operator under the tree node 'Flat File Operators' on the right hand side panel the properties should be displayed - one of these properties is 'Target Data File Name', enter the name of your target data file name.
Cheers
David

Error while deploying generated code from sup to iPhone

Hi
I generated the code using Sap unwired platform for Objective-c. I followed the steps specified in the below link
http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc01213.0153/doc/html/mqu1264543829068.html
for deploying the generated code into iPhone simulator, i am getting the following error
Undefined symbols:
"_OBJC_CLASS_$_SUPEntityAlias", referenced from:
objc-class-ref-to-SUPEntityAlias in SUP101_Customer.o
objc-class-ref-to-SUPEntityAlias in SUP101_LogRecordImpl.o
Can any one help me in this
Edited by: KiranSanka on Dec 2, 2010 1:18 PM
Edited by: KiranSanka on Dec 3, 2010 7:26 AM

Hi
While compiling did you get a warning? something along the line "missing required architecture i386 in fileu201D? if so refer this link http://stackoverflow.com/questions/1456185/build-error-missing-required-architecture-i386-in-file
Regards
Jinesh

Auto generated code in makefile

For our product we have a TCL script that reads a series of text files and generates C++ classes for easy access to database records. Our code has been in use for make years and works very well. We have always used a solaris command prompt dmake to compile, which first generates the C++ files then complies them. It uses a series of enviroment variables which a user must set before compilation.
I recently tried to create a Sun Studio Express based on NetBeans 6.5.rc1 project from a make file. This has worked for every other makefile except for this one. The others do not have any auto generated code.
To run sun studio I in a command prompt source in the environments then run netbeans. Then I choose to build the product but I get an error. I then try to copy the command it is running into telnet window and it works fine. Does anyone have an idea on why in the sun studio I get and error while the telnet window works fine.

I think the problem is that the SunStudio IDE runs the build command in a wrong directory.
Can you verify that the working directory is correct?
(it is in project properties: Build > Make)
Also you can find this directory in the message in the output, when you try to build the project.
That's the message, that you copied to the terminal window.
Thanks,
Nik

Installed Sun studio 12.2. ran 'discover' command on C++ code.Gives warning

Hi,
I installed Sun studio 12.2. I compiled C++ code with C++ 5.11 compiler, and ran discover command as shown below:
> #CC -g -O2 test.cpp
> #discover -w - a.out
> discover (warning): a.out will be analyzed in lite mode because it has no annotations. See discover documentation for compiler flag/OS recommendations
I get the discover warning. After runnig discover command, I executed ./a.out. On cosole, only memory leaks will be displayed and no other error.
Any reason why discover gives warning??????????????????
Edited by: Archit on Apr 5, 2011 11:09 PM
Edited by: Archit on Apr 5, 2011 11:10 PM
Edited by: Archit on Apr 5, 2011 11:10 PM
Edited by: Archit on Apr 5, 2011 11:13 PM

Hi,
What a woderful fix you have provided !!!!!!!!!!
It really works.
I tried running on Solaris 10 update 8. discover tool runs properly. Where as , the tool runs in lite mode on Solaris update 4.
If possible , can you pint me to some links where I can this kind of info.?
Thank you very much.

JAXB generated code gives deprecation warnings on compile

Similar Messages

Maybe you are looking for