Forte to Java Migration Forum

AGILE IT PARTNERS ANNOUNCES "FORTE TO JAVA MIGRATION" DISCUSSION FORUM
In response to the Forte community's request for a forum to discuss Forte to Java migration topics, Agile IT Partners has responded by hosting a forum on their website. The forum can be visited at http://www.agileitpartners.com/forum. A link has also been created on our home-page at http://www.agileitpartners.com
Please use this forum to discuss topics related to Forte/Java migration. Don't hesitate to post any questions you may have or problems you have encountered. The Forte user community has, over the years, provided invaluable support to it's members. Agile IT Partners also commits to being an interactive partner in this forum - we will make every attempt to answer your question and also post topics of interest.
Forum URL: http://www.agileitpartners.com/forum

In my view, GUI has to be rewritten in JAVA, I do not think any tool can change that or should be used.
I would think it will be good to re-do again keeping in view of new concepts, rather than using tool and implement your old code.
Since most of the forte application are build long back and if you reuse the same code again, you are not doing good. I think we should used the latest concepts of SWT framework for windows or JSF and tiles for Web pages.
I can only think of using tool may be in business layer if business has not changed much and your framework is still good enough.
There are no white papers or articles to convert to VB.NET, it would be better if you can convert first each of loosely coupled Forte components to VB.NET (Rather I would prefer using C#) and build a framework to connect to existing forte application using Geneva. This step by step approach may help you to use the existing application and also deliver something to client timely, rather than completely whole application one time for long period of time.
Srikanth

Similar Messages

  • Forte to Java Help

    Hello All,
    I am new to this forum and new to Forte (working with it for about a year). I wanted to know the benefits of moving from Forte to Java. I am suppose to list all the benefits- pros & cons. I am reading on the subject but any help or advice from your end will also help.
    thanks.

    As one of the engineers supporting Fort� and IS EAI, I would like to add to the solid comments from "fortever" -- which I basically agree with. These are my personal comments, and do not represent any offical position by Sun. (I also really love the product, and worked for Fort� before the acquisition in 1999.)
    The fact is, computer science students and professional software developers have been focusing on Java for much more than a decade, and the pool of trained talent is thousands of times greater for Java, and growing. Fort� is written in C++, and as a computer science student, I welcome and honor the migration to languages that have a garbage-collected runtime, like Java, TOOL, and Objective-C. As stable as Fort� is, Java is refining and progressing the state of the art.
    I also believe that the open source model for Java is a good thing, long term. Yes, products that are tightly integrated, like Fort�, are wonderful. But I've been a software engineer for nearly 30 years, and I've lost count of the number of proprietary, tightly-integrated products that have fallen by the wayside. (I've been a part of companies that have wasted tens of millions of dollars on proprietary technology, and struggled to keep them alive for decades.) We are in the middle of a paradigm shift for large IT organizations. Once upon a time, you could not go wrong by recommending IBM and their proprietary technologies. Now, we have studies by the European Economic Community and governments in South America and Asia that are recommending open source products as a long-term, strategic solution -- BECAUSE they won't fall by the wayside in the same way.
    New service-oriented architecture technologies are being support in the Java world, but not in Fort�. For example, our Java CAPS development environment makes it easy to build very sophisticated applications and integration solutions using the latest WSDL, BPEL, etc. standards. Support for these standards are very basic and rather out-of-date in Fort� UDS and IS EAI, and unlikely to improve as the product moves towards end of life.
    Quite honestly, I don't believe you or your organization have a choice about moving from Fort�. As flawed as Java is, it's getting better and better, and it's the only non-proprietary solution I know of that supports industrial sized, scalable, distributed, manageable, heterogeneous applications on all kinds of hardware.

  • Forte(for java) CE question

    Hello people!
    (I found no forum on Forte for java, so I ask my question here)
    Here is it. How can I make Forte know my packages, and support dot notation? ie, say I have a mypack.myotherpack.SomeClass class. When I type
    import mypack.
    at this point it should show what subpackages are available in mypack.
    And if
    SomeClass instance = new ...;
    instance.
    here it should show methods, fields.... But Forte shows all these only in packages and classes that "it already knows" somehow. Does anybody how this is done? It is very frustrating that it does not happen. Thx!

    What class is not found?

  • Error in "Run Java migration toolkit", doing a SAP system copy.

    Hi all,
    Migration to new hardware with system copy, get an error in CI installation on "Run Java Migration Toolkit".
    From the sapinst.log:
    ERROR 2009-05-13 12:46:47.188
    FJS-00003  TypeError: ci.getInstanceDir() has no properties (in script NW_Doublestack_CI|ind|ind|ind|ind, line 120276: ???)
    ERROR 2009-05-13 12:46:48.318
    FCO-00011  The step InitPrivateContext with step key |NW_Doublestack_CI|ind|ind|ind|ind|0|0|NW_CI_Instance|ind|ind|ind|ind|12|0|NW_CI_Instance_Configure_Java|ind|ind|ind|ind|4|0|NW_RUN_MIGRATION_CONTROLLER|ind|ind|ind|ind|2|0|InitPrivateContext was executed with status ERROR .
    From the sapinst_dev.log:
    ERROR      2009-05-13 12:46:47.188 [iaxxejsbas.cpp:204]
    FJS-00003  TypeError: ci.getInstanceDir() has no properties (in script NW_Doublestack_CI|ind|ind|ind|ind, line 120276: ???)
    TRACE      2009-05-13 12:46:48.038 [syuxctask.cpp:1382]
               CSyTaskImpl::start(bool)
    A child process has been started. Pid = 23620
    ERROR      2009-05-13 12:46:48.318 [sixxcstepexecute.cpp:951]
    FCO-00011  The step InitPrivateContext with step key |NW_Doublestack_CI|ind|ind|ind|ind|0|0|NW_CI_Instance|ind|ind|ind|ind|12|0|NW_CI_Instance_Configure_Java|ind|ind|ind|ind|4|0|NW_RUN_MIGRATION_CONTROLLER|ind|ind|ind|ind|2|0|InitPrivateContext was executed with status ERROR .
    TRACE      2009-05-13 12:46:48.368 [iaxxgenimp.cpp:752]
                CGuiEngineImp::showMessageBox
    <html> <head> </head> <body> <p> An error occurred while processing service SAP NetWeaver 7.0 Support Release 3 > Software Life-Cycle Options > System Copy > Oracle > Target System Installation > High-Availability System > Based on AS ABAP and AS Java > Central Instance . You may now </p> <ul> <li> choose <i>Retry</i> to repeat the current step. </li> <li> choose <i>View Log</i> to get more information about the error. </li> <li> stop the task and continue with it later. </li> </ul> <p> Log files are written to /tmp/sapinst_instdir/NW04S/LM/COPY/ORA/SYSTEM/HA/AS/CI. </p> </body></html>
    TRACE      2009-05-13 12:46:48.368 [iaxxgenimp.cpp:1255]
               CGuiEngineImp::acceptAnswerForBlockingRequest
    Waiting for an answer from GUI
    I had checked the INSTANCE_NAME parameter, in every profile, and is ok.
    I tried a new instalation, after importing the profiles, and checking the INSTANCE_NAME, but got the same error.
    Please, advice.
    Thanks in advance.
    Best Regards.
    Jorge

    Thanks Manoj for your advice.
    We had already checked the procedures, we are working based on the System Copy Guide: "System Copy for SAP Systems Based on SAP NetWeaver 7.0 SR3 ABAP+Java".
    I had to mention that source and target systems are HP-UX, 11.23, Itanium and the DataBase is Oracle 10.2.02.
    The copy was made from a Central System (ABAP + Java) to a High-Availability System (ABAP + Java), and the problem appeared when copying the Central Instance.
    Thanks in adavance.
    Regards.
    Jorge

  • Error during java migration tool kit phase

    Hi All ,
    We are migrating the BI 7.00 EHP1 from  (Win 2008/SQL 2008) to Target (Win 2008/SQL 2008).This is a export/Import based method using sapinst tool.
    Import stopped at the "Java Migration Toolkit" phase.The following are the error logs , if anybody faced same issue please help with your inputs.
    runJmt.log
    java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:282)
    at com.sap.sdt.jmt.migrationtool.ConfigurationHandlerFactoryManager.getConfigurationHandlerFactory(ConfigurationHandlerFactoryManager.java:63)
    at com.sap.sdt.jmt.migrationtool.MigrationToolUtils.getSourceConfigurationFactory(MigrationToolUtils.java:178)
    at com.sap.sdt.jmt.migrationtool.MigrationToolImport.startTool(MigrationToolImport.java:260)
    at com.sap.sdt.jmt.migrationtool.MigrationToolImport.main(MigrationToolImport.java:1561)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:331)
    at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    Caused by: com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
    at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:365)
    at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:130)
    at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)
    at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:149)
    at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:236)
    at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:49)
    ... 13 more
    Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The port number error_con is not valid.
    at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(Unknown Source)
    at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Source)
    at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)
    at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:215)
    at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:608)
    at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:285)
    at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:307)
    ... 18 more
    java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:282)
    at com.sap.sdt.jmt.migrationtool.ConfigurationHandlerFactoryManager.getConfigurationHandlerFactory(ConfigurationHandlerFactoryManager.java:63)
    at com.sap.sdt.jmt.migrationtool.MigrationToolUtils.getTargetConfigurationFactory(MigrationToolUtils.java:190)
    at com.sap.sdt.jmt.migrationtool.MigrationToolImport.startTool(MigrationToolImport.java:262)
    at com.sap.sdt.jmt.migrationtool.MigrationToolImport.main(MigrationToolImport.java:1561)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:331)
    at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    Caused by: com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
    at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:365)
    at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:130)
    at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)
    at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:149)
    at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:236)
    at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:49)
    ... 13 more
    Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The port number error_con is not valid.
    at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(Unknown Source)
    at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Source)
    at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)
    at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:215)
    at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:608)
    at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:285)
    at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:307)
    ... 18 more
    Could not initialize the offline configuration managers.

    Hi,
    First check you port numbers as per error, that port is not use.
    The port number error_con is not valid.
    Also check this sap note
    1788188 - Couldn't connect to DB during java install
    Then also check this link with same problem, suggestion is replacing the default kernel from DVD with later one.
    http://scn.sap.com/thread/1203147
    KInd Regards,
    Johan

  • Java system copy problems with the Java Migration Toolkit

    During the JAVA system copy, we have have got the error in second last
    step i.e;Java Migration Toolkit. We tried to do the system copy twice
    but every time we have got the below error.
    Is this a know bug? I have got the OSS note 966752 but the value
    of 'src.ci.host' is already correct. has anybody come across the similar issue. please help.
    " CJSlibModule::writeInfo_impl()
    Output of /usr/java14_64/bin/java -
    classpath /usr/sap/CMT/SYS/global/sltools/sharedlib/launcher.jar:. -Xj9
    com.sap.engine.offline.OfflineToolStart
    com.sap.sdt.jmt.migrationtool.MigrationToolImport /usr/sap/CMT/SYS/global/sltools/jmt:/usr/sap/CMT/SYS/global/sltools/sharedlib import.switch
    resume downtime mti.properties is written to the
    logfile /home/cmtadm/CI_Import_08312009/runJmt.log.
    WARNING 2009-09-01 20:49:43.473
    CJSlibModule::writeWarning_impl()
    Execution of the command "/usr/java14_64/bin/java -
    classpath /usr/sap/CMT/SYS/global/sltools/sharedlib/launcher.jar:. -Xj9
    com.sap.engine.offline.OfflineToolStart
    com.sap.sdt.jmt.migrationtool.MigrationToolImport /usr/sap/CMT/SYS/global/sltools/jmt:/usr/sap/CMT/SYS/global/sltools/sharedlib import.switch
    resume downtime mti.properties" finished with return code 27. Output:
    ERROR 2009-09-01 20:49:43.477
    CJSlibModule::writeError_impl()
    CJS-20068 Error when running the J2EE Migration Toolkit.<br>SOLUTION:
    See output of logfile /home/cmtadm/CI_Import_08312009/runJmt.log: ''.
    ERROR 2009-09-01 20:49:43.479
    CJSlibModule::writeError_impl()
    CJS-20068 Error when running the J2EE Migration Toolkit.<br>SOLUTION:
    See output of logfile /home/cmtadm/CI_Import_08312009/runJmt.log: ''.
    ERROR 2009-09-01 20:49:43.480 [iaxxgenimp.cpp:731]
    showDialog()
    FCO-00011 The step RunMigrationController with step key
    |NW_Doublestack_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Configure_Java|ind|ind|ind|ind|4|0|NW_RUN_MIGRATION_CONTROLLER|ind|ind|ind|ind|2|0|RunMigrationController was executed with status ERROR ."
    There is no log file by the name runJmt.log.
    Regards,
    Sagar

    This issue was resolved by OSS note 966752 itself. Below is the important line in the OSS note.
    Note: The default value is crucial! If a custom value other than the default value was applied, we highly recommend that you restore the default value.
    Thanks,
    Sagar

  • The Sun is down and I can't get Forte for Java (?)

    What's up here. I REQUIRE the newest version of Forte for Java as an IDE for JDK 1.4. The version that I have currently is over a year old. Everytime I select it from the "Products & APIs", I get a message:
    Portions of sun.com are temporarily undergoing maintenance.
    How long is this going to last? It's been unavailable for the last 10 hours (from my standpoint) and my project is at a screeching halt because of it (and since Borland has decided to soak me dry if I want a 'good' version of JBuilder that supports 1.4).
    Not only is the project being squeezed inbetween an old version of the JDK and a just-released version, which not only will require uninstallation of the old and installation of the new, but will hopefully not break the project, requiring code changes.
    Robert Templeton

    Okay, I finally found it. Java.sun.com needs to update its product link to "SUN ONE" since it no longer goes by "Forte for Java". Talk about a lack of internal communication.
    Robert Templeton

  • WD Java Migration error

    Hello all,
    I'm facing a 700 to 730 migration and I'm having some problems with some (not all) WD Java migration. Steps I'm following:
    Development Infraestructure perspective > DC > Sync / Create Project > Create Project
    The system detects that it's an older version and gives me the option Migrate Projects > Next
    Migration Summary:
    Total projects migrated 1
    Projects migrated with warnings 1
    Migration Details:
    Started migration for project DEP_TRACK_Dzhratse_ndp~diba.com OK
    Migrating all of the controller's context in Web Dynpro project OK
    If there are build errors in Web Dynpro Project after migration,this might be due to internal API usages (see SAP Note 928485) For migrating internal API usages -> In Web Dynpro Explorer, right click on Project Node and choose Repair->Internal API Usages
    Web Dynpro perspective > Project > Rebuild, and yes, there are build errors:
    MessageManager cannot be resolved to a type     ATSE_ProPer.java     /DEP_TRACK_Dzhratse_ndp~diba.com/gen_wdp/packages/realtech/com/atse/wdp     line 159     Java Problem
    MessageManager cannot be resolved to a type     ATSE_ProPer.java     /DEP_TRACK_Dzhratse_ndp~diba.com/gen_wdp/packages/realtech/com/atse/wdp     line 159     Java Problem
    MessageManager cannot be resolved to a type     ATSE_ProPer.java     /DEP_TRACK_Dzhratse_ndp~diba.com/gen_wdp/packages/realtech/com/atse/wdp     line 482     Java Problem
    MessageManager cannot be resolved to a type     ATSE_ProPer.java     /DEP_TRACK_Dzhratse_ndp~diba.com/gen_wdp/packages/realtech/com/atse/wdp     line 662     Java Problem
    MessageManager cannot be resolved to a type     ATSE_ProPer.java     /DEP_TRACK_Dzhratse_ndp~diba.com/gen_wdp/packages/realtech/com/atse/wdp     line 722     Java Problem
    MessageManager cannot be resolved to a type     ATSE_ProPer.java     /DEP_TRACK_Dzhratse_ndp~diba.com/gen_wdp/packages/realtech/com/atse/wdp     line 793     Java Problem
    MessageManager cannot be resolved to a type     ATSE_ProPer.java     /DEP_TRACK_Dzhratse_ndp~diba.com/gen_wdp/packages/realtech/com/atse/wdp     line 795     Java Problem
    MessageManager cannot be resolved to a type     ATSE_ProPerMainView.java     /DEP_TRACK_Dzhratse_ndp~diba.com/gen_wdp/packages/realtech/com/atse/wdp     line 129     Java Problem
    MessageManager cannot be resolved to a type     ATSE_ProPerMainView.java     /DEP_TRACK_Dzhratse_ndp~diba.com/gen_wdp/packages/realtech/com/atse/wdp     line 129     Java Problem
    MessageManager cannot be resolved to a type     ATSE_ProPerMainView.java     /DEP_TRACK_Dzhratse_ndp~diba.com/gen_wdp/packages/realtech/com/atse/wdp     line 563     Java Problem
    MessageManager cannot be resolved to a type     ATSE_ProPer_PermanenciaView.java     /DEP_TRACK_Dzhratse_ndp~diba.com/gen_wdp/packages/realtech/com/atse/wdp     line 119     Java Problem
    MessageManager cannot be resolved to a type     ATSE_ProPer_PermanenciaView.java     /DEP_TRACK_Dzhratse_ndp~diba.com/gen_wdp/packages/realtech/com/atse/wdp     line 119     Java Problem
    MessageManager cannot be resolved to a type     ATSE_ProPer_PermanenciaView.java     /DEP_TRACK_Dzhratse_ndp~diba.com/gen_wdp/packages/realtech/com/atse/wdp     line 229     Java Problem
    MessageManager cannot be resolved to a type     ATSE_ProPer_PermanenciaView.java     /DEP_TRACK_Dzhratse_ndp~diba.com/gen_wdp/packages/realtech/com/atse/wdp     line 235     Java Problem
    MessageManager cannot be resolved to a type     ATSE_ProPer_PermanenciaView.java     /DEP_TRACK_Dzhratse_ndp~diba.com/gen_wdp/packages/realtech/com/atse/wdp     line 250     Java Problem
    The import com.sap.tc.webdynpro.progmodel.controller cannot be resolved     ATSE_ProPer.java     /DEP_TRACK_Dzhratse_ndp~diba.com/gen_wdp/packages/realtech/com/atse/wdp     line 43     Java Problem
    The import com.sap.tc.webdynpro.progmodel.controller cannot be resolved     ATSE_ProPerMainView.java     /DEP_TRACK_Dzhratse_ndp~diba.com/gen_wdp/packages/realtech/com/atse/wdp     line 33     Java Problem
    The import com.sap.tc.webdynpro.progmodel.controller cannot be resolved     ATSE_ProPer_PermanenciaView.java     /DEP_TRACK_Dzhratse_ndp~diba.com/gen_wdp/packages/realtech/com/atse/wdp     line 26     Java Problem
    Then I do what he said:
    Web Dynpro perspective > Project > Repair > Internal Web Dynpro API Usages
    Web Dynpro perspective > Project > Rebuild
    And right now, everything is ok! No more errors in the Web Dynpro project code...
    Right now, I should deploy it, right?
    Web Dynpro perspective > Project > Deploy > Make consistent first (Create Archive) > OK
    And then an error occurs:
    Build
      zhr/atse_ndp diba.com The Build terminated with errors
    Archive file ' DEP_TRACK_Dzhratse_ndpdiba.com gen default deploy diba.comzhr~atse_ndp.ear' not found. Check the problems view for error messages and create a new archive.
    Any idea?
    Thanks!!!

    [wdgen] [Info]    Generating packages/realtech/com/atse/wdp/wdp/ResourceATSE_ProPer.properties
         [wdgen] [Info]    Catching throwable null
         [wdgen] [Info]    java.lang.reflect.InvocationTargetException
         [wdgen]      at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source)
         [wdgen]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         [wdgen]      at java.lang.reflect.Method.invoke(Method.java:597)
         [wdgen]      at com.sap.ide.generationfwk.task.GenerationTaskJavaMethod.executePersistent(GenerationTaskJavaMethod.java:139)
         [wdgen]      at com.sap.ide.generationfwk.GenerationBase.doPersistentGeneration(GenerationBase.java:207)
         [wdgen]      at com.sap.ide.generationfwk.GenerationBase.doPersistentGeneration(GenerationBase.java:164)
         [wdgen]      at com.sap.ide.webdynpro.generation.Generation.doPersistentGenerationForComponentDefaultResource(Generation.java:541)
         [wdgen]      at com.sap.ide.webdynpro.generation.Generation.doPersistentGenerationForComponentResources(Generation.java:3188)
         [wdgen]      at com.sap.ide.webdynpro.generation.Generation.doPersistentGenerationForComponentRecursively(Generation.java:1788)
         [wdgen]      at com.sap.ide.webdynpro.generation.Generation.generateComponentsForArchive(Generation.java:2660)
         [wdgen]      at com.sap.ide.webdynpro.generation.Generation.generateMDOsForArchive(Generation.java:2604)
         [wdgen]      at com.sap.ide.webdynpro.generation.Generation.generatePersistentArchive(Generation.java:1630)
         [wdgen]      at com.sap.ide.webdynpro.generation.console.GenerationConsole.generate(GenerationConsole.java:190)
         [wdgen]      at com.sap.webdynpro.generation.ant.GenerationAnt.main(GenerationAnt.java:69)
         [wdgen]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         [wdgen]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         [wdgen]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         [wdgen]      at java.lang.reflect.Method.invoke(Method.java:597)
         [wdgen]      at com.sap.webdynpro.generation.ant.WDGenAntTask.execute(WDGenAntTask.java:240)
         [wdgen]      at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
         [wdgen]      at sun.reflect.GeneratedMethodAccessor27.invoke(Unknown Source)
         [wdgen]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         [wdgen]      at java.lang.reflect.Method.invoke(Method.java:597)
         [wdgen]      at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
         [wdgen]      at org.apache.tools.ant.Task.perform(Task.java:348)
         [wdgen]      at org.apache.tools.ant.Target.execute(Target.java:357)
         [wdgen]      at org.apache.tools.ant.Target.performTasks(Target.java:385)
         [wdgen]      at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
         [wdgen]      at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
         [wdgen]      at com.sap.tc.buildplugin.ant.util.AntRunner.run(AntRunner.java:115)
         [wdgen]      at com.sap.tc.buildplugin.DefaultAntBuildAction.execute(DefaultAntBuildAction.java:53)
         [wdgen]      at com.sap.tc.buildplugin.DefaultPlugin.processSequence(DefaultPlugin.java:235)
         [wdgen]      at com.sap.tc.buildplugin.DefaultPlugin.handleBuildStepSequence(DefaultPlugin.java:174)
         [wdgen]      at com.sap.tc.buildplugin.DefaultPlugin.performBuild(DefaultPlugin.java:165)
         [wdgen]      at com.sap.tc.buildplugin.DefaultPluginV3Delegate$BuildRequestHandler.handle(DefaultPluginV3Delegate.java:66)
         [wdgen]      at com.sap.tc.buildplugin.DefaultPluginV3Delegate.requestV3(DefaultPluginV3Delegate.java:48)
         [wdgen]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         [wdgen]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         [wdgen]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         [wdgen]      at java.lang.reflect.Method.invoke(Method.java:597)
         [wdgen]      at com.sap.tc.buildtool.v2.impl.PluginHandler2.maybeInvoke(PluginHandler2.java:403)
         [wdgen]      at com.sap.tc.buildtool.v2.impl.PluginHandler2.request(PluginHandler2.java:149)
         [wdgen]      at com.sap.tc.buildtool.v2.impl.PluginHandler2.build(PluginHandler2.java:87)
         [wdgen]      at com.sap.tc.buildtool.PluginHandler2Wrapper.execute(PluginHandler2Wrapper.java:59)
         [wdgen]      at com.sap.tc.devconf.internal.DCProxyMake.make(DCProxyMake.java:276)
         [wdgen]      at com.sap.tc.devconf.internal.DCProxy.make(DCProxy.java:1459)
         [wdgen]      at com.sap.tc.devconf.internal.DCProxy.make(DCProxy.java:1441)
         [wdgen]      at com.sap.tc.devconf.internal.DCProxy.make(DCProxy.java:3927)
         [wdgen]      at com.sap.ide.dii08.internal.commandz.BuildDcsCommand.build(BuildDcsCommand.java:333)
         [wdgen]      at com.sap.ide.dii08.internal.commandz.BuildDcsCommand.execute(BuildDcsCommand.java:176)
         [wdgen]      at com.sap.ide.dii08.internal.service.CommandExecutor$2.run(CommandExecutor.java:77)
         [wdgen]      at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
         [wdgen]      at com.sap.ide.dii05.util.internal.lock.DiiConsistencyServiceImpl.executeConsistentWorkspaceRunnable(DiiConsistencyServiceImpl.java:90)
         [wdgen]      at com.sap.ide.dii05.util.internal.lock.DiiConsistencyServiceImpl.executeConsistentWorkspaceRunnable(DiiConsistencyServiceImpl.java:52)
         [wdgen]      at com.sap.ide.dii08.internal.service.CommandExecutor.executeInWorkspaceAndDevConfLocks(CommandExecutor.java:90)
         [wdgen]      at com.sap.ide.dii08.internal.service.InternalDiiCommandService.buildDcs(InternalDiiCommandService.java:179)
         [wdgen]      at com.sap.ide.dii08.internal.service.InternalDiiCommandService.buildDcs(InternalDiiCommandService.java:986)
         [wdgen]      at com.sap.ide.dii05.ui.internal.actions.dc.BuildAction$2.run(BuildAction.java:193)
         [wdgen]      at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
         [wdgen] Caused by: java.lang.NullPointerException
         [wdgen]      at com.sap.ide.metamodel.core.i18n.TranslatableTextProxy.getResourceType(TranslatableTextProxy.java:197)
         [wdgen]      at com.sap.ide.webdynpro.generation.runtime._Resource.vm_dumpTextPool(_Resource.java:135)
         [wdgen]      at com.sap.ide.webdynpro.generation.runtime._Resource.v_main(_Resource.java:83)
         [wdgen]      at com.sap.ide.webdynpro.generation.runtime.DefaultResource.v_main(DefaultResource.java:80)
         [wdgen]      at com.sap.ide.webdynpro.generation.runtime.DefaultResource.doGenerate(DefaultResource.java:56)
         [wdgen]      at com.sap.ide.generationfwk.velocity.runtime.CompiledTemplateBase.generate0(CompiledTemplateBase.java:232)
         [wdgen]      at com.sap.ide.generationfwk.velocity.runtime.CompiledTemplateBase.generate(CompiledTemplateBase.java:164)
         [wdgen]      ... 59 more
         [wdgen] [Info]    Generation error while processing template defaultResource
         [wdgen] [Info]    Catching throwable null
         [wdgen] [Info]    java.lang.reflect.InvocationTargetException
         [wdgen]      at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source)
         [wdgen]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         [wdgen]      at java.lang.reflect.Method.invoke(Method.java:597)
         [wdgen]      at com.sap.ide.generationfwk.task.GenerationTaskJavaMethod.executePersistent(GenerationTaskJavaMethod.java:139)
         [wdgen]      at com.sap.ide.generationfwk.GenerationBase.doPersistentGeneration(GenerationBase.java:207)
         [wdgen]      at com.sap.ide.generationfwk.GenerationBase.doPersistentGeneration(GenerationBase.java:164)
         [wdgen]      at com.sap.ide.webdynpro.generation.Generation.doPersistentGenerationForComponentDefaultResource(Generation.java:541)
         [wdgen]      at com.sap.ide.webdynpro.generation.Generation.doPersistentGenerationForComponentResources(Generation.java:3188)
         [wdgen]      at com.sap.ide.webdynpro.generation.Generation.doPersistentGenerationForComponentRecursively(Generation.java:1788)
         [wdgen]      at com.sap.ide.webdynpro.generation.Generation.generateComponentsForArchive(Generation.java:2660)
         [wdgen]      at com.sap.ide.webdynpro.generation.Generation.generateMDOsForArchive(Generation.java:2604)
         [wdgen]      at com.sap.ide.webdynpro.generation.Generation.generatePersistentArchive(Generation.java:1630)
         [wdgen]      at com.sap.ide.webdynpro.generation.console.GenerationConsole.generate(GenerationConsole.java:190)
         [wdgen]      at com.sap.webdynpro.generation.ant.GenerationAnt.main(GenerationAnt.java:69)
         [wdgen]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         [wdgen]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         [wdgen]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         [wdgen]      at java.lang.reflect.Method.invoke(Method.java:597)
         [wdgen]      at com.sap.webdynpro.generation.ant.WDGenAntTask.execute(WDGenAntTask.java:240)
         [wdgen]      at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
         [wdgen]      at sun.reflect.GeneratedMethodAccessor27.invoke(Unknown Source)
         [wdgen]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         [wdgen]      at java.lang.reflect.Method.invoke(Method.java:597)
         [wdgen]      at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
         [wdgen]      at org.apache.tools.ant.Task.perform(Task.java:348)
         [wdgen]      at org.apache.tools.ant.Target.execute(Target.java:357)
         [wdgen]      at org.apache.tools.ant.Target.performTasks(Target.java:385)
         [wdgen]      at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
         [wdgen]      at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
         [wdgen]      at com.sap.tc.buildplugin.ant.util.AntRunner.run(AntRunner.java:115)
         [wdgen]      at com.sap.tc.buildplugin.DefaultAntBuildAction.execute(DefaultAntBuildAction.java:53)
         [wdgen]      at com.sap.tc.buildplugin.DefaultPlugin.processSequence(DefaultPlugin.java:235)
         [wdgen]      at com.sap.tc.buildplugin.DefaultPlugin.handleBuildStepSequence(DefaultPlugin.java:174)
         [wdgen]      at com.sap.tc.buildplugin.DefaultPlugin.performBuild(DefaultPlugin.java:165)
         [wdgen]      at com.sap.tc.buildplugin.DefaultPluginV3Delegate$BuildRequestHandler.handle(DefaultPluginV3Delegate.java:66)
         [wdgen]      at com.sap.tc.buildplugin.DefaultPluginV3Delegate.requestV3(DefaultPluginV3Delegate.java:48)
         [wdgen]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         [wdgen]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         [wdgen]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         [wdgen]      at java.lang.reflect.Method.invoke(Method.java:597)
         [wdgen]      at com.sap.tc.buildtool.v2.impl.PluginHandler2.maybeInvoke(PluginHandler2.java:403)
         [wdgen]      at com.sap.tc.buildtool.v2.impl.PluginHandler2.request(PluginHandler2.java:149)
         [wdgen]      at com.sap.tc.buildtool.v2.impl.PluginHandler2.build(PluginHandler2.java:87)
         [wdgen]      at com.sap.tc.buildtool.PluginHandler2Wrapper.execute(PluginHandler2Wrapper.java:59)
         [wdgen]      at com.sap.tc.devconf.internal.DCProxyMake.make(DCProxyMake.java:276)
         [wdgen]      at com.sap.tc.devconf.internal.DCProxy.make(DCProxy.java:1459)
         [wdgen]      at com.sap.tc.devconf.internal.DCProxy.make(DCProxy.java:1441)
         [wdgen]      at com.sap.tc.devconf.internal.DCProxy.make(DCProxy.java:3927)
         [wdgen]      at com.sap.ide.dii08.internal.commandz.BuildDcsCommand.build(BuildDcsCommand.java:333)
         [wdgen]      at com.sap.ide.dii08.internal.commandz.BuildDcsCommand.execute(BuildDcsCommand.java:176)
         [wdgen]      at com.sap.ide.dii08.internal.service.CommandExecutor$2.run(CommandExecutor.java:77)
         [wdgen]      at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
         [wdgen]      at com.sap.ide.dii05.util.internal.lock.DiiConsistencyServiceImpl.executeConsistentWorkspaceRunnable(DiiConsistencyServiceImpl.java:90)
         [wdgen]      at com.sap.ide.dii05.util.internal.lock.DiiConsistencyServiceImpl.executeConsistentWorkspaceRunnable(DiiConsistencyServiceImpl.java:52)
         [wdgen]      at com.sap.ide.dii08.internal.service.CommandExecutor.executeInWorkspaceAndDevConfLocks(CommandExecutor.java:90)
         [wdgen]      at com.sap.ide.dii08.internal.service.InternalDiiCommandService.buildDcs(InternalDiiCommandService.java:179)
         [wdgen]      at com.sap.ide.dii08.internal.service.InternalDiiCommandService.buildDcs(InternalDiiCommandService.java:986)
         [wdgen]      at com.sap.ide.dii05.ui.internal.actions.dc.BuildAction$2.run(BuildAction.java:193)
         [wdgen]      at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
         [wdgen] Caused by: java.lang.NullPointerException
         [wdgen]      at com.sap.ide.metamodel.core.i18n.TranslatableTextProxy.getResourceType(TranslatableTextProxy.java:197)
         [wdgen]      at com.sap.ide.webdynpro.generation.runtime._Resource.vm_dumpTextPool(_Resource.java:135)
         [wdgen]      at com.sap.ide.webdynpro.generation.runtime._Resource.v_main(_Resource.java:83)
         [wdgen]      at com.sap.ide.webdynpro.generation.runtime.DefaultResource.v_main(DefaultResource.java:80)
         [wdgen]      at com.sap.ide.webdynpro.generation.runtime.DefaultResource.doGenerate(DefaultResource.java:56)
         [wdgen]      at com.sap.ide.generationfwk.velocity.runtime.CompiledTemplateBase.generate0(CompiledTemplateBase.java:232)
         [wdgen]      at com.sap.ide.generationfwk.velocity.runtime.CompiledTemplateBase.generate(CompiledTemplateBase.java:164)
         [wdgen]      ... 59 more
         [wdgen] [Error]   Generation error while processing D:/Documents and Settings/corellavpd/NWDS_73.jdi/0/t/52509E1C6529CF3CE8D0B5F0D24D8066/gen_wdp/packages/realtech/com/atse/wdp/wdp/ResourceATSE_ProPer.properties (java.lang.reflect.InvocationTargetException)
         [wdgen] [Error]   Generation failed due to errors (10 seconds)
    Ant runtime 24.953 seconds
    Ant build finished with ERRORS
    [Error]   Generation failed!
    Build stopped due to an error: [Error]   Generation failed!

  • Open Forte for java project in Sun java studio enterprise

    Hi Everyone, I am new to Java development. I have a java application developed in Forte for java 4 and I need to open and compile it in Sun java studio enterprise. Could anybody tell me how to do that? Thank you very much.

    The recent versions of the IDE (starting with NetBeans 4.1 and JSE 8) are based on a more-robust project system that is ant based. Projects from Forte for Java 4, unfortunately, cannot be directly opened in JSE8, NB4.1 and later.
    If you do have access to the original source code, pl. try the following in the latest version of JSE or NetBeans:
    - Create a fresh project in jse using File | New Project. (For a java standalone app, you would choose General | Java Application from the dialog).
    - Add the existing files to the empty project. You can do so by right-clicking on the project, selecting properties and adding the existing source directories under 'Source Packages' in 'Sources' category.
    Or from the new project dialog, you could select 'General | Java Project with existing sources' option.

  • Forte for Java and webLogic

    How do I integrate WebLogic 6.1 and Forte for Java?

    Hi.
    You might check with Sun/Forte for info on how to do this.
    Regards,
    Michael
    Stjepan Maric wrote:
    How do I integrate WebLogic 6.1 and Forte for Java?--
    Michael Young
    Developer Relations Engineer
    BEA Support

  • Problems uninstalling Forte for java 4 community edition

    I just installed Forte for java 4 community edition at work, and when i tried to uninstalled it with add/remove programs from control panel. And the uninstall wizard start but then a Sun window apper and it is written, uninstalling and the uninstall program seems to be frozen.

    i have the same problem, reading the documentation it seems you got to run the installer again and you ll get prompted with the "file deletion confirmation"
    too bad i have a self-installing package and i don't get the prompt...
    guesses anyone?

  • Forte For Java GUI Editor

    Hi everyone,
    I've been trying to switch usage between Forte for Java running on 2 platforms (Win NT and Solaris 8). For this reason, I want to try to use the GUI Editor in each. But when I tried copying the same .class file from one platform to another and running opening the file under Forte for Java, the GUI Editor doesn't show up the form and Component Editor. Is there a way to make Forte for Java able to recognize the GUI components in a class file not creatd in Forte or not in that version of Forte? Thank you for any help!
    Bob

    Hi,
    this happens not just with class file but also with .java
    file. I created a GUI with Forte ( on windows ) and because I did not jave runtime setup on windows, I copied, java file that was created to the unix env. Then added some code to it and copied back to the windows.
    After that, GUI editor never came up. I lost all that I did
    to create a GUI. Now I can modify GUI only manually.
    I you have found answer to this, please let meknow
    at [email protected]
    rgds,
    sam

  • Java Discussion Forum - Post topic not working

    I've deployed the Java Discussion Forum contributed by CLAURENT in Knowledge Exchange. Deployed to 10gAS in JDev 9051. I've modified a few deprecated classes and made the appropraite changes to orion-applications.xml to point to the correct JPDK jars when deployed under Linux.
    The application is operating properly with no errors. The administartion portlet can modify and create new forums. However, Posting a topic does NOT work. And it doesn't throw any errors on screen or in the console log (application.log) or the log4j log (forumprovider.log). Has anyone run into a problem like this?
    Thanks. LEH

    I have exactly the same problem on the Portal 10g release 2.
    Normally the "dit of a new topic" calls the EditPostAction but after submitting the form, nothing reachs this action.
    I check this in debug mode and add several logs and I don't see nothing appearing for this action.
    Did you find a solution?

  • Question on forte for java

    Hi,
    I'm developing using the Forte for JAVA ide, but I get an error though i know certainly that my code is correct.
    I get this error:
    Tue Nov 06 11:35:29 CET 2001: java.lang.NoSuchMethodError: Posted StackTrace
    Annotation: Exception occurred in Request Processor
    org.openide.util.RequestProcessor$Holder: Posted StackTrace(task org.netbeans.modules.web.core.jsploader.TagLibParseSupport$ParsingRunnable@772046 [-2433, 9, -1])
    at org.openide.util.RequestProcessor$Task.createHolder(RequestProcessor.java:322)
    at org.openide.util.RequestProcessor.post(RequestProcessor.java:100)
    at org.openide.util.RequestProcessor.postRequest(RequestProcessor.java:185)
    at org.netbeans.modules.web.core.jsploader.TagLibParseSupport.parseObject(TagLibParseSupport.java:110)
    at org.netbeans.modules.web.core.jsploader.TagLibParseSupport.prepare(TagLibParseSupport.java:97)
    at org.netbeans.modules.web.core.jsploader.TagLibParseSupport.getTagLibEditorData(TagLibParseSupport.java:67)
    at org.netbeans.modules.web.core.jsploader.TagLibParseSupport.getTagLibEditorData(TagLibParseSupport.java:55)
    at org.netbeans.modules.web.core.syntax.JSPKit.createSyntax(JSPKit.java:94)
    at org.netbeans.editor.BaseDocument.getFreeSyntax(BaseDocument.java:377)
    at org.netbeans.editor.DrawEngine.draw(DrawEngine.java:876)
    at org.netbeans.editor.LeafView.paintAreas(LeafView.java:145)
    at org.netbeans.editor.BaseView.paint(BaseView.java:129)
    at org.netbeans.editor.BaseTextUI$RootView.paint(BaseTextUI.java:594)
    at org.netbeans.editor.BaseTextUI.paintRegion(BaseTextUI.java:238)
    at org.netbeans.editor.EditorUI.paint(EditorUI.java:1315)
    at org.netbeans.editor.BaseTextUI.paint(BaseTextUI.java:217)
    at javax.swing.plaf.ComponentUI.update(ComponentUI.java:39)
    at javax.swing.JComponent.paintComponent(JComponent.java:395)
    at javax.swing.JComponent.paint(JComponent.java:687)
    at javax.swing.JComponent.paintChildren(JComponent.java:498)
    at javax.swing.JComponent.paint(JComponent.java:696)
    at javax.swing.JViewport.paint(JViewport.java:668)
    at javax.swing.JComponent.paintChildren(JComponent.java:498)
    at javax.swing.JComponent.paint(JComponent.java:696)
    at javax.swing.JComponent.paintChildren(JComponent.java:498)
    at javax.swing.JComponent.paint(JComponent.java:696)
    at javax.swing.JComponent.paintChildren(JComponent.java:498)
    at javax.swing.JComponent.paint(JComponent.java:696)
    at javax.swing.JComponent.paintChildren(JComponent.java:498)
    at javax.swing.JComponent.paint(JComponent.java:696)
    at javax.swing.JComponent.paintChildren(JComponent.java:498)
    at javax.swing.JComponent.paint(JComponent.java:696)
    at javax.swing.JComponent.paintWithBuffer(JComponent.java:3878)
    at javax.swing.JComponent._paintImmediately(JComponent.java:3821)
    at javax.swing.JComponent.paintImmediately(JComponent.java:3672)
    at javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:370)
    at org.netbeans.core.windows.frames.PinRepaintRM.paintDirtyRegions(PinRepaintRM.java:75)
    at javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run(SystemEventQueueUtilities.java:124)
    at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:154)
    [catch] at java.awt.EventQueue.dispatchEvent(EventQueue.java:337)
    at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:131)
    at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:98)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:85)
    Tue Nov 06 11:35:29 CET 2001: java.lang.NoSuchMethodError: null
    java.lang.NoSuchMethodError
    at org.netbeans.modules.web.core.jsploader.TagLibParseSupport.parsePage(TagLibParseSupport.java:150)
    at org.netbeans.modules.web.core.jsploader.TagLibParseSupport.access$200(TagLibParseSupport.java:41)
    at org.netbeans.modules.web.core.jsploader.TagLibParseSupport$ParsingRunnable.run(TagLibParseSupport.java:119)
    at org.openide.util.Task.run(Task.java:124)
    [catch] at org.openide.util.RequestProcessor$ProcessorThread.run(RequestProcessor.java:626)
    I seems that it can't compile my jsp to servlet
    THX

    ive ran into many problems with compiling in forte. I just compile everything from the command line now, lets me know exactly what switches i want, and it works! ive never seen an error like that in forte though, i would just recommend compiling it from the command line with "javac"...

  • About Forte for java

    I'm a really beginner on Java.
    I don't the guru use what kind of java developing tools.
    There's only one I can use is "Forte for java".
    Dose anyone there who familiar to it and can help me?

    I'm a really beginner on Java.
    I don't the guru use what kind of java developing
    tools.
    There's only one I can use is "Forte for java".
    Dose anyone there who familiar to it and can help me?I used Forte for Java when I was really really new to Java too. I liked it.
    I liked the way different words in the Java program were shown in different colors. It helped me to understand the language. I thought it was a nice tool.
    But unfortunately, I only learned Java with Forte. I associated all my work with Forte. I was thinking much about Forte. I didn't learn about directory structures in an application or how Java uses a classpath until I stopped using Forte.
    So yawmark is right. If you use Mac OSX try using BBEdit as an editor. It will color your code. And outside of an IDE you will be aware of the basics of Java. If you use another Operating System, there are other text editors available that can color your code and that can be helpful.

Maybe you are looking for