x27;s working fine now ;) It was working fine before ... I just didn't
know it. Shees.
Twylite
nticate in their own
way against their own database(s). i.e. not using Realms at all.
Thanks,
Twylite
page and logon-error-page in the web.xml, and all that jazz. I do not intend writing
my own logic to handle the
authentication!
Can this be done?
If it can't, would it be possible to do it by making a new RequestInterceptor?
Twylite
g. I can't see anything else wrong with your configuration.
I can only stress that I'm using Tomcat 3.2.1 ... your version, if different, may have
problems ...?
Anyone else care to shed some light on this?
Twylite
re, specify the location when you use keytool,
and specify the location in the
server.xml .
Twylite
he next bit, which is XML, will be missing. Have a
nice day.)
Now restart your tomcat server, and watch as it hopefully finds everything and starts
listening for SSL
connections on port 8443.
Twylite
"on the off
chance" that you may need
them. Either you do or you don't.
Wells, thats my R2.
Given the exchange rate ... that's not far off 2c.
Shyte.
Twylite
ject, and on
every request transfers
this into the request object.
Hope this clarifies things, and that I haven't made any glaring errors ;)
Twylite
uses a POST method to communicate logon information, not the
Authorization header. That
header is only used if you are using Basic logon. Things will remain that way until
browsers and servers define
other methods of logon.
Twylite
Hi,
>Who Can Provide Me org.hsql.jdbcDriver ?Thanks In Advance.
http://hsqldb.sourceforge.net
Twylite
Hi,
>Statement s=cn.createStatement
(ResultSet.TYPE_SCROLL_INSENSITIVE,ResultSet.CONCUR_READ_ONLY);
> if (!rs.isFirst()) rs.previous();
> %>
> <%=rs.getString(1)%><%
> }
> [Microsoft][ODBC Driver Manager] Invalid cursor state
You never close
ir trying to use xtags:style ... the xsl= path MUST
have a leading / )
3. You can generate XML from the JSP page, and allow the browser to do the XSL
formatting by associating
the appropriate stylesheet with the xml generated:
http://www.mydomain.com";>
Hope this helps
Twylite
.xml is server-wide, and must be available to Tomcat when you start
the server. Anything in
web.xml is context-wide, and must be available to the context when you first access it.
Twylite
y to tackle these issues?
Does anyone else have a system in which the responsibility is divided among multiple
servers (not a load-
balancing scenario!), and if so, how have you tackled the problem?
Thanks in advance.
Twylite
14 matches
Mail list logo
