Eclipse Community Forums: Remote Application Platform (RAP)

Home » Eclipse Projects » Remote Application Platform (RAP) » RWT Standalone

RWT Standalone [message #81968]

Tue, 08 April 2008 17:10

Eclipse User

Hi,

IŽm just trying to investigate RWT Standalone.
But somehow, I canŽt get it to work, what I get is

org.eclipse.swt.SWTException: Invalid thread access
at org.eclipse.swt.SWT.error(SWT.java:1683)
at org.eclipse.swt.SWT.error(SWT.java:1603)
at org.eclipse.swt.SWT.error(SWT.java:1574)
at org.eclipse.swt.widgets.Widget.error(Widget.java:775)
at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:718)
at org.eclipse.swt.widgets.Composite.getChildren(Composite.java :107)
at
org.eclipse.swt.internal.widgets.WidgetTreeVisitor.accept(Wi dgetTreeVisitor.java:49)
at org.eclipse.rwt.lifecycle.WidgetUtil.find(WidgetUtil.java:19 4)
at
org.eclipse.swt.internal.widgets.displaykit.DisplayLCA.readF ocusControl(DisplayLCA.java:482)
at
org.eclipse.swt.internal.widgets.displaykit.DisplayLCA.readD ata(DisplayLCA.java:255)
at org.eclipse.rwt.internal.lifecycle.ReadData.execute(ReadData .java:26)
at
org.eclipse.rwt.internal.lifecycle.RWTLifeCycle.continueLife Cycle(RWTLifeCycle.java:208)
at
org.eclipse.rwt.internal.lifecycle.RWTLifeCycle$UIThreadCont roller.run(RWTLifeCycle.java:115)
at java.lang.Thread.run(Thread.java:619)

I couldnŽt find any tutorial or information about that, I read the one
post which describes which libraries to use, but seems that is not enough.
Some ideas?

Martin

Re: RWT Standalone [message #81998 is a reply to message #81968]

Wed, 09 April 2008 02:52

Eclipse User

We use RWT standalone without problems
in Tomcat.
 
 (currently use M2 + M3)
 
 Since we needed some time to find out
how it was done, maybe the following information might help you to find
the missing pieces in your puzzle:
 
 1) We use the following jars from RAP:

         -
org.eclipse.core.commands
         -
org.eclipse.equinox.common
         -
org.eclipse.rap.jface
         -
org.eclipse.rap.rwt
 
 2) We have a normal implementation of
IEntryPoint.createUI
 ----------
          
      Display display = new
Display();
          
      Shell shell = new
Shell(display);
 
          
      shell.open();
          
      shell.setMaximized(true);
          
      while
(!shell.isDisposed()) {
          
              if
(!display.readAndDispatch()) {
          
               
      display.sleep();
          
              }
          
      }
          
      return
0;
 ----------
 
 2) In WEB-INF/conf we have a w4t.xml:
 (a question to the RAP developers - will this hopefully be obsolete
in the future ? We'd like to have it in the web.xml as well )
 
 ----------
 <?xml
version="1.0"
encoding="UTF-8"?>
 <w4t:application
xmlns:w4t="<a href=http://w4toolkit.com/>http://w4toolkit.com/</a>"
      
  xmlns:xsi="<a href="http://www.w3.org/2001/XMLSchema-instance">http://www.w3.org/2001/XMLSchema-instance</a>"
      
  xsi:schemaLocation="<a href=http://w4toolkit.com/>http://w4toolkit.com/</a>
w4t.xsd ">
         <initialisation>
          
      <lifecycle>
          
              org.eclipse.rwt.internal.lifecycle.RWTLifeCycle
          
      </lifecycle>
         </initialisation>
 </w4t:application>
 ----------
 
 3) In WEB-INF we have a simple web.xml:
 
 -----------
 <?xml
version="1.0"
encoding="ISO-8859-1"?>
 <web-app
xmlns="<a href=http://java.sun.com/xml/ns/j2ee>http://java.sun.com/xml/ns/j2ee</a>"
      
  xmlns:xsi="<a href="http://www.w3.org/2001/XMLSchema-instance">http://www.w3.org/2001/XMLSchema-instance</a>"
      
  xsi:schemaLocation="<a href=http://java.sun.com/xml/ns/j2ee>http://java.sun.com/xml/ns/j2ee</a>
<a href="http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd</a>"
      
  version="2.4">
 
         <display-name>Welcome
to Tomcat</display-name>
         <description>Welcome
to Tomcat</description>
 
         <context-param>
          
      <param-name>org.eclipse.rwt.entryPoints</param-name>
          
      <param-value>de.tolina.web.RAPEntryPoint</param-value>
         </context-param>
 
         <listener>
          
      <listener-class>
          
              org.eclipse.rwt.internal.engine.RWTServletContextListener
          
      </listener-class>
         </listener>
 
         <servlet>
          
      <servlet-name>rapServlet</servlet-name>
          
      <servlet-class>
          
              org.eclipse.rwt.internal.engine.RWTDelegate
          
      </servlet-class>
         </servlet>
 
         <servlet-mapping>
          
      <servlet-name>rapServlet</servlet-name>
          
      <url-pattern>/main</url-pattern>
         </servlet-mapping>
 </web-app>
 -----------
 
 4) You can use different features (branding
+ theming), that normally are done with extension points by specifiying
some variables.
 This is optional:
 
         <context-param>
          
      <param-name>org.eclipse.rwt.themes</par am-name> 
          
      <param-value>useradmin#theme/theme.properties& amp;lt;/param-value> 
         </context-param>
 
         <context-param>
          
      <param-name>org.eclipse.rwt.brandings</ param-name> 
          
      <param-value>rap.RAPUseradminBranding</ param-value> 
         </context-param>
 
 Hope this helps you
?

Re: RWT Standalone [message #82014 is a reply to message #81998]

Wed, 09 April 2008 05:32

Eclipse User

Originally posted by: rherrmann.innoopract.com

Hi,

thanks for the detailed instructions.
Regarding your question about W4T.xml: yes this file will become
obsolete one day. But as this file is necessary to maintain
compatibility with W4Toolkit, we can only remove it when there are
no more W4Toolkit users.

Cheers,
Rüdiger

stefan.hansel@tolina.de wrote:
>
> We use RWT standalone without problems in Tomcat.
>
> (currently use M2 + M3)
>
> Since we needed some time to find out how it was done, maybe the
> following information might help you to find the missing pieces in your
> puzzle:
>
> 1) We use the following jars from RAP:
> - org.eclipse.core.commands
> - org.eclipse.equinox.common
> - org.eclipse.rap.jface
> - org.eclipse.rap.rwt
>
> 2) We have a normal implementation of IEntryPoint.createUI
> ----------
> Display display = *new* *Display*();
> Shell shell = *new* *Shell*(display);
>
> shell.*open*();
> shell.*setMaximized*(*true*);
> *while* (!shell.*isDisposed*()) {
> *if* (!display.*readAndDispatch*()) {
> display.*sleep*();
> }
> }
> *return* 0;
> ----------
>
> 2) In WEB-INF/conf we have a w4t.xml: (a question to the RAP developers
> - will this hopefully be obsolete in the future ? We'd like to have it
> in the web.xml as well )
>
> ----------
> <?xml version="1.0" encoding="UTF-8"?>
> <w4t:application xmlns:w4t="http://w4toolkit.com/"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://w4toolkit.com/ w4t.xsd ">
> <initialisation>
> <lifecycle>
> org.eclipse.rwt.internal.lifecycle.RWTLifeCycle
> </lifecycle>
> </initialisation>
> </w4t:application>
> ----------
>
> 3) In WEB-INF we have a simple web.xml:
>
> -----------
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
> http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
> version="2.4">
>
> <display-name>Welcome to Tomcat</display-name>
> <description>Welcome to Tomcat</description>
>
> <context-param>
> <param-name>org.eclipse.rwt.entryPoints</param-name>
> <param-value>de.tolina.web.RAPEntryPoint</param-value>
> </context-param>
>
> <listener>
> <listener-class>
>
> org.eclipse.rwt.internal.engine.RWTServletContextListener
> </listener-class>
> </listener>
>
> <servlet>
> <servlet-name>rapServlet</servlet-name>
> <servlet-class>
> org.eclipse.rwt.internal.engine.RWTDelegate
> </servlet-class>
> </servlet>
>
> <servlet-mapping>
> <servlet-name>rapServlet</servlet-name>
> <url-pattern>/main</url-pattern>
> </servlet-mapping>
> </web-app>
> -----------
>
> 4) You can use different features (branding + theming), that normally
> are done with extension points by specifiying some variables.
> This is optional:
>
> <context-param>
> <param-name>org.eclipse.rwt.themes</param-name>
> <param-value>useradmin#theme/theme.properties</param-value >
> </context-param>
>
> <context-param>
> <param-name>org.eclipse.rwt.brandings</param-name>
> <param-value>rap.RAPUseradminBranding</param-value>
> </context-param>
>
> Hope this helps you ?

Re: RWT Standalone [message #82060 is a reply to message #82014]

Wed, 09 April 2008 08:25

Eclipse User

Is there anything interesting that could
be configured there for non W4T-users ?
 
 Otherwise wouldn't it be possible just
to have a fallback - if that file doesn't exist, than take a simple default
(actually there is only one listener registered) ?
 
 Kind regards, 
 
 Stefan

Re: RWT Standalone [message #82104 is a reply to message #82060]

Wed, 09 April 2008 09:15

Eclipse User

Originally posted by: rherrmann.innoopract.com

Stefan,

you are right, the only sensible thing to be configured here is the
RWTLifeCycle.
There are default values defined, but as said, we can't change these
without breaking W4Toolkit applications.

Cheers,
Rüdiger

stefan.hansel@tolina.de wrote:
>
> Is there anything interesting that could be configured there for non
> W4T-users ?
>
> Otherwise wouldn't it be possible just to have a fallback - if that file
> doesn't exist, than take a simple default (actually there is only one
> listener registered) ?
>
> Kind regards,
>
> Stefan

Re: RWT Standalone [message #83007 is a reply to message #81998]

Tue, 15 April 2008 07:47

Eclipse User

Originally posted by: ifurnadjiev.innoopract.com

Hi Stefan,

thank you once again for the detailed instructions. They are included in
RAP wiki FAQ page http://wiki.eclipse.org/RapFaq .

Cheers,
Ivan

Previous Topic:	[ANN] RAP 1.1 M3 released
Next Topic:	SWT.INHERIT_DEFAULT should be default?

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Aug 31 01:41:46 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter