Hi,
This only seems to happen with Simple - either of the Jetty servers seem
fine - just thought it was my bad code. Note that its not just
TemplateRepresentations either, I've rolled my own STaX (Woodstox)
representation and this fell over with Simple.
AJ
Quoting Zohar Melamed <[EMAIL PROTECTED
Okay here are the results of my first test with JMX integration
I was able to stop the container but when I try and start it again ...
I get an "address already bound" exception
So that means stop doesn't stop all connectors which makes sense but
then why does start try and start a new connector
Hi
I have a simple app with a single restlet using the TemplateRepresentation.
On every request I get :
INFO: Error while handling an HTTP server call
java.io.IOException: Stream closed
at simple.http.ResponseStream.ensureOpen(Unknown Source)
at simple.http.ResponseStream.flushBuffer(Unknown Source
thanks that explains it ...and so does the
result.getAllowedNames().add("127.0.0.1"); in the static method
createLocalHost
Hi Pyiush,
> I added this line
>
> host.getAllowedNames().add("localhost");
>
>
> and now my url
>
> localhost:8182/something works
>
> but
>
> 127.0.0.1:8182/something doesn't work
[...]
> Could you answer: why didn't the first one work for the
> 127.0.0.1 url?
Hi Jerome,
I added this line
host.getAllowedNames().add("localhost");
and now my url
localhost:8182/something works
but
127.0.0.1:8182/something doesn't work
Using getDefaultHost() and then attaching the target works fine in
both the cases.
And when I do
VirtualHost h
Hi Pyiush,
Your virtual host doesn't allow any domain names. That's why it fails. Use
VirtualHost.getAllowedNames();
You can also use container.getDefaultHost().attach() directly if you prefer,
it is setup to accept all requests.
Best regards,
Jerome
> -Message d'origine-
> De : Piyu
Hi Jerome,
I wanted to update my code. Before that in order to comprehend things
I started implementing some simple use cases. The following code
doesn't work as intended I always get a 404
public class Playground {
public static void main(String[] args) throws Exception {
Contai
Hi Jerome,
You've requested a feedback for the new Application feature.
Unfortunally I am unable to give feedback before next Monday. Sorry. I
am busy with aligning one of my projects to b19 but I didn't enter
the 'higher' Application level, yet. :/
Best regards,
Lars
--
http://www.semagia.com
Hi Pyiush,
> What about lifecycles? It is nice to be able to document lifecycle of
> a restlet and container etc...
This would be centralized on RestletMBean because the Restlet class has the
start(), stop(), isStarted() and isStopped() methods.
> Then we can expose status through the MBeans
Hi Sean,
> I think any component or restlet that has useful telemetry
> and/or knobs is a
> candidate for exposure as an MBean. The two above make sense to me.
Agreed.
> Logging control is a candidate.
Actually, in beta 19, the call logging (writing a file similar to an HTTP
log) will be c
Hi Jerome,
What about lifecycles? It is nice to be able to document lifecycle of
a restlet and container etc...
Then we can expose status through the MBeans ... and ways (operations)
to transit from one state to another.
Looks like a comprehensive list and I don't see why we can't have a
hierar
Hi,
IMO, a JMX interface is primarily useful for an administrator who wants to
monitor/manage a Resltet container, its connectors, its virtual hosts and of
course its applications. Here is my candidate list:
- ContainerMBean
- ClientMBean | ServerMBean
- ClientRouterMBean | ServerRouterMBean
Hi Chris,
Thanks for helping polish the rough edges of b19;
[...]
> A few questions:
>
> 1) Where does the 'Application' fit in? Previously I had a
> subclass of
> Component that setup:
>
> - HostRouter
> - Any number of filters, assigning the first filter as the
> 'root' and
> the
14 matches
Mail list logo
