Great Margo! Maven support on Swiz was always a need and the swiz team
never set up the pom.xml, so hope you'll find it helpful.
As to the rest of people, if you have something in the future to share
regarding swiz, please consider this fork. We could make this fork
progress and maintain for the t
I'd like to second the THANK YOU. I use swiz extensively in my projects
and really appreciate the inclusion.
Regards
Margo
On 10/20/2012 3:45 PM, Carlos Rovira wrote:
You're welcome! great to see interest in this two little upgrades on the forks
:)
Carlos
2012/10/19 dude :
Just wanted to
You're welcome! great to see interest in this two little upgrades on the forks
:)
Carlos
2012/10/19 dude :
> Just wanted to *Thank You* for your work and for sharing this. The
> timing is just perfect, we're currently looking into upgrading to
> hibernate 4.1.
>
> Cheers
>
>
> Am 15.10.2012 12
Just wanted to *Thank You* for your work and for sharing this. The
timing is just perfect, we're currently looking into upgrading to
hibernate 4.1.
Cheers
Am 15.10.2012 12:19, schrieb Carlos Rovira:
> Hi,
>
> I think it would be worth to share here two forked projects in github
> that are almos
You're welcome Nick! :),
taking into account that sharing is so easy with github, we call to
arms to all the people wants to share things on our fork. As we really
depend on swiz for our business we are sure we will (at least)
maintain our fork to continue working.
Best,
Carlos
2012/10/17 Nick
Thank you very much for your contribution. I love Swiz and was sad to
see its owners give up on the project, even though I understand their
reasons why.
On Mon, Oct 15, 2012 at 5:19 AM, Carlos Rovira
wrote:
> Hi,
>
> I think it would be worth to share here two forked projects in github
> that are
Hi,
I think it would be worth to share here two forked projects in github
that are almost dead nowadays. Mostly maintenance upgrades highly
needed for our business that we decided to share with people with the
same need:
* spring-flex : Our version brings support for Hibernate 4.1
* swiz-framewo
akagaki
>
>
> 2012/7/27 Franck Wolff :
>> Stefan,
>>
>> Did you consider using GraniteDS (http://www.graniteds.org) instead of
>> BlazeDS? It has a lot of interesting features you won't find in BlazeDS, it
>> is actively developed and commercial suppo
Hi, Franck.
>
> Is it open-source-software? Is the license like Apache License?
> These things are indispensable requirements.
>
>
> thanks
>
> Shigeru Nakagaki
>
> 2012/7/27 Franck Wolff :
> > Stefan,
> >
> > Did you consider using GraniteDS (http://
Hello Frank
I use GraniteDS on several projects, however, I have some clients using
BlazeDS, because this I have some doubts about its future.
Regards
Stefan Horochovec
Software Engineer
Blog: http://www.horochovec.com.br/
Twitter: http://twitter.com/horochovec
2012/7/26 Franck Wolff
Hi, Franck.
Is it open-source-software? Is the license like Apache License?
These things are indispensable requirements.
thanks
Shigeru Nakagaki
2012/7/27 Franck Wolff :
> Stefan,
>
> Did you consider using GraniteDS (http://www.graniteds.org) instead of
> BlazeDS? It has a lot of
Hi, Franck.
Is it open-source-software? Is the license like Apache License?
These things are indispensable requirements.
thanks
Shigeru Nakagaki
2012/7/27 Franck Wolff :
> Stefan,
>
> Did you consider using GraniteDS (http://www.graniteds.org) instead of
> BlazeDS? It
Stefan,
Did you consider using GraniteDS (http://www.graniteds.org) instead of
BlazeDS? It has a lot of interesting features you won't find in BlazeDS, it
is actively developed and commercial support is available through
subscriptions (http://www.granitedataservices.com).
Franck Wolff.
2
Great news Rohit!
Thanks
Stefan Horochovec
Software Engineer
Blog: http://www.horochovec.com.br/
Twitter: http://twitter.com/horochovec
2012/7/26 Rohit Kumar
> Work is underway to donate BlazeDS to Apache.
>
> Rohit
>
> -Original Message-
> From:
Work is underway to donate BlazeDS to Apache.
Rohit
-Original Message-
From: Stefan Horochovec [mailto:stefan.horocho...@gmail.com]
Sent: Thursday, July 26, 2012 8:18 PM
To: flex-dev@incubator.apache.org
Subject: Re: BlazeDS status
Hello Rohit
I would also like to know more
Hi, Rohit.
It's status of the donation.
Shigeru Nakagaki
2012/7/26 Rohit Kumar :
> Hi Shigeru,
>
> Can you elaborate what you want to know about BlazeDS?
>
> Rohit
>
> -Original Message-
> From: pepe.f...@gmail.com [mailto:pepe.f...@gmail.com] On Behalf
Hello Rohit
I would also like to know more information about the progress of
BlazeDS. Recently you make a post on the Adobe forums about donation the
project to Apache but after that had no news.
The process is underway?
Best regards
Stefan Horochovec
Software Engineer
Blog: http
I have seen nothing new beyond what is on Adobe's forum:
http://forums.adobe.com/message/4373089#4373089
Posted a question there about status of the donation
On 7/25/2012 10:04 PM, Shigeru Nakagaki wrote:
Hi.
This subject might not be fit here. But my client wants to know
current status very m
Hi Shigeru,
Can you elaborate what you want to know about BlazeDS?
Rohit
-Original Message-
From: pepe.f...@gmail.com [mailto:pepe.f...@gmail.com] On Behalf Of Shigeru
Nakagaki
Sent: Thursday, July 26, 2012 10:35 AM
To: flex-dev@incubator.apache.org
Subject: BlazeDS status
Hi.
This
Hi.
This subject might not be fit here. But my client wants to know
current status very much.
Any information?
thanks
Shigeru Nakagaki
t: Freitag, 25. Mai 2012 15:12
> An: flex-dev@incubator.apache.org
> Betreff: Re: blazeds
>
> I can also vouch for GraniteDS as a replacement for BlazeDS/LCDS. I'm using
> it in a big project and I have nothing to complain about. We have their
> Enterprise Support package and the response on issues is extremely fast and
> professional.
Mai 2012 15:12
An: flex-dev@incubator.apache.org
Betreff: Re: blazeds
I can also vouch for GraniteDS as a replacement for BlazeDS/LCDS. I'm using it
in a big project and I have nothing to complain about. We have their Enterprise
Support package and the response on issues is extremely fast and professional.
I can also vouch for GraniteDS as a replacement for BlazeDS/LCDS. I'm using
it in a big project and I have nothing to complain about. We have their
Enterprise Support package and the response on issues is extremely fast and
professional.
lking about BlazeDS).
2012/5/24 filippo dipisa
> there are conflictiing annotations so I don't see an easy way to integhrate
> it, and I never had any problem with blazeds + dphibernate + custom
> extensions
>
> If I wasn't happy with blazeds I'd go probably for the pi
there are conflictiing annotations so I don't see an easy way to integhrate
it, and I never had any problem with blazeds + dphibernate + custom
extensions
If I wasn't happy with blazeds I'd go probably for the pimento dataservice
that offers the same as graniteds
On 24 May 2
e used in enterprise development
>
>
> On 24 May 2012 10:15, John Fletcher wrote:
>
> > 2012/5/24 Michael Montoya
> >
> > > GraniteDS is as very valid replacement for BlazeDS in case you are
> > looking
> > > for alternatives.
> > >
> >
>
> the problem of graniteds is that I had many problem in integrating it with
> parsley that it is quite used in enterprise development
In my experience the mailinglist for GraniteDS is very active and quick to
help.
cheers,
Roland
the problem of graniteds is that I had many problem in integrating it with
parsley that it is quite used in enterprise development
On 24 May 2012 10:15, John Fletcher wrote:
> 2012/5/24 Michael Montoya
>
> > GraniteDS is as very valid replacement for BlazeDS in case you are
>
2012/5/24 Michael Montoya
> GraniteDS is as very valid replacement for BlazeDS in case you are looking
> for alternatives.
>
GraniteDS is more feature-complete than BlazeDS. It's more like Livecycle.
It's worth questioning whether BlazeDS should really be integrated into
Fle
I know graniteds but the annotations conflicts with the parsley ones.
I always used blazeds and dphibernate and they work quite well.
I gave a go also to pimento but I still prefer blazeds.
I saw on the dphibernate website that is deprecated...why?
I think would be nice to continue the development
GraniteDS is as very valid replacement for BlazeDS in case you are looking for
alternatives.
On May 22, 2012, at 3:08 PM, Om wrote:
> Relevant:
>
> http://markmail.org/thread/j4mzs6i4h22vihcc
> http://blogs.adobe.com/rohit/2012/05/03/donating-blazeds-to-apache-software-founda
Relevant:
http://markmail.org/thread/j4mzs6i4h22vihcc
http://blogs.adobe.com/rohit/2012/05/03/donating-blazeds-to-apache-software-foundation/
http://forums.adobe.com/message/4371894#4371894
Thanks,
Om
On Tue, May 22, 2012 at 10:21 AM, filippo dipisa wrote:
> tks
>
> On 22 May 2
tks
On 22 May 2012 18:02, Nicholas Kwiatkowski wrote:
> BlazeDS is not apart of the Apache Foundation at this time (neither as
> a separate project, nor ours). It is currently being hosted by Adobe
> OpenSource on Sourceforge (
> http://sourceforge.net/adobe/blazeds/wiki/Home/
BlazeDS is not apart of the Apache Foundation at this time (neither as
a separate project, nor ours). It is currently being hosted by Adobe
OpenSource on Sourceforge ( http://sourceforge.net/adobe/blazeds/wiki/Home/
)
The owner of that project has been putting out the feelers to donate it to
Hi Guys,
is BlazeDS already part of the Apache foundation?
If yes can you give me the git or svn url please?
Thanks
Filippo
Some folks on the BlazeDS are starting to find cycles to look into the donation
of BlazeDS to Apache. They want to try one more time to determine if there is
enough of a community to try to incubate as its own podling or whether to
donate the source code to the Apache Flex podling. If you are
T, PPTX, XLSX, SWF,
and PNG output. These are served with JSP, HTML and Java servlets on Apache
Tomcat. The SWF creation is via Transform SWF from PS pages. We've contributed
to Apache POI including some graphic support in PPT, PPTX, and XLSX generation
in Java.
Having an available BlazeDS s
s.org
>>
>>
>> -- Sebastian
>>
>>
>>
>> On Jan 8, 2012, at 12:24 PM, Sebastian Mohr wrote:
>>
>>> Hi BlazeDS guys,
>>>
>>> Is there any interest to merge with GraniteDS at some stage?
>>>
>>> http://w
On 1/10/12 1:14 AM, "João Fernandes"
wrote:
> BTW Alex, is Adobe having someone to keep contributing to BlazeDS once
> it's an Apache (sub-)Project?
>
> João Fernandes
One could argue that BlazeDS never had any dedicated staff. It is
effectively the underpinnin
tage in future?
>
> http://www.graniteds.org
>
>
> -- Sebastian
>
>
>
> On Jan 8, 2012, at 12:24 PM, Sebastian Mohr wrote:
>
> > Hi BlazeDS guys,
> >
> > Is there any interest to merge with GraniteDS at some stage?
> >
> > http://www.graniteds.o
Sorry again,
Any interest to merge with GraniteDS at some stage in future?
http://www.graniteds.org
-- Sebastian
On Jan 8, 2012, at 12:24 PM, Sebastian Mohr wrote:
> Hi BlazeDS guys,
>
> Is there any interest to merge with GraniteDS at some stage?
>
> http://ww
BTW Alex, is Adobe having someone to keep contributing to BlazeDS once
it's an Apache (sub-)Project?
João Fernandes
If it comes to choose between having the BlazeDS project under Flex and
leaving it alone to die then I would personally agree with the above
statements. Bring it in Flex for now.
Either way, if the project evolves on its own then it might be possible to
separate the two. Am I missing something
on this. I'd rather have BlazeDS integrated into the Apache
Flex project, at least for now, than have it die alone as a separate Apache
project. As badly as I want to see BlazeDS evolve I cannot commit as an
initial commiter for a separate project, but I think that we could find a
way to
On Mon, Jan 9, 2012 at 6:46 AM, Alex Harui wrote:
> On 1/8/12 8:55 AM, "Doug Arthur" wrote:
>
>> Last thing on this note, if we do bring BlazeDS into Apache Flex, how will
>> release management take place, and how will the product remain to be its
>> own within
On 1/8/12 8:55 AM, "Doug Arthur" wrote:
> Last thing on this note, if we do bring BlazeDS into Apache Flex, how will
> release management take place, and how will the product remain to be its
> own within another product? Especially since its an a optional server-side
>
On Jan 8, 2012 12:31 AM, "Alex Harui" wrote:
>
> Hi Doug,
>
> Do you have any idea what you would contribute?
I'm not sure off the top of my head, but I do know in the past, I have had
the need for customizing BlazeDS and had to monkey patch the rpc
components. I belie
terøe [mailto:yoji...@gmail.com]
Sent: Saturday, January 07, 2012 5:02 AM
To: flex-dev@incubator.apache.org
Subject: Re: BlazeDS
On 6 January 2012 23:39, Alex Harui wrote:
> Adobe promised to contribute BlazeDS to Apache. The question is: should
it be its own project?
It should be its own project IM
Hi BlazeDS guys,
Is there any interest to merge with GraniteDS at some stage?
http://www.graniteds.org
- Sebastian
On Jan 8, 2012, at 10:42 AM, Gary Huitson wrote:
Hi Guys
I think BlazeDS is really important for Flex to survive as an
enterprise product.
Java+Flex seems to be the most
Hi Guys
I think BlazeDS is really important for Flex to survive as an enterprise
product.
Java+Flex seems to be the most common configuration.
I've heard it anecdotally that a large proportion of the enterprise flex
community are java developers.
Hopefully theres a pool of talent there to
Hi Doug,
Do you have any idea what you would contribute? Especially given that
rpc.swc is in the Flex contribution?
Or maybe one goal would be to move rpc.swc to this new project and make it
the umbrella for all server-side work? If we manage to get permission to
contribute parts of LCDS at an
While conceptually, I think that BlazeDS would fit within a project outside
ApacheFlex, in a practical way, until not having much commiters, etc ..., it
should have its place in ApacheFlex until there is enough community interest
and we stand ready to make a full project of it, the risk
I am willing to be an initial committer for this effort.
On Jan 7, 2012 2:52 PM, "Anne Kathrine Petterøe" wrote:
> On 7 January 2012 20:54, Alex Harui wrote:
>
> >> there someone championing the project at ASF?
> > Are you volunteering to be champion?
>
> I cannot champion a project because I am
On 7 January 2012 20:54, Alex Harui wrote:
>> there someone championing the project at ASF?
> Are you volunteering to be champion?
I cannot champion a project because I am not an officer or a member of ASF [1]
> I guess some folks are willing to work on it, but what needs to be done to
> it?
On 1/7/12 2:02 AM, "Anne Kathrine Petterøe" wrote:
> From the top of my head:
> Would you be able to get enough initial committers for a proposal?
That's one thing I'm worried about.
> there someone championing the project at ASF?
Are you volunteering to be champion?
> I don't know how many
On 1/7/12 7:32 AM, "Nicholas Kwiatkowski" wrote:
> Are we getting the FULL rpc.swc with
> it?
RPC is in the Flex donation. I'm not aware that we hide any source for it.
The plan would be to donate what is on the opensource.adobe.com site for
BlazeDS right now, unless w
ridge when we come to it.
>
> Greg
>
I pretty much have two views of this one :
- Flex SDK and Blaze DS are completely different models, and came from
completely different houses. Server Side / Client Side, it came from a
paid product vs. it was always a free product, etc.
They should b
Hi Alex, I also agree with everyone here that BlazeDS should be
proposed as a separated project to Apache.
Did Adobe already defined what are they willing to donate to Apache
Foundation from the BlazeDS stack?
João Fernandes
That's what ipod do with inappropriate hands.
One touch to disaster.
Sorry for spam
And now I need to say something, BlazeDS is also important for company I
work and more or less we depend on it now.
I'm interested in BlazeDS project as much as flex one.
I managed to get deep into all
--
Michal Szczepanski
Flash Platform Developer
www: http://blog.vane.pl
Send from mobile
On 7 sty 2012, at 01:33, "Rui Silva" wrote:
> +1 to what Greg said. And I'd also like to say that I'd be interested in
> participating in BlazeDS.
>
> Original
On 6 January 2012 23:39, Alex Harui wrote:
> Adobe promised to contribute BlazeDS to Apache. The question is: should it
> be its own project?
It should be its own project IMO.
Blaze DS is a server-side product, like Jeffrey also points out.
>
> Mentors, what criteria woul
On Jan 6, 2012 5:19 PM, "Rui Silva" wrote:
>
> +1 to what Greg said. And I'd also like to say that I'd be interested in
> participating in BlazeDS.
>
> Original Message
> > From: "Greg Reddin"
> > Sent:
+1 to what Greg said. And I'd also like to say that I'd be interested in
participating in BlazeDS.
Original Message
> From: "Greg Reddin"
> Sent: sexta-feira, 6 de Janeiro de 2012 23:12
> To: flex-dev@incubator.apache.org
> Subject: Re: BlazeDS
Hi Alex,
my intention is to apply to be a committer has soon as I have the time.
This should happen in few months from now. Although, I would like to
contribute to the standard flex SDK since I think BlazeDS is right now in a
very stable state (as you say if there's only two bugs, we could e
On 1/6/12 3:06 PM, "Carlos Rovira" wrote:
> Separate projects IMO.
>
Carlos, do you expect to be a leader in the BlazeDS community? Unless we
can find some leadership, it is unclear that it can survive as it own
project. I think there are only two open bugs right now. We
Just a newby getting his feet wet...
I agree. Flex is a huge enviorement in itself. Besides, getting started
myself in this community I already feel overwhelmed.
Calvin
On Friday, January 6, 2012, Carlos Rovira
wrote:
> Separate projects IMO.
>
> One project can have dependencies on other pro
On Jan 6, 2012, at 4:06 PM, Jeffry Houser wrote:
>
> I--personally--could care less about BlazeDS and do not forsee myself
> contributing to it any way.
Although I care about Blaze DS...
>
> I would vote for it to be a separate project. Flex and BlazeDS are two very
> d
Separate projects IMO.
One project can have dependencies on other projects and this should not be
a problem. More over if we finaly get maven artifacts ; )
We have to take into account that the Flex ecosystem is huge and should be
in the end many projects with subartifacts in each project (modula
I--personally--could care less about BlazeDS and do not forsee myself
contributing to it any way.
I would vote for it to be a separate project. Flex and BlazeDS are
two very different pieces of software. Does it make sense to combine a
Server side tool and a client side framework into
On Fri, Jan 6, 2012 at 4:39 PM, Alex Harui wrote:
> Mentors, what criteria would you use to determine if Blaze should be its own
> project?
I would say it would be its own project if it has its own distinct
community. The two communities can certainly overlap, but if there's a
significant number
Adobe promised to contribute BlazeDS to Apache. The question is: should it be
its own project? Or should we just check it into the Flex code base somewhere?
I’m asking on this list to see who on this list would want to contribute to
the BlazeDS code. It isn’t clear that it has a strong
71 matches
Mail list logo
