Re: Still unable to get a first working default: Pleasehelp

Hi Mike, Jacques

to get a working local version of Keel to test the multilanguage features
I worked my way through the problems with the dependency problems
last week.
I got a working version by changing all dependencies to keel-core 5.0
and keel-common 4.0. For each module the necessary svc...api dependency
had to be added. All other keel-... dependencies had to be enhanced to the
newest versions.

Another problem occured, because AuthorizationException was replaced by
AuthenticationException in some modules.


Other problems were missing dependencies to avalon-framework-api.
I replaced every Commons-Collections 2.0 to Commons-Collection 3.1, since my
tomcat installation was in conflict with Commons-Collections 2.0

Eventually I got a working Version to get going with my tests, using the
default
sample. If it is helpfull to you I can send you a copy of this "work" setup
to
help solving the dependency problems. Especially with the fix of
AuthorizationException
problem my version is not tested well, but it can be a reference when trying
to solve the
problems.

Uta

-----Ursprungliche Nachricht-----
Von: keelgroup-bounces-rI8AND0JKYOgdSakss0wQjGcDxdMUgRv@public.gmane.org
[mailto:keelgroup-bounces-rI8AND0JKYOgdSakss0wQjGcDxdMUgRv@public.gmane.org]Im Auftrag von Michael
Nash
Gesendet: Mittwoch, 9. November 2005 13:13
An: developers-6VIttnCrOeJXNEnpj1eHPNi2O/[email protected]; keel.jsmit-4WVpuZSLeeJWk0Htik3J/[email protected]
Betreff: Re: [Keelgroup] Still unable to get a first working default:
Pleasehelp


Jacques:

Further info: There is indeed no 4.2 of keel-core. I believe I remember
what happened - we were working on a new release, but API changes in
keel-core meant we jumped all the way to 5.0, and those changes were not
fully tested and all dependencies resolved. As a result, some modules
are pointing to a version that was never released.

The correct cleanup for this is to release the keel-core 5.0 version,
and reference the new versions of other modules to that new release.
I'll be doing that cleanup right away, and checking it with a working
sample app (several, in fact)...

Mike

On Wed, 2005-11-09 at 08:59, keel.jsmit-4WVpuZSLeeJWk0Htik3J/[email protected] wrote:
> I am embarrassed because I am recommending the Keel route for our project
development, but
> I can't get a working Keel demonstration!
>
> A)  I tried using the latest versions from HEAD in CVS as suggested on the
mailinglist
> (see http://www.mail-archive.com/keelgroup-
> keelframework.com-rI8AND0JKYOgdSakss0wQjGcDxdMUgRv@public.gmane.org/msg03032.html )
> but this runs into the dependancy problem (looking for keel-core 4.2  and
keel-common-3.2 that
> can't be found in the repositories). Plus the 4.2 version is not tagged in
the CVS so it cant be
> built from there (as far as I understand).
> I used the 1.3.3 plugin for the above.
>
> B) I went back to tthe 1.2.18 plugin and the default example in keel-build
3.2.2 . I tried to follow
> the tips in the mailinglist.
>
> If I ignore maven keel:maven (since the dependency check is broken) and
just run
> maven war  on the example-projects/default directory, no proper war file
is built.
> (I clear the Maven cache every time)
>
> Adding the following dependency to the project.xml  file  will cause a
full .war file to be built:
>   <dependency>
>     <groupId>keel</groupId>
>     <artifactId>keel-client</artifactId>
>     <version>2.2.1</version> <!-- first tried 2.3  - Jacques -->
>     <properties>
>       <war.bundle>true</war.bundle>
>       <keel.client>true</keel.client>
>     </properties>
>   </dependency>
>
> This gives a Tomcat error quoted below.
>
> My questions:
>
> a) Should I continue with A or B above?
>
> b) How can I get past the errors?
>
> Regards
> Jacques
>
> -------------
> Tomcat Error
>
> exception
>
> javax.servlet.ServletException: Servlet execution threw an exception
>
> root cause
>
> java.lang.NoClassDefFoundError:
org/keel/core/exception/ClientNestedException
> 	java.lang.ClassLoader.defineClass0(Native Method)
> 	java.lang.ClassLoader.defineClass(Unknown Source)
> 	java.security.SecureClassLoader.defineClass(Unknown Source)
>
>
org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLo
ader.java:16
> 50)
>
>
org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.jav
a:856)
>
>
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.jav
a:1305)
>
>
org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.jav
a:1187)
> 	java.lang.ClassLoader.loadClassInternal(Unknown Source)
> 	org.keel.clients.struts.ModelAction.execute(ModelAction.java:72)
>
>
org.apache.struts.action.RequestProcessor.processActionPerform(RequestProces
sor.java:421)
>
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:226)
> 	org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164)
> 	org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:397)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>
> http://keelframework.org/documentation.shtml
> keelgroup mailing list
> [email protected]
> http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com

http://keelframework.org/documentation.shtml
keelgroup mailing list
[email protected]
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com

http://keelframework.org/documentation.shtml
keelgroup mailing list
[email protected]
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com