Hi All,
We have a project called the Enterprise Sign On Engine (
http://esoeproject.org ) which is an Apache 2.0 licensed platform for
authentication, authorization and accountability for both internal
enterprise users and federated contexts. About 4 months ago I talked to
some of you on this list and there was some interest in integration, we
are now in a position to really try and bring this forward.
With ESOE integrated into Xwiki you would automatically get the benefits
of using openID and Shibboleth. Xwiki would also get our ability to do
true single sign on from Active Directory enabled enterprise clients. We
also have a very powerful XACML based authorization engine which allows
some really unique flexibility in providing access control to content.
All said and done we are trying to provide a clean general purpose
solution to identity and federation that can be used across many
products without needing to continually reimplement this kind of thing.
You don't have to write your own database for every application you
create we believe it should and can be the same way with identity.
We intend to support further technologies in the future such as Yahoo's
BBAuth and Microsofts Identity Card. The really neat thing is that the
application side doesn't need to be changed at all when these new
options come on board for end users.
Please take a look around the website and I would really like to talk
further with you guys if there is an interest in doing some work together.
regards,
Bradley
--
Bradley Beddoes
Lead Software Architect
Intient
http://intient.com - "Building intelligent open source solutions for
your enterprise"
Hi everyone,
I'd like to propose voting Thomas Mortagne as a XWiki committer. He's
been sending lots of good patches lately (for the the Core and for
XEM) and his patches show a good understanding of how XWiki works.
He's also working at full steam on XEM and I'm tired of applying his
patches so I propose we let him do it by himself! ;)
Here's my +1.
Note: For full disclosure, Thomas is working for XPertNet, the
company behind the creation of XWiki. FWIW, out of the 23 committers
(http://www.xwiki.org/xwiki/bin/view/Community/HallOfFame), 6 are
working for XPertNet (including myself). Note that we're running
XWiki as a meritocratic project (trying to follow the Apache rules as
much as possible) and thus anyone can become a committer (see http://
www.xwiki.org/xwiki/bin/view/Community/Committership). The more the
merrier!
Thanks
-Vincent
I did the refactoring with IDEA and all went fine but when I
committed SVN failed so I had to commit bit by bit.
I think IDEA's refactoring are not all implemented correctly WRT SVN,
i.e. SVN doesn't support several refactorings on top of one another.
What a pain...
-Vincent
Hi,
I have been trying to build XWiki from source code and follow the instructions from
http://www.xwiki.org/xwiki/bin/view/Community/Building#HCheckingoutthesourc…
but i have difficulties in getting all the souce codes. Though it is possible to obtain the source codes from http://svnmirror.xwiki.org/svn/mirror/xwiki/ , and it is very tedious to donwload the individual files. Furthermore, i can't download the zip file from http://fisheye2.cenqua.com/browse/xwiki/.. Therefore, is there any place where i can download different version of XWiki source codes in a zip file?
Regards
---------------------------------
Real people. Real questions. Real answers. Share what you know.
Hello!
I'm planning the development of the following functionality:
- Running xwiki instance on MySQL;
- There will be an external database (a Datawarehouse to be more
precise), with business indicators
- If any of the indicators reached a predefined limit value, I' d like
to have my xwiki generate a document with information about this event and
send an e-mail alert to the administrator (or other users)
My strategy may be to create a IndicatorClass with some properties like
name, description, businessarea, currentvalue, limitvalue, externalTable,
externalColumn etc. Then I'll have to update these indicators on a regular
basiis, which I could do with a procedure that will check the external
database and get the latest values. For those which reached the limit
values, I'd like to generate automaticaly a document (of the class Risk for
instance) and send an e-mail to warn of these risks.
What do you think? Maybe a plugin could be a more structured way of doing
this...
Thanks in advance for your tips :)
Bye,
Ricardo.
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
Hi,
I'm about to commit the Application Manager from Thomas Mortagne. He
has partially implemented this idea: http://www.xwiki.org/xwiki/bin/
view/Design/ApplicationManager
It's composed of 2 modules:
- a plugin
- a set of documents (XAR)
It allows to create applications inside a wiki by creating a page
which acts as an Application Descriptor and which contains definition
of all documents in an application, the version of the application,
etc. It also allows to export an application as a XAR file (a
standard XAR + this Application Descriptor). All in all it has 2-3
pages for managing applications, listing installed applications, etc.
I'm going to do the following:
1) Commit his work in platform/plugins and platform/applications
2) Document it on xwiki.org in the Applications section of the Code Zone
Later on, I think we could start using it for splitting XE into
separate applications.
Just to let you know. As usual let me know if you think there's a
problem.
Thanks
-Vincent
Hi,
With the 1.1M3 release we have currently only released a hsql version
of the platform WAR. That war only includes the HSQL JAR but not the
driver JARS for other DBs.
In our current build we can generate the platform WAR for other DBs
using for ex: mvn install -Pmysql. That includes the driver JAR for
that DB.
Before we were bundling all driver JARs into our WAR so our users may
be a bit confused and we need to decide on the strategy we want to
have. I can see 3 possible strategies:
1) 1 WAR per database
- We could start by releasing only 2 WARs: one for HSQL and one for
MySQL. I don't think we need more and releasing more is going to be a
pain as each WAR weights 40MB.
2) 1 WAR with everything
- Cons: having all these DB drivers makes our WAR fatter
- Possible solution: we only release the HSQL and MySQL drivers
3) 1 empty WAR
I feel 3) might actually be the best solution for the following reasons:
- if the user is non technical he'll install the standalone version
- if the user is technical it means he shouldn't have any problem
following install instructions that tell him to download such driver
at such location and put it in WEB-INF/lib
- we only release one common WAR and our XWiki Platform is
environment independent (which is a new property to have I think)
- releasing one WAR makes our release process simpler (only 40MB to
release once)
WDYT?
Thanks
-Vincent