Mistake in Forte WebEnterprise Designer

Hi :
I have a "odd error" in my aplications, this error is ERRATIC.
The error is the following :
qqdb_ResourceException caught while executing EXECUTE tag named
SUBMISSIONHandler.ProcessAction
Original message: Execute failed for dynamic SQL statement 54, error from
database is: ORA-00604: error occurred at recursive SQL level 1 ORA-01000:
maximum open cursors exceeded
Thanks in advance ...

Hi MVG
You may try this
1. Add To your bean method like
public java.awt.Container contentPanel()
  //innerPanel is some contained container (usally
  //JPanel) you need to add into your container bean.
  //It has to be empty with some kind of LayoutManager
  return innerPanel;
}2. In the getBeanDescriptor method of the bean's
BeanInfo class:
public java.bean.BeanDescriptor getBeanDescriptor()
  java.bean.BeanDescriptor rv;
  rv = new java.bean.BeanDescriptor(yourBean.clsss);
  //Here is the punch line
  rv.setValue("containerDelegate","contentPanel"); 
  return rv;
}Notes:
a. The key "containerDelegate" is a must, on the other hand the name "contentPanel" is not pre-request as long
as the names in the bean class and in the BeanInfo are
the same.
b. This works for NetBeans, since Forte is build around NetBeans I guess it should work in Forte too.
HTH,
Yair

Similar Messages

  • Forte WebEnterprise w/ ISAPI - 10055 error

    Forte Users,
    We have a Forte application that is web-enabled via Forte WebEnterprise and
    intermittently we are receiving 10055 error when following a link. After
    receiving the error you can either use the back arrow and retry the link or
    just hit the refresh button and the page will download. The problem seems
    to be intermittent and only seems to happen when the ISAPI Plug-in
    (forteisapi.dll) is configured, we have not seen the problem when using the
    CGI interface.
    I contacted Forte support regarding the error but they are not able to
    recreate the error either.
    Any help is greatly appreciated!
    Please see the following for details on my configuration and environment.
    Thanks,
    -----Original Message-----
    From: MailAgent [mailto:[email protected]]
    Sent: Wednesday, November 03, 1999 10:56 AM
    To: [email protected]
    Subject: Forte Virtual Call Center Case No. -- 56768
    Thank you for submitting Case No. 56768. Please save this email as a record
    of
    your request. If you do not get a response from us within the time period
    outlined in our support priority matrix, please email us at
    [email protected]
    and include the text of this email.
    Contact Information
    Case No.: 56768
    Case Details
    FORTE: 3.0.L.3
    CONDUCTOR: Not Applicable
    EXPRESS: Not Applicable
    WEB: WE.1.0.D.1
    Client Platform: Windows NT 4.0
    Server Platform: SunOS 4.1.3
    Database: Not Applicable
    Netowork: sockets
    Reproducible: Intermittent
    Requested Priority: 2 - Medium
    Subject:
    socket send() to Forte HTTPAccess service object failed. errno=10055
    Description:
    Runtime Error:Socket Error: socket send() to Forte HTTPAccess service
    object
    failed. errno=10055
    If I refresh or go back and try the link again it usually works.
    I am using IIS and have the isapi interface enabled.
    Errors:
    socket send() to Forte HTTPAccess service object failed. errno=10055
    End of message

  • Web for Forte - what is the right product?

    We are using Web Enterprise on a new application and on another existing
    Forte application.
    Concerning our experiences on the new application:
    1) Watch what version of Forte and WE you use. Earlier that 3.M.2 and WE
    E.1, we experienced a page truncation bug (that Forte admitted was their
    bug).
    2) Upgrades between Forte versions have been difficult as each upgrade means
    an upgrade to the WE pieces. The only way we have been successful in these
    upgrades is by recreating the repository, creating the new HTTP/HTML
    libraries/projects, and importing (in order) our projects. This is time
    consuming. It would be nice if Forte did not force the WE upgrade when the
    Forte version changes.
    3) As of yet, we have not been able to get a load balanced Web Access SO to
    work. The help desk has suggested using a higher port number range (from
    1780 up to 6000) but we haven't tried this yet.
    Concerning our experiences with the existing application conversion:
    1) The GUI interface of a windows application and a browser application are
    basically different. There are things that are easy in a std GUI that are
    much more difficult with a browser. So, if using std HTML, typically the
    application will behave somewhat differently.
    2) We used JavaScript within our HTML to do some basic editing within the
    browser. This was much easier than doing std HTML to Forte for every type
    of edit. In fact, we even used Forte to dynamically generate JavaScript in
    certain circumstances.
    3) We did NOT use Java at all.
    4) The Forte application we are converting is old (4+ yrs) and was not
    designed in the ideal way. Much of the processing logic and sql is embedded
    inside windows. My point is that if the architecture of the existing
    application is 'good' (good separation of pure GUI functions from business
    rules from db access), then moving to WE can be fairly easy. If every Forte
    window operation calls some method rather than invoking inline code, then
    that is a good step. If every window operation calls some external
    (non-window) method, then that is even better. That makes the replacement
    of the Forte GUI with a browser based GUI much easier.
    5) We tested, very briefly, the Window Converter operations of WE. It did
    seem to work but we really could not utilize this facility because of the
    poor design of the Forte GUI. We would have been forced to re-write our
    existing GUI to take advantage of this.
    6) We are attempting to reuse what we can from the existing application but
    we are also taking advantage of this rewrite to implement a cleaner
    architecture within a newly developed framework.
    Jerry Fatcheric
    Verizon Wireless
    Hi Forte Experts
    We are developing an application in 'pure' Forte 4GL, but have now reachedthe point >where some 20 windows must also be used from a WWW interface,
    both for dataentry and >lookup of info.
    So what is the right product(s) to look for / buy? Forte for Java ,WebEnterprise, >WebEnterprise Designer or is the functionality already in
    30M2 and all we need to do >is to open the documentation-kit...?
    Suggestions or War-stories are welcomed...
    thanks
    jens chr /KAD Denmark

    Adobe makes three products that could work here: Photoshop Elements, Lightroom and Photoshop. Other companies also make programs that will do these tasks.
    You make it sound like this is a one-time need. If that's true, I would think that the Adobe products are overkill. In fact, to edit the photos you might want to look at freeware products like RawTherapee, and there are plenty of freeware slideshow applications.

  • Forte Migration - Need Suggestion regarding Forte Migration.

    Hi friends,
    I need some suggestion in designing GUI.
    we have an application designed on mainframes and also in forte. And lots of users life the mainframes, since they have been using for long time and it is easy for data entry and it is faster and by hitting F2/F4 keys the data entry people finish the work fast and they is incentive to do fast and more.
    And we have the same application in Forte too, Forte GUI design is also great, it provides lots of data compared to mainframes, but little slower and it cannot be done in the same speed as mainframes.
    In such a situation, if you have to migrate what technology would you opt and how to think about converting the console based forte application, which also provides in data entry and provides lots of information.
    And it is process oriented, where we could like complete one step before going to other step and also go and modify the data entered in step1. Example, while entering the telephone order, after validating customer details, we would like to provide telephone services. But we should be also able to modify the customer information.
    The reason I gave the example before, if you think about using J2EE and provide Web browser interface, which would be best and cut lots of cost and time on deployment (usually in case of Forte console based application), but major draw back would be we cannot control the users activity and you cannot back and forth and update the data. (Think about lot of Tab in Forte application.).
    So, the need is for thin client and lots of Tabs and user should be able to go back and forth and real fast application client like mainframes to enter lots of data fast and provider look up for validations.
    How would you do migration for such a application ?
    1.     J2EE, how would you think about providing user interface. (web browser or java console application using swing) ? Did any body of you done using swing.
    2.     .NET application. (client using ASP.NET with C# for business logic/middle tier)
    Please give me some suggestion and how did you migrate under such circumstances.
    I know, it is difficult to suggest without seeing the application, but please give me the high level idea. May be you much also faced similar situation.
    Thanks in advance.

    NET, Swing, Web - all provide options to allow back and forth moving from one tab to the other.
    However, No matter how fast the screens are in web, they are a fraction of a second slower when the browser renders the screen.
    This is not controlled by programming and it is the browser that takes time. In such scenario, going for Swing may be a better option
    All of them support the shortcut keys- Going to Web - you may need to forgo some of the function keys - like f5 for refresh.
    You can also introduce numbers in front of values in combos - for easy input of data.
    We have experience in migrating thick client to web and thick client to thick client. Please contact me if you need more info.
    Amit Raj
    [email protected]

  • Bus error in the Forte executable

    Hi,
    We have an environment with forte' (ver. 3.0.G.2) running
    on AIX 4.1 (The name of central server is cld_app1 and the nodemgr start
    with the name cld_TDR). In our environment we are using two differnet
    repository. In rep1 we have a very simple project (called 'aaa') that
    use one small class with two methods. One method print the date & time.
    The second method communicate with a serviceobject that use MQSeries to
    put/get some messages in the queues.
    The project work correctly in test run and in distribuite mode.
    If we export the same project (aaa) and we import in other repository
    (rep2 in the same environment) the project doesn't work. Infact,
    during test run forte' return the following:
    Begin Stack Backtrace
    =========================================================
    =
    Trace caused by a bus error in the Forte executable:
    ftexec Version 3.0.G.2
    IBM RS6000/Aix 4.1
    Forte Application Environment (tm), Forte Runtime Environment (tm),
    Forte Conductor (tm):
    Copyright (c) 1994-1998, Forte Software, Inc. and its licensors.
    US Patent No. 5,457,797
    Forte Express (tm), Forte WebEnterprise (tm):
    Copyright (c) 1995-1998, Forte Software, Inc.
    All Rights Reserved.
    Unpublished rights reserved under the copyright laws of the United
    States.
    Fri Mar 13 16:07:45 1998
    Fault at 25-Mar-1999 10:42:53, pid '2292', node 'cld_app1':
    0xd0b8886c = d0b8886c()
    0xd0b88ae4 = d0b88ae4()
    qqos_StkTrc: Cannot print stack trace.
    Recursive stack trace detected. Exiting.
    If we try to run in partitioning mode, the same error appears when
    forte' "loading partition into server" with the following adding
    message:
    Unable to start the partition aaa_cl0_Part1 on any of nodes to wich
    been assigned. See the remainder of the error stack for more
    information.
    In the "more" informations we have the following:
    SYSTEM ERROR: Unable to start the partition aaa_cl0_Part1 on any of the
    nodes to which it has been assigned. See the remainder of the error
    stack for more
    information.
    Class: qqsp_ResourceException
    Error #: [1602, 593]
    Detected at: qqcf_StandardConfig::LoadRemotePartition at 5
    Last TOOL statement: method overview.StartApplication
    Error Time: Thu Mar 25 09:22:21
    Exception occurred (locally) on partition "Forte_cl0_Client",
    (partitionId
    = 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
    [546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
    application
    "Forte_cl0", pid 20236 on node cld_app1 in environment
    Collaudo_TDR.
    SYSTEM ERROR: Unable to start partition aaa_cl0_Part1 on node cld_TDR.
    Class: qqsp_ErrorDescriptor
    Error #: [1602, 592]
    Detected at: qqcf_StandardConfig::LoadRemotePartition at 3
    Error Time: Thu Mar 25 09:22:21
    Exception occurred (locally) on partition "Forte_cl0_Client",
    (partitionId
    = 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
    [546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
    application
    "Forte_cl0", pid 20236 on node cld_app1 in environment
    Collaudo_TDR.
    SYSTEM ERROR: Lost contact with remote server while trying to load
    partition
    aaa_cl0_Part1. Check server log file for more information about the
    specific
    problem.
    Class: qqsp_ResourceException
    Error #: [1301, 102]
    Detected at: qqem_IPartitionAgent::Startup at 5
    Error Time: Thu Mar 25 09:22:21
    Exception occurred (locally) on partition "Forte_cl0_Client",
    (partitionId
    = 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
    [546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
    application
    "Forte_cl0", pid 20236 on node cld_app1 in environment
    Collaudo_TDR.
    INFORMATION: The connection to the partner was terminated by the
    Communication
    Manager for the reasons below.
    Class: qqsp_DistAccessException
    Detected at: qqdo_PartitionMgr::StopLocation at 1
    Error Time: Thu Mar 25 09:22:20
    Distributed method called: qqrt_ForteExecAgentProxy.LoadPartition!6
    (object name Unnamed) from partition "Forte_Executor",
    (partitionId =
    546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158, taskId =
    [546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158.19]) in application
    "Forte_cl0", pid 20236 on node cld_app1 in environment
    Collaudo_TDR
    Exception occurred (locally) on partition "Forte_cl0_Client",
    (partitionId
    = 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
    [546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
    application
    "Forte_cl0", pid 20236 on node cld_app1 in environment
    Collaudo_TDR.
    INFORMATION: Network partner closed connection. This usually means the
    process at the other end of the wire failed. Please go look there and
    find
    out why.
    Class: qqsp_DistAccessException
    Detected at: qqcm_HoseFSM::ReceivedClose at 2
    Error Time: Thu Mar 25 09:22:20
    Exception occurred (locally) on partition "Forte_cl0_Client",
    (partitionId
    = 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
    [546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
    application
    "Forte_cl0", pid 20236 on node cld_app1 in environment
    Collaudo_TDR.
    INFORMATION: Error parameters for Set:0 Msg:0:
    Class: qqsp_DistAccessException
    Detected at: qqcm_HoseFSM::ReceivedClose at 1
    Error Time: Thu Mar 25 09:22:20
    Exception occurred (locally) on partition "Forte_cl0_Client",
    (partitionId
    = 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
    [546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
    application
    "Forte_cl0", pid 20236 on node cld_app1 in environment
    Collaudo_TDR.
    Thanks in advance
    Luz Marina e Massimiliano
    Get Your Private, Free Email at http://www.hotmail.com
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

    Hi,
    We have an environment with forte' (ver. 3.0.G.2) running
    on AIX 4.1 (The name of central server is cld_app1 and the nodemgr start
    with the name cld_TDR). In our environment we are using two differnet
    repository. In rep1 we have a very simple project (called 'aaa') that
    use one small class with two methods. One method print the date & time.
    The second method communicate with a serviceobject that use MQSeries to
    put/get some messages in the queues.
    The project work correctly in test run and in distribuite mode.
    If we export the same project (aaa) and we import in other repository
    (rep2 in the same environment) the project doesn't work. Infact,
    during test run forte' return the following:
    Begin Stack Backtrace
    =========================================================
    =
    Trace caused by a bus error in the Forte executable:
    ftexec Version 3.0.G.2
    IBM RS6000/Aix 4.1
    Forte Application Environment (tm), Forte Runtime Environment (tm),
    Forte Conductor (tm):
    Copyright (c) 1994-1998, Forte Software, Inc. and its licensors.
    US Patent No. 5,457,797
    Forte Express (tm), Forte WebEnterprise (tm):
    Copyright (c) 1995-1998, Forte Software, Inc.
    All Rights Reserved.
    Unpublished rights reserved under the copyright laws of the United
    States.
    Fri Mar 13 16:07:45 1998
    Fault at 25-Mar-1999 10:42:53, pid '2292', node 'cld_app1':
    0xd0b8886c = d0b8886c()
    0xd0b88ae4 = d0b88ae4()
    qqos_StkTrc: Cannot print stack trace.
    Recursive stack trace detected. Exiting.
    If we try to run in partitioning mode, the same error appears when
    forte' "loading partition into server" with the following adding
    message:
    Unable to start the partition aaa_cl0_Part1 on any of nodes to wich
    been assigned. See the remainder of the error stack for more
    information.
    In the "more" informations we have the following:
    SYSTEM ERROR: Unable to start the partition aaa_cl0_Part1 on any of the
    nodes to which it has been assigned. See the remainder of the error
    stack for more
    information.
    Class: qqsp_ResourceException
    Error #: [1602, 593]
    Detected at: qqcf_StandardConfig::LoadRemotePartition at 5
    Last TOOL statement: method overview.StartApplication
    Error Time: Thu Mar 25 09:22:21
    Exception occurred (locally) on partition "Forte_cl0_Client",
    (partitionId
    = 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
    [546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
    application
    "Forte_cl0", pid 20236 on node cld_app1 in environment
    Collaudo_TDR.
    SYSTEM ERROR: Unable to start partition aaa_cl0_Part1 on node cld_TDR.
    Class: qqsp_ErrorDescriptor
    Error #: [1602, 592]
    Detected at: qqcf_StandardConfig::LoadRemotePartition at 3
    Error Time: Thu Mar 25 09:22:21
    Exception occurred (locally) on partition "Forte_cl0_Client",
    (partitionId
    = 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
    [546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
    application
    "Forte_cl0", pid 20236 on node cld_app1 in environment
    Collaudo_TDR.
    SYSTEM ERROR: Lost contact with remote server while trying to load
    partition
    aaa_cl0_Part1. Check server log file for more information about the
    specific
    problem.
    Class: qqsp_ResourceException
    Error #: [1301, 102]
    Detected at: qqem_IPartitionAgent::Startup at 5
    Error Time: Thu Mar 25 09:22:21
    Exception occurred (locally) on partition "Forte_cl0_Client",
    (partitionId
    = 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
    [546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
    application
    "Forte_cl0", pid 20236 on node cld_app1 in environment
    Collaudo_TDR.
    INFORMATION: The connection to the partner was terminated by the
    Communication
    Manager for the reasons below.
    Class: qqsp_DistAccessException
    Detected at: qqdo_PartitionMgr::StopLocation at 1
    Error Time: Thu Mar 25 09:22:20
    Distributed method called: qqrt_ForteExecAgentProxy.LoadPartition!6
    (object name Unnamed) from partition "Forte_Executor",
    (partitionId =
    546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158, taskId =
    [546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158.19]) in application
    "Forte_cl0", pid 20236 on node cld_app1 in environment
    Collaudo_TDR
    Exception occurred (locally) on partition "Forte_cl0_Client",
    (partitionId
    = 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
    [546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
    application
    "Forte_cl0", pid 20236 on node cld_app1 in environment
    Collaudo_TDR.
    INFORMATION: Network partner closed connection. This usually means the
    process at the other end of the wire failed. Please go look there and
    find
    out why.
    Class: qqsp_DistAccessException
    Detected at: qqcm_HoseFSM::ReceivedClose at 2
    Error Time: Thu Mar 25 09:22:20
    Exception occurred (locally) on partition "Forte_cl0_Client",
    (partitionId
    = 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
    [546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
    application
    "Forte_cl0", pid 20236 on node cld_app1 in environment
    Collaudo_TDR.
    INFORMATION: Error parameters for Set:0 Msg:0:
    Class: qqsp_DistAccessException
    Detected at: qqcm_HoseFSM::ReceivedClose at 1
    Error Time: Thu Mar 25 09:22:20
    Exception occurred (locally) on partition "Forte_cl0_Client",
    (partitionId
    = 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
    [546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
    application
    "Forte_cl0", pid 20236 on node cld_app1 in environment
    Collaudo_TDR.
    Thanks in advance
    Luz Marina e Massimiliano
    Get Your Private, Free Email at http://www.hotmail.com
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

  • Business Graphics and WebEnterprise

    I have a two part question.
    First, what is the best way to create business graphics such as line, bar,
    and point graphs? OLE to Excel, OCX, some third party commercial graphics
    library such as Brahma Software's Beacon?
    Second, once I have a business graphic what is the best way to display these
    graphics on a web page? A number of Forte field widgets such as ellipse,
    polyline, and point do not have a corresponding HTML element and therefore
    the Forte WebEnterprise WindowConverter class cannot convert these windows.
    Is there a way to save Forte images as BMP/JPG images?
    Thanks,
    Douglas Wheeler (mailto:[email protected])
    BORN Information Services, Inc. (http://www.born.com)
    Tel: 612.404.4379 Fax: 621.404.4441
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

    exactly!
    many ways to do this
    1.U can use WDCopyService(Source ,Target)  here Source : return node of model data
                                                                               Target : Your temporary value node which bound to BG.
    Note : Each time when ever model data get updated(CRUD) u have to call this node.
    2. Use Mapping type node and bind it to BG ui element  exe : when we create any node It has 4 options one of them is Mapping select this and provide the model node
      (mapping of node with model node is replica of the content there in model node, here u don't have to worry about updated content since its replica and get changed eveytime when model operations is performed)
    Best Regards
    Satish Kumar

  • JDBC Design Patterns

    Hi All,
    I am new to patterns and have started understanding them using the Head First Series.
    I would like to know what all design patterns are there in JDBC?
    Can i say that JDBC uses a Facade design patterns as it hides the database specific details and provides us a interface which helps us to connect to a database. What other design patterns exist as part of the JDBC?
    Request you to clarify my doubts.
    Many thanks in advance

    I would really appreciate a good discussion on it
    rather than any spoon feeding.
    A typical JDBC code will appear as follows:
    try
    /* Load the jdbc-odbc driver
    Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
    // Open a connection to data source
    con
    =DriverManager.getConnection("jdbc:odbc:DBName","","")
    // Get a statement from the connection
    Statement stmt = conn.createStatement() ;
    // Execute the query
    ResultSet rs = stmt.executeQuery( "select * from
    table_name" ) ;
    1. Is it ok to look into each statement of the above
    code snippet in terms of Design Patterns.it's ok, yes. not necessarily appropriate or worthwhile, though
    2. How can one dissect each line of the code in terms
    of various design patterns?you can't. design patterns exist at a higher level of abstraction than code. 'in terms of' is also disconcertingly vague.
    3. Is it correct to conclude that java.sql package
    overall uses Abstract Factory Pattern.
    As it uses lot of interfaces and implemetation is
    provided by the Vendors. yep. that sounds fair enough. not very useful, though
    4. Consider a particular package like
    java.sql.Statement,java.sql.Blob,java.sql.Connection
    etc. is is correct to conclude that
    its an example of a Factory Method Pattern as any
    client would instantiate. Here the client would be
    Statement object,
    Creator is Connection Interface and createStatement()
    is the factory method.possibly. there's little value in trying to define everything as a "design pattern", though. rather than thinking "oh, they must be using PATTERN X here", think "if I were writing this code, I think PATTERN X would be appropriate". or, more usefully, "is there a pattern that solves this problem?". there isn't, necessarily
    5. I am not able to understand if a statement like
    Class.forName() should be viewed only in terms of a
    programming instruction or
    any design patternit's a line of code, nothing more. stop trying to make everything into a pattern. until you realise where patterns are and aren't applicable, you'll never understand them
    6. Can "stmt.executeQuery()" can be viewed as A
    Strategy Pattern? nope. what makes you think that?
    I would really welcome a good discussion on the above
    questions.does the discussion have to involve design patterns? you know, of course, that design patterns aren't magic beans, right? I know you've just discovered patterns, and are all excited by them, but seriously, they're only ideas, not Infallible Solutions To All Software Problems &#8482;. the most common mistake people make using design patterns is to see them everywhere, and try to bend every problem to fit a particular pattern
    for the record, nobody really views JDBC in terms of patterns. there's little value in viewing existing technologies in those terms, since the most you can "gain" is to have guessed what some other developer did, before.

  • Exciting opportunities for Forte/UDS & J2EE engineers

    ******** EXCITING OPPORTUNITIES *********
    Looking for project managers, Architects, Technical Leads, Programmers with experience in migration from Legacy applications to new platforms. (Migration experience from Forte to Java or Forte to .Net technologies )
    Skills Areas:
    * JAVA expertise
    * FORTE background
    * Familiar with USE CASE format requirements
    * Familiar with UML concepts
    * Service Oriented Architecture (nice to have)
    * Web Services (nice to have)
    * Good Organizational and Analytical skills
    * Good communication skills
    Will pay upto $2000 to $5000 for REFERRALS.
    Pl email me : [email protected]

    Worked for both Forte Software & Sun Micro
    on both Forte 4GL and Java J2EE for several years.
    Was a member of the Forte Training/Consulting group and Sun Java/J2EE training and Enterprise Services group for a few years.
    Certified in teaching/training many Java/J2EE/XML
    and Forte courses, i.e. Forte Dev, Forte Advanced Patterns, Forte WebEnterprise, Forte OOAD.
    Contact: [email protected]
    & [email protected]

  • Making Forte service objects available to VisiBrokerclients

    Hello!
    In the Forte manual, Interfacing with External Systems, there's a section on
    making Forte service objects available to ObjectBroker(DEC). We are using
    VisiBroker as our ORB. Does anyone know if the instructions for
    ObjectBroker can be used? Does anyone have experience making Forte service
    objects visible to VisiBroker clients specifically?
    Thanks in Advance!
    Mark Savory
    GTE Gov. Systems
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

    Hi,
    If you are going to make Forte service objects accessible to the VisiBroker
    CORBA/IIOP clients (C++, or Java clients), read Forte manual called "A Guide to
    WebEnterprise Release 1.0.B (any new release???) of Forte WebEnterprise". You
    may find that all materials beginning from Chapter 14 are useful and helpful.
    I've posted many comments and issues unsolved to Forte forum in this area.
    ObjectBroker is one of ORB products made by BEA, and is the first ORB product on
    the market. It runs on dozens of platforms. In 1997, BEA acquired ObjectBroker
    from Digital (DEC). All ORB products (most established products such as
    VisiBroker for C++ 3.x and VisiBroker for Java 3.x from
    Inprise(Borland/Visigenic), Orbix 3.x for C++ and OrbixWeb for Java 3.x from
    Iona, ObjectBroker and Tuxedo from BEA, JavaIDL from JavaSoft) are made based on
    OMG's CORBA/IIOP specifications. Theoretically, all ORBs products should be
    interoperable.
    Hope this help!
    Shilong Yin
    US West in Denver
    =========================
    Savory, Mark wrote:
    Hello!
    In the Forte manual, Interfacing with External Systems, there's a section on
    making Forte service objects available to ObjectBroker(DEC). We are using
    VisiBroker as our ORB. Does anyone know if the instructions for
    ObjectBroker can be used? Does anyone have experience making Forte service
    objects visible to VisiBroker clients specifically?
    Thanks in Advance!
    Mark Savory
    GTE Gov. Systems
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>-
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

  • 300 MB to 1.2 GB Forte log file automatically created

    General information
    ===================
    -One server: Windows NT 4.0 Server Enterprise Edition (service pack 6a), PC/x86, dual Pentium Pro 200 MHz.
    -Five workstations: Windows NT 4.0 Workstation (service pack 6a), PC/x86.
    -Forte 4GL 3.0.N.0.
    -SQL Server 7.0 (service pack 3), clustered.
    -Forte application partitioned into 1 server process (runs on server) and 1 client process (runs on all workstations).
    Has anyone seen this?...
    Problem description
    ===================
    About once per month, our Forte server partition log file grows to 300+ MB, and then the process crashes. This problem is not reproducible, and I don't yet know if there is any pattern in the sequence of events that leads to the error. All the log files appear to be similar because the traceback shows the same method.
    The error started happening after upgrading from Forte 3.0.G.2 to Forte 3.0.N.0.
    All of the client and server log files have the string "<unknown>" where the Forte environment name normally is. I believe that nodemgr.exe crashes, and usually it cannot be restarted. When the Forte Environment Manager is manually restarted, a Windows NT "Services" error window appears that says - "Could not start the Forte Environment Manager 3.0.N.0 service on \\SERVERA. Error 1067: The process terminated unexpectedly." Rebooting the server always recovers.
    Here is an example of the text extracted from one of the huge Forte log files...
    NOTE:
    -Some of the text lines may be wrapped (in the actual file, none of the lines are wrapped).
    -forte_ex_274.log was 263,119 KB.
    -The string "..." means that many lines are not included.
    -All hex values, except for addresses, have been changed to "0x00000000".
    -Note that "Page:45713 @ 0x02CA4400" is included, but appears to be empty.
    ********** BEGINNING OF FILE **********
    ftexec Forte Version 3.0.N.0
    Windows NT
    Forte Application Environment (tm), Forte Runtime Environment (tm),
    Forte Conductor (tm):
    Copyright (c) 1994-2000, Forte Software, Inc. and its licensors.
    US Patent No. 5,457,797
    Forte Express (tm), Forte WebEnterprise (tm):
    Copyright (c) 1994-2000, Forte Software, Inc.
    All Rights Reserved.
    Unpublished rights reserved under the copyright laws of the United States.
    Wed Oct 11 21:52:48 2000
    Process ID 274
    Attached to manager for node SERVERA.
    Loading partition IBIS_cl0_Part1 built on 23-Aug-2001 07:10:49.
    aud Sun Aug 26 05:45:17 : Loading partition IBIS_cl0_Part1 built on 23-Aug-2001
    07:10:49.
    Attached to manager for node SERVERA.
    ! Interpreter Traceback
    Traceback:
    IbisCommunicationHandler.ReadSocket at offset 268
    # Page 45713 contains Object 0x02CA4408 that has bad SIZE(0)
    # Scanning for value in range 0x2ca4400:0x2ca4410
    # Found 0x2ca4408 at qqin_ActivationRecord+0x28(0x2ca3bb8)
    ! Page:45713 @ 0x02CA4400 { Small Object Mobile  } Current
    # Page 45714 should be marked SPAN.
    # Page 45715 should be marked SPAN.
    # Page 45716 should be marked SPAN.
    # Page 45717 should be marked SPAN.
    # Page 45718 should be marked SPAN.
    # Page 45719 should be marked SPAN.
    # Page 45720 should be marked SPAN.
    # Page 45721 should be marked SPAN.
    # Page 45722 should be marked SPAN.
    # Page 45723 should be marked SPAN.
    # Page 45724 should be marked SPAN.
    # Page 45725 should be marked SPAN.
    # Page 45726 should be marked SPAN.
    # Page 45727 should be marked SPAN.
    # Page 45728 should be marked SPAN.
    # Page 45729 should be marked SPAN.
    # Page 45730 should be marked SPAN.
    # Page 45731 should be marked SPAN.
    # Page 45732 should be marked SPAN.
    # Page 45733 should be marked SPAN.
    # Page 45734 should be marked SPAN.
    # Page 45735 should be marked SPAN.
    # Page 45736 should be marked SPAN.
    # Page 81525 should be marked SPAN.
    # Page 81526 should be marked SPAN.
    # Page 81527 should be marked SPAN.
    # Page 81528 should be marked SPAN.
    # Page 81529 should be marked SPAN.
    # Page 81530 should be marked SPAN.
    # Page 81531 should be marked SPAN.
    # Page 81532 should be marked SPAN.
    # Page 81533 should be marked SPAN.
    # Page 81534 should be marked SPAN.
    # Page 81535 should be marked SPAN.
    ! Page:17536 @ 0x01120000 { Small Object Mobile  } Current
    ! 0x01120000: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120010: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120020: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120030: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120040: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120050: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120060: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120070: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120080: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120090: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011200A0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011200B0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011200C0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011200D0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011200E0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011200F0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120100: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120110: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120120: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120130: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120140: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120150: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120160: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120170: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120180: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120190: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011201A0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011201B0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011201C0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011201D0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011201E0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011201F0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120200: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120210: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120220: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120230: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120240: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120250: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120260: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120270: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120280: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120290: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011202A0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011202B0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011202C0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011202D0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011202E0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011202F0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120300: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120310: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120320: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120330: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120340: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120350: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120360: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120370: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120380: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120390: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011203A0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011203B0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011203C0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011203D0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011203E0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011203F0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! Page:17537 @ 0x01120400 { Small NonObject Mobile  } Current
    ! 0x01120400: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120410: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120420: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120430: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120440: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120450: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120460: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120470: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120480: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120490: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011204A0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011204B0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011204C0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011204D0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011204E0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011204F0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120500: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120510: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120520: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120530: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120540: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120550: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120560: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120570: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120580: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120590: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011205A0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011205B0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011205C0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011205D0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011205E0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011205F0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120600: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120610: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120620: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120630: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120640: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120650: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120660: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120670: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120680: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120690: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011206A0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011206B0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011206C0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011206D0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011206E0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011206F0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120700: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120710: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120720: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120730: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120740: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120750: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120760: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120770: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120780: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120790: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011207A0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011207B0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011207C0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011207D0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011207E0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011207F0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! Page:17538 @ 0x01120800 { Large Object Mobile  } Current
    ! Page:45712 @ 0x02CA4000 { Small NonObject Mobile  } Current
    ! 0x02CA4000: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4010: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4020: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4030: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4040: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4050: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4060: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4070: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4080: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4090: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA40A0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA40B0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA40C0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA40D0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA40E0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA40F0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4100: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4110: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4120: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4130: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4140: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4150: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4160: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4170: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4180: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4190: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA41A0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA41B0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA41C0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA41D0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA41E0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA41F0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4200: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4210: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4220: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4230: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4240: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4250: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4260: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4270: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4280: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4290: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA42A0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA42B0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA42C0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA42D0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA42E0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA42F0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4300: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4310: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4320: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4330: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4340: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4350: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4360: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4370: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4380: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4390: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA43A0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA43B0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA43C0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA43D0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA43E0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA43F0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! Page:45713 @ 0x02CA4400 { Small Object Mobile  } Current
    ! Page:45714 @ 0x02CA4800 { Small Object Mobile  } Current
    ! 0x02CA4800: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4810: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4820: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4830: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4840: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4850: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4860: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4870: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4880: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4890: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA48A0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA48B0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA48C0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA48D0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA48E0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA48F0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4900: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4910: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4920: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4930: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4940: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4950: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4960: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4970: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4980: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4990: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA49A0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA49B0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F030: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F040: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F050: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F060: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F070: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F080: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F090: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F0A0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F0B0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F0C0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F0D0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F0E0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F0F0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F100: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F110: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F120: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F130: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F140: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F150: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F160: 0x00000000 0x00000000 0x00000000 0x00000000
    ********** END OF FILE **********

    This appears to the general output generated when a partition gets a SEGV or AccessViolation type problem. The runtime code always performs a memory check to determine if a possible cause for the problem was a memory corruption. In this case it thinks it found a problem and is attempting to dump information related to the problem. There was a bug in this routine that caused to dump more stuff than was really needed (I believe that this was fixed in 5.0)
    The actual error was someone wrote a 0 on the header of an object that describes the size of the object. Given that this was the first object on the page it could be a problem with someone overrunning the end of an object on the previous page.
    This can either be a runtime problem or an application problem. Its a little hard to tell from this output. The best way to collect more information would be to install MSDEV/Visual Studio on the machine and enable
    JustInTimeDebugging (this is normally enabled for you) and then add the following environment variable
    FORTE_NOHANDLER=yes
    This bypasses the exception handling and causes the MSDEV debugger to start. This should allow you to get a stack trace which will give more clues as to the problem.

  • Existing Forte App to Forte Conductor

    Hi all,
    I would like to ask if anybody has successfully "ported" an existing
    Forte Application (designed and implemented without Forte Conductor)
    to a Forte Conductor Application. If you do have some experience about
    this.... I would like to find out what are the activities involved in
    "porting" the application over to Forte Conductor. Was it an easy task ?
    If not, why?
    What if we are proposing to our customers to build a system without
    Forte conductor first (due to budget limitations) but to implement it
    only one year later. What would your suggestions be regarding this?
    Any help would be greatly appreciated,
    Thanks...
    Regards,
    Steven Wong,
    Distributed Objects Sdn Bhd
    Tel : 603-5310777 ext. 417
    Email : [email protected]
    [email protected]
    [email protected]
    Get Your Private, Free Email at http://www.hotmail.com

    Alexander,
    One thing we had to worry about was coming up with a logon script that
    changes the port used by Forte for each user. This is necessary because
    otherwise all forte requests on the terminal server will run against the
    Launch Server that is running in the account of the FIRST person who happens
    to run your app.
    In each users account script you need to have a line like this with a
    different number for each user:
    set FORTE_FTLAUNCH_PORT=3000
    If you have a large number of users, you could write a global script that all
    users run that gives out the next available port in a range not used in your
    environment.
    Hope this helps!
    Here to help,
    Stephen :-{)
    Stephen Brand
    Xpedior
    stephen.brandxpedior.com
    www.xpedior.com

  • Sun to buy Forte for $540 million

    http://cbs.marketwatch.com/archive/19990823/news/current/frte.htx?source=blq
    /yhoo&dist=yhoo
    PALO ALTO, Calif. (CBS.MW) -- Sun Microsystems said Monday it
    will buy Forte Software for about $540 million in stock in
    a purchase that
    will augment Sun's range of network-computing products.
    Under the pact, each share of Forte (FRTE: news,
    msgs) will be converted into 0.3 shares of Sun
    Micro's common stock (SUNW: news, msgs).
    Based on Sun's Friday closing price, the deal
    represents a 31 percent premium of about $22.275
    per Forte share.
    Forte shares rose 2 1/4 to 19 1/4 while Sun Micro rose 1
    1/4 to 75 1/2 in
    trading before the market opened Monday, according to
    Island, the
    electronic communications network.
    The merger is expected to be completed during
    Sun's fiscal 2000 second quarter, which ends Dec.
    31. If the transaction is completed, Forte will
    operate under its own name as a subsidiary of Sun.
    "Companies across the globe are 'dot-com'-ing
    their businesses at an incredible pace -- by
    extending legacy applications to run across the
    Internet and by creating new applications to run
    across all platforms," Ed Zander, Sun's president
    and chief operating officer, said in a statement.
    Forte software is used for developing applications
    and deploying them throughout a computer
    network. Its Forte Application Environment
    software enables businesses to create, integrate,
    customize, manage and deploy applications across
    multiplatform networks for thousands of users
    simultaneously, according to Hoover's Inc.
    Forte WebEnterprise makes applications available
    via the Web, and Forte Conductor manages work
    flow.
    Kamran Amin
    [email protected]
    (203)-459-7362 or 8-204-7362 - Trumbull

    If you had installed Forte on your machine and try to Sun One in Windoze, you might be aware of some registry conflicts that may arise. Pls. go to the Java Tutorial (Yes the first one) and look on how to install the SDK and all that stuff. Those registry deletions you must do are described there.
    By the way, Linux is much more stable so you might try on your Mandrake and very possibly it will run.
    Finally you may try to download and install the NetBeans IDE which is the base for Forte and Sun One. It misses a couple of Sun One's features but it runs even without an installer. You can download the ZIP version and install it with the instructions in that web site.
    http://www.netbeans.org
    Good luck!

  • RE: Documentation for Forti

    Marcus Wilson wrote:
    Does anyone know of any other documentation that
    has been written for Forte' users? I've just started
    using Forte' and I was wondering if there is a book
    available that may contain sample code, examples,
    etc.I don't know of any such book, but it so happens that a colleague and I are
    hoping to fill that void. Bob Griffin and I, both in Digital's consulting
    organization, are working on a book that will capitalize on our experience on
    several Forti projects, numerous consulting engagements, and lots of teaching.
    We plan to cover the development cycle, from requirements through deployment
    and operation, with lots of specific tie-ins to Forti features, design options
    and abundant examples.
    We hope to have the book ready by mid-year or so, and are working with people
    in Forti Software, Inc. to include them in our review cycle.
    So, watch this space. If any of you think of specific topics that would be
    particularly valuable to you, please let us know and we'll see about including
    them if they aren't already in our plans.
    Tim Quinn ([email protected])
    Digital Equipment Corporation
    Nashua, NH
    (603) 881-0426

    Confirmation of reading: your message -
    Date: 6 Mar 96 14:19
    To: [email protected]
    Subject: Re: Documentation for Forte'
    Was read at 12:40, 9 Mar 96.

  • How do I write a select statement to see if table field is in variable list

    I was wondering if someone knew the best way to write a query to pull back rows where a table field is found in a a variable string.  I'm using Cold Fusion 10 on Microsoft SQL Server.
    The table has a series of fields such as
    carcode          carname
    G                Garage
    C                Carport
    A               Attached
    D               Detached
    And another query pulls back a field that stores as text all the abbreviations that apply
    I want to pull back all the carnames that would match the abbreviations stored in that field.  I thought I could use a contains line but that does not work.  How do I pull back matches against a variable string... I tried an IN statment but that didn't work.
    CFQUERY...
    Select carname from CarTable WHERE CONTAINS (carcode, '#query.carlist#') does not work. 
       select carname from CarTable WHERE CONTAINS(carcode, 'G,A')
    I'm stumped.  The list of abbreviations could be very LOOOONG or short and I just need to translate those abbreviations into the full names by grabbing it from another table.  It isn't just one abbreviation so I can't use LIKE in the one to one sense.
    Thank you so much.

    If you have records with these values,
    G,A
    0
    then your first mistake is that you designed your database poorly.  Storing lists in a single field is essentially stroring unuseable data.  A one to many relationship is better.  If you don't know what that is, I've heard good things about the book, Database Design for Mere Mortals.
    Next, this syntax, #queryname.car_storage#, only returns the first record.  To get all the records, use the valuelist function.
    Next, in sql, if you have a list of strings, each one has to be quoted.  Something like this.
    where myfield in ('a', 'b', 'c')
    The best way to achieve this in ColdFusion is to use the cfqueryparam tag with the list attribute set to yes.

  • Development philosphy PL/SQL vs SQL

    Hi All
    I talked to another fellow developer and both he and me both agrees that our company code base uses too much for loop in the PL/SQL.
    (1)He says if the data is in Oracle already better avoid PL/SQL all together and just use SQL statement.
    Any suggestions on (1)
    This company is really data-sensitive so perhaps in the very beginning they would do it row-by-row because of that.
    And this fellow engineer talks about we can use ON ERROR when in cases like that.
    Anyone can give an example for using this ON ERROR ?
    Or can someone show an re-startable SQL example. For example: when processing 10 million rows and it fails in the middle how we can re-start the process in SQL without re-doing the whole thing?
    -Thanks for all your inputs

    Hi,
    vxwo0owxv wrote:
    Hi All
    I talked to another fellow developer and both he and me both agrees that our company code base uses too much for loop in the PL/SQL.
    (1)He says if the data is in Oracle already better avoid PL/SQL all together and just use SQL statement.
    Any suggestions on (1).Doing things in PL/SQL shat should be done in pure SQL is definitely a common mistake. Let's call this Mistake A.
    Doing things in SQL that should be done in PL/SQL is also a mistake. Let's call it Mistake B. In practice, Mistake B is much less common mistake than Mistake A, but it's a mistake just the same.
    FOR loops are one common way people make Mistake A. SQL was designed for efficiently hanlding sets of rows, for example, executing a query and inserting its result set into a table. A common manifestation of Msitake A is to put the query in a cursor FOR loop, and INSERT the data one row at a time. (Among the mad wags, this is called Slow-by-Slow Priocessing .)
    This company is really data-sensitive so perhaps in the very beginning they would do it row-by-row because of that.What does "data-sensitive" mean?
    Whatever it means, I don't see how it can justify doing soemthing in a slow, error-prone way.
    And this fellow engineer talks about we can use ON ERROR when in cases like that.
    Anyone can give an example for using this ON ERROR ?
    Or can someone show an re-startable SQL example. For example: when processing 10 million rows and it fails in the middle how we can re-start the process in SQL without re-doing the whole thing?ON ERROR is a SQL*Plus mechanism for trapping errors.
    PL/SQL's error handling is better, so this might be an occasion for committing Mistake B. (It would be more accurate to call this Mistake C, since SQL*Plus is not the same as SQL.)
    Within PL/SQL, you can use many of the best features of SQL (for example, a multi-row INSERT rather than a FOR loop), and also take advantage of the good features of PL/SQL (such as EXCEPTION handling).

Maybe you are looking for

  • Why Can't I Install Final Cut Studio?

    I have a MacBook Pro which is about 12 months old. It has a 2.66GHz Intel Core i7 Processor and 8G of RAM. I have been trying to install Final Cut Studio 5.1. Yeah I know that is an OLLLLLLLLLLLD version. Why I chose not to update is neither here nor

  • Why getAbsolutePath() doesn't return path?

    Hi, all: My code: public class Test { public static void main(String args[]) {  File aFile=new File("MustBeThere.doc"); if (aFile.exists()) String path=aFile.getAbsolutePath(); else System.out.println("Null"); It always return "Null". I assume to get

  • Why can't i get iWork for free on my new MBPro

    I recently purchased a new 13" MB Pro and tranfer3ed all my dta from my old MB Pro. However it seems i cant get the new versions Pages, Numbers and Keynote from the Appm store. I mnaged to egt ILife all upgraded without any issues.

  • Vendor material info record

    hi, When am trying to create vendor material info record,i see the<b> valid to</b> is <b>mandatory feild</b> but it is <b>disabled .</b>. i cannot enter any value in that. i:e    In <b>T/C me11</b> after i enter the details in the first screen,click

  • Using ODI send mail tool in procedure

    Hi, I want to use an ODI send mail option in procedure when certain condition is met. for example: I have one table "Dummy_table" as Dummy_table PRODUCTID PRODTYPE PRODCODE 11111 A 11111 22222 A 22222 33333 B 33333 00000 A 00000 And a procedure which