Ann: Super 8.0 with SuperJMX

Acelet has released new version of Super - a toolkit for J2EE. The new module SuperJMS provide capability to visually create JMS message and triggers, which can be exported to SuperScheduler and SuperWatchdog. Now, you do JMS by clicking.
It is free.
It can be anonymously downloaded from: http://www.acelet.com.

you can use the cheesy film damage effect that is built-in to quicktime. but, if you're going for cheese than quality counts and i'll offer up a third voice of complete endorsement for nattress film efx. a hunnert bucks is cheap, CHEAP for this great set of plug-ins and while you're at nattress spending money, also purchase set one as the G Super Levels alone is more than worth the purchase price.
zeb

Similar Messages

  • Helloo! I have super big problem with my Air.

    Helloo! I have super big problem with my Air,10.8.5 ,it asks every 10 sec to make some changes and asks me for password all the time!! I cant acces my documesnt,pics,music,NOTHING at all! Finder is not working,i cant open any folder,icons are missing also,i cant open any of them,mozzila,chrome..im really going crazy.. i updated tonight my phone on new IOS 7 through my comp,cant be that i messed up everything because of that..this comp.is like 10 days old.
    btw. i created new user,and everything is working ok.

    Back up all data. Don't continue unless you're sure you can restore from a backup, even if you're unable to log in.
    This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it.
    Step 1
    If you have more than one user account, and the one in question is not an administrator account, then temporarily promote it to administrator status in the Users & Groups preference pane. To do that, unlock the preference pane using the credentials of an administrator, check the box marked Allow user to administer this computer, then reboot. You can demote the problem account back to standard status when this step has been completed.
    Triple-click the following line on this page to select it. Copy the selected text to the Clipboard (command-C):
    { sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -R $UID:staff ~ $_ ; sudo chmod -R u+rwX ~ $_ ; chmod -R -N ~ $_ ; } 2> /dev/null
    Launch the Terminal application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
    Paste into the Terminal window (command-V). You'll be prompted for your login password. Nothing will be displayed when you type it. You may get a one-time warning to be careful. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
    The command will take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.
    Step 2 (optional)
    Take this step only if you have trouble with Step 1 or if it doesn't solve the problem.
    Boot into Recovery. When the OS X Utilities screen appears, select
    Utilities ▹ Terminal
    from the menu bar. A Terminal window will open.
    In the Terminal window, type this:
    res
    Press the tab key. The partial command you typed will automatically be completed to this:
    resetpassword
    Press return. A Reset Password window will open. You’re not  going to reset a password.
    Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.
    Select your username from the menu labeled Select the user account if not already selected.
    Under Reset Home Directory Permissions and ACLs, click the Reset button.
    Select
     ▹ Restart
    from the menu bar.

  • Ann: Super 2.20 - a suite of J2EE tools

    Announcement: Super 2.20 - a suite of EJB/J2EE monitoring/admin tools with
    SuperEnvironment
    SuperLogging
    SuperPeekPoke
    SuperReport
    SuperScheduler
    SuperStress
    and SuperPatrol, as a schedule job.
    The evaluation edition can be anonymously downloaded from:
    http://www.ACElet.com.
    Super is a component based monitor and administration tool
    for EJB/J2ee. It provides built-in functionality as well as
    extensions, as SuperComponents. Users can install
    SuperComponents onto it, or uninstall them from it.
    Super has the following functions:
    * A J2EE monitor.
    * A gateway to J2EE/EJB servers from different vendors.
    * A framework holding user defined SuperComponents.
    * A full-featured J2EE logging and J2EE tracing tool for centralized,
    chronological logging.
    * An EJB tool for Peeking and Poking attributes from EJBs.
    * An EJB Stress test tool.
    * A J2EE global environment tool.
    * A J2EE report tool.
    * A J2EE Scheduler tool.
    * A J2EE Business patrol tool.
    It is written entirely in the Java(TM) programming language.
    The current version support:
    * JOnAS 2.4 and 2.6
    * SunONE 7.0
    * Universal servers.
    * Weblogic 6.0, 6.1 and 7.0
    * Websphere 4.0
    * jBoss 2.4.4 and 3.0
    ********** What is new:
    Version 2.20 Jan. 2003
    Enhancement:
    1. Add desktop and start menu shortcuts for MS-Windows.
    2. Add support for SunONE 7, JOnAS 2.6 and jBoss 3.0.
    3. SuperLogging 2.40: Add new sendAlarmEmail() method.
    4. SuperScheduler 1.40: Add SuperSchedulerEJB for managing when
    direct database is not practical; Allow user to choose
    favorite logging software; Add Last day as Monthly
    repeating attribute.
    Change:
    1. Change Unusual to PatrolAlarm. The name "Unusual" was misleading.
    Bug fix:
    1. SuperEnvironment 1.31: Bug fix: if database is broken, could not
    open Environment Manager.
    2. SuperLogging client 1.52: Annoying exception thrown when you use
    JDK 1.4 (the program runs okay).
    3. SuperPeekPoke 1.61: Fix bug where input object contains
    java.lang.Double and alike.
    4. SuperScheduler 1.40: Bug fixes in: Memory leak; Reporting
    PatrolAlarm for SuperPatrol; Composite task with members;
    Non-scheduled run on other host; Around edges of last
    days in Monthly with holiday policy.
    Version 2.10 July 2002
    Enhancement:
    1. SuperScheduler 1.3: Add Future View to check future schedule in
    both text and Gantt-chart mode.
    2. SuperScheduler 1.3: Add graphic Gantt view for monitoring task's
    activities.
    3. SuperEnvironment 1.3: uses new graphic package adding print and
    preference facilities.
    4. SuperPeekPoke 1.6: uses new graphic package adding print and
    preference facilities.
    5. SuperStress 1.21: uses new graphic package.
    Bug fix:
    1. SuperStress 1.21: fixed graphic related bugs.
    Version 2.01 June 2002
    Enhancement:
    1. Add options for Look & Feel.
    2. Preference is persistent now.
    Bug fix:
    1. Installation for WebLogic 7.0: extEnv may not be installed on the
    right place, so SuperLibrar on the server side was not loaded and
    causes other problems.
    Version 2.00 June 2002
    Enhancement:
    1. SuperScheduler 1.2: All copies of SuperScheduler refresh themselves
    when any Doer causes things to change.
    2. SuperScheduler 1.2: Support default HTML browser for reading HTML document.
    3. SuperReport 1.2: Support default HTML browser for reading HTML document.
    4. Support WebLogic 7.0.
    5. SuperEnvironment 1.21: Database Panel appears when it is necessary.
    6. SuperEnvironment 1.21: New SuperEnvironment tour.
    Bug fix:
    1. WebSphere Envoy did not always list all JNDI names.
    Version 1.90 May 2002
    Enhancement:
    1. Rewritten SuperLogging engine. Add Alarm Email on SuperLogging.
    2.Rewritten SuperScheduler allowing multiple Doers. Add support to holiday policy,
    effective period. Add Patrol job type as SuperPatrol.
    3. Add support for both JOnAS and jBoss.
    4. Add more elements on Report criteria.
    Change:
    1. Now, both left and right mouse clicks are the same on Table Panel: toggle ascend
    and descend.
    2. New log database.
    Bug fix:
    1. Alert email should be sent once in the interval, regarding number of servers
    in the clustering.
    2. Minor bug fixes to make errors handled better on SuperLogging.
    3. If withFileInfo or withTimestamp are changed alone, Style Panel did not save
    them.
    4. Rewritten SuperLogging and SuperScheduler with many bug fixes.
    Version 1.80 March 2002
    Enhancement:
    1. Add new component: SuperScheduler
    Bug fix:
    1. SuperLogging: Verbose should ignore class registration.
    2. SuperLogging-tracing: an exception was thrown if the java class without package
    name.
    Version 1.70 January 2002
    Enhancement:
    1. SuperLogging: Scope can dynamically change both for upgrade to downgrade (for
    weblogic 6.1, need download an application).
    2. Add alias names for log threshold as new Java suggests.
    3. New component: SuperReport.
    Change:
    1. SuperLogging: Log database parameters are specified in a properties file, instead
    of EJB's deployment descriptor. It is more convenient and it avoids some potential
    problems. No change for development, easier for administration.
    Bug fix:
    1. Add Source Path Panel now accepts both directory and jar file.
    2. Bug in SuperEnvironment example (for version 1.60 only).
    Version 1.60 December 2001
    Enhancement:
    1. SuperPeekPoke and SuperStress can use user defined dynamic argument list.
    2. Add timeout parameter to logging access.
    3. New installation program with A). Easy install. B). Remote command line install.
    4. Support EJB 2.0 for Weblogic 6.1.
    5. Support SuperPeekPoke, SuperEnvironment and SuperStress for Websphere 4.0 (SuperLogging
    was supported since version 1.5).
    Change:
    1. Poke: argument list is set at define time, not invoke time.
    2. Default log database change to server mode from web server mode, booting performance
    to 10-20 times.
    Bug fix:
    1. If the returned object is null, Peek did not handle it correctly.
    2. If the value was too big, TimeSeries chart did not handle it correctly. Now
    it can handle up to 1.0E300.
    3. Help message was difficult to access in installation program.
    4. Source code panel now both highlights and marks the line in question (before
    it was only highlight using JDK 1.2, not JDK 1.3).
    5. Delete an item on PeekPoke and add a new one generated an error.
    Version 1.50 August, 2001
    Enhancement:
    1. Source code level tracing supports EJB, JSP, java helper and other
    programs which are written in native languages (as long as you
    write correct log messages in your application).
    2. Redress supports JSP now.
    3. New installation with full help document: hope it will be easier.
    4. Support WebSphere 4.0
    Version 1.40 June, 2001
    Enhancement:
    1. Add SuperEnvironment which is a Kaleidoscope with TableView, TimeSeriesView
    and PieView for GlobalProperties.
    GlobalProperties is an open source program from Acelet.
    2. SuperPeekPoke adds Kaleidoscope with TableView, TimeSeriesView and PieView.
    Changes:
    1. The structure of log database changed. You need delete old installation and
    install everything new.
    2. The format of time stamp of SuperLogging changed. It is not locale dependent:
    better for report utilities.
    3. Time stamp of SuperLogging added machine name: better for clustering environment.
    Bug fix:
    1. Under JDK 1.3, when you close Trace Panel, the timer may not be stopped and
    Style Panel may not show up.
    Version 1.30 May, 2001
    Enhancement:
    1. Add ConnectionPlugin support.
    2. Add support for Borland AppServer.
    Version 1.20 April, 2001
    Enhancement:
    1. Redress with option to save a backup file
    2. More data validation on Dump Panel.
    3. Add uninstall for Super itself.
    4. Add Log Database Panel for changing the log database parameters.
    5. Register Class: you can type in name or browse on file system.
    6. New tour with new examples.
    Bug fix:
    1. Redress: save file may fail.
    2. Install Bean: some may fail due to missing manifest file. Now, it is treated
    as foreign beans.
    3. Installation: Both installServerSideLibrary and installLogDatabase can be worked
    on the original file, do not need copy to a temporary directory anymore.
    4. PeekPoke: if there is no stub available, JNDI list would be empty for Weblogic5-6.
    Now it pick up all availble ones and give warning messages.
    5. Stress: Launch>Save>Cancel generated a null pointer exception.
    Changes:
    1. installLogDatabase has been changed from .zip file to .jar file.
    2. SuperLogging: If the log database is broken, the log methods will not try to
    access the log database. It is consistent with the document now.
    3. SuperLogging will not read system properties now. You can put log database
    parameters in SuperLoggingEJB's deployment descriptor.
    Version 1.10 Feb., 2001
    Enhancement:
    1. Re-written PeekPoke with Save/Restore functions.
    2. New SuperComponent: SuperStress for stress test.
    3. Set a mark at the highlighted line on<font size=+0> the Source Code
    Panel (as a work-a-round for JDK 1.3).</font>
    4. Add support for WebLogic 6.0
    Bug fix:
    1. Uninstall bean does physically delete the jar file now.
    2. WebLogic51 Envoy may not always list all JNDI names. This is fixed.
    Version 1.00 Oct., 2000
    Enhancement:
    1. Support Universal server (virtual all EJB servers).
    2. Add Lost and Found for JNDI names, in case you need it.
    3. JNDI ComboBox is editable now, so you can PeekPoke not listed JNDI name (mainly
    for Envoys which do not support JNDI list).
    Version 0.90: Sept, 2000
    Enhancement:
    1. PeekPoke supports arbitrary objects (except for Vector, Hashtable
    and alike) as input values.
    2. Reworked help documents.
    Bug fix:
    1. Clicking Cancel button on Pace Panel set 0 to pace. It causes
    further time-out.
    2. MDI related bugs under JDK 1.3.
    Version 0.80: Aug, 2000
    Enhancement:
    1. With full-featured SuperLogging.
    Version 0.72: July, 2000
    Bug fix:
    1. Ignore unknown objects, so Weblogic5.1 can show JNDI list.
    Version 0.71: July, 2000
    Enhancement:
    1. Re-worked peek algorithm, doing better for concurent use.
    2. Add cacellable Wait dialog, showing Super is busy.
    3. Add Stop button on Peek Panel.
    4. Add undeploy example button.
    Bug fix:
    1. Deletion on Peek Panel may cause error under JDK 1.3. Now it works for both
    1.2 and 1.3
    Version 0.70: July, 2000
    Enhancement:
    1. PeekPoke EJBs without programming.
    Bug fix:
    1. Did not show many windows under JDK 1.3. Now it works for both 1.2 and 1.3
    Changes:
    1. All changes are backward compatible, but you may need to recompile monitor
    windows defined by you.
    Version 0.61: June, 2000
    Bug fix:
    1. First time if you choose BUFFER as logging device, message will not show.
    2. Fixed LoggingPanel related bugs.
    Version 0.60: May, 2000
    Enhancement:
    1. Add DATABASE as a logging device for persistent logging message.
    2. Made alertInterval configurable.
    3. Made pace for tracing configurable.
    Bug fix:
    1. Fixed many bugs.
    Version 0.51, 0.52 and 0.53: April, 2000
    Enhancement:
    1. Add support to Weblogic 5.1 (support for Logging/Tracing and
    user defined GUI window, not support for regular monitoring).
    Bug fix:
    1. Context sensitive help is available for most of windows: press F1.
    2. Fix installation related problems.
    Version 0.50: April, 2000
    Enhancement:
    1. Use JavaHelp for help system.
    2. Add shutdown functionality for J2EE.
    3. Add support to Weblogic 4.5 (support for Logging/Tracing and
    user defined GUI window, not support for regular monitoring).
    Bug fix:
    1. Better exception handling for null Application.
    Version 0.40: March, 2000
    Enhancement:
    1.New installation program, solves installation related problems.
    2. Installation deploys AceletSuperApp application.
    3. Add deploy/undeploy facilities.
    4. Add EJB and application lists.
    Change:
    1.SimpleMonitorInterface: now more simple.
    Version 0.30: January, 2000
    Enhancement:
    1. Add realm support to J2EE
    2. Come with installation program: you just install what you want
    the first time you run Super.
    Version 0.20: January, 2000
    Enhancement:
    Add support to J2EE Sun-RI.
    Change:
    1. Replace logging device "file" with "buffer" to be
    compliant to EJB 1.1. Your code do not need to change.
    Version 0.10: December, 1999
    Enhancement:
    1. provide SimpleMonitorInterface, so GUI experience is
    not necessary for developing most monitoring applications.
    2. Sortable table for table based windows by mouse
    click (left or right).
    Version 0.01 November., 1999:
    1. Bug fix: An exception thrown when log file is large.
    2. Enhancement: Add tour section in Help information.
    Version 0.00: October, 1999
    Thanks.

    I get the error message: Server object error &#39;ASP 0177 : 800401f3&#39;  Server.CreateObject Failed  /x-objects-new/dbconnect/DatabaseConnect.inc, line 588  800401f3  and the download url is http://resources.businessobjects.com/labs/cal/quark_platform_1.2.0_133.zip -- should that be 135?

  • Ann: Super 2.10: a J2EE tool

    Announcement: Super 2.10 - an EJB/J2EE monitoring/admin tool with
    SuperEnvironment
    SuperLogging
    SuperPeekPoke
    SuperReport
    SuperScheduler
    SuperStress
    and SuperPatrol, as a schedule job.
    You can anonymously down load evaluation copy from:
    http://www.ACElet.com.
    Super is a component based administration tool for EJB/J2ee.
    It provides built-in functionality as well as
    extensions, as SuperComponents. Users can install
    SuperComponents onto it, or uninstall them from it.
    Super has the following functions:
    * A J2EE monitor.
    * A gateway to J2EE/EJB servers from different vendors.
    * A framework holding user defined SuperComponents.
    * A full-featured J2EE logging and J2EE tracing tool for centralized,
    chronological logging.
    * An EJB tool for Peeking and Poking attributes from EJBs.
    * An EJB Stress test tool.
    * A J2EE global environment tool.
    * A J2EE report tool.
    * A J2EE Scheduler tool.
    * A J2EE Business patrol tool.
    It is written entirely in the Java(TM) programming language.
    The current version support:
    * JOnAS 2.4
    * Universal servers.
    * Weblogic 6.0, 6.1 and 7.0
    * Websphere 4.0
    * jBoss 2.4.4
    ********** What is new:
    Version 2.10 July 2002
    Enhancement:
    1. SuperScheduler 1.3: Add Future View to check future schedule in
    both text and Gantt-chart mode.
    2. SuperScheduler 1.3: Add graphic Gantt view for monitoring task's
    activities.
    3. SuperEnvironment 1.3: uses new graphic package adding print and
    preference facilities.
    4. SuperPeekPoke 1.6: uses new graphic package adding print and
    preference facilities.
    5. SuperStress 1.21: uses new graphic package.
    Bug fix:
    1. SuperStress 1.21: fixed graphic related bugs.
    Version 2.01 June 2002
    Enhancement:
    1. Add options for Look & Feel.
    2. Preference is persistent now.
    Bug fix:
    1. Installation for WebLogic 7.0: extEnv may not be installed on the
    right place, so SuperLibrar on the server side was not loaded and
    causes other problems.
    Version 2.00 June 2002
    Enhancement:
    1. SuperScheduler 1.2: All copies of SuperScheduler refresh themselves
    when any Doer causes things to change.
    2. SuperScheduler 1.2: Support default HTML browser for reading HTML document.
    3. SuperReport 1.2: Support default HTML browser for reading HTML document.
    4. Support WebLogic 7.0.
    5. SuperEnvironment 1.21: Database Panel appears when it is necessary.
    6. SuperEnvironment 1.21: New SuperEnvironment tour.
    Bug fix:
    1. WebSphere Envoy did not always list all JNDI names.
    Version 1.90 May 2002
    Enhancement:
    1. Rewritten SuperLogging engine. Add Alarm Email on SuperLogging.
    2.Rewritten SuperScheduler allowing multiple Doers. Add support to holiday policy,
    effective period. Add Patrol job type as SuperPatrol.
    3. Add support for both JOnAS and jBoss.
    4. Add more elements on Report criteria.
    Change:
    1. Now, both left and right mouse clicks are the same on Table Panel: toggle ascend
    and descend.
    2. New log database.
    Bug fix:
    1. Alert email should be sent once in the interval, regarding number of servers
    in the clustering.
    2. Minor bug fixes to make errors handled better on SuperLogging.
    3. If withFileInfo or withTimestamp are changed alone, Style Panel did not save
    them.
    4. Rewritten SuperLogging and SuperScheduler with many bug fixes.
    Version 1.80 March 2002
    Enhancement:
    1. Add new component: SuperScheduler
    Bug fix:
    1. SuperLogging: Verbose should ignore class registration.
    2. SuperLogging-tracing: an exception was thrown if the java class without package
    name.
    Version 1.70 January 2002
    Enhancement:
    1. SuperLogging: Scope can dynamically change both for upgrade to downgrade (for
    weblogic 6.1, need download an application).
    2. Add alias names for log threshold as new Java suggests.
    3. New component: SuperReport.
    Change:
    1. SuperLogging: Log database parameters are specified in a properties file, instead
    of EJB's deployment descriptor. It is more convenient and it avoids some potential
    problems. No change for development, easier for administration.
    Bug fix:
    1. Add Source Path Panel now accepts both directory and jar file.
    2. Bug in SuperEnvironment example (for version 1.60 only).
    Version 1.60 December 2001
    Enhancement:
    1. SuperPeekPoke and SuperStress can use user defined dynamic argument list.
    2. Add timeout parameter to logging access.
    3. New installation program with A). Easy install. B). Remote command line install.
    4. Support EJB 2.0 for Weblogic 6.1.
    5. Support SuperPeekPoke, SuperEnvironment and SuperStress for Websphere 4.0 (SuperLogging
    was supported since version 1.5).
    Change:
    1. Poke: argument list is set at define time, not invoke time.
    2. Default log database change to server mode from web server mode, booting performance
    to 10-20 times.
    Bug fix:
    1. If the returned object is null, Peek did not handle it correctly.
    2. If the value was too big, TimeSeries chart did not handle it correctly. Now
    it can handle up to 1.0E300.
    3. Help message was difficult to access in installation program.
    4. Source code panel now both highlights and marks the line in question (before
    it was only highlight using JDK 1.2, not JDK 1.3).
    5. Delete an item on PeekPoke and add a new one generated an error.
    Version 1.50 August, 2001
    Enhancement:
    1. Source code level tracing supports EJB, JSP, java helper and other
    programs which are written in native languages (as long as you
    write correct log messages in your application).
    2. Redress supports JSP now.
    3. New installation with full help document: hope it will be easier.
    4. Support WebSphere 4.0
    Version 1.40 June, 2001
    Enhancement:
    1. Add SuperEnvironment which is a Kaleidoscope with TableView, TimeSeriesView
    and PieView for GlobalProperties.
    GlobalProperties is an open source program from Acelet.
    2. SuperPeekPoke adds Kaleidoscope with TableView, TimeSeriesView and PieView.
    Changes:
    1. The structure of log database changed. You need delete old installation and
    install everything new.
    2. The format of time stamp of SuperLogging changed. It is not locale dependent:
    better for report utilities.
    3. Time stamp of SuperLogging added machine name: better for clustering environment.
    Bug fix:
    1. Under JDK 1.3, when you close Trace Panel, the timer may not be stopped and
    Style Panel may not show up.
    Version 1.30 May, 2001
    Enhancement:
    1. Add ConnectionPlugin support.
    2. Add support for Borland AppServer.
    Version 1.20 April, 2001
    Enhancement:
    1. Redress with option to save a backup file
    2. More data validation on Dump Panel.
    3. Add uninstall for Super itself.
    4. Add Log Database Panel for changing the log database parameters.
    5. Register Class: you can type in name or browse on file system.
    6. New tour with new examples.
    Bug fix:
    1. Redress: save file may fail.
    2. Install Bean: some may fail due to missing manifest file. Now, it is treated
    as foreign beans.
    3. Installation: Both installServerSideLibrary and installLogDatabase can be worked
    on the original file, do not need copy to a temporary directory anymore.
    4. PeekPoke: if there is no stub available, JNDI list would be empty for Weblogic5-6.
    Now it pick up all availble ones and give warning messages.
    5. Stress: Launch>Save>Cancel generated a null pointer exception.
    Changes:
    1. installLogDatabase has been changed from .zip file to .jar file.
    2. SuperLogging: If the log database is broken, the log methods will not try to
    access the log database. It is consistent with the document now.
    3. SuperLogging will not read system properties now. You can put log database
    parameters in SuperLoggingEJB's deployment descriptor.
    Version 1.10 Feb., 2001
    Enhancement:
    1. Re-written PeekPoke with Save/Restore functions.
    2. New SuperComponent: SuperStress for stress test.
    3. Set a mark at the highlighted line on<font size=+0> the Source Code
    Panel (as a work-a-round for JDK 1.3).</font>
    4. Add support for WebLogic 6.0
    Bug fix:
    1. Uninstall bean does physically delete the jar file now.
    2. WebLogic51 Envoy may not always list all JNDI names. This is fixed.
    Version 1.00 Oct., 2000
    Enhancement:
    1. Support Universal server (virtual all EJB servers).
    2. Add Lost and Found for JNDI names, in case you need it.
    3. JNDI ComboBox is editable now, so you can PeekPoke not listed JNDI name (mainly
    for Envoys which do not support JNDI list).
    Version 0.90: Sept, 2000
    Enhancement:
    1. PeekPoke supports arbitrary objects (except for Vector, Hashtable
    and alike) as input values.
    2. Reworked help documents.
    Bug fix:
    1. Clicking Cancel button on Pace Panel set 0 to pace. It causes
    further time-out.
    2. MDI related bugs under JDK 1.3.
    Version 0.80: Aug, 2000
    Enhancement:
    1. With full-featured SuperLogging.
    Version 0.72: July, 2000
    Bug fix:
    1. Ignore unknown objects, so Weblogic5.1 can show JNDI list.
    Version 0.71: July, 2000
    Enhancement:
    1. Re-worked peek algorithm, doing better for concurent use.
    2. Add cacellable Wait dialog, showing Super is busy.
    3. Add Stop button on Peek Panel.
    4. Add undeploy example button.
    Bug fix:
    1. Deletion on Peek Panel may cause error under JDK 1.3. Now it works for both
    1.2 and 1.3
    Version 0.70: July, 2000
    Enhancement:
    1. PeekPoke EJBs without programming.
    Bug fix:
    1. Did not show many windows under JDK 1.3. Now it works for both 1.2 and 1.3
    Changes:
    1. All changes are backward compatible, but you may need to recompile monitor
    windows defined by you.
    Version 0.61: June, 2000
    Bug fix:
    1. First time if you choose BUFFER as logging device, message will not show.
    2. Fixed LoggingPanel related bugs.
    Version 0.60: May, 2000
    Enhancement:
    1. Add DATABASE as a logging device for persistent logging message.
    2. Made alertInterval configurable.
    3. Made pace for tracing configurable.
    Bug fix:
    1. Fixed many bugs.
    Version 0.51, 0.52 and 0.53: April, 2000
    Enhancement:
    1. Add support to Weblogic 5.1 (support for Logging/Tracing and
    user defined GUI window, not support for regular monitoring).
    Bug fix:
    1. Context sensitive help is available for most of windows: press F1.
    2. Fix installation related problems.
    Version 0.50: April, 2000
    Enhancement:
    1. Use JavaHelp for help system.
    2. Add shutdown functionality for J2EE.
    3. Add support to Weblogic 4.5 (support for Logging/Tracing and
    user defined GUI window, not support for regular monitoring).
    Bug fix:
    1. Better exception handling for null Application.
    Version 0.40: March, 2000
    Enhancement:
    1.New installation program, solves installation related problems.
    2. Installation deploys AceletSuperApp application.
    3. Add deploy/undeploy facilities.
    4. Add EJB and application lists.
    Change:
    1.SimpleMonitorInterface: now more simple.
    Version 0.30: January, 2000
    Enhancement:
    1. Add realm support to J2EE
    2. Come with installation program: you just install what you want
    the first time you run Super.
    Version 0.20: January, 2000
    Enhancement:
    Add support to J2EE Sun-RI.
    Change:
    1. Replace logging device "file" with "buffer" to be
    compliant to EJB 1.1. Your code do not need to change.
    Version 0.10: December, 1999
    Enhancement:
    1. provide SimpleMonitorInterface, so GUI experience is
    not necessary for developing most monitoring applications.
    2. Sortable table for table based windows by mouse
    click (left or right).
    Version 0.01 November., 1999:
    1. Bug fix: An exception thrown when log file is large.
    2. Enhancement: Add tour section in Help information.
    Version 0.00: October, 1999
    Thanks.

    one more thing: if you are looking at testing a specific feature (file adapter wizard for example), please let us know: we are looking for "champions" for each of the new features. -Edwin

  • Ann: Super 2.0: J2EE tool

    Announcement: Super 2.0 - an EJB/J2EE monitoring/admin tool with
    SuperEnvironment
    SuperLogging
    SuperPeekPoke
    SuperReport
    SuperScheduler
    SuperStress
    ane SuperPatrol, as a schedule job.
    You can anonymously down load evaluation copy from:
    http://www.ACElet.com.
    Super is a component based administration tool for EJB/J2ee.
    It provides built-in functionality as well as
    extensions, as SuperComponents. Users can install
    SuperComponents onto it, or uninstall them from it.
    Super has the following functions:
    * A J2EE monitor.
    * A gateway to J2EE/EJB servers from different vendors.
    * A framework holding user defined SuperComponents.
    * A full-featured J2EE logging and J2EE tracing tool for centralized,
    chronological logging.
    * An EJB tool for Peeking and Poking attributes from EJBs.
    * An EJB Stress test tool.
    * A J2EE global environment tool.
    * A J2EE report tool.
    * A J2EE Scheduler tool.
    * A J2EE Business patrol tool.
    It is written entirely in the Java(TM) programming language.
    The current version support:
    * JOnAS 2.4
    * Universal servers.
    * Weblogic 6.0, 6.1 and 7.0
    * Websphere 4.0
    * jBoss 2.4.4
    What is new:
    Version 2.00 June 2002
    Enhancement:
    1. SuperScheduler 1.2: All copies of SuperScheduler refresh themselves when any Doer
    causes things to change.
    2. SuperScheduler 1.2: Support default HTML browser for reading HTML document.
    3. SuperReport 1.2: Support default HTML browser for reading HTML document.
    4. Support WebLogic 7.0.
    5. SuperEnvironment 1.21: Database Panel appears when it is necessary.
    6. SuperEnvironment 1.21: New SuperEnvironment tour.
    Change:
    Bug fix:
    1. WebSphere Envoy did not always list all JNDI names.
    Version 1.90 May 2002
    Enhancement:
    1. Rewritten SuperLogging engine. Add Alarm Email on SuperLogging.
    2.Rewritten SuperScheduler allowing multiple Doers. Add support to holiday policy,
    effective period. Add Patrol job type as SuperPatrol.
    3. Add support for both JOnAS and jBoss.
    4. Add more elements on Report criteria.
    Change:
    1. Now, both left and right mouse clicks are the same on Table Panel: toggle ascend
    and descend.
    2. New log database.
    Bug fix:
    1. Alert email should be sent once in the interval, regarding number of servers in
    the clustering.
    2. Minor bug fixes to make errors handled better on SuperLogging.
    3. If withFileInfo or withTimestamp are changed alone, Style Panel did not save them.
    4. Rewritten SuperLogging and SuperScheduler with many bug fixes.
    Version 1.80 March 2002
    Enhancement:
    1. Add new component: SuperScheduler
    Bug fix:
    1. SuperLogging: Verbose should ignore class registration.
    2. SuperLogging-tracing: an exception was thrown if the java class without package
    name.
    Version 1.70 January 2002
    Enhancement:
    1. SuperLogging: Scope can dynamically change both for upgrade to downgrade (for
    weblogic 6.1, need download an application).
    2. Add alias names for log threshold as new Java suggests.
    3. New component: SuperReport.
    Change:
    1. SuperLogging: Log database parameters are specified in a properties file, instead
    of EJB's deployment descriptor. It is more convenient and it avoids some potential
    problems. No change for development, easier for administration.
    Bug fix:
    1. Add Source Path Panel now accepts both directory and jar file.
    2. Bug in SuperEnvironment example (for version 1.60 only).
    Version 1.60 December 2001
    Enhancement:
    1. SuperPeekPoke and SuperStress can use user defined dynamic argument list.
    2. Add timeout parameter to logging access.
    3. New installation program with A). Easy install. B). Remote command line install.
    4. Support EJB 2.0 for Weblogic 6.1.
    5. Support SuperPeekPoke, SuperEnvironment and SuperStress for Websphere 4.0 (SuperLogging
    was supported since version 1.5).
    Change:
    1. Poke: argument list is set at define time, not invoke time.
    2. Default log database change to server mode from web server mode, booting performance
    to 10-20 times.
    Bug fix:
    1. If the returned object is null, Peek did not handle it correctly.
    2. If the value was too big, TimeSeries chart did not handle it correctly. Now it
    can handle up to 1.0E300.
    3. Help message was difficult to access in installation program.
    4. Source code panel now both highlights and marks the line in question (before it
    was only highlight using JDK 1.2, not JDK 1.3).
    5. Delete an item on PeekPoke and add a new one generated an error.
    Version 1.50 August, 2001
    Enhancement:
    1. Source code level tracing supports EJB, JSP, java helper and other
    programs which are written in native languages (as long as you
    write correct log messages in your application).
    2. Redress supports JSP now.
    3. New installation with full help document: hope it will be easier.
    4. Support WebSphere 4.0
    Version 1.40 June, 2001
    Enhancement:
    1. Add SuperEnvironment which is a Kaleidoscope with TableView, TimeSeriesView and
    PieView for GlobalProperties.
    GlobalProperties is an open source program from Acelet.
    2. SuperPeekPoke adds Kaleidoscope with TableView, TimeSeriesView and PieView.
    Changes:
    1. The structure of log database changed. You need delete old installation and install
    everything new.
    2. The format of time stamp of SuperLogging changed. It is not locale dependent:
    better for report utilities.
    3. Time stamp of SuperLogging added machine name: better for clustering environment.
    Bug fix:
    1. Under JDK 1.3, when you close Trace Panel, the timer may not be stopped and Style
    Panel may not show up.
    Version 1.30 May, 2001
    Enhancement:
    1. Add ConnectionPlugin support.
    2. Add support for Borland AppServer.
    Version 1.20 April, 2001
    Enhancement:
    1. Redress with option to save a backup file
    2. More data validation on Dump Panel.
    3. Add uninstall for Super itself.
    4. Add Log Database Panel for changing the log database parameters.
    5. Register Class: you can type in name or browse on file system.
    6. New tour with new examples.
    Bug fix:
    1. Redress: save file may fail.
    2. Install Bean: some may fail due to missing manifest file. Now, it is treated as
    foreign beans.
    3. Installation: Both installServerSideLibrary and installLogDatabase can be worked
    on the original file, do not need copy to a temporary directory anymore.
    4. PeekPoke: if there is no stub available, JNDI list would be empty for Weblogic5-6.
    Now it pick up all availble ones and give warning messages.
    5. Stress: Launch>Save>Cancel generated a null pointer exception.
    Changes:
    1. installLogDatabase has been changed from .zip file to .jar file.
    2. SuperLogging: If the log database is broken, the log methods will not try to access
    the log database. It is consistent with the document now.
    3. SuperLogging will not read system properties now. You can put log database parameters
    in SuperLoggingEJB's deployment descriptor.
    Version 1.10 Feb., 2001
    Enhancement:
    1. Re-written PeekPoke with Save/Restore functions.
    2. New SuperComponent: SuperStress for stress test.
    3. Set a mark at the highlighted line on<font size=+0> the Source Code
    Panel (as a work-a-round for JDK 1.3).</font>
    4. Add support for WebLogic 6.0
    Bug fix:
    1. Uninstall bean does physically delete the jar file now.
    2. WebLogic51 Envoy may not always list all JNDI names. This is fixed.
    Version 1.00 Oct., 2000
    Enhancement:
    1. Support Universal server (virtual all EJB servers).
    2. Add Lost and Found for JNDI names, in case you need it.
    3. JNDI ComboBox is editable now, so you can PeekPoke not listed JNDI name (mainly
    for Envoys which do not support JNDI list).
    Version 0.90: Sept, 2000
    Enhancement:
    1. PeekPoke supports arbitrary objects (except for Vector, Hashtable
    and alike) as input values.
    2. Reworked help documents.
    Bug fix:
    1. Clicking Cancel button on Pace Panel set 0 to pace. It causes
    further time-out.
    2. MDI related bugs under JDK 1.3.
    Version 0.80: Aug, 2000
    Enhancement:
    1. With full-featured SuperLogging.
    Version 0.72: July, 2000
    Bug fix:
    1. Ignore unknown objects, so Weblogic5.1 can show JNDI list.
    Version 0.71: July, 2000
    Enhancement:
    1. Re-worked peek algorithm, doing better for concurent use.
    2. Add cacellable Wait dialog, showing Super is busy.
    3. Add Stop button on Peek Panel.
    4. Add undeploy example button.
    Bug fix:
    1. Deletion on Peek Panel may cause error under JDK 1.3. Now it works for both 1.2
    and 1.3
    Version 0.70: July, 2000
    Enhancement:
    1. PeekPoke EJBs without programming.
    Bug fix:
    1. Did not show many windows under JDK 1.3. Now it works for both 1.2 and 1.3
    Changes:
    1. All changes are backward compatible, but you may need to recompile monitor windows
    defined by you.
    Version 0.61: June, 2000
    Bug fix:
    1. First time if you choose BUFFER as logging device, message will not show.
    2. Fixed LoggingPanel related bugs.
    Version 0.60: May, 2000
    Enhancement:
    1. Add DATABASE as a logging device for persistent logging message.
    2. Made alertInterval configurable.
    3. Made pace for tracing configurable.
    Bug fix:
    1. Fixed many bugs.
    Version 0.51, 0.52 and 0.53: April, 2000
    Enhancement:
    1. Add support to Weblogic 5.1 (support for Logging/Tracing and
    user defined GUI window, not support for regular monitoring).
    Bug fix:
    1. Context sensitive help is available for most of windows: press F1.
    2. Fix installation related problems.
    Version 0.50: April, 2000
    Enhancement:
    1. Use JavaHelp for help system.
    2. Add shutdown functionality for J2EE.
    3. Add support to Weblogic 4.5 (support for Logging/Tracing and
    user defined GUI window, not support for regular monitoring).
    Bug fix:
    1. Better exception handling for null Application.
    Version 0.40: March, 2000
    Enhancement:
    1.New installation program, solves installation related problems.
    2. Installation deploys AceletSuperApp application.
    3. Add deploy/undeploy facilities.
    4. Add EJB and application lists.
    Change:
    1.SimpleMonitorInterface: now more simple.
    Version 0.30: January, 2000
    Enhancement:
    1. Add realm support to J2EE
    2. Come with installation program: you just install what you want
    the first time you run Super.
    Version 0.20: January, 2000
    Enhancement:
    Add support to J2EE Sun-RI.
    Change:
    1. Replace logging device "file" with "buffer" to be
    compliant to EJB 1.1. Your code do not need to change.
    Version 0.10: December, 1999
    Enhancement:
    1. provide SimpleMonitorInterface, so GUI experience is
    not necessary for developing most monitoring applications.
    2. Sortable table for table based windows by mouse
    click (left or right).
    Version 0.01 November., 1999:
    1. Bug fix: An exception thrown when log file is large.
    2. Enhancement: Add tour section in Help information.
    Version 0.00: October, 1999
    Thanks.

    Mohit,
    We are discussing this topic in the fourm below. I'm having the same problem so feel free to join our conversation.
    ~Howard
    http://forum.java.sun.com/thread.jsp?forum=13&thread=478054

  • Ann: Super 3.00 - a suite of j2ee tools

    Announcement: Super 3.00 - a suite of EJB/J2EE monitoring/admin tools.
    Acelet is the leader in J2EE tools area. If you google "j2ee tools",
    "j2ee logging", "j2ee scheduler" or alike, you will find Acelet
    is at the top of the result.
    Super 3.00 comes with:
    SuperEnvironment
    SuperLogging
    SuperPeekPoke
    SuperReport
    SuperScheduler
    SuperStress
    and SuperPatrol, as a schedule job.
    The evaluation edition can be anonymously downloaded from:
    http://www.ACElet.com.
    Super is a component based monitor and administration tool
    for EJB/J2ee. It provides built-in functionality as well as
    extensions, as SuperComponents. Users can install
    SuperComponents onto it, or uninstall them from it.
    Super has the following functions:
    * A J2EE monitor.
    * A gateway to J2EE/EJB servers from different vendors.
    * A framework holding user defined SuperComponents.
    * A full-featured J2EE logging and J2EE tracing tool for centralized,
    chronological logging.
    * An EJB tool for Peeking and Poking attributes from EJBs.
    * An EJB Stress test tool.
    * A J2EE global environment tool.
    * A J2EE report tool.
    * A J2EE Scheduler tool.
    * A J2EE Business patrol tool.
    It is written entirely in the Java(TM) programming language.
    The current version support:
    * JOnAS 2.4 and 2.6
    * SunONE 7.0
    * Universal servers.
    * Weblogic 6.1, 7.0 and 8.1
    * Websphere 4.0 and 5.0.1
    * jBoss 3.0 and 3.2
    ********** What is new:
    Version 3.00 July, 2003
    Enhancement:
    1. SuperLoggingLibrary 3.00: New implementation for change scope adding "Smart" scope,
    with enhancements and bug fixes.
    2. SuperLoggingLibrary 3.00: Support mail server which requires user name and password.
    Add MenuTreePanel.
    3. Improved GUI and document.
    4. Add support to WebLogic 8.1.
    Bug fix:
    1. SuperScheduler 2.0: Fix a bug in FutureView for Hourly and Minutely.
    2. SuperScheduler 2.0: Startup should never be reported as missed.
    3. SuperScheduler 2.0: Could not reset job for existing task in some situation.
    Version 2.20 Jan. 2003
    Enhancement:
    1. Add desktop and start menu shortcuts for MS-Windows.
    2. Add support for SunONE 7, JOnAS 2.6 and jBoss 3.0.
    3. SuperLogging 2.40: Add new sendAlarmEmail() method.
    4. SuperScheduler 1.40: Add SuperSchedulerEJB for managing when
    direct database is not practical; Allow user to choose
    favorite logging software; Add Last day as Monthly
    repeating attribute.
    Change:
    1. Change Unusual to PatrolAlarm. The name "Unusual" was misleading.
    Bug fix:
    1. SuperEnvironment 1.31: Bug fix: if database is broken, could not
    open Environment Manager.
    2. SuperLogging client 1.52: Annoying exception thrown when you use
    JDK 1.4 (the program runs okay).
    3. SuperPeekPoke 1.61: Fix bug where input object contains
    java.lang.Double and alike.
    4. SuperScheduler 1.40: Bug fixes in: Memory leak; Reporting
    PatrolAlarm for SuperPatrol; Composite task with members;
    Non-scheduled run on other host; Around edges of last
    days in Monthly with holiday policy.
    Version 2.10 July 2002
    Enhancement:
    1. SuperScheduler 1.3: Add Future View to check future schedule in
    both text and Gantt-chart mode.
    2. SuperScheduler 1.3: Add graphic Gantt view for monitoring task's
    activities.
    3. SuperEnvironment 1.3: uses new graphic package adding print and
    preference facilities.
    4. SuperPeekPoke 1.6: uses new graphic package adding print and
    preference facilities.
    5. SuperStress 1.21: uses new graphic package.
    Bug fix:
    1. SuperStress 1.21: fixed graphic related bugs.
    Version 2.01 June 2002
    Enhancement:
    1. Add options for Look & Feel.
    2. Preference is persistent now.
    Bug fix:
    1. Installation for WebLogic 7.0: extEnv may not be installed on the
    right place, so SuperLibrar on the server side was not loaded and
    causes other problems.
    Version 2.00 June 2002
    Enhancement:
    1. SuperScheduler 1.2: All copies of SuperScheduler refresh themselves
    when any Doer causes things to change.
    2. SuperScheduler 1.2: Support default HTML browser for reading HTML document.
    3. SuperReport 1.2: Support default HTML browser for reading HTML document.
    4. Support WebLogic 7.0.
    5. SuperEnvironment 1.21: Database Panel appears when it is necessary.
    6. SuperEnvironment 1.21: New SuperEnvironment tour.
    Bug fix:
    1. WebSphere Envoy did not always list all JNDI names.
    Version 1.90 May 2002
    Enhancement:
    1. Rewritten SuperLogging engine. Add Alarm Email on SuperLogging.
    2.Rewritten SuperScheduler allowing multiple Doers. Add support to holiday policy, effective period. Add Patrol job type as SuperPatrol.
    3. Add support for both JOnAS and jBoss.
    4. Add more elements on Report criteria.
    Change:
    1. Now, both left and right mouse clicks are the same on Table Panel: toggle ascend and descend.
    2. New log database.
    Bug fix:
    1. Alert email should be sent once in the interval, regarding number of servers in the clustering.
    2. Minor bug fixes to make errors handled better on SuperLogging.
    3. If withFileInfo or withTimestamp are changed alone, Style Panel did not save them.
    4. Rewritten SuperLogging and SuperScheduler with many bug fixes.
    Version 1.80 March 2002
    Enhancement:
    1. Add new component: SuperScheduler
    Bug fix:
    1. SuperLogging: Verbose should ignore class registration.
    2. SuperLogging-tracing: an exception was thrown if the java class without package name.
    Version 1.70 January 2002
    Enhancement:
    1. SuperLogging: Scope can dynamically change both for upgrade to downgrade (for weblogic 6.1, need download an application).
    2. Add alias names for log threshold as new Java suggests.
    3. New component: SuperReport.
    Change:
    1. SuperLogging: Log database parameters are specified in a properties file, instead of EJB's deployment descriptor. It is more convenient and it avoids some potential problems. No change for development, easier for administration.
    Bug fix:
    1. Add Source Path Panel now accepts both directory and jar file.
    2. Bug in SuperEnvironment example (for version 1.60 only).
    Version 1.60 December 2001
    Enhancement:
    1. SuperPeekPoke and SuperStress can use user defined dynamic argument list.
    2. Add timeout parameter to logging access.
    3. New installation program with A). Easy install. B). Remote command line install.
    4. Support EJB 2.0 for Weblogic 6.1.
    5. Support SuperPeekPoke, SuperEnvironment and SuperStress for Websphere 4.0 (SuperLogging was supported since version 1.5).
    Change:
    1. Poke: argument list is set at define time, not invoke time.
    2. Default log database change to server mode from web server mode, booting performance to 10-20 times.
    Bug fix:
    1. If the returned object is null, Peek did not handle it correctly.
    2. If the value was too big, TimeSeries chart did not handle it correctly. Now it can handle up to 1.0E300.
    3. Help message was difficult to access in installation program.
    4. Source code panel now both highlights and marks the line in question (before it was only highlight using JDK 1.2, not JDK 1.3).
    5. Delete an item on PeekPoke and add a new one generated an error.
    Version 1.50 August, 2001
    Enhancement:
    1. Source code level tracing supports EJB, JSP, java helper and other
    programs which are written in native languages (as long as you
    write correct log messages in your application).
    2. Redress supports JSP now.
    3. New installation with full help document: hope it will be easier.
    4. Support WebSphere 4.0
    Version 1.40 June, 2001
    Enhancement:
    1. Add SuperEnvironment which is a Kaleidoscope with TableView, TimeSeriesView and PieView for GlobalProperties.
    GlobalProperties is an open source program from Acelet.
    2. SuperPeekPoke adds Kaleidoscope with TableView, TimeSeriesView and PieView.
    Changes:
    1. The structure of log database changed. You need delete old installation and install everything new.
    2. The format of time stamp of SuperLogging changed. It is not locale dependent: better for report utilities.
    3. Time stamp of SuperLogging added machine name: better for clustering environment.
    Bug fix:
    1. Under JDK 1.3, when you close Trace Panel, the timer may not be stopped and Style Panel may not show up.
    Version 1.30 May, 2001
    Enhancement:
    1. Add ConnectionPlugin support.
    2. Add support for Borland AppServer.
    Version 1.20 April, 2001
    Enhancement:
    1. Redress with option to save a backup file
    2. More data validation on Dump Panel.
    3. Add uninstall for Super itself.
    4. Add Log Database Panel for changing the log database parameters.
    5. Register Class: you can type in name or browse on file system.
    6. New tour with new examples.
    Bug fix:
    1. Redress: save file may fail.
    2. Install Bean: some may fail due to missing manifest file. Now, it is treated as foreign beans.
    3. Installation: Both installServerSideLibrary and installLogDatabase can be worked on the original file, do not need copy to a temporary directory anymore.
    4. PeekPoke: if there is no stub available, JNDI list would be empty for Weblogic5-6. Now it pick up all availble ones and give warning messages.
    5. Stress: Launch>Save>Cancel generated a null pointer exception.
    Changes:
    1. installLogDatabase has been changed from .zip file to .jar file.
    2. SuperLogging: If the log database is broken, the log methods will not try to access the log database. It is consistent with the document now.
    3. SuperLogging will not read system properties now. You can put log database parameters in SuperLoggingEJB's deployment descriptor.
    Version 1.10 Feb., 2001
    Enhancement:
    1. Re-written PeekPoke with Save/Restore functions.
    2. New SuperComponent: SuperStress for stress test.
    3. Set a mark at the highlighted line on<font size=+0> the Source Code
    Panel (as a work-a-round for JDK 1.3).</font>
    4. Add support for WebLogic 6.0
    Bug fix:
    1. Uninstall bean does physically delete the jar file now.
    2. WebLogic51 Envoy may not always list all JNDI names. This is fixed.
    Version 1.00 Oct., 2000
    Enhancement:
    1. Support Universal server (virtual all EJB servers).
    2. Add Lost and Found for JNDI names, in case you need it.
    3. JNDI ComboBox is editable now, so you can PeekPoke not listed JNDI name (mainly for Envoys which do not support JNDI list).
    Version 0.90: Sept, 2000
    Enhancement:
    1. PeekPoke supports arbitrary objects (except for Vector, Hashtable
    and alike) as input values.
    2. Reworked help documents.
    Bug fix:
    1. Clicking Cancel button on Pace Panel set 0 to pace. It causes
    further time-out.
    2. MDI related bugs under JDK 1.3.
    Version 0.80: Aug, 2000
    Enhancement:
    1. With full-featured SuperLogging.
    Version 0.72: July, 2000
    Bug fix:
    1. Ignore unknown objects, so Weblogic5.1 can show JNDI list.
    Version 0.71: July, 2000
    Enhancement:
    1. Re-worked peek algorithm, doing better for concurent use.
    2. Add cacellable Wait dialog, showing Super is busy.
    3. Add Stop button on Peek Panel.
    4. Add undeploy example button.
    Bug fix:
    1. Deletion on Peek Panel may cause error under JDK 1.3. Now it works for both 1.2 and 1.3
    Version 0.70: July, 2000
    Enhancement:
    1. PeekPoke EJBs without programming.
    Bug fix:
    1. Did not show many windows under JDK 1.3. Now it works for both 1.2 and 1.3
    Changes:
    1. All changes are backward compatible, but you may need to recompile monitor windows defined by you.
    Version 0.61: June, 2000
    Bug fix:
    1. First time if you choose BUFFER as logging device, message will not show.
    2. Fixed LoggingPanel related bugs.
    Version 0.60: May, 2000
    Enhancement:
    1. Add DATABASE as a logging device for persistent logging message.
    2. Made alertInterval configurable.
    3. Made pace for tracing configurable.
    Bug fix:
    1. Fixed many bugs.
    Version 0.51, 0.52 and 0.53: April, 2000
    Enhancement:
    1. Add support to Weblogic 5.1 (support for Logging/Tracing and
    user defined GUI window, not support for regular monitoring).
    Bug fix:
    1. Context sensitive help is available for most of windows: press F1.
    2. Fix installation related problems.
    Version 0.50: April, 2000
    Enhancement:
    1. Use JavaHelp for help system.
    2. Add shutdown functionality for J2EE.
    3. Add support to Weblogic 4.5 (support for Logging/Tracing and
    user defined GUI window, not support for regular monitoring).
    Bug fix:
    1. Better exception handling for null Application.
    Version 0.40: March, 2000
    Enhancement:
    1.New installation program, solves installation related problems.
    2. Installation deploys AceletSuperApp application.
    3. Add deploy/undeploy facilities.
    4. Add EJB and application lists.
    Change:
    1.SimpleMonitorInterface: now more simple.
    Version 0.30: January, 2000
    Enhancement:
    1. Add realm support to J2EE
    2. Come with installation program: you just install what you want
    the first time you run Super.
    Version 0.20: January, 2000
    Enhancement:
    Add support to J2EE Sun-RI.
    Change:
    1. Replace logging device "file" with "buffer" to be
    compliant to EJB 1.1. Your code do not need to change.
    Version 0.10: December, 1999
    Enhancement:
    1. provide SimpleMonitorInterface, so GUI experience is
    not necessary for developing most monitoring applications.
    2. Sortable table for table based windows by mouse
    click (left or right).
    Version 0.01 November., 1999:
    1. Bug fix: An exception thrown when log file is large.
    2. Enhancement: Add tour section in Help information.
    Version 0.00: October, 1999
    Thanks.

    i use the adobe creative suite (indesign) for all print
    documentation...i use captivate for online tutorials, but from what
    i'm hearing the captivate team has been disbanded by adobe and
    they've outsourced the 'development' of future releases to india.
    buyer beware.

  • So many problems, Super Slow, inundated with apps I never use, yet they still run, No Contract, Can I do something about this? Or am I destined to be contracted for the rest of my life?

    I just want to own my phone.  I don't like the speed of it after 2 years, if it didn't have so much crap that I never use on it then at least I would know that it is degradation of the hardware and would renew contract and upgrade, but how can I justify that when it is more than likely the system software that is bogging the phone down.  Seriously I have lost all of my photos and videos, numerous times.  Had my 32g sd card wiped (required me to format it after the camera app saved a picture that was corrupt.  Aside from breaking my already broken (removed) phone, what are the downsides?  If I am going to end up renewing either way, why would you not try to salvage the already paid for device?  If verizon is unable to work with me on this should I take my business (customer since 2005, but lost my data plan so not real inclined to stay other than I've had zero problems in that time frame)  I am confused.  I don't want the hassle of having to change carriers, but my fear is that I will not be given an adequate option?  Any light that could be shone down upon this matter would be greatly appreciated.  and sorry, I know this is probably a hot topic (maybe not) but I just want some legit answers and HTC puts the blame square on Verizon.  Thanks
    Edited as required by the Verizon Wireless Terms of Service
    Message was edited by: Admin Moderator

        beenycrocker,
    I can understand having a phone that is in good working condition. I am sorry to hear about the SD card getting formatted. I use my phone as my digital camera now days. Have you tried to perform a factory reset on the device to see if that will help with the speed of the phone?
    Good news! You can always upgrade to a new phone without having to sign a 2 year contact. We do have the great program that is called EDGE. With this program you would get a brand new device at full retail cost of the phone. But those payments are split up into 24 months. Once you have paid off more than 50% of the phone and had the EDGE for longer than 30 days you can trade in that phone and get a brand new device. You can see the full details on that plan here: www.verizonwireless.com/edge Please keep us posted.
    Kevin_R
    Follow us on Twitter @VZWSupport

  • Pages always opens in a super wide window with extra columns

    I work with simple spreadsheets, often with just two or three columns, and usually with just one table that fits easily on a single page.
    In spite of this, when I open files the opened windows are much wider that they were when saved and have additional columns that were not there when last saved. I believe sometimes the columns are wider than they were when last saved.
    How can I stop this from happening?
    Thanks,
    Eric Weir

    EricWeir wrote:
    In spite of this, when I open files the opened windows ... have additional columns that were not there when last saved. I believe sometimes the columns are wider than they were when last saved.
    Hi Eric,
    Your tables are definitely not likely to be growing new columns or wider columns as they sleep unopened. I don't doubt that it looks that way to you, but we need to find something else to blame this on.
    With Numbers, it's best to eliminate all unused rows and columns before working with your data or Saving. Whatever columns or rows you don't need for data or calculations, delete them. Then Save. Otherwise, when you go to print your work, you'll get extra pages with blank cells on them. The Numbers way of doing spreadsheet work is that when you need to do a summary or add some different type of data, don't appropriate some unused cells in your main table, make a new table that fits what you are about to do. This way you don't have a patchwork of occupied and unoccupied cells in an oversize table.
    Hope this help.
    Jerry

  • SUPER strange problem with an old account - passow...

    Ok so here's the story - I created a Skype account years ago - when it all started - must have been 2005-2006 even and I have used it since. I have installed the windows on my PC and Laptop about 2 years ago and the Skype was set to autologin.
    Now I have reinstalled Windows on my laptop and when I needed to login to Skype I couldn't remember my password. When trying to recover it, I found out that my main email address had another Skype account attached to it ( seems I made this one years ago ) - this one I am using to write this message. Now I do also have other 2 email account I occasionally use but it seems that neither of them are registered to skype.
    The crazy thing is I am still logged in on my home PC with the account I need the password to. Also on my iPhone. I suspect it has something to do with the rule of having both letters and numbers - and I have NO IDEA what I could have used ( my usual passwords don't have numbers in ).
    Now comes the fun part - I just found out that from inside the Skype software you can see under Account - what email address is registered to that account. So I logged in home and when entered the Account section - it says : You do not have a registered email address. - so how the hell am I suppose to reset my password if there isn't any email to send the reset code to ?? When tried to enter a new email adreess I am being asked for my password of course
    So bottom line is, I can login on my iPhone ( autologin ) and on my home PC ( autologin ) - but I have NO WAY IN HELL to reset my password because there is NO EMAIL ATTACHED TO IT. How can this be possible ?? I suppose it has something to do that my account was originally created in the old times, when skype had different settings/options. I tried to find if there are any password recovery options - but nothing worked. I can of course prove I am the owner of the account
    My account name in question is : cornholio4ya - WHAT CAN I DO ? I am desperate.

    abybody ??

  • ANN: New layer capabilities with Presentation Asst v3 (TimeSavers add-on)

    The Layer Assistant was recently integrated into the Presentation Assistant (v.3), offering the following capabilities:
    Text/Symbol Layer shortcuts
    Add the specified string, associated with a layer (with control over font, size and color; horizontal/vertical location adjustment)
    Shape Layer shortcuts
    (rectangle, rounded rectangle, shaded rectangle and circle; can control fill/border color, line width)
    -- optionally also create a link that toggles layer visibility
    -- optionally specify that the shape border is visible at all times, regardless of the layer and its visibility
    Image Layer shortcuts
    Include JPEG images as a layer
    (this may also be used to set a non-printing page background tint to reduce screen glare, or for navigation buttons)
    Underline/Strikethrough Layer shortcuts
    Layers can be created from FM content (text / graphics) based on RGB color composition
    (this does not require hypertext markers)
    Layer visibility links/bookmarks:
    (show layer; hide layer, show layer only, toggle layer, show next/previous layer, show all layers, hide all layers)
    Specific layers can be set as initially hidden or as non-printing (through the settings files or through shortcuts)
    Support for transparency of shapes and JPEG images
    Visit http://www.microtype.com/showcasePresentAsst.html for PDFs demonstrating the new capabilities
    [ FrameMaker-to-Acrobat TimeSavers v5.5 required ]
    Shlomo Perets
    MicroType * http://www.microtype.com
    FrameMaker/Acrobat training & consulting * FrameMaker-to-Acrobat TimeSavers/Assistants
    1-hour webinars (free), starting 10am PDT | 1pm EDT | 5pm UTC/GMT:
    Tuesday, August 18: Enhancing PDFs with Form Fields (with FM-to-Acrobat TimeSavers + Form Asst)
    https://student.gototraining.com/register/3420308416844530916
    Thursday, Sept. 10: Liven up your PDFs with FrameMaker-to-Acrobat TimeSavers/Assistants 
    https://student.gototraining.com/register/8019702938678710980

    Thanks gimbal2
    but I am using the standard TopLink JPA provider shipped with Glassfish. The Eclipse code is called from the standard Glassfish v3 setup. The eclipse code below Here is my persistence domain descriptor:
    <?xml version="1.0" encoding="UTF-8"?>
    <persistence xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.0">
    <persistence-unit name="persistence_sbss">
    <provider>oracle.toplink.essentials.ejb.cmp3.EntityManagerFactoryProvider</provider>
    <jta-data-source>sbssJdbcResource</jta-data-source>
    <non-jta-data-source>sbssJdbcResource</non-jta-data-source>
    <properties>
         <property name="toplink.ddl-generation" value="drop-and-create-tables"/>
    <!--      <property name="toplink.ddl-generation" value="create-tables"/> -->
    </properties>
    </persistence-unit>
    </persistence>
    I will try and find the source code though.
    Edited by: FritzSolmsA on Mar 10, 2010 11:45 AMg
    Edited by: FritzSolmsA on Mar 10, 2010 12:40 PM

  • ANN: Spring 1.2 with TopLink Integration Released

    Version 1.2 of the Spring Framework has been released. New in the 1.2 final release is support for TopLink "out of the box". Prior to 1.2, TopLink support was an "add on" that was available on OTN. Now Spring ships with the integration code required to use TopLink as a persistence provider. TopLink 10.1.2 (9.0.4) and 10.1.3 (preview) are supported.
    To get started, try out the Pet Clinic sample app configured to use TopLink.
    NB: Spring doesn't include TopLink; it provides the necessary integration classes. You still need to download both Spring and TopLink.
    - Shaun
    Spring Home page: http://www.springframework.org
    Spring 1.2 Announcement: http://www.springframework.org/node/86

    Version 1.2 of the Spring Framework has been released. New in the 1.2 final release is support for TopLink "out of the box". Prior to 1.2, TopLink support was an "add on" that was available on OTN. Now Spring ships with the integration code required to use TopLink as a persistence provider. TopLink 10.1.2 (9.0.4) and 10.1.3 (preview) are supported.
    To get started, try out the Pet Clinic sample app configured to use TopLink.
    NB: Spring doesn't include TopLink; it provides the necessary integration classes. You still need to download both Spring and TopLink.
    - Shaun
    Spring Home page: http://www.springframework.org
    Spring 1.2 Announcement: http://www.springframework.org/node/86

  • Super-strange problem with display - EFI BIOS missing or corrupted?

    OK, so here's the breakdown.
    When I insert Windows CD/DVD - screen lights up, installation goes, no problems.
    When I insert OS X Install CD - no picture, no go. It "installs in the background without providing any picture to my LCD screen". Zapping, resetting, taking out battery, nothing works. I have three Mac Edition VGA's, all exhibit the same problems so this is absolutely not a VGA problem.
    For example, out of pure misery, I tried installing iAtkos v7. It works. Of course, this has a classic DOS/ISO compatible booting procedure that doesn't require Mac CD/DVD format.
    Please help, run out of ideas.

    OK, so, wrong group but... don't kill me
    We're talking about a early-2008 Mac Pro, two quad-core Xeons at 3.0, 16GB memory, three different VGA's tried (they're not inside at the same time - I bought two more so I can test and check if it's VGA that's the problem, so, only one inside at the time) - 7300GT, and two GT120's. No other hardware inside, nothing connected, no network connection at this time.
    All three VGA's work happily when I put the Win 7 install DVD (Ultimate 64-bit, but I tried with Vista and XP as well and it boots and everything is ok), but as soon as I put Snow Leopard Retail DVD inside (or the original DVD that came with it) - the screen remains blank while computer powers up and never reaches the "gray screen" status. None of the keyboard combinations (Option key, D key, C key, X key - while starting up the computer) - managed to do a thing about it.
    It just seems to me that my previous OS X installation that used to work (the one that was up there when I bought it brand new) - installed some firmware update that screwed up something on the motherboard. That's why I'm saying that it seems as though EFI BIOS on the motherboard is corrupted or something.
    Is there some way to re-flash the bios of this motherboard via bootable cd and/or from Windows? I tried that firmware restore CD, but as it never reaches the grey screen, I can't tell what's going on so - no help on that part.
    Any help would be hugely welcome.

  • ANN: LR/Mogrify integration with Jeffrey Friedl's Plug-ins and LR/Transporters

    Hi all,
    You've been asking for this, and thanks to Jeffrey's hard work it's now possible.
    LR/Mogrify can now be used in tandem with any of Jeffrey's plug-ins and with my own LR/Transporter. Here are the appropriate links :
    http://regex.info/blog/2008-01-15/692
    http://timothyarmes.com/lrmogrify.php
    http://timothyarmes.com/lrtransporter.php
    Regards,
    Tim

    Congratulations, Tim!
    Piglet architecture and your cooperation with Jeffrey so impressed me!
    Now your tools fit to my workflow and work quite well for me.
    (I am using transporter + mogrify piglet for automatic JPG proofs preparation and export to separate folder tree)
    The main problem now (I am on PC) is spawning MOGRIFY.EXE - it is popping up for each image on top of the other windows and take focus, not allowing to do anything on PC until export finished.
    I think it should be the way to use CORE_RL_magick_.dll directly from LUA code.
    If not, spawning MOGRIFY.EXE _minimized_ will help alot.
    Thank you for you geat tool again!
    Grafin

  • Super laggy, problems with disk utility:  ardagent?

    my macbook has been laggy i'd say for about a month now -- super SLOW, lots of rainbow waiting mans going on...
    cpu: user: 4%, system: 2%, Idle: 98%
    right now i'm only running safari and mail and it's uber slow... i don't know what to do. ran disk utility.. here are the results!
    120.03 gb internal sata disk: "Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired."
    then pressed "repair disk permissions" and it told me:
    Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
    then ran disk permissions on my hd and it said:
    Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
    is this what's making is slow? what should i doooo?
    help. PLEASE.

    B.Murph wrote:
    my macbook has been laggy i'd say for about a month now -- super SLOW, lots of rainbow waiting mans going on...
    Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
    is this what's making is slow? what should i doooo?
    No. That's normal. See http://support.apple.com/kb/TS1448
    You may have a hard drive problem. How full is it? OSX needs considerable room to operate; a rule of thumb is 15% free space.
    If that's not it, try running this: [Intel-based Macs: Using Apple Hardware Test|http://support.apple.com/kb/HT1509].
    and/or the (free) Rember, a heavy-duty memory tester, from: http://www.kelleycomputing.net/

  • Super slow wifi with 4th gen Time Capsule

    So, I got my 4th gen 3TB Time Capsule yesterday, hooked it up to my main computer (iMac, mid 2010) with ethernet cable, updated the firmware, and let it sit for it's first back up.
    Today when I was going to properly set up the wifi at home (two room apartment) it seemed to be going well, iPhone and iPad get decent wifi, it just seems that the wifi range in the apartment isn't as good as with my old junky Belkin router, but it manages. But then I started up a PC running Windows 7 (64-bit) and connected to the wifi network, tried to download something off of Steam and hit about 114kb/s as max download rate (but the average speed is just a couple of kb/s, if even that)... Before I downloaded at about 1-1,5mb/s.
    I started Steam through Parallels Desktop on my iMac and tried downloading through there, and had a download rate of about 3mb/s, so I'm blaming it on the wifi.
    I fooled around with the Time Capsules wireless settings, 802.11a/n - 802.11b/g/n / b/g and so forth, with only a decrease in performance, the automatic setting works the "best". I tried giving the 5GHz network it's own name but I dunno, I can't find the network with that name through the PC. But still, as I don't get the same consistent wifi cover in my apartment as with the Belkin router, I'm thinking something is generally messed with the Time Capsules wifi, not just the PC.
    Any ideas, any solutions? It would be greatly appreciated!

    Today I also tried connecting my Playstation 3 to the router, both are in the same room, about 5 meters apart, t'was SLOW And needless to say, with the Belkin router it was much, much faster. For once I'm not blaming Windows on this one.
    Also, ran a speedtest app on my iPhone, it was MUCH faster yesterday with the time capsule (though not satisfactory), today it's about 1/10th of yesterdays slow speed...

Maybe you are looking for