Dan,
Thank you for the quick response. I'm not clear how to tell what
specific url/path is being written to. I did not recognize an option to
set this. The error occurs when I click the "+" symbol to add an
artifact, select a file, fill in the name/version, and click the "Add"
button. The error message appears in yellow background text above the
"Add Artifact" form.
Let me know if there is any other information that might help.
Thanks,
Alan
-----Original Message-----
From: Dan Diephouse [mailto:
dan.diephouse@...]
Sent: Wednesday, February 06, 2008 1:50 PM
To:
user@...
Subject: Re: [galaxy-user] 404 Error Adding Artifact Under WL
Hi Alan,
It sounds like this could be a bug when running under a different
context path. However, I don't think that error was given by Galaxy at
all. What URL are you attempting to post to? I know there was a bug in
beta-1 where it didn't like it if you appended a "/" at the end of the
URL. So if you are doing that, it may be worth trying it without the
trailing slash.
Cheers,
- Dan
Stoddard, Alan wrote:
> I receive the following error when attempting to add an artifact when
> running the war file deployed under WebLogic 9.2 (Java version
> 1.50.0_06). All other functions appear to operate correctly. This does
> not occur with the standalone jar running from the command line on the
> same machine. Am I missing something that needs to be configured?
>
>
> <FONT face=Helvetica><BR clear=all>
> <TABLE cellSpacing=5 border=0>
> <TBODY>
> <TR>
> <TD><BR clear=all><FONT face=Helvetica color=black size=3>
> <H2>Error 404--Not Found</H2></FONT></TD></TR></TBODY></TABLE>
> <TABLE cellPadding=10 width="100%" border=0>
> <TBODY>
> <TR>
> <TD vAlign=top width="100%" bgColor=white><FONT face="Courier
New"><FONT
> face=Helvetica size=3>
> <H3>From RFC 2068 <I>Hypertext Transfer Protocol --
> HTTP/1.1</I>:</H3></FONT><FONT face=Helvetica size=3>
> <H4>10.4.5 404 Not Found</H4></FONT>
> <P><FONT face="Courier New">The server has not found anything matching
> the Request-URI. No indication is given of whether the condition is
> temporary or permanent.</P>
> <P>If the server does not wish to make this information available to
the
> client, the status code 403 (Forbidden) can be used instead. The 410
> (Gone) status code SHOULD be used if the server knows, through some
> internally configurable mechanism, that an old resource is permanently
> unavailable and has no forwarding
> address.</FONT></P></FONT></TD></TR></TBODY></TABLE></FONT>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>
http://admin.muleforge.org/manage_email>
>
>
--
Dan Diephouse
MuleSource
http://mulesource.com |
http://netzooid.com/blog---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://admin.muleforge.org/manage_email---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://admin.muleforge.org/manage_email--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "MuleForge Dev" group.
To post to this group, send email to
muleforgedev@...
To unsubscribe from this group, send email to
muleforgedev-unsubscribe@...
For more options, visit this group at
http://groups.google.com/group/muleforgedev?hl=en-~----------~----~----~----~------~----~------~--~---