These are meant to be included as <[EMAIL PROTECTED] which is like a cut and paste into the JSP. Maybe someoe tried a <ww:include or something that needs to be corrected. Thanks!

- Brett

On 27/09/2006, at 12:12 AM, Mohni, Daniel wrote:

Hi Brett

after all I now found the cause of my problems :-)

as you mentioned before, parts of the jsps are rendered
as text. after looking in the source of createAdmin.jsp
I found the culprit....

the includes inside the pages are .jspf files, now tomcat
will by default only process *.jsp and *.jspx files.

this is configured in $tomcat_home$/conf/web.xml

to keep things in scope with archiva I added

     <servlet-mapping>
        <servlet-name>jsp</servlet-name>
        <url-pattern>*.jspf</url-pattern>
    </servlet-mapping>

to archiva\archiva-webapp\src\main\webapp\WEB-INF\web.xml
and rebuilded the war

using my archiva.xml with the resource definition and the war
works as it should, I can now start working with archiva

tnx for your support...

Daniel

-----Original Message-----
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 26, 2006 12:48 PM
To: [email protected]
Subject: Re: AW: working war for testing

Yes, that's a known issue with the current development
mechanism with
the war overlaying. It won't affect releases, but can be a bit of a
pain. It shouldn't be the cause of your problems either though, as
you've noticed :(

On 26/09/2006, at 7:38 PM, Mohni, Daniel wrote:

Ok, I found some strange things

when I look at the libs in WEB_INF/lib there are some duplicated
SNAPSHOT jars, this may create some problems...

the following jars are present in 2 different versions

plexus-security-authentication-api-1.0-20060920.052713-16.jar
plexus-security-authentication-api-1.0-SNAPSHOT.jar

plexus-security-authorization-rbac-model-1.0-20060920.052713-16.jar
plexus-security-authorization-rbac-model-1.0-SNAPSHOT.jar

plexus-security-policy-1.0-20060920.052713-9.jar
plexus-security-policy-1.0-SNAPSHOT.jar

plexus-security-rbac-template-1.0-20060920.052713-3.jar
plexus-security-rbac-template-1.0-SNAPSHOT.jar

plexus-security-ui-web-taglib-1.0-20060920.052713-6.jar
plexus-security-ui-web-taglib-1.0-SNAPSHOT.jar

removing one of the 2 jars either the snapshot versions
or the timestamp versions doesn't help :-(

but this looks like there is a problem in the dependency
configuration
of the artefacts...

still searching for the real problem

Daniel

-----Original Message-----
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 26, 2006 9:42 AM
To: [email protected]
Subject: Re: AW: working war for testing

Not in 5.5, I think it uses the eclipse compiler. Can't hurt to try
though. I assume you use JDK 5.0?

- Brett

On 26/09/2006, at 5:30 PM, Emmanuel Venisse wrote:

You need a jdk for compiling JSPs

Emmanuel

Mohni, Daniel a écrit :
still the same problem, I'will now try with Tomcat 5.0.28...
can it be a problem if in tomcat5.5 I use the jre to run Tomcat
instead of the jdk ?
Daniel
-----Original Message-----
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent:
Tuesday, September 26, 2006 8:54 AM
To: [email protected]
Subject: Re: AW: working war for testing

Can you try with an extracted archiva war instead of the war.
Archiva create some files/directory under archiva directory, so
it's maybe the pb.

Emmanuel

Mohni, Daniel a écrit :
Ok, I started from scratch

uninstalled Tomcat and reinstalled the latest Tomcat
5.5.17 with
the Windows Installer, then I installed Tomcat Admin
in the same
directory. The Install directory is the default proposed by the
Installer (C:\Program Files\Apache Software
Foundation\Tomcat5.5)

after that i rebuild archiva using 'mvn clean install' in
the root folder
and put the war from archiva/archiva-webapp/target in a
directory for installation
then I copied 'archiva.xml'
 <?xml version="1.0" encoding="UTF-8"?>
<Context path="/archiva"
    docBase="C:/Program Files/Apache Software
Foundation/archiva/archiva-webapp-1.0-SNAPSHOT.war">
        <Resource name="jdbc/users" auth="Container"
type="javax.sql.DataSource"
            username="archiva"
            password="archiva"

driverClassName="org.apache.derby.jdbc.EmbeddedDriver"
            url="jdbc:derby:database/archiva;create=true"
           />

<!--
        <Resource name="jdbc/users" auth="Container"
type="javax.sql.DataSource"
            username="archiva"
            password="archiva"
            driverClassName="com.mysql.jdbc.Driver"

url="jdbc:mysql://localhost/archiva?autoReconnect=true"
           />
-->
</Context>
 to $tomcat_home$/conf/Catalina/localhost/

copied derby-10.1.3.1.jar from

archiva\archiva-webapp\target\archiva-webapp-1.0-SNAPSHOT\WEB-INF
\lib
to $tomcat_home$/common/lib

startup tomcat...

-> still the same problems, that jsp's are not rendered

I didn't have this problems with the build from the
18.September, could there be a problem with
a snapshot dependency ?

Daniel


-----Original Message-----
From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Tuesday,
September 26, 2006 4:30 AM
To: [email protected]
Subject: Re: AW: working war for testing

Something is misconfigured as it is serving the JSP as text.

What version of Tomcat? I think you might need 5.0+.

- Brett

On 26/09/2006, at 1:56 AM, Mohni, Daniel wrote:

Hello Brett,

I was tweaking with tomcat a little bit to get the
embeddedDerby  driver to work, as a
result I have a archiva.xml that I copy to
$tomcat_home$/conf/
Catalina/localhost

I put the generated war somewhere on the drive and reference
the  war using the docbase attribute

<?xml version="1.0" encoding="UTF-8"?>
<Context path="/archiva"
    docBase="C:/Program Files/Apache Software Foundation/
archiva/ archiva-webapp-1.0-SNAPSHOT.war">

        <Resource name="jdbc/users" auth="Container"
type="javax.sql.DataSource"
            username="archiva"
            password="archiva"

driverClassName="org.apache.derby.jdbc.EmbeddedDriver"

url="jdbc:derby:webapps/archiva/WEB-INF/db;create=true"
           />
</Context>

now archiva will be deployed after the next start of tomcat
and  everything looks fine from
a tomcat starting point...

looking at localhost:8080/archiva the screen looks realy
strange  (look at the screenshot)

or here is a sample

<%-- ~ Copyright 2005-2006 The Codehaus. ~ ~ Licensed under
the  Apache License, Version 2.0 (the "License"); ~
you may not
use this
file except in compliance with the License. ~ You may
obtain a copy
of the License at ~ ~
http://www.apache.org/licenses/LICENSE-2.0 ~
~ Unless required by applicable law or agreed to in writing,
software ~ distributed under the License is distributed
on an "AS
IS" BASIS, ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either
express or implied. ~ See the License for the specific
language  governing permissions and ~ limitations under the
License.
--%> <%@
taglib uri="/webwork" prefix="ww" %> <%@ taglib uri="http://
java.sun.com/jsp/jstl/core" prefix="c" %>     Login -
Register
Welcome,    ${sessionScope.securityUser.username}   $
{sessionScope.securityUser.username}    Unknown User    -
Logout  <
%-- Admin Functions --%>  [ ADMIN   User List <%-- |  Role
List  |
Role Create  --%>  ]

this is what I see in the header part

Any hints on this point...

thanks for putting me on track

Daniel

-----Ursprüngliche Nachricht-----
Von: Brett Porter [mailto:[EMAIL PROTECTED]
Gesendet: Samstag, 23. September 2006 02:20
An: [email protected]
Betreff: Re: working war for testing

Hi Daniel,

The current WAR should be a lot more stable, however
you need to
configure a data source in your application server
for the user
database. You can use the settings from the
src/jetty-env.xml
file if
that is helpful - I'll look into making that an
easier default.

Other than that, I'd suggest going to SVN a bit more than
a week ago
before the user management changes.

HTH,
Brett

On 22/09/2006, at 11:50 PM, Mohni, Daniel wrote:

Hello

I'am currently trying to get a working copy of
archiva.war to
use for testing.
I update the sources daily and build the project
using maven
(of
course...),
and install the war on my local tomcat. currently
archiva will not
startup as
there is to much ongoing changes with the user managment.

I'have a build form the 18. September that is coming up and
everyting
can be
configured, the problem with this version is, that I
can't access
any of
the
repositories using
http://www.example.com:8080/archiva/proxy/my_repo
when I access the browse window it will mention that the
repository
has
not been
indexed and that I have to try again later. If I hit the
'run_now' on
the administration
page, nothing happens...

does someone have a working archiva.war on a repository,
that can be
downloaded for
testing purpose ?

maybe there is a snapshot repository somewhere...

Regards

Daniel







Reply via email to