Pretty sure it just means that they have fully integrated Acegi into
spring as opposed to it being a separate project.
Nice work to Andrea for picking Acegi as our security framework :).
Arne Kepp wrote:
> No idea what that means for us, yet:
>
> http://www.springframework.org/node/627
>
> -Ar
No idea what that means for us, yet:
http://www.springframework.org/node/627
-Arne
ps. I'm somewhat amused that their website is running Drupal / PHP ;P
-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Andrea Aime ha scritto:
> Hi all,
> so I switched all read only tests on trunk to "one time setup". This
> made it so that the time required for building geoserver on my machine
> halved, going down to 3 minutes 30 seconds (I have the wfsv online tests
> running that do take 30 seconds and that mos
Unfortunate stack trace of imminent dm!
---
Key: GEOS-1875
URL: http://jira.codehaus.org/browse/GEOS-1875
Project: GeoServer
Issue Type: Bug
Affects Versions: 1.6.3
Reporter: Jody G
Andrea Aime ha scritto:
> Hi all,
> so I switched all read only tests on trunk to "one time setup". This
> made it so that the time required for building geoserver on my machine
> halved, going down to 3 minutes 30 seconds (I have the wfsv online tests
> running that do take 30 seconds and that mos
Justin Deoliveira ha scritto:
> The wfs spec says that when an attribute is null it should be committed
> as a property, instead of included an empty. I am not sure the latter is
> valid.
Right right... yet, what if for any strange reason the user really
wanted to provide an empty string as the
The wfs spec says that when an attribute is null it should be committed
as a property, instead of included an empty. I am not sure the latter is
valid.
However, I would say we should be lax in this case, I have run into the
same issue with openlayers wfs client as well.
Jesse Eichar wrote:
> W
Andrea Aime ha scritto:
> Hi all,
> so I switched all read only tests on trunk to "one time setup". This
> made it so that the time required for building geoserver on my machine
> halved, going down to 3 minutes 30 seconds (I have the wfsv online tests
> running that do take 30 seconds and that mos
See http://gridlock.openplans.org:8080/hudson/job/geoserver-trunk/88/changes
-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use p
Hi all,
so I switched all read only tests on trunk to "one time setup". This
made it so that the time required for building geoserver on my machine
halved, going down to 3 minutes 30 seconds (I have the wfsv online tests
running that do take 30 seconds and that most of you don't have enabled
I gues
Andrew Hughes ha scritto:
...
> Hum, ok, but I don't know how to push a .war onto a repository... I'm
> not even sure we would like to do so. Each .war is 30MB, we'd have to
> make sure the .war are pushed onto the repo only during the release
> process (as opposed to publishing the
See http://gridlock.openplans.org:8080/hudson/job/geoserver-trunk/87/changes
Changes:
[aaime] GEOS-1874, Switch all read only tests to a one time setup architecture
[simboss] -minor clean up of unused read parameters
-improve code readability
[simboss] -tentative on GEOS-1868
-
Switch all read only tests to a "one time setup" architecture
-
Key: GEOS-1874
URL: http://jira.codehaus.org/browse/GEOS-1874
Project: GeoServer
Issue Type: Improvement
Affects
On Tue, Apr 15, 2008 at 5:16 PM, Andrea Aime <[EMAIL PROTECTED]> wrote:
> Andrew Hughes ha scritto:
>
> > Hi Guys,
> >
> > I've looked into this a little and found a few things out...
> >
> > 1. A war can most certainly be a dependency, and dependency:unpack
> > can be used to unpack it (pr
Problem adding new features using WFS-T
---
Key: GEOS-1873
URL: http://jira.codehaus.org/browse/GEOS-1873
Project: GeoServer
Issue Type: Bug
Components: WFS
Affects Versions: 1.6.3
Will do.
On 15-Apr-08, at 9:49 AM, Andrea Aime wrote:
> Jesse Eichar ha scritto:
>> Hi,
>> I've done some research for a uDig user. For Geoserver 1.6.3 uDig
>> can't add new features to a postgis via the WFS-T protocol. I've
>> tested 1.5.4 and it work fine. The problem seems to be an xml
Jesse Eichar ha scritto:
> Hi,
>
> I've done some research for a uDig user. For Geoserver 1.6.3 uDig can't
> add new features to a postgis via the WFS-T protocol. I've tested 1.5.4
> and it work fine. The problem seems to be an xml parsing problem.
> Seems the same problem occurs when editin
Andrew Hughes ha scritto:
> Hi Guys,
>
> I've looked into this a little and found a few things out...
>
>1. A war can most certainly be a dependency, and dependency:unpack
> can be used to unpack it (providing the dependency is hosted in a
> repository).
Hum, ok, but I don't know
18 matches
Mail list logo
