Hi Laura
When trying the API-M requests, try setting the URL to the https endpoint,
ie https://localhost:8443 at the beginning rather than http://localhost:8080
Steve
> -Original Message-
> From: Laura delli Paoli [mailto:laura-...@hotmail.it]
> Sent: 12 March 2011 07:31
> To: fedora-co
Scott Prater writes:
>
> Good idea, Steve. I'll take a look at those issues.
>
Can you explain me how to apply your suggestions???
--
Colocation vs. Managed Hosting
A question and answer guide to determining the be
writes:
>
> A further suggestion: have you tried executing an
API-A request? If you can
successfully so do, it may be
> that the problem is with authentication
(as has been suggested). If not, then at
least you can rule that
> out, assuming that you did not enable
https-only access to API-
writes:
>
> A further suggestion: have you tried executing an API-A request? If you can
successfully so do, it may be
> that the problem is with authentication (as has been suggested). If not, then
at least you can rule that
> out, assuming that you did not enable https-only access to API-A w
Good idea, Steve. I'll take a look at those issues.
-- Scott
Steve Bayliss wrote:
> Or maybe pick it up from $CATALINA_HOME/conf/server.xml? (I think that's
> where it is specified?)
>
> Sounds related to https://jira.duraspace.org/browse/FCREPO-783 and
> https://jira.duraspace.org/browse/FCRE
A further suggestion: have you tried executing an API-A request? If you can
successfully so do, it may be that the problem is with authentication (as has
been suggested). If not, then at least you can rule that out, assuming that you
did not enable https-only access to API-A when you installed F
writes:
>
> Which indicates that your repo seems to be functioning fine.
I haven't much help
to offer for the error
> you're receiving, except to note that you're receiving
a rather low-level
exception
> "java.net.ConnectException: Connection refused" from
> java.net.PlainSocketImpl.socketC
Which indicates that your repo seems to be functioning fine. I haven't much
help to offer for the error you're receiving, except to note that you're
receiving a rather low-level exception "java.net.ConnectException: Connection
refused" from java.net.PlainSocketImpl.socketConnect(), which implies
writes:
>
> If you're using a browser like Firefox, it may be showing you only the text
content of the XML being returned
> from that address. Does the source (shown via View->Page Source) contain more?
>
I use Chrome. The source of the page is:
http://www.w3.org/2001/XMLSchema-instance";
x
If you're using a browser like Firefox, it may be showing you only the text
content of the XML being returned from that address. Does the source (shown via
View->Page Source) contain more?
---
A. Soroka
Online Library Environment
the University of Virginia Library
On Mar 11, 2011, at 1:15 PM
Matthew Stephens writes:
>
>
Now I've installed fedora and tomcat again so I can answer you question more
carefully!
> 1. Is Tomcat running, i.e., can you see the welcome page
> http://localhost:8080 in a web browser?
Yes it is!
>
> 2. Is Fedora running: can you see
> http://localhost:8080
Matthew Stephens writes:
>
> We're getting to the point where there are a great many
> suggestions/considerations on the table. Perhaps we should eliminate
> what we can:
Now I'm installing again both fedora and Tomcat! I tried to use the tomcat
version included in fedora but i failed point 1
yes, all looks good now. Thanks for the fix, Aaron and thanks Steve for
verifying.
Also, I don't know if anyone else has been using Maven3, but I'm happy to
report Fedora looks to build just fine w/ Maven 3.0.3.
On 10 Mar 2011, at 8:30 AM, Steve Bayliss wrote:
> Aaron has committed a fix for
We're getting to the point where there are a great many
suggestions/considerations on the table. Perhaps we should eliminate
what we can:
1. Is Tomcat running, i.e., can you see the welcome page
http://localhost:8080 in a web browser?
2. Is Fedora running: can you see
http://localhost:8080/fed
Just a thought, could this be because the fedora-supplied certificate is not
trusted?
> -Original Message-
> From: Laura delli Paoli [mailto:laura-...@hotmail.it]
> Sent: 11 March 2011 15:38
> To: fedora-commons-developers@lists.sourceforge.net
> Subject: Re: [fcrepo-dev] A simple SOAP Cl
writes:
>
> When you say "it doesn't work", what did you try to do and what message did
you receive? When you say you
> "reboot[ed your] system" do you mean you restarted Tomcat (which you
> shouldn't
have to do) or that you
> rebooted your entire system (which you also shouldn't have to do)
When you say "it doesn't work", what did you try to do and what message did you
receive? When you say you "reboot[ed your] system" do you mean you restarted
Tomcat (which you shouldn't have to do) or that you rebooted your entire system
(which you also shouldn't have to do)?
---
A. Soroka
Onl
Or maybe pick it up from $CATALINA_HOME/conf/server.xml? (I think that's
where it is specified?)
Sounds related to https://jira.duraspace.org/browse/FCREPO-783 and
https://jira.duraspace.org/browse/FCREPO-836 - in general we should check
tomcat config rather than assuming default locations for st
writes:
>
> Also, your CATALINA_HOME needs to point to your actual Tomcat installation,
which, based on your earlier
> emails, seems to be "C:\Tomcat 7.0", not "C:\Tomcat" as you have it below.
I edited these variables and reboot my system bat it doesn't work!
bye
Laura
--
+1. Part of my standard in-house install is to edit the
FEDORA_HOME/server/bin/env-server.sh and
FEDORA_HOME/client/bin/env-client.sh to manually set the location of the
webapps directory (I like to keep the webapps separate from the
application server install -- makes upgrading application se
Also, your CATALINA_HOME needs to point to your actual Tomcat installation,
which, based on your earlier emails, seems to be "C:\Tomcat 7.0", not
"C:\Tomcat" as you have it below.
---
A. Soroka
Online Library Environment
the University of Virginia Library
On Mar 11, 2011, at 9:59 AM, Laura d
That WEBAPP_NAME seems to be wrong. The webapp name is the context-name under
which the Fedora webapp is running inside your servlet container. So assuming
you took the default, and that you expect to find your webapp answering
requests at "http://localhost:8080/fedora";, the WEBAPP_NAME will ju
writes:
>
> It looks fine. Did you set CATALINA_HOME to the base directory of your Tomcat
instance before trying to use
> the command-line utilities?
>
CATALINA_HOME is C:\Tomcat! Is it ok?
the other env variables are:
CLASSPATH ->D:\Università\Tesi\Applicazione\SimpleServer\bin
FEDORA_H
It looks fine. Did you set CATALINA_HOME to the base directory of your Tomcat
instance before trying to use the command-line utilities?
---
A. Soroka
Online Library Environment
the University of Virginia Library
On Mar 11, 2011, at 9:51 AM, Laura delli Paoli wrote:
> writes:
>
>>
>> This
writes:
>
> This _may_ be a problem we have often discovered:
>
> If you look in env-server.sh, you will see the line:
>
> webinf="$CATALINA_HOME"/webapps/$webapp_name/WEB-INF
>
> encoding the assumption that the Fedora webapp can be found in
"$CATALINA_HOME/webapps". If you have
> already
This _may_ be a problem we have often discovered:
If you look in env-server.sh, you will see the line:
webinf="$CATALINA_HOME"/webapps/$webapp_name/WEB-INF
encoding the assumption that the Fedora webapp can be found in
"$CATALINA_HOME/webapps". If you have already set CATALINA_HOME to the base
writes:
>
> I may have missed this info in a previous email of yours,
>but are you using the Tomcat container that is
> included with Fedora, or a servlet container that
>was already installed on your
>system?
>
Hi!
I use a previous installation of Tomcat(7.0)
Thanks Laura
-
I may have missed this info in a previous email of yours, but are you using the
Tomcat container that is included with Fedora, or a servlet container that was
already installed on your system?
---
A. Soroka
Online Library Environment
the University of Virginia Library
On Mar 11, 2011, at 9
Matthew Stephens writes:
>
> Hi Laura,
>
> The connection might be refused because your client isn't authorized
> to do API-M methods to your fedora server. I would do a test ingest
> from the command line, once from the client, once from the server, and
> see if the client is similarly refuse
Hi Laura,
The connection might be refused because your client isn't authorized
to do API-M methods to your fedora server. I would do a test ingest
from the command line, once from the client, once from the server, and
see if the client is similarly refused access. If so, you could tweak
your con
Laura delli Paoli writes:
>
> Steve Bayliss writes:
>
Thanks a lot!
I added a number of libraries to my path andin started working!
The next step in my object consists of adding a simple abject to my repository.
I took as exmaple the DemoSOAPClient that you ca find in
FEDORA_HOME\client\demo
Steve Bayliss writes:
>
> Hi Laura
>
> It looks like the required library isn't on your classpath.
>
> Regards
> Steve
>
Thanks a lot!!
--
Colocation vs. Managed Hosting
A question and answer guide to determining
32 matches
Mail list logo
