Send Webobjects-dev mailing list submissions to
email@hidden
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.apple.com/mailman/listinfo/webobjects-dev
or, via email, send a message with subject or body 'help' to
email@hidden
You can reach the person managing the list at
email@hidden
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Webobjects-dev digest..."
Today's Topics:
1. Re: Resetting the admin password in OpenBase 7.x?
(Elizabeth Lynch)
2. security and redirects (Greg Kick)
3. Re: security and redirects (MacFirst)
4. Re: security and redirects (Bob Stuart)
5. Re: Quicktime - SMILE - WO ? (Josh Paul)
6. Caching reference data (Jason McInnes)
7. Re: Caching reference data (Ben Ketteridge)
8. Re: Caching reference data (Jason McInnes)
9. Re: Caching reference data (Ben Ketteridge)
----------------------------------------------------------------------
Message: 1
Date: Sat, 16 Oct 2004 20:23:54 +0100
From: Elizabeth Lynch <email@hidden>
Subject: Re: Resetting the admin password in OpenBase 7.x?
To: email@hidden
Cc: email@hidden
Message-ID: <email@hidden>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Jason
You almost certainly need to install OpenBase 8 (latest version,
downloadable from www.openbase.com; pick up a free personal license on
the site as well).
The version of OpenBase that comes with WebObjects 5.2 is still version
7, which works fine under Mac OS X Jaguar. However, if you're using
Panther then OpenBase 7 needs to be upgraded to OpenBase 8.
Liz
On 16 Oct 2004, at 19:05, Jason Garman wrote:
Quick question for all you WebObjects experts-
As part of the premiere ADC membership we have at work, I received a
copy
of the WebObjects 5.2 package in the mail the other day, and wanted to
give it a whirl. For ease of set up I just wanted to use the built in
OpenBase database -- as I'm not really doing anything fancy yet.
However, whenever I try to connect to one of the built in databases
(WOPetStoreX, etc) or create a new database and connect to it, the
OpenBase manager application refuses any password specified for the
'admin' user. As I understand it, I should be able to simply hit
enter
for the password-- as there is none set, yet this is refused as well?
Thanks for any help,
--
Jason Garman / email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden
------------------------------
Message: 2
Date: Sun, 17 Oct 2004 03:16:47 -0700
From: Greg Kick <email@hidden>
Subject: security and redirects
To: WebObjects (Group) <email@hidden>
Message-ID: <email@hidden>
Content-Type: text/plain; charset=US-ASCII; format=flowed
I am trying to implement a system for securing components in which the
components that are restricted are listed in an xml file. The
application reads that file and if a user tries to access a component
listed without having authenticated the application will redirect
him/her to a login page. I have gotten the xml portion and the
comparison to work without any problems, but i am having trouble
finding a way to implement the redirect. Also, I want the redirect to
happen before the construction of the restricted component if possible.
I have tried diverting the process at just about every point in the
request-response loop I can find, but so far, no luck. Any
suggestions?
Greg
------------------------------
Message: 3
Date: Sun, 17 Oct 2004 08:30:15 -0700
From: MacFirst <email@hidden>
Subject: Re: security and redirects
To: WOdev <email@hidden>
Message-ID: <BD97DE17.2ABDA%email@hidden>
Content-Type: text/plain; charset="US-ASCII"
on 10/17/04 3:16 AM, Greg Kick <email@hidden> went on and on saying,
in
part:
I am trying to implement a system for securing components in which the
components that are restricted are listed in an xml file. The
application reads that file and if a user tries to access a component
listed without having authenticated the application will redirect
him/her to a login page. I have gotten the xml portion and the
comparison to work without any problems, but i am having trouble
finding a way to implement the redirect. Also, I want the redirect to
happen before the construction of the restricted component if
possible.
I have tried diverting the process at just about every point in the
request-response loop I can find, but so far, no luck. Any
suggestions?
Wouldn't you just do something like:
public WOComonent myAction() {
if (userIsLoggedIn())
setSecurePageMode();
else
setLoginPageMode();
return null;
}
Or
public WOComonent myAction() {
WOComponent nextPage = null;
if (userIsLoggedIn())
nextPage = PageWithName ("MySecurePage");
else
nextPage = PageWithName ("LoginPage");
return nextPage;
}
? This sounds very straightforward -- am I misunderstanding the
problem?
------------------------------
Message: 4
Date: Sun, 17 Oct 2004 11:55:34 -0400
From: Bob Stuart <email@hidden>
Subject: Re: security and redirects
To: Greg Kick <email@hidden>, WebObjects (Group)
<email@hidden>
Message-ID: <a06002007bd984315ca52@[192.168.200.5]>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
To achieve this I used a interface LoginRequiredInterface and check
during pageWithName. loginTest just does whatever on session is
required for proving the user is logged in. You could do the same
just checking the pageName against the list of protected pages. I
throw during pageWithName so that I get to handleException returning
the login page. I didn't return the login page during pageWithName
since it might be a subcomponent and really messed up runtime cast
problems.
pseudo code there was a lot of other stuff I ripped out. Not sure
this compiles but should explain the concept.
In Application
public WOComponent pageWithName(String name, WOContext context){
pageToReturn = super.pageWithName(name,context);
if ((pageToReturn instanceof LoginRequiredInterface) &&
( session == null || !session.loginTest() ){
throw new LoginException(); }
}
return pageToReturn;
}
public WOResponse handleException(Exception anException,
WOContext aContext){
WOResponse responseToReturn;
if (anException instanceof LoginException){
responseToReturn =
super.pageWithName("Login",aContext).generateResponse();
} else {
responseToReturn =
super.handleException(anException, aContext);
}
return responseToReturn;
}
At 3:16 AM -0700 10/17/04, Greg Kick wrote:
I am trying to implement a system for securing components in which
the components that are restricted are listed in an xml file. The
application reads that file and if a user tries to access a
component listed without having authenticated the application will
redirect him/her to a login page. I have gotten the xml portion and
the comparison to work without any problems, but i am having trouble
finding a way to implement the redirect. Also, I want the redirect
to happen before the construction of the restricted component if
possible. I have tried diverting the process at just about every
point in the request-response loop I can find, but so far, no luck.
Any suggestions?
Greg
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden
--
Bob Stuart
------------------------------
Message: 5
Date: Sun, 17 Oct 2004 09:25:30 -0700
From: Josh Paul <email@hidden>
Subject: Re: Quicktime - SMILE - WO ?
To: Yves Dufour <email@hidden>,
<email@hidden>
Message-ID: <BD97EB0A.7BE5%email@hidden>
Content-Type: text/plain; charset="US-ASCII"
My opinion is that Apple only has so many resources and the WO team is
being
used for projects in addition WO. Whether it's the Music Store, Core
Data or
something else, only Apple knows. So, even when they are working on WO,
there are features like "Direct to XXX" which are much more of a
priority
than Quicktime.
That being said, I think QT was integrated initially simply because it
was
an Apple technology and it was easy to implement. The OTCQuicktime
component
should fill in where Apple has left off and you should be able to
extend it,
as well.
Best,
Josh
On 10/16/04 11:10 PM, "Yves Dufour" <email@hidden> wrote:
You either need to write a method for each binding:
hotspot1: method1
hotspot2: method2
hotspot3: method3
or look at how I implemented the QTNEXT tag in OTCQuicktime, which
iterates
over an array and builds the bindings at runtime.
Thanks Josh, That's what I am going to do as I need to access hotspots
from various selected QTVR movies.
My msg to the list and so few feedback confirm what I suggested...
QTVR/Qt in WO are quite deserted by Apple
time to look for Java applets like PTViewer , isn't it ?
Erwin
"The best proof that there's intelligent life in the universe is that
it hasn't come here." Arthur C. Clarke
------------------------------
Message: 6
Date: Sun, 17 Oct 2004 09:57:56 -0700 (PDT)
From: Jason McInnes <email@hidden>
Subject: Caching reference data
To: email@hidden
Message-ID: <email@hidden>
Content-Type: text/plain; charset=us-ascii
I've got a requirements issue...challenge...that
involves caching.
I've gone 10 or 11 reference types in my model. I have
a requirement that I need to track the last user to
update reference types. What I did originally is I
added relationships between these reference types and
my user entity (add user, update user). Actually,
almost all of my entities inherit from a core entity
that has these relationships.
The problem now is that I was fetching these reference
types into the shared editing context like a good boy,
but like a bad boy, they have relationships to
non-shared entities (i.e., the users). So when I
create an object, log out, and log back in I get a
shared entity context violation error.
I want the benefit of caching these reference types
without the overhead of having to do the
localInstanceOfObject step storing them in arrays on
my Application object, and I'd like to not have to
change my model (e.g., storing just the user name on
reference types rather than a relationship to user).
Am I out of luck?
=====
Jason McInnes
2 Degrees
Cell: 206.849.3680
Email: email@hidden
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
------------------------------
Message: 7
Date: Sun, 17 Oct 2004 19:01:18 +0100
From: Ben Ketteridge <email@hidden>
Subject: Re: Caching reference data
To: Jason McInnes <email@hidden>
Cc: email@hidden
Message-ID: <email@hidden>
Content-Type: text/plain; charset=US-ASCII
On Sun, 17 Oct 2004 09:57:56 -0700 (PDT), Jason McInnes
<email@hidden> wrote:
I want the benefit of caching these reference types
without the overhead of having to do the
localInstanceOfObject step storing them in arrays on
my Application object, and I'd like to not have to
change my model (e.g., storing just the user name on
reference types rather than a relationship to user).
Am I out of luck?
Yes, basically.
If you want the power of WORelationships that change every time the
object changes, then, clearly, the object is not truly static.
Therefore, it does not belong in the EOSharedEditingContext. Such a
Context is for 'true' static data that never* changes.
*Well, almost always never... you can use localInstanceOfObject on the
rare occassion that the reference data changes, but the existing
shared instances may well not get the updates without being refreshed.
Hmmm, sounds to me like a case for a maintenance program to maintain
'reference data' outside the main program.
$0.02,
Ben Ketteridge
ps. caveat - I've not used EOSharedEditingContexts for a few years,
though maybe I ought to reconsider adding such optimisations to our
static data.
--
| Ben Ketteridge email@hidden, aka Gremlin |
| It is by caffeine alone that I set my mind in motion. |
| It is by the coffee that the thoughts acquire speed, |
| the lips acquire stains, the stains become a warning. |
| It is by caffeine alone that I set my mind in motion. |
------------------------------
Message: 8
Date: Sun, 17 Oct 2004 11:13:36 -0700 (PDT)
From: Jason McInnes <email@hidden>
Subject: Re: Caching reference data
To: Ben Ketteridge <email@hidden>
Cc: email@hidden
Message-ID: <email@hidden>
Content-Type: text/plain; charset=us-ascii
You're right that the data isn't truly static -
although it will change very, very rarely.
Unfortunatley, even if I had a separate application to
manage the reference data, I'd still have the same
problem because the reference entities still point to
a dynamic entity, namely, the user entity.
I'm pretty sure I'll have to implement my own caching
scheme because of my model. Sigh. If anyone has any
suggestions or gotchas, I'd love to hear them.
Jason
--- Ben Ketteridge <email@hidden> wrote:
On Sun, 17 Oct 2004 09:57:56 -0700 (PDT), Jason
McInnes
<email@hidden> wrote:
I want the benefit of caching these reference
types
without the overhead of having to do the
localInstanceOfObject step storing them in arrays
on
my Application object, and I'd like to not have to
change my model (e.g., storing just the user name
on
reference types rather than a relationship to
user).
Am I out of luck?
Yes, basically.
If you want the power of WORelationships that change
every time the
object changes, then, clearly, the object is not
truly static.
Therefore, it does not belong in the
EOSharedEditingContext. Such a
Context is for 'true' static data that never*
changes.
*Well, almost always never... you can use
localInstanceOfObject on the
rare occassion that the reference data changes, but
the existing
shared instances may well not get the updates
without being refreshed.
Hmmm, sounds to me like a case for a maintenance
program to maintain
'reference data' outside the main program.
$0.02,
Ben Ketteridge
ps. caveat - I've not used EOSharedEditingContexts
for a few years,
though maybe I ought to reconsider adding such
optimisations to our
static data.
--
| Ben Ketteridge email@hidden, aka
Gremlin |
| It is by caffeine alone that I set my mind in
motion. |
| It is by the coffee that the thoughts acquire
speed, |
| the lips acquire stains, the stains become a
warning. |
| It is by caffeine alone that I set my mind in
motion. |
=====
Jason McInnes
2 Degrees
Cell: 206.849.3680
Email: email@hidden
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
------------------------------
Message: 9
Date: Sun, 17 Oct 2004 19:18:08 +0100
From: Ben Ketteridge <email@hidden>
Subject: Re: Caching reference data
To: Jason McInnes <email@hidden>
Cc: email@hidden
Message-ID: <email@hidden>
Content-Type: text/plain; charset=US-ASCII
It occurs to me that you could solve this by storing the user id of
the user in the reference data and implementing a very simple getter
(caching in private instance variables if you like) to simulate the
relationship - then you can put your reference data in the EOSharedEC
and the users remain in the EOECs.
Not difficult, and not exactly the WO-Way... but it should work :)
Ben Ketteridge
On Sun, 17 Oct 2004 11:13:36 -0700 (PDT), Jason McInnes
<email@hidden> wrote:
You're right that the data isn't truly static -
although it will change very, very rarely.
Unfortunatley, even if I had a separate application to
manage the reference data, I'd still have the same
problem because the reference entities still point to
a dynamic entity, namely, the user entity.
I'm pretty sure I'll have to implement my own caching
scheme because of my model. Sigh. If anyone has any
suggestions or gotchas, I'd love to hear them.
Jason
--- Ben Ketteridge <email@hidden> wrote:
On Sun, 17 Oct 2004 09:57:56 -0700 (PDT), Jason
McInnes
<email@hidden> wrote:
I want the benefit of caching these reference
types
without the overhead of having to do the
localInstanceOfObject step storing them in arrays
on
my Application object, and I'd like to not have to
change my model (e.g., storing just the user name
on
reference types rather than a relationship to
user).
Am I out of luck?
Yes, basically.
If you want the power of WORelationships that change
every time the
object changes, then, clearly, the object is not
truly static.
Therefore, it does not belong in the
EOSharedEditingContext. Such a
Context is for 'true' static data that never*
changes.
*Well, almost always never... you can use
localInstanceOfObject on the
rare occassion that the reference data changes, but
the existing
shared instances may well not get the updates
without being refreshed.
Hmmm, sounds to me like a case for a maintenance
program to maintain
'reference data' outside the main program.
$0.02,
Ben Ketteridge
ps. caveat - I've not used EOSharedEditingContexts
for a few years,
though maybe I ought to reconsider adding such
optimisations to our
static data.
--
| Ben Ketteridge email@hidden, aka
Gremlin |
| It is by caffeine alone that I set my mind in
motion. |
| It is by the coffee that the thoughts acquire
speed, |
| the lips acquire stains, the stains become a
warning. |
| It is by caffeine alone that I set my mind in
motion. |
=====
Jason McInnes
2 Degrees
Cell: 206.849.3680
Email: email@hidden
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
--
| Ben Ketteridge email@hidden, aka Gremlin |
| It is by caffeine alone that I set my mind in motion. |
| It is by the coffee that the thoughts acquire speed, |
| the lips acquire stains, the stains become a warning. |
| It is by caffeine alone that I set my mind in motion. |
------------------------------
_______________________________________________
Webobjects-dev mailing list
email@hidden
http://lists.apple.com/mailman/listinfo/webobjects-dev
End of Webobjects-dev Digest, Vol 1, Issue 55
*********************************************