What´s happening with Deltaspike development?

[rafaelmeireles]

The last release of deltaspyke was release in August, 2012. The development still continuous? The project have future?

I was thinking about use my faces CODI, because I don´t see any progres in deltaspike in recent months.

I would like to have an opinion about deltaspike, both community and the developers.

[lightguard]

Yes, DeltaSpike is still being developed. We have commits nearly every week. We're working on JSF integration now. We also recently graduated the Apache Incubator, but we're waiting on an infrastructure ticket to make the switch. We lagged awhile because of some core contributors having other things (like the day job) taking more time than before.

[rafaelmeireles]

For a project that beginning now, what do you indicates? My Faces CODI? Is easy to migrate after to Deltaspike?

And for security, My Faces CODI don´t have a security module, what do you recommends?

[lightguard]

I recommend DeltaSpike (if your company will allow it) and PicketLink. DeltaSpike is good, don't be scared about the version. We're moving forward to release 0.4 this week, possibly early next week depending on when the vote happens.

[rafaelmeireles]

But the problem is the time, I need to begin the project in a few days and deltaspike is too incomplete, or not? If compare with CODI?

I think that CODI, is the best way to migrate after, to deltaspike, don´t you?

[lightguard]

When you say it's too incomplete, what are you missing, is it just the JSF integration?

[rafaelmeireles]

I didn´t see:

- the integration with ViewScope in JSF Module

- support to extended persistence context like seam and CODI in JPA Module

- the security module, apparently is incomplete. Or the purpose of delta spike isn't have the complete security module like seam(that is very powerfull)?

Can you explain this topics above?

[lightguard]

Rafael Meireles wrote:

- the integration with ViewScope in JSF Module

Are you talking about what will be in 0.4, or what's in 0.3?

Rafael Meireles wrote:

- support to extended persistence context like seam and CODI in JPA Module

Honestly, this is an anti-pattern and we probably won't be doing it. Use what's already there and learning how persistence contexts work will save you much hair pulling and bug reports later.

Rafael Meireles wrote:

- the security module, apparently is incomplete. Or the purpose of delta spike isn't have the complete security module like seam(that is very powerfull)?

We decided not to do a complex model. We recommend you use Picketlink (the new IDM stuff) or integrate DeltaSpike with another security provider with what's available.

[rafaelmeireles]

Jason Porter wrote:

Are you talking about what will be in 0.4, or what's in 0.3?

How can I see what have in the 0.4 version?

Jason Porter wrote:

Honestly, this is an anti-pattern and we probably won't be doing it. Use what's already there and learning how persistence contexts work will save you much hair pulling and bug reports later.

I think a little different about this. The solution extended persistence context that maintain the entity manager open in @ViewScope attends me very well.

Jason Porter wrote:

We decided not to do a complex model. We recommend you use Picketlink (the new IDM stuff) or integrate DeltaSpike with another security provider with what's available.

Honestly, I didn't understand the purpose of DeltaSpike Security Module. If I use picketlink I don't need to use DeltaSpike Security Module?

I forgot to mention about the control of transactions like RequiresNew in EJB and etc in JPA Module.

[adrianosch]

Jason Porter wrote:

Rafael Meireles wrote:

- support to extended persistence context like seam and CODI in JPA Module

Honestly, this is an anti-pattern and we probably won't be doing it. Use what's already there and learning how persistence contexts work will save you much hair pulling and bug reports later.

I certainly disagree that the use of extended persistence contexts is an anti-pattern, even when used across multiple requests (conversation).

If you take a look at the introduction of seam-persistence module (here) you'll see many arguments explaining why statefulness is a good thing.

I really hope that we’ll have an enterprise solution (deltaspike) for the stateless problem.

[tiago.wanke.marques]

Im having the same felling that Rafael about Deltaspike.

Rafael, what was your decision about what tecnologi to use?

Tnks

[ctomc]

Did you check what happened to DeltaSpike since the last post on this thread?

Version 1.0 was recently released http://deltaspike.apache.org/news.html#8th-release-100-14062014

Check docs http://deltaspike.apache.org/documentation.html to see what is the state now.

in any case best place to discuss deltaspike would be on it's mailing list.

You can find details here: http://deltaspike.apache.org/community.html