I'm updating old DITA-OT and there is file used catalog-dita.txt which contents seems same as catalog-dita.xml - only thing that in newer DITA-OT there is no txt files
catalog-dita.txt:
-- (C) Copyright OASIS Open 2005, 2009. --
-- (C) Copyright IBM Corporation 2001, 2004. --
-- All Rights Reserved. --
-- --
-- UPDATES: --
-- 2005.11.15 RDA: Corrected system ID for topicAttr.mod --
-- 2005.11.15 RDA: Corrected public ID for tblDecl.mod --
-- 2005.11.15 RDA: Removed #xml:base from <group> --
-- 2006.06.07 RDA: Added commonElements.mod --
-- 2006.06.07 RDA: Added indexing domain --
-- 2006.06.20 RDA: Added bookmap and XNAL domain --
-- 2006.11.30 RDA: Added version specific public IDs --
-- 2008.01.25 RDA: Added DITA 1.2 version specific IDs --
-- 2008.02.01 RDA: *.ent files for topic types --
-- 2008.02.12 RDA: Add hazard statement domain --
-- 2008.02.13 RDA: Added DITA 1.x PUBLIC IDs --
-- 2008.04.11 RDA: Added Learning specializations --
-- 2008.04.15 RDA: Added Machine Industry specializations --
-- 2008.04.15 RDA: Reorganized DTDs into subdirectories --
-- 2008.06.03 RDA: Added glossary group, glossary domains --
-- 2008.11.24 RDA: Added ditaval --
-- 2009.01.05 RDA: Rename machineIndustry dir to machinery --
-- 2009.11.10 RDA: Add entries for glossentry.* --
-- 2009.12.03 RDA: Add entry for learningInteractionBaseDomain --
-- 2010.04.08 RDA: Add basemap.dtd and basetopic.dtd --
-- Catalog for Dita DTDs --
BASE "base/dtd/"
PUBLIC "-//OASIS//ELEMENTS DITA Topic//EN" "topic.mod"
PUBLIC "-//OASIS//ELEMENTS DITA 1.x Topic//EN" "topic.mod"
PUBLIC "-//OASIS//ELEMENTS DITA 1.2 Topic//EN" "topic.mod"
PUBLIC "-//OASIS//ENTITIES DITA Topic Definitions//EN" "topicDefn.ent"
PUBLIC "-//OASIS//ENTITIES DITA 1.x Topic Definitions//EN" "topicDefn.ent"
PUBLIC "-//OASIS//ENTITIES DITA 1.2 Topic Definitions//EN" "topicDefn.ent"
PUBLIC "-//OASIS//ENTITIES DITA Topic Class//EN" "topicAttr.mod"
PUBLIC "-//OASIS//ELEMENTS DITA Map//EN" "map.mod"
PUBLIC "-//OASIS//ELEMENTS DITA 1.x Map//EN" "map.mod"
PUBLIC "-//OASIS//ELEMENTS DITA 1.2 Map//EN" "map.mod"
catalog-dita.xml:
<?xml version="1.0" ?>
<!-- (C) Copyright OASIS Open 2005, 2009. -->
<!-- (C) Copyright IBM Corporation 2001, 2004. -->
<!-- All Rights Reserved. -->
<!-- -->
<!-- UPDATES: -->
<!-- 2005.11.15 RDA: Corrected system ID for topicAttr.mod -->
<!-- 2005.11.15 RDA: Corrected public ID for tblDecl.mod -->
<!-- 2005.11.15 RDA: Removed #xml:base from <group> -->
<!-- 2006.06.07 RDA: Added commonElements.mod -->
<!-- 2006.06.07 RDA: Added indexing domain -->
<!-- 2006.06.20 RDA: Added bookmap and XNAL domain -->
<!-- 2006.11.30 RDA: Added version specific public IDs -->
<!-- 2008.01.25 RDA: Added DITA 1.2 version specific IDs -->
<!-- 2008.02.01 RDA: *.ent files for topic types -->
<!-- 2008.02.12 RDA: Add hazard statement domain -->
<!-- 2008.02.13 RDA: Added DITA 1.x PUBLIC IDs -->
<!-- 2008.04.11 RDA: Added Learning specializations -->
<!-- 2008.04.15 RDA: Added Machine Industry specializations -->
<!-- 2008.04.15 RDA: Reorganized DTDs into subdirectories -->
<!-- 2008.06.03 RDA: Added glossary group, glossary domains -->
<!-- 2008.11.24 RDA: Added ditaval -->
<!-- 2009.01.05 RDA: Rename machineIndustry dir to machinery -->
<!-- 2009.11.10 RDA: Add entries for glossentry.* -->
<!-- 2009.12.03 RDA: Add entry for learningInteractionBaseDomain -->
<!-- 2010.04.08 RDA: Add basemap.dtd and basetopic.dtd -->
<catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"
prefer="public">
<!-- Catalog for Dita DTDs -->
<group xml:base="base/dtd/">
<!-- Topics -->
<public publicId="-//OASIS//ELEMENTS DITA Topic//EN"
uri="topic.mod"/>
<public publicId="-//OASIS//ELEMENTS DITA 1.x Topic//EN"
uri="topic.mod"/>
<public publicId="-//OASIS//ELEMENTS DITA 1.2 Topic//EN"
uri="topic.mod"/>
<public publicId="-//OASIS//ENTITIES DITA Topic Definitions//EN"
uri="topicDefn.ent"/>
<public publicId="-//OASIS//ENTITIES DITA 1.x Topic Definitions//EN"
uri="topicDefn.ent"/>
<public publicId="-//OASIS//ENTITIES DITA 1.2 Topic Definitions//EN"
uri="topicDefn.ent"/>
<!-- topicAttr.mod is only used in DITA 1.0; kept for backwards compatibility -->
<public publicId="-//OASIS//ENTITIES DITA Topic Class//EN"
uri="topicAttr.mod"/>
Could somebody say what this txt file is? What format it is? Easiest would be to transform the new xml to txt if there would be such tools.
I believe it's just a text representation of the XML catalog. It has not been included since (I believe) 2.0 (current version is 3.3.4).
Related
I am learning GWT and was trying to run this tutorial by Vogella and also the official GWT tutorial.
Using the Eclipse GWT plugin 3.0 on Windows 10 and JDK 11
I marked the Maven Project checkbox.
When I right-click and Run As
Turning off precompile in incremental mode.
Super Dev Mode starting up
workDir: C:\Users\My\AppData\Local\Temp\gwt-codeserver-8137229043727681777.tmp
2021-04-29 12:03:13.494:INFO::main: Logging initialized #718ms
Loading Java files in de.vogella.gwt.helloworld.De_vogella_gwt_helloworld.
[ERROR] Hint: Check that your module inherits 'com.google.gwt.core.Core' either directly or indirectly (most often by inheriting module 'com.google.gwt.user.User')
I see that it is inheriting User
<?xml version="1.0" encoding="UTF-8"?>
<!--
When updating your version of GWT, you should also update this DTD reference,
so that your app can take advantage of the latest GWT module capabilities.
-->
<!DOCTYPE module PUBLIC "-//Google Inc.//DTD Google Web Toolkit 2.8.1//EN"
"http://www.gwtproject.org/doctype/2.8.1/gwt-module.dtd">
<module rename-to='de_vogella_gwt_helloworld'>
<!-- Inherit the core Web Toolkit stuff. -->
<inherits name='com.google.gwt.user.User'/>
<!-- Inherit the default GWT style sheet. You can change -->
<!-- the theme of your GWT application by uncommenting -->
<!-- any one of the following lines. -->
<inherits name='com.google.gwt.user.theme.clean.Clean'/>
<!-- <inherits name='com.google.gwt.user.theme.standard.Standard'/> -->
<!-- <inherits name='com.google.gwt.user.theme.chrome.Chrome'/> -->
<!-- <inherits name='com.google.gwt.user.theme.dark.Dark'/> -->
<!-- Other module inherits -->
<!-- Specify the app entry point class. -->
<entry-point class='de.vogella.gwt.helloworld.client.De_vogella_gwt_helloworld'/>
<!-- Specify the paths for translatable code -->
<source path='client'/>
<source path='shared'/>
<!-- allow Super Dev Mode -->
<add-linker name="xsiframe"/>
</module>
This SO question was not relevant to my issue.
Almost certainly you are either missing gwt-user.jar from your classpath, or somehow the gwt-user.jar version doesn't match the gwt-dev.jar, which will cause problems. Every module automatically inherits com.google.gwt.core.Core (despite the error message), and as your .gwt.xml shows, you already have User added.
--
Additionally, from your linked SO post, do check the comments - there are some better, more modern tutorials listed.
I have been searching around for this specific problem of mine. We have a folder that is on a shared folder on another server "\\server1\shares\web\images" and I want to link this folder into my web application in Jboss 7.2.2. I'm migrating from Jboss 4.2.2 to Jboss 7.2.2.
Here is my server.xml file from Jboss 4.2.2. You'll notice that the <Context> tag handles this link for me.
<Server>
<Service name="jboss.web">
<!-- ... -->
<Engine name="jboss.web" defaultHost="localhost">
<!-- ... -->
<Host name="myApp" autoDeploy="false" deployOnStartup="false"
deployXML="false" configClass="org.jboss.web.tomcat.security.config.JBossContextConfig">
<!-- ... -->
<Context path="/images" appBase="" docBase="\\server1\shares\web\images"
debug="99" reloadable="true" />
<!-- ... -->
</Host>
</Engine>
</Service>
My research has lead me to use modules, but I cannot figure out how to use the modules properly for this problem. Most examples shows how to provide some link to a folder on the same machine as the Jboss server is on.
So, am I suppose to use modules or is there another way of doing this?
Every time I need to update my emdx from database, the update wizard takes an incredible amount of time to do so rendering itself as not responding once you hit the finish (as finish the update) button.
I use Visual Studio 2015 and LocalDb SQL Server 2014. Some people suggested to install the Service Pack 1 to address the issue. I have installed the SP1 for LocalDb, but it has not helped. My installation of VS2015 is also rather new.
I have the latest Entity Framework 6 version (from nuget).
Setting the compatibility level of the database to 110 has worked for me.
To check the compatibility level, run this script:
select compatibility_level from sys.databases where name = '<YOUR_DB_NAME>'
To set the compatibility level, use this script:
alter database <YOUR_DB_NAME> set compatibility_level = 110
Running the following on the DB worked for me:
ALTER DATABASE SCOPED CONFIGURATION SET LEGACY_CARDINALITY_ESTIMATION=ON
Then, after the update, setting it back using:
ALTER DATABASE SCOPED CONFIGURATION SET LEGACY_CARDINALITY_ESTIMATION=OFF
This is per this thread over at the EF6 repo on Github.
It should be noted that the following is also reported in that thread to work though I have not tested it because the former worked so well for me:
UPDATE STATISTICS sys.syscolpars
UPDATE STATISTICS sys.sysschobjs
UPDATE STATISTICS sys.syssingleobjrefs
UPDATE STATISTICS sys.sysiscols
They also punted this back to the SQL Server team and opened up this issue over at Microsoft Connect.
Today, my coworkers and I left the wizard alone and let it update for ~10 minutes. While it took quite a while, it did complete. This is the best solution for us (for now), since we are unable to set the compatibility level of our DB without the proper permissions.
Changing SQL Server compatibility level or trace-flag 9481 is no option for me.
I gave EntityFramework Reverse POCO Generator a try.
https://visualstudiogallery.msdn.microsoft.com/ee4fcff9-0c4c-4179-afd9-7a2fb90f5838
It's a configurable generic T4 Template and works very well till now.
It even has an Option for the mentioned trace-flag
IncludeQueryTraceOn9481Flag = false; // If SqlServer 2014 appears frozen / take a long time when this file is saved, try setting this to true (you will also need elevated privileges).
Ironically it works fast even if the flag is off :)
Seems like they are using different queries for metadata compared to the VS EF Designer.
I still had to do this with Microsoft SQL Server 2014 (SP2-GDR) (KB4019093) - 12.0.5207.0 (X64) Jul 3 2017 02:25:44 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor) using Entity Framework 6.2.0. How in the world has this not yet been solved?!
MariaDB Lethargic Manual Remedy
Using EF6, VisualStudio 2015 against MariaDB 10.2.
Just like #Santhos indicated, blowing away a ton of time for me. Seems like VisualStudio is slow at parsing that huge XML file (my development machine only has 8gb RAM). No joke, about 15 minutes to refresh.
I learned that manually 'resetting' a couple of files, then proceeding through the GUI update squared me away quickly. I'm in and out with shiny new models ~1-2 mins.
Manual Refresh Steps
Replace the contents of your .edmx.diagram file with the EDMX Diagram Boilerplate below
Replace the contents of your .edmx file with the EDMX Runtime Boilerplate below
Return to VisualStudio, double-click your EDMX > in the right click in the empty screen > Update Models from Database
EDMX Diagram Boilerplate
<?xml version="1.0" encoding="utf-8"?>
<edmx:Edmx Version="3.0" xmlns:edmx="http://schemas.microsoft.com/ado/2009/11/edmx">
<!-- EF Designer content (DO NOT EDIT MANUALLY BELOW HERE) -->
<edmx:Designer xmlns="http://schemas.microsoft.com/ado/2009/11/edmx">
<!-- Diagram content (shape and connector positions) -->
<edmx:Diagrams>
<Diagram DiagramId="820459acb0f543cfaf7db8643f38c2d6" Name="Diagram1" ZoomLevel="85">
</Diagram>
</edmx:Diagrams>
</edmx:Designer>
</edmx:Edmx>
EDMX Runtime Boilerplate
<?xml version="1.0" encoding="utf-8"?>
<edmx:Edmx Version="3.0" xmlns:edmx="http://schemas.microsoft.com/ado/2009/11/edmx">
<!-- EF Runtime content -->
<edmx:Runtime>
<!-- SSDL content -->
<edmx:StorageModels>
<Schema Namespace="ShareDirectModel.Store" Provider="MySql.Data.MySqlClient" ProviderManifestToken="5.5" Alias="Self" xmlns:store="http://schemas.microsoft.com/ado/2007/12/edm/EntityStoreSchemaGenerator" xmlns:customannotation="http://schemas.microsoft.com/ado/2013/11/edm/customannotation" xmlns="http://schemas.microsoft.com/ado/2009/11/edm/ssdl">
<EntityContainer Name="ShareDirectModelStoreContainer">
</EntityContainer>
</Schema></edmx:StorageModels>
<!-- CSDL content -->
<edmx:ConceptualModels>
<Schema Namespace="ShareDirectModel" Alias="Self" annotation:UseStrongSpatialTypes="false" xmlns:annotation="http://schemas.microsoft.com/ado/2009/02/edm/annotation" xmlns:customannotation="http://schemas.microsoft.com/ado/2013/11/edm/customannotation" xmlns="http://schemas.microsoft.com/ado/2009/11/edm">
<EntityContainer Name="ShareDirectContext" annotation:LazyLoadingEnabled="true">
</EntityContainer>
</Schema>
</edmx:ConceptualModels>
<!-- C-S mapping content -->
<edmx:Mappings>
<Mapping Space="C-S" xmlns="http://schemas.microsoft.com/ado/2009/11/mapping/cs">
<EntityContainerMapping StorageEntityContainer="ShareDirectModelStoreContainer" CdmEntityContainer="ShareDirectContext">
</EntityContainerMapping>
</Mapping>
</edmx:Mappings>
</edmx:Runtime>
<!-- EF Designer content (DO NOT EDIT MANUALLY BELOW HERE) -->
<Designer xmlns="http://schemas.microsoft.com/ado/2009/11/edmx">
<Connection>
<DesignerInfoPropertySet>
<DesignerProperty Name="MetadataArtifactProcessing" Value="EmbedInOutputAssembly" />
</DesignerInfoPropertySet>
</Connection>
<Options>
<DesignerInfoPropertySet>
<DesignerProperty Name="ValidateOnBuild" Value="true" />
<DesignerProperty Name="EnablePluralization" Value="true" />
<DesignerProperty Name="IncludeForeignKeysInModel" Value="true" />
<DesignerProperty Name="UseLegacyProvider" Value="false" />
<DesignerProperty Name="CodeGenerationStrategy" Value="None" />
<DesignerProperty Name="DDLGenerationTemplate" Value="$(VSEFTools)\DBGen\SSDLToMySQL.tt" />
</DesignerInfoPropertySet>
</Options>
<!-- Diagram content (shape and connector positions) -->
<Diagrams></Diagrams>
</Designer>
</edmx:Edmx>
This kind of problem usually happen because the server running SQL server it self is not in good condition.
Maybe the disk space or memory on the server is getting too low to finish the task.
Check the server that running your DB.
The objective I have is to develop a bus with Mule, to run it into a JBoss.
My IDE is eclipse kepler, I have the Anypoint Studio plugin installed, a JBoss 7.1.1, a 3.5 CE runtime, Maven etc etc.
I took a look a this page : Deploy War into Mule Standalone server but I don't see haw it could help.
Context :
- Jboss is an imposed choice. I know it exists an EE version of the runtime, specially for the HA ability (that I need), but it's not an option for my client.
As it's "easier" to test my flows on the standalone (CE) runtime, I wanted to find a way to develop one Mule project to execute it on a CE runtime during the developing phase, and on a JBoss AS during the integration phase.
To do that, I tried to define :
- a jar maven project which contains all the flow
- a "mule" maven project, with the previous jar as the dependency
- a war maven project which athe previous jar and all the module/transport mule jars as dependencies
When I build the mule zip, my jar is included inside, but when it's executed none of ny flew is registered. So it doesn't work.
When I execute the war on JBoss, everything looks fine for the "first" flow (the input one), but I have a crash when the second one is called using a VM connector (other issue, I'll make another request)
Is there a way to do something working with this approach?
I tried to define 2 pom for the same mule project (one pom which generate a war, and a standalone-pom which generate the mule zip), but this is not very "easy to use" for my team, as the eclipse integration of this kind of project is not very friendly.
The last thing I can try is to keep the mule project pom with a mule packaging, and add a maven assembly to build the jar I could include in my war, but I'd prefer a nicer solution...
Thanks for all of your ideas!
Ah, the test flew I'm trying to integrate.
I have 3 flew :
- The first one stands for the HTTP request (to call my CE runtime)
- The second one stands for the Servlet request (to call my JBoss)
- The third one is called by both my CE runtime and my JBoss input flow, throw the VM connector. I'm thinking replace the VM connector by a Flow Call, as the VM inbound-endpoint is not registered when it's embedded into my war (but it works when executed in a CE runtime...)
main file :
<flow name="muleFlow1" doc:name="muleFlow1">
<http:inbound-endpoint exchange-pattern="request-response"
host="localhost" port="8081" doc:name="HTTP" />
<echo-component doc:name="Echo" />
<vm:outbound-endpoint path="receiver"
exchange-pattern="request-response" responseTimeout="10000" doc:name="VM" />
</flow>
<flow name="muleFlow2" doc:name="muleFlow2">
<servlet:inbound-endpoint path="servlet"
responseTimeout="10000" doc:name="Servlet" />
<echo-component doc:name="Echo" />
<vm:outbound-endpoint path="receiver"
exchange-pattern="request-response" responseTimeout="10000" doc:name="VM" />
</flow>
second file :
<flow name="otroFlow1" doc:name="otroFlow1">
<vm:inbound-endpoint path="receiver"
exchange-pattern="request-response" responseTimeout="10000" doc:name="VM" />
<set-payload value="it works" doc:name="Set Payload" />
<echo-component doc:name="Echo" />
</flow>
Thanks !
I didn't find anything else, so I opted for an assembly descriptor...
<assembly
xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2
http://maven.apache.org/xsd/assembly-1.1.2.xsd">
<id>mule</id>
<formats>
<format>zip</format>
</formats>
<includeBaseDirectory>false</includeBaseDirectory>
<fileSets>
<fileSet>
<directory>${project.build.directory}/classes</directory>
<outputDirectory>/</outputDirectory>
<includes>
<include>*.xml</include>
</includes>
</fileSet>
<fileSet>
<directory>${project.build.directory}</directory>
<outputDirectory>/</outputDirectory>
<includes>
<include>classes/**/*.class</include>
</includes>
</fileSet>
</fileSets>
<dependencySets>
<dependencySet>
<outputDirectory>/lib</outputDirectory>
<useProjectArtifact>false</useProjectArtifact>
<useTransitiveDependencies>true</useTransitiveDependencies>
<excludes>
<exclude>org.mule:mule-core</exclude>
<exclude>commons-cli:commons-cli</exclude>
<exclude>log4j:log4j</exclude>
<exclude>org.mule.mvel:mule-mvel2</exclude>
<exclude>org.mule.common:mule-common</exclude>
<exclude>org.mule.modules:mule-module-client</exclude>
<exclude>org.mule.modules:mule-module-spring-config</exclude>
<exclude>org.mule.modules:mule-module-annotations</exclude>
<exclude>org.mule.modules:mule-module-xml</exclude>
<exclude>org.mule.modules:mule-module-cxf</exclude>
<exclude>org.mule.modules:mule-module-spring-security</exclude>
<exclude>org.mule.transports:mule-transport-http</exclude>
<exclude>org.mule.transports:mule-transport-ssl</exclude>
<exclude>org.mule.transports:mule-transport-tcp</exclude>
<exclude>commons-codec:commons-codec</exclude>
<exclude>org.mule.modules:mule-module-spring-extras</exclude>
<exclude>org.mule.modules:mule-module-builders</exclude>
<exclude>org.mule.modules:mule-module-management</exclude>
<exclude>org.mule.modules:mule-module-scripting</exclude>
<exclude>org.mule.modules:mule-module-sxc</exclude>
<exclude>org.mule.tests:mule-tests-functional</exclude>
<exclude>org.mule:mule-core</exclude>
<exclude>org.mule.transports:mule-transport-file</exclude>
<exclude>org.mule.transports:mule-transport-jdbc</exclude>
<exclude>org.mule.transports:mule-transport-jms</exclude>
<exclude>org.mule.transports:mule-transport-servlet</exclude>
<exclude>org.mule.transports:mule-transport-vm</exclude>
</excludes>
</dependencySet>
</dependencySets>
</assembly>
My mule project is now a jar, which generate a jar file (for my webapp) and a zip file (for my runtime CE)
One important thing :
To realize the spring imports of each flow, we need to specify when mule is deployed in a web app, but the runtime expects to work. It can be done by creating a maven profile and enabling the resources filtering to determine when add "classpath:"...
I am developing a simple app (using GWT RPC & Hibernate) to insert data into database & retrieve. It was working fine with adding user method.
Now I write a method to retrieve data from database & display. It is raising source path errors when module is loaded into browser.
The structure of project in eclipse is:
-src
-user.hbm.xml
-hibernate.cfg.xml
->rpctest
->Rpctest.gwt.xml
->rpctest.hibDomain
->User.java
->rpctest.client
->Rpctest.java
->service interfaces
->rpctest.server
->service implementation
->HibernateUtil.java
Here is stack trace:
[DEBUG] [rpctest] - Validating newly compiled units
[TRACE] [rpctest] - Finding entry point classes
[ERROR] [rpctest] - Unable to find type 'rpctest.client.Rpctest'
[ERROR] [rpctest] - Hint: Previous compiler errors may have made this type unavailable
[ERROR] [rpctest] - Hint: Check the inheritance chain from your module; it may not be inheriting a required module or a module may not be adding its source path entries properly
[ERROR] [rpctest] - Failed to load module 'rpctest' from user agent 'Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C)' at 127.0.0.1:49465
Rpctest.gwt.xml
<?xml version="1.0" encoding="UTF-8"?>
<module rename-to='rpctest'>
<!-- Inherit the core Web Toolkit stuff. -->
<inherits name='com.google.gwt.user.User'/>
<!-- Inherit the default GWT style sheet. You can change -->
<!-- the theme of your GWT application by uncommenting -->
<!-- any one of the following lines. -->
<inherits name='com.google.gwt.user.theme.clean.Clean'/>
<!-- <inherits name='com.google.gwt.user.theme.standard.Standard'/> -->
<!-- <inherits name='com.google.gwt.user.theme.chrome.Chrome'/> -->
<!-- <inherits name='com.google.gwt.user.theme.dark.Dark'/> -->
<!-- Other module inherits -->
<!-- Specify the app entry point class. -->
<entry-point class='rpctest.client.Rpctest'/>
<!-- Specify the paths for translatable code -->
<source path='rpctest.client.Rpctest'/>
<source path='server'/>
<source path='hibDomain.User'/>
</module>
The class User in the hibDomain package is not included in your gwt source path
You can configure the classes that the gwt compiler should translate to javascript by adding them in your gwt xml file. Take a look at the docs: http://code.google.com/intl/de-DE/webtoolkit/doc/latest/DevGuideOrganizingProjects.html#DevGuideModuleXml