Hi Patrick
The rationale I am asking is the way web technology is, I think we may not
be able to block the arbitrary access of web pages. However, if we could
use user authentication as a way to check, terminate the unwanted sessions
and redirect to another stateless page, the impacts could
Hi Klaus,
nice article but you can achieve that with less work (or files). Instead of an
empty component you could just create an empty response object and return
that in your direct action:
[…]
if (noAuthenticationFound) {
ERXResponse authRequired = new ERXResponse();
I have only one Class to rewrite a little, and pus to wonder.
After wonder is released I will push the Framework and the Example.
But one Important problem I have:
Which of the Project Wonder LOGOS was the Winner
Ken
On 2012/04/08, at 1:06, Jesse Tayler wrote:
Great looking stuff -
Hi,
Most is only UI stuff.
The Demo is stateful, but i think with combing to ERRest stateless won't be
much problem.
Ken
On 2012/04/08, at 1:18, Farrukh Ijaz wrote:
Great work Ken! Are they stateless or stateful?
Farrukh
ISHIMOTO Ken lt;k...@ksroom.comgt; wrote:
Hi,
I am
Hello -
What is the trick to show a spinner when the user clicks a submit button?
Thanks
James
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
I'm pretty sure this feature is the only mechanism by which a user can
request a specific page (or component) by name. I would want to block
arbitrary access to pages as well as prevent spurious session creation.
But yes, there are ways to mitigate the effects. If an authenticated user is
Le 2012-04-09 à 15:27, Emmanuel Tote Dominguez Torres a écrit :
Good Afternoon List, hope everybody is ok,
I am working using ERRest and I had this wild idea, so I would like to know
if it is possible to achieve this and some pointers (if it is indeed
possible),
I have been using the
Le 2012-04-10 à 06:00, ISHIMOTO Ken a écrit :
I have only one Class to rewrite a little, and pus to wonder.
After wonder is released I will push the Framework and the Example.
But one Important problem I have:
Which of the Project Wonder LOGOS was the Winner
The logo battle was
OK fine I will replace it.
On 2012/04/10, at 15:48, Pascal Robert wrote:
Le 2012-04-10 à 06:00, ISHIMOTO Ken a écrit :
I have only one Class to rewrite a little, and pus to wonder.
After wonder is released I will push the Framework and the Example.
But one Important problem I have:
Thanks for the answer Pascal,
well, this came from a project i am doing with asterisk, at some time I
ended up with different little apps each one implementing a thread that was
consulting with the server,
then i learned about ERRest, and I changed the way things were done so that
my apps were
Kieran,
I see in your JasperReport example that in the DownloadIsCompletePage there is
a method to set the referringPage.
Is there a way to get the D2W context and apply it to the
DownloadIsCompletePage in the appendToResponse method so the
DownloadIsCompletePage has the PageWrapper?
I
Hi Ted,
You'll probably have to go through the steps of adding a normal component to
ERModernLook app to get the DownloadIsComplete page behaving as you wish.
http://wiki.wocommunity.org/display/WO/Adding+a+Normal+WOComponent+Page+to+an+ERModernLook+based+application
Wrap the
Thanks a lot for taking the time to explain it. That helps quite a bit.
Ricardo
On Apr 7, 2012, at 11:07 PM, Henrique Prange wrote:
Hi Ricardo,
WOInject is a framework that enables dependency injection in WebObjects
applications by integrating the Guice framework.
OK. It doesn't
Hi Paul,
Properties files are not loaded when tests are executed by JUnit. There is an
issue [1] for that problem. The current workaround is to load the Properties
files manually or set the required properties in a static method annotated with
@BeforeClass.
I'll try to spend some time with
Hi Everyone,
I was wondering, if I use the ErrorDocument in Apache for the 401 to
redirect on a direct action (for example ErrorDocument 401
/cgi-bin/WebObjects/wa/requireLogon ), is there a way in WO to obtain the
URI that cause the Authentication Error?
In PHP you can use the
All of my wrapper components have a conditional i.e. $rootPage.isAuthorized
around the WOComponentContent. Solves this issue and is handy in dozens of other ways.
On 4/10/12 7:14 AM, Patrick Robinson wrote:
I'm pretty sure this feature is the only mechanism by which a user can
request a
I have patched WOComponentRequestHandler and created a pull request in the
wonder/integration branch
then you will set the property:
ERXDirectComponentAccessAllowed=false
Amedeo
On 10/apr/2012, at 15:14, Patrick Robinson wrote:
I'm pretty sure this feature is the only mechanism by which a
Le 2012-04-10 à 13:29, Amedeo Mantica a écrit :
I have patched WOComponentRequestHandler and created a pull request in the
wonder/integration branch
then you will set the property:
ERXDirectComponentAccessAllowed=false
If someone wants to review it:
String originalURLFromRequest = request.headerForKey(request_uri);
On 2012-04-10, at 10:26 AM, Daniele Corti wrote:
Hi Everyone,
I was wondering, if I use the ErrorDocument in Apache for the 401 to redirect
on a direct action (for example ErrorDocument 401
On Mar 29, 2012, at 1:42 PM, Kieran Kelleher wrote:
All anyone has to do is add your fork's remote, fetch the remote, checkout
the feature branch (3 simple commands) and play with the feature or examine
it. Any peer can easily do diff between your tree and master or integration
to see
Commented already
https://github.com/projectwonder/wonder/pull/150
On Apr 10, 2012, at 10:33 AM, Pascal Robert wrote:
Le 2012-04-10 à 13:29, Amedeo Mantica a écrit :
I have patched WOComponentRequestHandler and created a pull request in the
wonder/integration branch
then you will set
Wow, that's great, Amedeo! I hadn't paid much attention to that little corner
of Project Wonder before. What is it that forces the patched PW version of
that class to be loaded rather than the original WO version?
On Apr 10, 2012, at 1:31 PM, Amedeo Mantica wrote:
I have patched
Good idea, so far as I understand it. I've not yet quite grasped the
distinction between the ER classes vs. the ERX classes.
Also, would you register the new handler with the same old request handler key?
On Apr 10, 2012, at 1:47 PM, Ramsey Gurley wrote:
Commented already
Probably should be ERX to be consistent. Yeah, WO is very pluggable. You can
register your own request handlers for any request handler key. Make up your
own request handlers and keys if you like.
WOApplication app = WOApplication.application();
app.registerRequestHandler(new
I originally replaced the WOComponentRequestHandler (get loaded in the
classpath before the WO one)
After Ramsey Suggestion I renamed and moved to ERXComponentRequestHandler, then
patched ERXApplication to assign ERXComponentRequestHandler to the
componenthandler key
Amedeo
On 10/apr/2012,
Thanks again for that. I hadn't realized it was that easy, or I'd have done it
myself. Maybe next time! :-)
- Patrick
On Apr 10, 2012, at 2:15 PM, Amedeo Mantica wrote:
I originally replaced the WOComponentRequestHandler (get loaded in the
classpath before the WO one)
After Ramsey
Hi
2012/4/10 Chuck Hill ch...@global-village.net
String originalURLFromRequest = request.headerForKey(request_uri);
is it so easy? I thought it was more complicated...
Thank you Chuck!
On 2012-04-10, at 10:26 AM, Daniele Corti wrote:
Hi Everyone,
I was wondering, if I use the
Much ado about nothing ;-)
On Apr 10, 2012, at 11:20 AM, Patrick Robinson wrote:
Thanks again for that. I hadn't realized it was that easy, or I'd have done
it myself. Maybe next time! :-)
- Patrick
On Apr 10, 2012, at 2:15 PM, Amedeo Mantica wrote:
I originally replaced the
Hey Chuck,
I know this is a little late, but I'd like to see something about...
- Best way to handle freshness across multiple instances.
- How best to do operations not handled by fetch specs. (e.g. group by,
adding a column that needs to come from another data source [like an
Hi Henrique,
On 11/04/2012, at 2:46 AM, Henrique Prange wrote:
Properties files are not loaded when tests are executed by JUnit. There is an
issue [1] for that problem.
I was obviously imagining it yesterday when I wrote I can see the properties
get picked up at launch. You're right
There is a section of the link:
http://wiki.wocommunity.org/display/WO/Adding+a+Normal+WOComponent+Page+to+an+ERModernLook+based+application
If I read this I need to create the DownloadIsCompletePage as a D2W component
with the factory method in:
public class FileTaskDownloadController
On 11/04/2012, at 3:31 AM, Amedeo Mantica wrote:
I have patched WOComponentRequestHandler and created a pull request in the
wonder/integration branch
then you will set the property:
ERXDirectComponentAccessAllowed=false
You might want to add that property to the default project
On Apr 7, 2012, at 8:07 PM, Henrique Prange wrote:
Suppose you have a Service interface and a BasicService implementation for
it. This Service is required across your components. So you have something
like this:
class ComponentOne {
Service service = new BasicService();
}
33 matches
Mail list logo
