Awt/Swing Problem on Solaris

Not sure if this a JRE question - sorry if it's off topic.
Whenever I try to run any graphic application on my Solaris machine, I get a fatal exception:
"libmawt.so: open failed: No such file or directory".
This happens if I try to execute appletviewer or run a graphic program from the comand line. Applets inside the browser (NS 4.7) do not have this problem.
I have libmawt.so on my system in a couple of places:
$JAVA_HOME/jre/motif12/libmawt.so
$JAVA_HOME/jre/motif21/libmawt.so
but the system can't seem to find the files. Is there some environment variable that must be set???
Using jdk 1.3.1 on Solaris 7 (2.7)
TIA
Pete

Nevermind, I found the answer -- should have searched for previous postings.
"Solved" it by establishing a soft link to one of the existing files:
..jre/lib/sparc/libmawt.so -> ..jre/lib/sparc/motif21/libmawt.so
Pete

Similar Messages

Focus Problem on Solaris with jdk 1.3.1

Hi all,
We are having a focus problem on Solaris. The same code works fine on Windows without any problem.
I am sending the test code and run steps below which you can compile and repeat the problem.
NOTE: When we put a comment on the line "f1.requestFocus();" in TestFocus.java it works OK.
Run Steps :
1. Run TestFocus.class
2. A JFrame appears with 2 text field and a button
3. Try to write something on the text fields. It works OK.
4. Click the button to open a new JFrame
5. A new JFrame opens with a single text field and a button.
6. Click the button to close the second frame
7. You are now on the main JFrame
8. Try to write something on the text fields. It works OK.
9. Repeat the steps 4-7
10. Try to write something on the text fields. You are able to focus and write on the first field. BUT you cannot select or write the second Field!
JAVA SOURCE FILES :
PenHesapListener.java :
public interface PenHesapListener extends java.util.EventListener {
void tamam_actionPerformed(java.util.EventObject newEvent);
void iptal_actionPerformed(java.util.EventObject newEvent);
------PenHesapLisEventMulticaster.java----------------------------------
public class PenHesapLisEventMulticaster extends java.awt.AWTEventMulticaster implements PenHesapListener {
* Constructor to support multicast events.
* @param a java.util.EventListener
* @param b java.util.EventListener
protected PenHesapLisEventMulticaster(java.util.EventListener a, java.util.EventListener b) {
     super(a, b);
* Add new listener to support multicast events.
* @return muhasebe.HesappenListener
* @param a muhasebe.HesappenListener
* @param b muhasebe.HesappenListener
public static PenHesapListener add(PenHesapListener a, PenHesapListener b) {
     return (PenHesapListener)addInternal(a, b);
* Add new listener to support multicast events.
* @return java.util.EventListener
* @param a java.util.EventListener
* @param b java.util.EventListener
protected static java.util.EventListener addInternal(java.util.EventListener a, java.util.EventListener b) {
     if (a == null) return b;
     if (b == null) return a;
     return new PenHesapLisEventMulticaster(a, b);
* @return java.util.EventListener
* @param oldl muhasebe.HesappenListener
protected java.util.EventListener remove(PenHesapListener oldl) {
     if (oldl == a) return b;
     if (oldl == b) return a;
     java.util.EventListener a2 = removeInternal(a, oldl);
     java.util.EventListener b2 = removeInternal(b, oldl);
     if (a2 == a && b2 == b)
          return this;
     return addInternal(a2, b2);
* Remove listener to support multicast events.
* @return muhasebe.HesappenListener
* @param l muhasebe.HesappenListener
* @param oldl muhasebe.HesappenListener
public static PenHesapListener remove(PenHesapListener l, PenHesapListener oldl) {
     if (l == oldl || l == null)
          return null;
     if(l instanceof PenHesapLisEventMulticaster)
          return (PenHesapListener)((PenHesapLisEventMulticaster) l).remove(oldl);
     return l;
public void tamam_actionPerformed(java.util.EventObject newEvent) {
     ((PenHesapListener)a).tamam_actionPerformed(newEvent);
     ((PenHesapListener)b).tamam_actionPerformed(newEvent);
public void iptal_actionPerformed(java.util.EventObject newEvent) {
     ((PenHesapListener)a).iptal_actionPerformed(newEvent);
     ((PenHesapListener)b).iptal_actionPerformed(newEvent);
---------TestFocus2.java-----------------------------------------
import javax.swing.*;
import javax.swing.JOptionPane;
import java.awt.event.WindowAdapter;
import java.awt.event.KeyListener;
import java.awt.event.KeyAdapter;
import java.awt.event.KeyEvent;
import java.awt.event.ActionEvent;
import java.awt.event.WindowEvent;
import java.awt.event.ActionListener;
import java.util.ArrayList;
import java.util.StringTokenizer;
import java.text.SimpleDateFormat;
import java.awt.Dimension;
import java.awt.Toolkit;
import java.awt.Color;
import java.util.Locale;
import java.util.ResourceBundle;
public class TestFocus2 extends JFrame implements ActionListener
     protected transient PenHesapListener PenhListener = null ;
     JTextField f10 = null;
     JButton b10= null ;
     JTextField f1 = new JTextField() ;
     JButton b1 = new JButton() ;
     JFrame f20 = null;
     public TestFocus2()
          getContentPane().setLayout(new BoxLayout(getContentPane(), BoxLayout.Y_AXIS));
          getContentPane().add(f1);
          getContentPane().add(b1);
          pack();
          setVisible(true);
          b1.addActionListener(this);
     public void actionPerformed(ActionEvent e)
          if(e.getSource() == b1)
               fireTamam_actionPerformed(e);
     public void addPenHesapListener(PenHesapListener newListener)
          PenhListener = PenHesapLisEventMulticaster.add(PenhListener, newListener);
          return;
     protected void fireTamam_actionPerformed(java.util.EventObject newEvent) {
          PenhListener.tamam_actionPerformed(newEvent);
          this.setVisible(false);
     protected void fireiptal_actionPerformed(java.util.EventObject newEvent) {
          PenhListener.iptal_actionPerformed(newEvent);
     public static void main(String x[])
          TestFocus2 gen01 = new TestFocus2();
--------TestFocus.java-----------------------------------
import javax.swing.*;
import javax.swing.JOptionPane;
import java.awt.event.WindowAdapter;
import java.awt.event.KeyListener;
import java.awt.event.KeyAdapter;
import java.awt.event.KeyEvent;
import java.awt.event.ActionEvent;
import java.awt.event.WindowEvent;
import java.awt.event.ActionListener;
import java.util.ArrayList;
import java.util.StringTokenizer;
import java.text.SimpleDateFormat;
import java.awt.Dimension;
import java.awt.Toolkit;
import java.awt.Color;
import java.util.Locale;
import java.util.ResourceBundle;
import java.awt.Container;
public class TestFocus extends JFrame implements ActionListener
     PenKreKart aPenKreKart = null ;
     Container ctn = null;
     JTextField f10 = null;
     JButton b10= null ;
     JTextField f1 = new JTextField() ;
     JTextField f2 = new JTextField() ;
     JButton b1 = new JButton() ;
     JFrame f20 = null;
     public TestFocus()
          //aPenKreKart = new PenKreKart(true);
          //aPenKreKart.aTemelPencere.setVisible(false);
          getContentPane().setLayout(new BoxLayout(getContentPane(), BoxLayout.Y_AXIS));
          getContentPane().add(f1);
          getContentPane().add(f2);
          getContentPane().add(b1);
          pack();
          setVisible(true);
          b1.addActionListener(this);
     public void actionPerformed(ActionEvent e)
          if(e.getSource() == b1)
               pencere_islemi();
     // pencere koyma k?sm? .. begin
     public void pencere_islemi() {
          ctn = this;
          ctn.setEnabled(false);
          TestFocus2 fpen = new TestFocus2();
          //aPenKreKart.aTemelPencere.setVisible(true); //buras?
          //aPenKreKart.aTemelPencere.addPenHesapListener(new PenHesapListener() {
          fpen.addPenHesapListener(new PenHesapListener() {
                    // metod      tamam_actionPerformed begin...
                    public void tamam_actionPerformed(java.util.EventObject newEvent) {
                         ctn.setEnabled(true);
                         ctn.requestFocus();
                         // Problem is when we comment the below line it works .....
                         f1.requestFocus();
                         System.out.println("tamam");
                    // metod      tamam_actionPerformed end...
                    // metod      iptal_actionPerformed begin...
                    public void iptal_actionPerformed(java.util.EventObject newEvent) {
                         ctn.setEnabled(true);
                         ctn.requestFocus();
                         System.out.println("iptal");
                    // metod      iptal_actionPerformed begin...
     // pencere koyma k?sm? .. end
     public static void main(String x[])
          TestFocus gen01 = new TestFocus();

Hi all,
We are having a focus problem on Solaris. The same code works fine on Windows without any problem.
I am sending the test code and run steps below which you can compile and repeat the problem.
NOTE: When we put a comment on the line "f1.requestFocus();" in TestFocus.java it works OK.
Run Steps :
1. Run TestFocus.class
2. A JFrame appears with 2 text field and a button
3. Try to write something on the text fields. It works OK.
4. Click the button to open a new JFrame
5. A new JFrame opens with a single text field and a button.
6. Click the button to close the second frame
7. You are now on the main JFrame
8. Try to write something on the text fields. It works OK.
9. Repeat the steps 4-7
10. Try to write something on the text fields. You are able to focus and write on the first field. BUT you cannot select or write the second Field!
JAVA SOURCE FILES :
PenHesapListener.java :
public interface PenHesapListener extends java.util.EventListener {
void tamam_actionPerformed(java.util.EventObject newEvent);
void iptal_actionPerformed(java.util.EventObject newEvent);
------PenHesapLisEventMulticaster.java----------------------------------
public class PenHesapLisEventMulticaster extends java.awt.AWTEventMulticaster implements PenHesapListener {
* Constructor to support multicast events.
* @param a java.util.EventListener
* @param b java.util.EventListener
protected PenHesapLisEventMulticaster(java.util.EventListener a, java.util.EventListener b) {
     super(a, b);
* Add new listener to support multicast events.
* @return muhasebe.HesappenListener
* @param a muhasebe.HesappenListener
* @param b muhasebe.HesappenListener
public static PenHesapListener add(PenHesapListener a, PenHesapListener b) {
     return (PenHesapListener)addInternal(a, b);
* Add new listener to support multicast events.
* @return java.util.EventListener
* @param a java.util.EventListener
* @param b java.util.EventListener
protected static java.util.EventListener addInternal(java.util.EventListener a, java.util.EventListener b) {
     if (a == null) return b;
     if (b == null) return a;
     return new PenHesapLisEventMulticaster(a, b);
* @return java.util.EventListener
* @param oldl muhasebe.HesappenListener
protected java.util.EventListener remove(PenHesapListener oldl) {
     if (oldl == a) return b;
     if (oldl == b) return a;
     java.util.EventListener a2 = removeInternal(a, oldl);
     java.util.EventListener b2 = removeInternal(b, oldl);
     if (a2 == a && b2 == b)
          return this;
     return addInternal(a2, b2);
* Remove listener to support multicast events.
* @return muhasebe.HesappenListener
* @param l muhasebe.HesappenListener
* @param oldl muhasebe.HesappenListener
public static PenHesapListener remove(PenHesapListener l, PenHesapListener oldl) {
     if (l == oldl || l == null)
          return null;
     if(l instanceof PenHesapLisEventMulticaster)
          return (PenHesapListener)((PenHesapLisEventMulticaster) l).remove(oldl);
     return l;
public void tamam_actionPerformed(java.util.EventObject newEvent) {
     ((PenHesapListener)a).tamam_actionPerformed(newEvent);
     ((PenHesapListener)b).tamam_actionPerformed(newEvent);
public void iptal_actionPerformed(java.util.EventObject newEvent) {
     ((PenHesapListener)a).iptal_actionPerformed(newEvent);
     ((PenHesapListener)b).iptal_actionPerformed(newEvent);
---------TestFocus2.java-----------------------------------------
import javax.swing.*;
import javax.swing.JOptionPane;
import java.awt.event.WindowAdapter;
import java.awt.event.KeyListener;
import java.awt.event.KeyAdapter;
import java.awt.event.KeyEvent;
import java.awt.event.ActionEvent;
import java.awt.event.WindowEvent;
import java.awt.event.ActionListener;
import java.util.ArrayList;
import java.util.StringTokenizer;
import java.text.SimpleDateFormat;
import java.awt.Dimension;
import java.awt.Toolkit;
import java.awt.Color;
import java.util.Locale;
import java.util.ResourceBundle;
public class TestFocus2 extends JFrame implements ActionListener
     protected transient PenHesapListener PenhListener = null ;
     JTextField f10 = null;
     JButton b10= null ;
     JTextField f1 = new JTextField() ;
     JButton b1 = new JButton() ;
     JFrame f20 = null;
     public TestFocus2()
          getContentPane().setLayout(new BoxLayout(getContentPane(), BoxLayout.Y_AXIS));
          getContentPane().add(f1);
          getContentPane().add(b1);
          pack();
          setVisible(true);
          b1.addActionListener(this);
     public void actionPerformed(ActionEvent e)
          if(e.getSource() == b1)
               fireTamam_actionPerformed(e);
     public void addPenHesapListener(PenHesapListener newListener)
          PenhListener = PenHesapLisEventMulticaster.add(PenhListener, newListener);
          return;
     protected void fireTamam_actionPerformed(java.util.EventObject newEvent) {
          PenhListener.tamam_actionPerformed(newEvent);
          this.setVisible(false);
     protected void fireiptal_actionPerformed(java.util.EventObject newEvent) {
          PenhListener.iptal_actionPerformed(newEvent);
     public static void main(String x[])
          TestFocus2 gen01 = new TestFocus2();
--------TestFocus.java-----------------------------------
import javax.swing.*;
import javax.swing.JOptionPane;
import java.awt.event.WindowAdapter;
import java.awt.event.KeyListener;
import java.awt.event.KeyAdapter;
import java.awt.event.KeyEvent;
import java.awt.event.ActionEvent;
import java.awt.event.WindowEvent;
import java.awt.event.ActionListener;
import java.util.ArrayList;
import java.util.StringTokenizer;
import java.text.SimpleDateFormat;
import java.awt.Dimension;
import java.awt.Toolkit;
import java.awt.Color;
import java.util.Locale;
import java.util.ResourceBundle;
import java.awt.Container;
public class TestFocus extends JFrame implements ActionListener
     PenKreKart aPenKreKart = null ;
     Container ctn = null;
     JTextField f10 = null;
     JButton b10= null ;
     JTextField f1 = new JTextField() ;
     JTextField f2 = new JTextField() ;
     JButton b1 = new JButton() ;
     JFrame f20 = null;
     public TestFocus()
          //aPenKreKart = new PenKreKart(true);
          //aPenKreKart.aTemelPencere.setVisible(false);
          getContentPane().setLayout(new BoxLayout(getContentPane(), BoxLayout.Y_AXIS));
          getContentPane().add(f1);
          getContentPane().add(f2);
          getContentPane().add(b1);
          pack();
          setVisible(true);
          b1.addActionListener(this);
     public void actionPerformed(ActionEvent e)
          if(e.getSource() == b1)
               pencere_islemi();
     // pencere koyma k?sm? .. begin
     public void pencere_islemi() {
          ctn = this;
          ctn.setEnabled(false);
          TestFocus2 fpen = new TestFocus2();
          //aPenKreKart.aTemelPencere.setVisible(true); //buras?
          //aPenKreKart.aTemelPencere.addPenHesapListener(new PenHesapListener() {
          fpen.addPenHesapListener(new PenHesapListener() {
                    // metod      tamam_actionPerformed begin...
                    public void tamam_actionPerformed(java.util.EventObject newEvent) {
                         ctn.setEnabled(true);
                         ctn.requestFocus();
                         // Problem is when we comment the below line it works .....
                         f1.requestFocus();
                         System.out.println("tamam");
                    // metod      tamam_actionPerformed end...
                    // metod      iptal_actionPerformed begin...
                    public void iptal_actionPerformed(java.util.EventObject newEvent) {
                         ctn.setEnabled(true);
                         ctn.requestFocus();
                         System.out.println("iptal");
                    // metod      iptal_actionPerformed begin...
     // pencere koyma k?sm? .. end
     public static void main(String x[])
          TestFocus gen01 = new TestFocus();

AWT/Swing gui flickering

I am trying to add the swing JDesktopPane to java.awt.Frame .The JDesktopPane includes
JInternalFrame.The problem is that the GUI is flickering when resized or moved.
I migrated from jre1.4 to jre1.5 and the flickering of the JDesktopPane stops but the
JInternalFrame is still flickering when resized/moved.I am wondering if at this point
this is a AWT/Swing issue.

Never ever mix AWT and Swing!At least not their components. :p ;)

A new AWT/Swing?

I have a question for the community.
IMHO, and I am not alone, AWT/Swing have major flaws that really ought to be fixed. Probably, because the APIs themselves are seriously flawed, what is required is a replacement for Swing.
How would one go about proposing such a thing and getting Sun's support?
Specific issues:
1) A set of specific design rules should be codified, which all conforming components, layout managers, UIs, etc., should obey. Along with the rules, there should be automated tests, so that it could be confirmed whether components, layout managers, UIs, etc., work correctly.
Currently, Swing and 3rd party components often do not work well together, for reasons such as
a) Highly irrational behavior of layout managers. Currently, none of the AWT/Swing layout managers behave in a reasonable way under all circumstances, with the possible exception of BorderLayout. Also, layout managers use constraints in inconsistent ways, and they are ill-suited to control by GUI builders.
b) Failure to use minimumSize, preferredSize, and size consistently.
c) Inconsistent use of UIs. What is the division of responsibility between the UI, layout managers, L&F, and the main class(es)?
2) Software design rules. For example, there is currently at least one Swing class that alters its behavior depending on which container it is placed in. That violates basic principles of OO development. Perusing the AWT/Swing source code, you will find plenty of objectional coding practices. It seems that the pressure to maintain backwards compatibility has been a real impediment to "doing things right".
3) Performance. AWT/Swing are notorious for various performance problems, including
a) Non-linear CPU cost associated with building certain graphical data structures (combo-boxes, for one).
b) Layout managers that call getMinimumSize or getPreferredSize on child components multiple times. Currently, the layout managers are the CPU bottleneck in many AWT/Swing GUIs.
c) Some text components are almost unbelievably slow. Try scrolling a lot of text through a JTextArea and you will be disappointed.
d) The current validation logic is extremely complex, inefficient, and undocumented. I count approximately 15 basic API methods that affect how and when components are repainted. I defy ANYONE to explain how it all works. The typical result is that repaints occur FAR more often than is necessary.
A lot of optimization is required to fix these problems. That means automating tests, profiling, removing extra repaints, CPU bottlenecks, etc.
4) Excessive complexity of the APIs. For example, it seems that building practical tables and trees is harder than it should be. The APIs are complex and documentation obscure or lacking in detail. Also, the separation between model and view is often tainted. It shouldn't be necessary to do so much conversion between model and view indices, for example. A basic set of model classes should be shared by all components that use underlying data models. These model classes should support standard functionality such as filtering, sorting, etc.
5) No portable remote operation. Yes, I am familiar with SAWT (slow and buggy), and the possibility of using X11 remotely when the Java application is run on a *nix platform (slow over a high-latency network such as the Internet and unusable on Windows systems). There does not seem to be a usable, universal solution.
Yes, I am familiar with SWT. However, for a variety of reasons, I believe that the AWT approach is superior. SWT is more platform dependent and it has the X11 reverse-object-orientation in which child classes know about their parents. I have done some performance testing, which suggests that
1) SWT layout managers are faster than their corresponding AWT/Swing managers
2) Most other graphics, including 2D graphics, are faster in AWT/Swing than SWT.
I am sure that SWT encapsulates some good ideas. However, it seems that if the efficiency of validation and layouts could be improved, then AWT/Swing performance would be excellent, while maintaining OO and platform-independent characteristics.
Possibly, these issues could be worked out piecemeal. For example, a new, rational set of layout managers could be developed entirely independently.
Other issues, such as defining how UIs, L&F, and component classes should be architected, are going to be more problematic. Creating order in the current chaos will be difficult.
Any ideas?

>
How would one go about proposing such a thing and
getting Sun's support?
As for proposing such a thing, you can always become a member of the Java Community Process Program (it's free for individual members): http://www.jcp.org/en/home/index. As a member you can post a Java Specification Request with your suggestions. If you want to operate on a smaller scale you can report bugs to the bug database.
As for getting Sun's support....well, good luck! :-)

Tutorial on AWT/Swing control flow

Greetings all,
Just wondering if any of you folks know of a good tutorial on AWT/Swing control flow? I'm doing some pretty complex stuff with a table whose editors call other windows and insert values into the table based on callback objects...weird stuff happening with loss of focus when the other windows come out, etc etc etc.
I have it working via a series of what I consider kludges, but I would really like to implement it cleanly, and it's looking like that's going to require understanding <ugh> <grin>
So it looks like it's time that I bit the bullet and got to grips with control flow in AWT/Swing. Is there a tutorial out there that could help me with this?
Many TIA

skiaddict1 wrote:
Let's take your word for it, but if you have the slightest doubt please consider the subject: EDT violation is a classic here.OK sure, but I really don't think I'm violating it. I avoid multi-threading like the plague, and only introduced it for my report writer because I wanted to have a little window advising the user that the report was in the process of being written.Raise your left hand and swear this report writer is not running when you experience the problem you describe! >o(
OK, this is just kidding, as per the rest of your description, it sounds reasonable now to assume that your problem is not related to EDT violation.
I'm doing some pretty complex stuff with a table whose editors call other windows and insert values into the table based on callback objects...This summary is a bit worrying, and I thought you would mention problems in the display of the table being edited. But you seem to refer to problems in other windows, or did I misunderstand?
Or do you mean, loss of focus in the editor still being edited? Can you please clarify what you do and what your problems are?
In particular, what does the other windows come out mean?OK, I was trying to be sparse with details because I didn't think they were relevant.Actually the worrying seems all the more justified, now that you have described it more extensively: I was afraid that you would raise other windows while editing, and that's the case. I know little of focus though...
I have a table in window A, one of whose columns has a custom editor which, when a cell in the column is double-clicked, registers itself with window B as a choice-listener (see later) then asks window B to come to the front. Window B, when the user performs a choice amongst the UI elements in there, fires a choice-event to its listener, i.e. the custom editor. At which point the editor saves away the chosen value (for use by getCellEditorValue()), sets the text in the cell appropriately, turns edit mode off via fireEditStopped(), and brings window A back to the front.
(...) once the custom editor asks window B to come to the front, the table in window A loses focus and when it is brought back to the front, the table's JScrollPane seems to have the focus (visually, it has the focus rectangle around it). Pressing the Tab key has no effect on focus; you have to use the mouse to focus something.I assume you have read the tutorial on using tables in Swing.
It contains an example where a custom editor is bringing up a dialog: http://download.oracle.com/javase/tutorial/uiswing/components/table.html#editor
AFAIK, the example does not suffer from focus problems.
What I am finding, and I reiterate this is new since I rewrote the windowing subsystem for the app (the custom editor was not changed in the rewrite), is that (...)Just what do you call "rewriting the windowing system" (just to rule out the possibility of something Ramboesque)?
I have no idea why this loss of focus is occurring, and I am at a loss to begin to figure it out. As I wrote above, I have a series of kludges which gets around the symptoms, but I would really rather figure it out and fix it.OK I admit I cannot tell what happens exactly, but:
1) instead of bringing window B to front, couldn't the editor bring up a dialog B (e.g. using JOptionPane.showXxxDialog() to bring up just the choice panel? The advantage is that it is more "synchronous", you can control when the window A's table model is updated.
2) what worries me too is that you update the model of the table being edited while you're editing one cell of it? Would it be possible, and make sense in your case, to update this model later (that is, post the model update as an invokeLater(...) call)? I don't see how seeing the table updating underneath helps the user editing its cell, but you may have your reasons.
What do you call flow control , or control flow in AWT/Swing?Basically, what I am after is something that will help me begin to understand/diagnose problems such as the above when they happen in my code. I am deeply averse to multi-threading (...) Things in my code were working, and that was enough for me.
But the above behaviour, and another weird behaviour I was having last week, which again I have solved with what I consider a kludge, and again which only began with my new windowing subsystem, have caused me to realise that it's time I really got to grips with this issue.Yes, when they say beware of threads when using Swing , nobody tells to not use threads! Just to be aware of how special Swing is with regards to threads (at least, compared to AWT, that didn't make such warning).
I would like, for example, to really deep-down understand exactly when listeners for AWT-Swing events get called. I don't really care so much when the events get put on the queue, but I do care when exactly my event handlers will be called. This will help me diagnose problems, I'm sure.Well they get called in the EDT, by some framework code that, in an infinite loop, does something along the lines of:
- pop next event from the event queue
- determine which is the target widget
- let the widget transform the event and send it to all registered listeners
Now with dialogs, things gets dimmer, because while a dialog is brought up (via a<tt>setVisible(true)</TT> call on the EDT, the EDT is indeed suspended, and a new event thread manages the events for the dialog).
I'm sorry I have no reference for that behavior, and my description is certainly blurry (and possibly wrong), but I don't think your problem is so much related to threading as I initially thought.
N.B.: Darryl's second link does features sequence diagrams that try to demonstrate what happen (in a specific example with asynchronous access, but you can derive the simpler, regular, working, from it).OK, yes I saw that diagram, I was offput by the asynchronicity but I will have another look tomorrow also. Thanks againDon't put too much hopes in there, indeed it's definitely not the kind of info I understand you're looking after.
Much luck all the same, and feel free to come back with your findings, or with more questions, about the initial subject (reference on event flow) and the specific problem (your focus issues with the editor).
I also cannot end this message without suggesting that you try to reproduce the problem with an SSCCE (http://sscce.org), that you could post here for us to try out. See this recent discussion about the multiple interests of this approach: {message:id=9587964}
Best regards,
J.

Content Server 6.0 Installation problem on Solaris

When I installed Content_Server_6.0_SP1_solaris_oracle on Solaris 10 ,I get the following error in log file.
dbg Bundled JRE is not binary compatible with host OS/Arch or it is corrupt. Testing bundled JRE failed.
How can I resolve it
please help me.
Regards
Sandeep

If I installed any installer for sparc Machine on x86.is there any problem.My Solaris machine is x86.
thanx.
Regards
Sandeep.

Metainit/striping problem on Solaris 9

We are trying to deploy the Apple XServe RAIDS to customers running Solaris 9. The issue is that Solaris 9 will not recognize a device/LUN that is > 2TB. (No problem with Solaris 10) In trying to solve this problem, we sliced a 7 disk (4.09 TB) RAID into 3 slices. This presents three 1.36TB disks to the Solaris system. Basically, we have 6 disks being presented across both controllers to Solaris. They are direct connected from the XServe to a dual port QLogic HBA. The problem comes in when you try to create a stripe/concatenation across the logical devices being presented. (The disks are being presented on C4 and C5)
Results from a format AFTER I split both 7 disk RAID5s into 3 slices.
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@1c,600000/scsi@2/sd@0,0
1. c1t1d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@1c,600000/scsi@2/sd@1,0
2. c1t2d0 <SEAGATE-ST373307LSUN72G-0507 cyl 14087 alt 2 hd 24 sec 424>
/pci@1c,600000/scsi@2/sd@2,0
3. c1t3d0 <SEAGATE-ST373307LSUN72G-0507 cyl 14087 alt 2 hd 24 sec 424>
/pci@1c,600000/scsi@2/sd@3,0
4. c4t600039300001F461d0 <APPLE Xserve RAID 1.51 aea84000>
/pci@1e,600000/SUNW,qlc@3/fp@0,0/ssd@w600039300001f461,0
5. c4t600039300001F461d1 <APPLE Xserve RAID 1.51 aea84000>
/pci@1e,600000/SUNW,qlc@3/fp@0,0/ssd@w600039300001f461,1
6. c4t600039300001F461d2 <APPLE Xserve RAID 1.51 aea84000>
/pci@1e,600000/SUNW,qlc@3/fp@0,0/ssd@w600039300001f461,2
7. c5t600039300001F2ECd0 <APPLE Xserve RAID 1.51 aea84000>
/pci@1e,600000/SUNW,qlc@3,1/fp@0,0/ssd@w600039300001f2ec,0
8. c5t600039300001F2ECd1 <APPLE Xserve RAID 1.51 aea84000>
/pci@1e,600000/SUNW,qlc@3,1/fp@0,0/ssd@w600039300001f2ec,1
9. c5t600039300001F2ECd2 <APPLE Xserve RAID 1.51 aea84000>
/pci@1e,600000/SUNW,qlc@3,1/fp@0,0/ssd@w600039300001f2ec,2
Specify disk (enter its number):
Results of the cfgadm command. You will see there three logical devices presented to each controller. Six disks.
cfgadm -al -o showFCPdev
Ap_Id Type Receptacle Occupant Condition
c4 fc-private connected configured unknown
c4::600039300001f461,0 disk connected configured unknown
c4::600039300001f461,1 disk connected configured unknown
c4::600039300001f461,2 disk connected configured unknown
c5 fc-private connected configured unknown
c5::600039300001f2ec,0 disk connected configured unknown
c5::600039300001f2ec,1 disk connected configured unknown
c5::600039300001f2ec,2 disk connected configured unknown
Trying to initialize a 6 device stripe via Solaris Volume Manager (AKA disksuite)
metainit -f d77 6 1 c4t600039300001F461d0s0 1 c4t600039300001F461d1s0 1 c4t600039300001F461d2s0 1 c5t600039300001F2ECd0s0 1 c5t600039300001F2ECd1s0 1 c5t600039300001F2ECd2s0
I receive the following error:
metainit: hostname: c4t600039300001F461d1s0: overlaps with device in d77
I tried to do a work around where I create three striped devices then concatenate them:
Creating the first 2 device stripe across controllers c4 and c5 (1 device each)
metainit -f d77 2 1 c4t600039300001F461d0s0 1 c5t600039300001F2ECd0s0
I was able to create the first metadevice d77 using one logical LUN from each controller.
When I tried to create a second metadevice across the controllers: (Using d1 from each controller)
metainit -f d78 2 1 c4t600039300001F461d1s0 1 c5t600039300001F2ECd1s0
metainit: hostneme: c4t600039300001F461d1s0: overlaps with device in d77
I received the same error.
In doing some reaearch, it seems the problem is due to a problem with the disk duplication process, disk device IDs stored on the disks are not unique. I was curious if this is the problem that Apple presents the split disks with the SAME diskid? Has anybody else successfully created stripes (due to a LUN size limit) across the disk successfully on a Solaris system?

I contacted Sun and here is an explination from them. I also noticed when I queried the Xserver RAIDS, there were no serial numbers.
Solaris 9 can support a 16Tb filesystem, but there is a scsi limitation on the device of 2Tb. So you are stuck with striping together several smaller devices if you want a single filesystem above 2Tb.
The problem you are having when metainit reports an overlap comes from the way Solaris Volume Manager identifies devices. The portion of the scsi inquiry that is returned is always unique when Sun firmware is involved, but in your case is not unique.
You may be able to make use of the appended infodoc to avoid this problem. I see no evidence of our having tested this with your particular scenario, but it has been successful in similar cases.
You might also inquire of whoever supports your storage device whether a mode is supported whereby the device's inquiry strings can be made unique.
Here is the steps he wanted me to take and the results. I still can not get the Xserve RAIDS to generate a unique device id:
Step 1
Determine the vendor and product strings. You can run these commands:
# netstat -k | grep -i vendor
# netstat -k | grep -i product
netstat -k | grep -i vendor
Soft Errors 2 Hard Errors 0 Transport Errors 0 Vendor APPLE
Soft Errors 2 Hard Errors 0 Transport Errors 0 Vendor APPLE
Soft Errors 2 Hard Errors 0 Transport Errors 0 Vendor APPLE
Soft Errors 2 Hard Errors 0 Transport Errors 0 Vendor APPLE
Soft Errors 2 Hard Errors 0 Transport Errors 0 Vendor APPLE
grep -i product
Product Xserve RAID Revision Revision 1.51 Serial No Size 1500294152192 Media Error 0 Device Not Ready 0
Product Xserve RAID Revision Revision 1.51 Serial No Size 1500294152192 Media Error 0 Device Not Ready 0
Product Xserve RAID Revision Revision 1.51 Serial No Size 1500294152192 Media Error 0 Device Not Ready 0
Product Xserve RAID Revision Revision 1.51 Serial No Size 1500294152192 Media Error 0 Device Not Ready 0
Product Xserve RAID Revision Revision 1.51 Serial No Size 1500294152192 Media Error 0 Device Not Ready 0
or you can run
# format -e
then select scsi, then inquiry.
scsi> inq
Inquiry:
00 00 05 12 5b 00 00 02 41 50 50 4c 45 20 20 20 ....[...APPLE
58 73 65 72 76 65 20 52 41 49 44 20 20 20 20 20 Xserve RAID
31 2e 35 31 63 00 00 00 00 00 00 00 00 00 00 00 1.51c...........
00 00 00 00 00 00 00 00 00 00 0d 40 0d a0 0e 20 ...........@...
0d 80 09 00 0a 00 00 20 00 00 00 20 20 20 20 20 ....... ...
20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
Vendor: APPLE
Product: Xserve RAID
Revision: 1.51
Removable media: no
Device type: 0
ISO version: 0
ECMA version: 0
ANSI version: 5
Async event notification: no
Terminate i/o process msg: no
Response data format: 2
Additional length: 91
Relative addressing: no
32 bit transfers: no
16 bit transfers: no
Synchronous transfers: no
Linked commands: no
Command queueing: yes
Soft reset option: no
Step 2
Add an entry in the file '/kernel/drv/sd.conf'.
sd-config-list=
"APPLE Xserve RAID ", "AppleRAID";
AppleRAID=1,0x8,0,0,0,0,0;
Step 3 Reboot.
Step 4 Check with SUNWexplo.
[email protected]:[/opt/SUNWexplo/bin] (8)# ./diskinfo.sparc
/dev/rdsk/c0t0d0s2: Device busy
AVAILABLE SCSI DEVICES:
Location Vendor Product Rev Serial #
c1t0d0 COMPAQ BD036863AC HPB5 B2FT4HMM
c1t1d0 SEAGATE ST336607LSUN36G 0507 0349A66VKQ
c1t2d0 SEAGATE ST373307LSUN72G 0507 0417B7C9ZC
c1t3d0 SEAGATE ST373307LSUN72G 0507 0425B7LV5Q
c4t600039300001F461d0 APPLE Xserve RAID 151 c
c4t600039300001F461d1 APPLE Xserve RAID 151 c
c4t600039300001F461d2 APPLE Xserve RAID 151 c
c5t600039300001F2ECd0 APPLE Xserve RAID 151 c
c5t600039300001F2ECd1 APPLE Xserve RAID 151 c
As you will notice, there are no serial numbers in this command or netstat -k | grep -i product commands.

Awt swing 1.1

Hi,
Where can I actually download AWT swing 1.1 package to run with jdk 1.1.?

http://java.sun.com/products/archive/jfc/1.1.1/index.html

Rsh disconnect problems in Solaris 10

My company uses rsh to transmit data to proprietary cards, from Ultra 25's running Solaris 10. We're experiencing random timeouts. The error is rsh connection timeout.
We never had this problem on Solaris 8 or Solaris 7.
Has anyone run across this before? It's to random to run snoop on. Thanks Mark

type passwd mgcusr as root. then you'll need to type new password for that user.

Help! swing problem

i keep getting the error: boxlayout can't be shared...
what's the problem?
Part of My code:
JPanel CatSubPanel = new JPanel() {
            public Dimension getMinimumSize() {
                return getPreferredSize();
            public Dimension getPreferredSize() {
                return new Dimension(400, super.getPreferredSize().height);
            public Dimension getMaximumSize() {
                return getPreferredSize();
CatSubPanel.setLayout(new BoxLayout(CatSubPanel, BoxLayout.X_AXIS));
if (MULTICOLORED) {
            CatSubPanel.setOpaque(true);
            CatSubPanel.setBackground(new Color(0, 0, 255));
        CatSubPanel.setBorder(BorderFactory.createEmptyBorder(0,1,10,5));
      CatSubPanel.add(anotherNewPanel);

help! swing problemI don't think so.
I just mentioned there is a Swing forum for posting Swing related questions.
I also gave you a link to a tutorial on How to Use Box Layout.

[b]the swing problem!,help me[/b]

the code:
JScrollPane p = new JScrollPane(JScrollPane.VERTICAL_SCROLLBAR_AS_NEEDED, JScrollPane.HORIZONTAL_SCROLLBAR_AS_NEEDED);
ImageIcon icon = new ImageIcon(getClass().getResource("images/275.tif"));
JLabel l = new JLabel(icon);
p.setViewportView(l);
this.getContentPane().add(p);
this.pack();
this.setSize(300,300);
this.setVisible(true);
question: I con't see the picture ,why? is the .tif format problem

the swing problem!,help meIf you know its a Swing problem then you should be posting in the "Swing forum".
You said it works for .jpg images, so the JDK may not support .tif images.

Problems with Solaris 11 11/11

Hi,
I need your help because I have problems with Solaris 11 11/11 installed in a Dell Latitude E4310.
Here, there are the problems:
1- No it power off with shutdown or init 5 or init 0 only work well the reboot.
2- It can not connect to the wifi with wpa, no receive ip by dhcp, the driver of the card is "iwp"
Thanks.
Jorge
Edited by: jdangelo on Nov 16, 2011 1:49 PM
Edited by: jdangelo on Nov 17, 2011 2:51 PM

Here is the info of my laptop;
Manufacture name:Dell Inc.
Manufacture model:Latitude E4310
64 Bit:True
OS version:SunOS solaris 5.11 11.0 i86pc i386 i86pc
CPU Type:Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz
CPU Number:1
Number Of Cores Per Processor:2
Number Of Threads Per Processor:4
Bios/Firmware Maker:Dell Inc. Version:A05 Release Date:11/20/2010
prtconf -pv:
System Configuration: Oracle Corporation i86pc
Memory size: 3958 Megabytes
System Peripherals (PROM Nodes):
Node 0x000001
bios-boot-device: '80'
stdout: 00000000
name: 'i86pc'
Node 0x000002
existing: 00c21000.00000000.02bc6001.00000000
name: 'ramdisk'
Node 0x000003
acpi-namespace: '\_SB_.PCI0'
compatible: 'pciex_root_complex'
device_type: 'pciex'
reg: 00000000.00000000.00000000.00000000.00000000
#size-cells: 00000002
#address-cells: 00000003
name: 'pci'
Node 0x000004
reg: 00000000.00000000.00000000.00000000.00000000
compatible: 'pci8086,44.1028.410.2' + 'pci8086,44.1028.410' + 'pci1028,410' + 'pci8086,44.2' + 'pci8086,44' + 'pciclass,060000' + 'pciclass,0600'
model: 'Host bridge'
power-consumption: 00000001.00000001
fast-back-to-back:
devsel-speed: 00000000
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 00000410
unit-address: '0'
class-code: 00060000
revision-id: 00000002
vendor-id: 00008086
device-id: 00000044
name: 'pci1028,410'
Node 0x000005
acpi-namespace: '\_SB_.PCI0.VID_'
assigned-addresses: 83001010.00000000.f0000000.00000000.00400000.c3001018.00000000.e0000000.00000000.10000000.81001020.00000000.000060b0.00000000.00000008.a1001000.00000000.000003b0.00000000.0000000c.a1001000.00000000.000003c0.00000000.00000020.a2001000.00000000.000a0000.00000000.00020000
reg: 00001000.00000000.00000000.00000000.00000000.03001010.00000000.00000000.00000000.00400000.43001018.00000000.00000000.00000000.10000000.01001020.00000000.00000000.00000000.00000008.a1001000.00000000.000003b0.00000000.0000000c.a1001000.00000000.000003c0.00000000.00000020.a2001000.00000000.000a0000.00000000.00020000
compatible: 'pci8086,46.1028.410.2' + 'pci8086,46.1028.410' + 'pci1028,410' + 'pci8086,46.2' + 'pci8086,46' + 'pciclass,030000' + 'pciclass,0300'
model: 'VGA compatible controller'
power-consumption: 00000001.00000001
fast-back-to-back:
devsel-speed: 00000000
interrupts: 00000001
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 00000410
device_type: 'display'
unit-address: '2'
class-code: 00030000
revision-id: 00000002
vendor-id: 00008086
device-id: 00000046
name: 'display'
Node 0x000006
acpi-namespace: '\_SB_.PCI0.GLAN'
assigned-addresses: 8200c810.00000000.f5400000.00000000.00020000.8200c814.00000000.f5480000.00000000.00001000.8100c818.00000000.00006040.00000000.00000020
reg: 0000c800.00000000.00000000.00000000.00000000.0200c810.00000000.00000000.00000000.00020000.0200c814.00000000.00000000.00000000.00001000.0100c818.00000000.00000000.00000000.00000020
compatible: 'pci8086,10ea.1028.410.5' + 'pci8086,10ea.1028.410' + 'pci1028,410' + 'pci8086,10ea.5' + 'pci8086,10ea' + 'pciclass,020000' + 'pciclass,0200'
model: 'Ethernet controller'
power-consumption: 00000001.00000001
devsel-speed: 00000000
interrupts: 00000001
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 00000410
unit-address: '19'
class-code: 00020000
revision-id: 00000005
vendor-id: 00008086
device-id: 000010ea
name: 'pci1028,410'
Node 0x000007
acpi-namespace: '\_SB_.PCI0.EHC2'
assigned-addresses: 8200d010.00000000.f5470000.00000000.00000400
reg: 0000d000.00000000.00000000.00000000.00000000.0200d010.00000000.00000000.00000000.00000400
compatible: 'pci8086,3b3c.1028.410.5' + 'pci8086,3b3c.1028.410' + 'pci1028,410' + 'pci8086,3b3c.5' + 'pci8086,3b3c' + 'pciclass,0c0320' + 'pciclass,0c03'
model: 'Universal Serial Bus EHCI compliant'
power-consumption: 00000001.00000001
fast-back-to-back:
devsel-speed: 00000001
interrupts: 00000001
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 00000410
unit-address: '1a'
class-code: 000c0320
revision-id: 00000005
vendor-id: 00008086
device-id: 00003b3c
name: 'pci1028,410'
Node 0x000008
acpi-namespace: '\_SB_.PCI0.HDEF'
assigned-addresses: 8300d810.00000000.f5460000.00000000.00004000
reg: 0000d800.00000000.00000000.00000000.00000000.0300d810.00000000.00000000.00000000.00004000
compatible: 'pciex8086,3b57.1028.410.5' + 'pciex8086,3b57.1028.410' + 'pciex8086,3b57.5' + 'pciex8086,3b57' + 'pciexclass,040300' + 'pciexclass,0403' + 'pci8086,3b57.1028.410.5' + 'pci8086,3b57.1028.410' + 'pci1028,410' + 'pci8086,3b57.5' + 'pci8086,3b57' + 'pciclass,040300' + 'pciclass,0403'
model: 'Mixed Mode device'
power-consumption: 00000001.00000001
devsel-speed: 00000000
interrupts: 00000001
subsystem-vendor-id: 00001028
subsystem-id: 00000410
unit-address: '1b'
class-code: 00040300
revision-id: 00000005
vendor-id: 00008086
device-id: 00003b57
name: 'pci1028,410'
Node 0x000009
acpi-namespace: '\_SB_.PCI0.RP01'
slot-names: 00000001.746f6c53.00003333
reg: 0000e000.00000000.00000000.00000000.00000000
compatible: 'pciex8086,3b42.5' + 'pciex8086,3b42' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,3b42.5' + 'pci8086,3b42' + 'pciclass,060400' + 'pciclass,0604'
model: 'PCI-PCI bridge'
ranges: 81000000.00000000.00005000.81000000.00000000.00005000.00000000.00001000.82000000.00000000.f4000000.82000000.00000000.f4000000.00000000.01400000
bus-range: 00000001.00000001
#size-cells: 00000002
#address-cells: 00000003
device_type: 'pciex'
power-consumption: 00000001.00000001
physical-slot#: 00000000
devsel-speed: 00000000
interrupts: 00000001
unit-address: '1c'
class-code: 00060400
revision-id: 00000005
vendor-id: 00008086
device-id: 00003b42
hotplug-capable:
pci-hotplug-type: 00000001
name: 'pci8086,3b42'
Node 0x00000a
acpi-namespace: '\_SB_.PCI0.RP02'
slot-names: 00000001.746f6c53.00003433
reg: 0000e100.00000000.00000000.00000000.00000000
compatible: 'pciex8086,3b44.5' + 'pciex8086,3b44' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,3b44.5' + 'pci8086,3b44' + 'pciclass,060400' + 'pciclass,0604'
model: 'PCI-PCI bridge'
ranges: 81000000.00000000.00004000.81000000.00000000.00004000.00000000.00001000.82000000.00000000.f2c00000.82000000.00000000.f2c00000.00000000.01400000
bus-range: 00000002.00000002
#size-cells: 00000002
#address-cells: 00000003
device_type: 'pciex'
power-consumption: 00000001.00000001
physical-slot#: 00000001
devsel-speed: 00000000
interrupts: 00000002
unit-address: '1c,1'
class-code: 00060400
revision-id: 00000005
vendor-id: 00008086
device-id: 00003b44
hotplug-capable:
pci-hotplug-type: 00000001
name: 'pci8086,3b44'
Node 0x000013
acpi-namespace: '\_SB_.PCI0.RP02.PXSX'
assigned-addresses: 83020010.00000000.f2c00000.00000000.00002000
reg: 00020000.00000000.00000000.00000000.00000000.03020010.00000000.00000000.00000000.00002000
compatible: 'pciex8086,422c.8086.1321.35' + 'pciex8086,422c.8086.1321' + 'pciex8086,422c.35' + 'pciex8086,422c' + 'pciexclass,028000' + 'pciexclass,0280' + 'pci8086,422c.8086.1321.35' + 'pci8086,422c.8086.1321' + 'pci8086,1321' + 'pci8086,422c.35' + 'pci8086,422c' + 'pciclass,028000' + 'pciclass,0280'
model: 'Network controller'
power-consumption: 00000001.00000001
devsel-speed: 00000000
interrupts: 00000001
subsystem-vendor-id: 00008086
subsystem-id: 00001321
unit-address: '0'
class-code: 00028000
revision-id: 00000035
vendor-id: 00008086
device-id: 0000422c
name: 'pci8086,1321'
Node 0x00000b
acpi-namespace: '\_SB_.PCI0.RP03'
slot-names: 00000001.746f6c53.00000038
reg: 0000e200.00000000.00000000.00000000.00000000
compatible: 'pciex8086,3b46.5' + 'pciex8086,3b46' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,3b46.5' + 'pci8086,3b46' + 'pciclass,060400' + 'pciclass,0604'
model: 'PCI-PCI bridge'
ranges: 81000000.00000000.00003000.81000000.00000000.00003000.00000000.00001000.82000000.00000000.f1800000.82000000.00000000.f1800000.00000000.01400000
bus-range: 00000003.00000003
#size-cells: 00000002
#address-cells: 00000003
device_type: 'pciex'
power-consumption: 00000001.00000001
physical-slot#: 00000002
devsel-speed: 00000000
interrupts: 00000003
unit-address: '1c,2'
class-code: 00060400
revision-id: 00000005
vendor-id: 00008086
device-id: 00003b46
hotplug-capable:
pci-hotplug-type: 00000001
name: 'pci8086,3b46'
Node 0x000014
acpi-namespace: '\_SB_.PCI0.RP03.PXSX'
assigned-addresses: 82030010.00000000.f1830000.00000000.00000100
reg: 00030000.00000000.00000000.00000000.00000000.02030010.00000000.00000000.00000000.00000100
compatible: 'pciex1180,e822.1028.410.1' + 'pciex1180,e822.1028.410' + 'pciex1180,e822.1' + 'pciex1180,e822' + 'pciexclass,080500' + 'pciexclass,0805' + 'pci1180,e822.1028.410.1' + 'pci1180,e822.1028.410' + 'pci1028,410' + 'pci1180,e822.1' + 'pci1180,e822' + 'pciclass,080500' + 'pciclass,0805'
model: 'SD Host controller'
power-consumption: 00000001.00000001
devsel-speed: 00000000
interrupts: 00000001
subsystem-vendor-id: 00001028
subsystem-id: 00000410
unit-address: '0'
class-code: 00080500
revision-id: 00000001
vendor-id: 00001180
device-id: 0000e822
name: 'pci1028,410'
Node 0x00000c
acpi-namespace: '\_SB_.PCI0.RP04'
slot-names: 00000001.746f6c53.00000039
reg: 0000e300.00000000.00000000.00000000.00000000
compatible: 'pciex8086,3b48.5' + 'pciex8086,3b48' + 'pciexclass,060400' + 'pciexclass,0604' + 'pci8086,3b48.5' + 'pci8086,3b48' + 'pciclass,060400' + 'pciclass,0604'
model: 'PCI-PCI bridge'
ranges: 81000000.00000000.00002000.81000000.00000000.00002000.00000000.00001000.82000000.00000000.f0400000.82000000.00000000.f0400000.00000000.01400000
bus-range: 00000004.00000009
#size-cells: 00000002
#address-cells: 00000003
device_type: 'pciex'
power-consumption: 00000001.00000001
physical-slot#: 00000003
devsel-speed: 00000000
interrupts: 00000004
unit-address: '1c,3'
class-code: 00060400
revision-id: 00000005
vendor-id: 00008086
device-id: 00003b48
hotplug-capable:
pci-hotplug-type: 00000001
name: 'pci8086,3b48'
Node 0x00000d
acpi-namespace: '\_SB_.PCI0.EHCI'
assigned-addresses: 8200e810.00000000.f5450000.00000000.00000400
reg: 0000e800.00000000.00000000.00000000.00000000.0200e810.00000000.00000000.00000000.00000400
compatible: 'pci8086,3b34.1028.410.5' + 'pci8086,3b34.1028.410' + 'pci1028,410' + 'pci8086,3b34.5' + 'pci8086,3b34' + 'pciclass,0c0320' + 'pciclass,0c03'
model: 'Universal Serial Bus EHCI compliant'
power-consumption: 00000001.00000001
fast-back-to-back:
devsel-speed: 00000001
interrupts: 00000001
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 00000410
unit-address: '1d'
class-code: 000c0320
revision-id: 00000005
vendor-id: 00008086
device-id: 00003b34
name: 'pci1028,410'
Node 0x00000e
acpi-namespace: '\_SB_.PCI0.P0P1'
slot-names: 0000002f.746f6c53.6c530031.0032746f.746f6c53.6c530033.0034746f.746f6c53.00000032
reg: 0000f000.00000000.00000000.00000000.00000000
compatible: 'pci8086,2448.a5' + 'pci8086,2448' + 'pciclass,060401' + 'pciclass,0604'
model: 'Subtractive Decode PCI-PCI bridge'
bus-range: 0000000a.0000000a
#size-cells: 00000002
#address-cells: 00000003
device_type: 'pci'
power-consumption: 00000001.00000001
devsel-speed: 00000000
unit-address: '1e'
class-code: 00060401
revision-id: 000000a5
vendor-id: 00008086
device-id: 00002448
name: 'pci8086,2448'
Node 0x00000f
#size-cells: 00000001
#address-cells: 00000002
ranges: 00000001.00000000.81000000.00000000.00000000.00000022.00000001.00000024.81000000.00000000.00000024.00000002.00000001.00000028.81000000.00000000.00000028.00000002.00000001.0000002c.81000000.00000000.0000002c.00000006.00000001.00000034.81000000.00000000.00000034.00000002.00000001.00000038.81000000.00000000.00000038.00000002.00000001.0000003c.81000000.00000000.0000003c.00000002.00000001.00000040.81000000.00000000.00000040.00000004.00000001.0000004e.81000000.00000000.0000004e.00000006.00000001.00000060.81000000.00000000.00000060.00000002.00000001.00000063.81000000.00000000.00000063.00000003.00000001.00000067.81000000.00000000.00000067.00000001.00000001.00000070.81000000.00000000.00000070.00000008.00000001.00000070.81000000.00000000.00000070.00000001.00000001.00000080.81000000.00000000.00000080.00000022.00000001.000000a4.81000000.00000000.000000a4.00000002.00000001.000000a8.81000000.00000000.000000a8.00000002.00000001.000000ac.81000000.00000000.000000ac.00000002.00000001.000000b0.81000000.00000000.000000b0.00000006.00000001.000000b8.81000000.00000000.000000b8.00000002.00000001.000000bc.81000000.00000000.000000bc.00000002.00000001.000000c0.81000000.00000000.000000c0.00000020.00000001.000000f0.81000000.00000000.000000f0.00000001.00000001.00000400.81000000.00000000.00000400.00000080.00000001.000004d0.81000000.00000000.000004d0.00000002.00000001.00000500.81000000.00000000.00000500.00000080.00000001.00000680.81000000.00000000.00000680.00000020.00000001.00000930.81000000.00000000.00000930.00000001.00000001.00000934.81000000.00000000.00000934.00000001.00000001.00000cf8.81000000.00000000.00000cf8.00000008.00000001.00001000.81000000.00000000.00001000.00000014.00000001.0000164e.81000000.00000000.0000164e.00000002.00000001.0000ffff.81000000.00000000.0000ffff.00000001.00000000.f54c0000.82000000.00000000.f54c0000.00001000.00000000.f8000000.82000000.00000000.f8000000.04000000.00000000.fed00000.82000000.00000000.fed00000.00000400.00000000.fed10000.82000000.00000000.fed10000.00004000.00000000.fed18000.82000000.00000000.fed18000.00002000.00000000.fed1c000.82000000.00000000.fed1c000.00024000.00000000.fed45000.82000000.00000000.fed45000.0004b000.00000000.fee00000.82000000.00000000.fee00000.00100000.00000000.ff000000.82000000.00000000.ff000000.01000000.00000000.ff000000.82000000.00000000.ff000000.01000000
acpi-namespace: '\_SB_.PCI0.LPCB'
device_type: 'isa'
reg: 0000f800.00000000.00000000.00000000.00000000
compatible: 'pci8086,3b0f.1028.410.5' + 'pci8086,3b0f.1028.410' + 'pci1028,410' + 'pci8086,3b0f.5' + 'pci8086,3b0f' + 'pciclass,060100' + 'pciclass,0601'
model: 'ISA bridge'
power-consumption: 00000001.00000001
devsel-speed: 00000001
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 00000410
unit-address: '1f'
class-code: 00060100
revision-id: 00000005
vendor-id: 00008086
device-id: 00003b0f
name: 'isa'
Node 0x00001c
unit-address: '1,60'
interrupts: 00000001.0000000c
reg: 00000001.00000060.00000001.00000001.00000064.00000001
name: 'i8042'
Node 0x00001d
compatible: 'pnpPNP,303'
device-type: 'keyboard'
interrupts: 00000001.0000000c
reg: 00000000
acpi-namespace: '\_SB_.PCI0.LPCB.PS2K'
model: 'System keyboard'
name: 'keyboard'
Node 0x00001e
compatible: 'pnpPNP,f03'
device-type: 'mouse'
reg: 00000001
interrupts: 0000000c
acpi-namespace: '\_SB_.PCI0.LPCB.PS2M'
model: 'PS/2 Port for PS/2-style Mice'
name: 'mouse'
Node 0x00001f
interrupts: 00000004
reg: 00000001.000003f8.00000008
model: 'Standard serial port'
compatible: 'PNP0500'
name: 'asy'
Node 0x000010
acpi-namespace: '\_SB_.PCI0.SAT0'
assigned-addresses: 8100fa10.00000000.00006090.00000000.00000008.8100fa14.00000000.00006080.00000000.00000004.8100fa18.00000000.00006070.00000000.00000008.8100fa1c.00000000.00006060.00000000.00000004.8100fa20.00000000.00006020.00000000.00000020.8200fa24.00000000.f5440000.00000000.00000800
reg: 0000fa00.00000000.00000000.00000000.00000000.0100fa10.00000000.00000000.00000000.00000008.0100fa14.00000000.00000000.00000000.00000004.0100fa18.00000000.00000000.00000000.00000008.0100fa1c.00000000.00000000.00000000.00000004.0100fa20.00000000.00000000.00000000.00000020.0200fa24.00000000.00000000.00000000.00000800
compatible: 'pci8086,3b2f.1028.410.5' + 'pci8086,3b2f.1028.410' + 'pci1028,410' + 'pci8086,3b2f.5' + 'pci8086,3b2f' + 'pciclass,010601' + 'pciclass,0106'
model: 'SATA AHCI 1.0 Interface'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000001
interrupts: 00000003
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 00000410
unit-address: '1f,2'
class-code: 00010601
revision-id: 00000005
vendor-id: 00008086
device-id: 00003b2f
name: 'pci1028,410'
Node 0x000011
acpi-namespace: '\_SB_.PCI0.SBUS'
assigned-addresses: 8300fb10.00000000.f5430000.00000000.00000100.8100fb20.00000000.00006000.00000000.00000020
reg: 0000fb00.00000000.00000000.00000000.00000000.0300fb10.00000000.00000000.00000000.00000100.0100fb20.00000000.00000000.00000000.00000020
compatible: 'pci8086,3b30.1028.410.5' + 'pci8086,3b30.1028.410' + 'pci1028,410' + 'pci8086,3b30.5' + 'pci8086,3b30' + 'pciclass,0c0500' + 'pciclass,0c05'
model: 'SMBus (System Management Bus)'
power-consumption: 00000001.00000001
fast-back-to-back:
devsel-speed: 00000001
interrupts: 00000003
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 00000410
unit-address: '1f,3'
class-code: 000c0500
revision-id: 00000005
vendor-id: 00008086
device-id: 00003b30
name: 'pci1028,410'
Node 0x000012
assigned-addresses: 8300fe10.00000000.f5420000.00000000.00001000
reg: 0000fe00.00000000.00000000.00000000.00000000.0300fe10.00000000.00000000.00000000.00001000
compatible: 'pci8086,3b32.1028.410.5' + 'pci8086,3b32.1028.410' + 'pci1028,410' + 'pci8086,3b32.5' + 'pci8086,3b32' + 'pciclass,118000' + 'pciclass,1180'
model: 'DSP/DAP controllers'
power-consumption: 00000001.00000001
devsel-speed: 00000000
interrupts: 00000003
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001028
subsystem-id: 00000410
unit-address: '1f,6'
class-code: 00118000
revision-id: 00000005
vendor-id: 00008086
device-id: 00003b32
name: 'pci1028,410'
Node 0x000015
device_type: 'acpirootnex'
compatible: 'SOLA0001' + 'acpirootnex' + 'SOLA0002' + 'acpivirtnex'
acpi-namespace: '\'
name: 'fw'
Node 0x000016
unit-address: '1'
compatible: 'SOLA0004' + 'acpicpu' + 'cpu'
apic-id: 00000000
acpi-processor-id: 00000001
acpi-namespace: '\_PR_.CPU0'
device_type: 'acpicpu'
name: 'cpu'
Node 0x000017
unit-address: '2'
compatible: 'SOLA0004' + 'acpicpu' + 'cpu'
apic-id: 00000004
acpi-processor-id: 00000002
acpi-namespace: '\_PR_.CPU1'
device_type: 'acpicpu'
name: 'cpu'
Node 0x000018
unit-address: '3'
compatible: 'SOLA0004' + 'acpicpu' + 'cpu'
apic-id: 00000001
acpi-processor-id: 00000003
acpi-namespace: '\_PR_.CPU2'
device_type: 'acpicpu'
name: 'cpu'
Node 0x000019
unit-address: '4'
compatible: 'SOLA0004' + 'acpicpu' + 'cpu'
apic-id: 00000005
acpi-processor-id: 00000004
acpi-namespace: '\_PR_.CPU3'
device_type: 'acpicpu'
name: 'cpu'
Node 0x00001a
unit-address: '0'
compatible: 'acpidevice' + 'SOLA0002' + 'acpivirtnex'
acpi-namespace: '\_SB_'
device_type: 'acpidevice'
name: 'sb'
Node 0x00001b
io-space: 00000000.00000020.00000020.00000002.00000024.00000002.00000028.00000002.0000002c.00000002.0000002e.00000002.00000030.00000002.00000034.00000002.00000038.00000002.0000003c.00000002.00000040.00000004.0000004e.00000002.00000050.00000004.00000060.00000001.00000061.00000001.00000063.00000001.00000064.00000001.00000065.00000001.00000067.00000001.00000070.00000008.00000070.00000001.00000080.00000001.00000081.00000011.00000092.00000001.00000093.0000000d.000000a0.00000002.000000a4.00000002.000000a8.00000002.000000ac.00000002.000000b0.00000002.000000b2.00000002.000000b4.00000002.000000b8.00000002.000000bc.00000002.000000c0.00000020.000000f0.00000001.00000400.00000080.000004d0.00000002.00000500.00000080.00000680.00000020.00000930.00000001.00000934.00000001.00000cf8.00000008.00001000.00000004.00001004.00000010.0000164e.00000002.0000ffff.00000001
device-memory: f54c0000.00001000.f8000000.04000000.fed00000.00000400.fed10000.00004000.fed18000.00001000.fed19000.00001000.fed1c000.00004000.fed20000.00020000.fed45000.0004b000.fee00000.00100000.ff000000.01000000.ff000000.01000000
dma-channels: 00000004
interrupts: 00000000.00000001.00000002.00000008.0000000c.0000000d
name: 'used-resources'
prtdiag:
System Configuration: Dell Inc. Latitude E4310
BIOS Configuration: Dell Inc. A05 11/20/2010
==== Processor Sockets ====================================
Version Location Tag
Intel(R) Core(TM) i5 CPU M 560 @ 2.67GH CPU 1
==== Memory Device Sockets ================================
Type Status Set Device Locator Bank Locator
Unknown in use 0 DIMM_A BANK 0
unknown empty 0 DIMM_B BANK 2
==== On-Board Devices =====================================
"Intel GM45 Graphics"
NETWORK_NAME_STRING
==== Upgradeable Slots ====================================
ID Status Type Description
0 available PCI Express x16 J5C1
1 available PCI Express J6C2
2 in use PCI Express J6D2
3 in use PCI Express J7C1
4 available PCI Express J7D2
System Information:
Manufacturer:Dell Inc.
Product:Latitude E4310
BIOS Information:
Vendor:Dell Inc.
Version:A05
Release Date:11/20/2010
BIOS Revision: BIOS Revision:4.6
Firmware Revision:
MotherBoard Information:
Product:0D8H24
Manufacturer:Dell Inc.
Version:A00
Onboard Devices:[Video,Disabled]"Intel GM45 Graphics"
CPU Information:
Processor 0:
Processor Socket Type:CPU 1
Processor Manufacturer:Intel
Current Voltage:0.0V
External Clock:533MHZ
Max Speed:4000MHZ
Current Speed:2666MHZ
Memory Information:
Physical Memory: 4G (4G)
Maximum Memory Support: 4096G
Memory Subsystem 0:
Array Used Function:System memory
Memory Error Correction Supported:None
Maximum Array Capacity:8G
Number of Memory Devices:2
Memory Device 0:
Memory Device Locator:DIMM_A
Total Width:64
Data Width:64
Installed Size:4096M
Memory Device Type:Unknown
Speed:1067MHZ
Memory Device 1:
[Not Installed]

Openwindows dt libs problems in Solaris 2.8

Hello
My Motif Apps work fine with solaris 2.6
Now, we are moving to solaris 2.8.
I compiled the SAME source code in solaris 2.8 - this App have a different look and feel - like fonts being different, bgcolor, etc.
however, if i compile with solaris 2.6 /usr/dt/lib and /usr/openwin/lib - all looks similar
can anyone point the problems with solaris 2.8
/usr/dt/lib and /usr/openwin/lib
Thanks,
venkat

Are you using the same dot files, from the same
login account in each case? This sounds like some
local settings are different. Using different
monitors can make a difference, too. There are two
different systems with the same monitor which you
are using from the same home dir?

Anyone interested in adf swing problems

adf 11g R1 swing problem
I test the new JDEV 11g 11.1.1.1.0 releas Juli 01
I'm using the JClient (Swing) with ADF (BC4J)
and test a simple app
JTable with Combobox don't work:
im set the binding with edit binding in context for JTable
the combobox has a static viewobject with ID and Text (ID 0,1 Text Yes No)
The Table with combobox render OK
but when Click the combobox i see no values in the Combobox
in Previous Release 11.1.1.0.2 work the sample.
It this a Bug in Classe from the bindig Definition file pageDef ????
RTClass="oracle.jbo.uicli.jui.JULOVEditorPropDef"
DTClass="oracle.adfdtinternal.model.ide.objects.jui.JUDTLOVEditorProp"
Hello,
this Bug is not fixed in 11.1.1.2.0
why ????
thank you in advance
Michael
Edited by: user4796211 on 21.07.2009 12:18
Edited by: user4796211 on 22.07.2009 00:59
Edited by: user4796211 on 24.07.2009 09:54
Edited by: user4796211 on 27.07.2009 09:59
Edited by: user4796211 on 16.11.2009 10:56

Hi,
I installed JDeveloper 11.1.1.3.0 and cracked the nut. The LOV driven ComboBoxes in JTables will remain empty after migrating to the new version, but it seems to be merely a bug in the migration. What you need to do in order to get the ComboBoxes working is the following:
I found out that in your PageDefs you need to add two attributes to the <combobox> definitions:
ControlClass="javax.swing.JComboBox" Editable="false"
This makes the ComboBoxes look like in previous releases. If you skip the "Editable" attribute, the user can type in values, which does not really work in LOVs but in static lists.
Unfortunately I experienced another bug in the 11.1.1.3.0 release concerning LOVs: When defining the LOV in the ViewDef, JDeveloper wouldn't let you specify any additional columns to be displayed in the LOV ("Display Attributes"). -> The workaround is much easier than I first thought: Just resize the dialog a little bigger and the selection fields that I first missed appear!
In the moment it looks to me like I could continue development with JDeveloper 11.1.1.3.0.
Mathias
Edited by: user7585671 on 05.05.2010 06:26

Difference between AWT,Swing and swt

Hello,
I am giving a seminar about swing in which I need to point out differences between AWT,Swing and SWT(Software Widget Tool).
I have two questions:
1)I read that-A heavyweight component is one that is associated with its own native screen resource (commonly known as a peer). A lightweight component is one that "borrows" the screen resource of an ancestor-which makes it lighter.Can anybody explain What native screen resource is and how it is borrowed?
2)I read that SWT uses native widgets and how can it be better than swing?If it is in what way?

Use Swing for new projects. AWT is the rendering layer underneath Swing in many cases, and AWT provides utility things like Graphics. SWT is an alternative to Swing which used more native rendering, but actually with Java 6, Swing is using a lot of native rendering.
Fire up NetBeans and use Matisse. Build an application. Run it under Windows, and then under Linux, and then realize how great it is.

Awt/Swing Problem on Solaris

Similar Messages

Maybe you are looking for