Seam 2.3 Booking
by Solerman Kaplon
Hi everyone,
I managed to get seam 2.3 Beta 2 working on my machinge against JBoss 7.1 and I
am testing it using the seam booking demo from the examples-ee6. Each time I try
to do a hotel booking or go into the settings page, I get conversation errors
(the conversation don't seem to be created or switched to properly). Is this
expected in the current version?
Solerman
13 years, 2 months
Sandbox for DeltaSpike
by Jason Porter
Hey everyone!
I wanted to bring up the idea of having a sandbox to add bits and other
non-core extensions. We have a great bunch of people from the
Seam development group looking to add their extensions, but they're either
not on the roadmap for DS, or are very far down. I suggest we setup a
sandbox on github people can write to, or at least do pull requests to so
we can get some of these modules and other ideas in and pull them into core
as we get there. We can also use this as a vetting ground for new ideas and
other things which may not exactly fit into core, like the forge extension.
To do this we need to
1. Setup the repo somewhere
2. Seed it with a basic structure (pom.xml, contribution instructions, etc)
3. Get some CI setup somewhere (we could leverage OpenShift for this if
needed)
What does everyone else think? I've cc'd the Seam Development list here
hoping to get some feedback from them as well and hopefully rekindle some
of the fire we had there.
--
Jason Porter
http://lightguard-jp.blogspot.com
http://twitter.com/lightguardjp
Software Engineer
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling
PGP key id: 926CCFF5
PGP key available at: keyserver.net, pgp.mit.edu
13 years, 2 months
Re: [seam-dev] Sandbox for DeltaSpike
by Jason Porter
Maybe we should do a new thread for the security stuff so we don't derail
this one.
Having talked to some of the Seam Contributors here at JBoss World / Red
Hat Summit it seems like a lot of them aren't quite sure how to get the
discussions started for their previous Seam modules, especially since many
of them target EE apis (I'm ccing the Seam dev list so hopefully those who
may not be following DeltaSpike dev will see this). That is a large part of
where this sandbox idea came from. If we want to create a new Apache repo,
or another sub directory in our current repo, or perhaps even different
branches for this work I'm fine. However, I do agree that getting too many
topics going all at once is bad. That happened in Seam and we were
overloaded. Perhaps we should create some sort policy for getting these
ideas in if they're not on the current roadmap. I'm not sure if any of
really know when we'll be tackling some of the EE stuff. Next release,
release after that one? I really don't want to lose these people and see
DeltaSpike stagnate with only a few developers doing it in their spare time.
On Thu, Jun 28, 2012 at 12:35 PM, Mark Struberg <struberg(a)yahoo.de> wrote:
> Oh yea, that was my fault. I was on a conference earlier that week and
> overlooked his mail. Found it now.
>
>
> Shane, what is the direction you working on? What are the basic ideas and
> what shortcomings did you identify while doing the review?
> I'm not sure if it wouldn't be better we would make that work directly in
> the deltaspike main repo. There are lots of other people looking at the
> repo and we got many questions regarding security already. And not being
> able to point people to a canonical repo which contains the latest stuff...
>
> Btw, welcome Bolek! We've talked on IRC already a few times. Would be
> great if you could introduce yourself with a few words and also if we move
> the technical discussions from IRC more to email. This is much easier to
> follow for people in different timezones. And it will also raise visibility
> and make people aware that there is a new face working on DeltaSpike :)
>
>
>
> There is a general ASF rule "If it isn't on the list, it didn't happen".
>
> Using IRC or even skype calls is fine for _additional_ ad hoc
> communication, but it must not lead to 'silently' doing things without
> having conversation on the list. IRC is just not a mail archive which can
> get scanned easily.
>
>
> txs and LieGrue,
> strub
>
>
>
> ----- Original Message -----
> > From: Jason Porter <lightguard.jp(a)gmail.com>
> > To: deltaspike-dev(a)incubator.apache.org; Mark Struberg <
> struberg(a)yahoo.de>
> > Cc:
> > Sent: Thursday, June 28, 2012 6:20 PM
> > Subject: Re: Sandbox for DeltaSpike
> >
> > On Thu, Jun 28, 2012 at 6:06 AM, Mark Struberg <struberg(a)yahoo.de>
> wrote:
> >
> >> But if we don't talk about that stuff at all, then there will be no
> >> visibility and no progress neither.
> >>
> >> There is really no problem with spreading out parallel topics, IF there
> >> are people interested in contributing.
> >>
> >>
> >> What I do _not_ like to have is starting with 15 different topics and
> not
> >> finishing anything!
> >>
> >> Btw, what is the state of deltaspike-security?
> >>
> >> I have no clue about it nor did I do any review. I've also not seen any
> >> commit lately.
> >>
> >> Who is working on that? Or is noone working on it at all?
> >
> >
> > https://github.com/sbryzak/DeltaSpike/tree/security
> >
> > I believe Shane has been working on it apparently, but there hasn't been
> > much discussion.
> >
> >
> >> LieGrue,
> >> strub
> >>
> >>
>
--
Jason Porter
http://lightguard-jp.blogspot.com
http://twitter.com/lightguardjp
Software Engineer
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling
PGP key id: 926CCFF5
PGP key available at: keyserver.net, pgp.mit.edu
13 years, 2 months
Re: [seam-dev] Sandbox for DeltaSpike
by Jason Porter
Why wouldn't this be in the public? The idea is to get people to contribute. If we need a separate Apache repo for a sandbox, okay fine but then we're back to the icla issue aren't we?
Sent from my iPhone
On Jun 27, 2012, at 14:10, Mark Struberg <struberg(a)yahoo.de> wrote:
> Btw, another thingy.
>
> It is not the best community building approach to develop something 'in the dark' and then drop all that on all other community members.
> Don't get me wrong, it's perfectly fine to experiment around if ideas are good at all. But doing this 'in public' is much more appreciated. You can get lots or precious feedback that way.
>
>
> LieGrue,
> strub
>
>
>
> ----- Original Message -----
>> From: Mark Struberg <struberg(a)yahoo.de>
>> To: "deltaspike-dev(a)incubator.apache.org" <deltaspike-dev(a)incubator.apache.org>
>> Cc:
>> Sent: Wednesday, June 27, 2012 7:33 PM
>> Subject: Re: Sandbox for DeltaSpike
>>
>> basically +1
>>
>>
>> BUT we really have to be careful that we don't do too much at github!
>>
>> All commits done on github must either be done by a deltaspike committer or
>> someone who has at least an iCLA on file.
>>
>> Commits from other people need to get added via an attachment in a Jira ticket.
>> I know this sounds not really git-like, but it's the only way we can ensure
>> IP clearance.
>>
>> LieGrue,
>> strub
>>
>>
>> ----- Original Message -----
>>> From: Mehdi Heidarzadeh <heidarzadeh2(a)gmail.com>
>>> To: deltaspike-dev(a)incubator.apache.org
>>> Cc:
>>> Sent: Wednesday, June 27, 2012 7:28 PM
>>> Subject: Re: Sandbox for DeltaSpike
>>>
>>> +1
>>> Great idea.
>>>
>>> On Wed, Jun 27, 2012 at 4:52 AM, Shane Bryzak <sbryzak(a)redhat.com>
>> wrote:
>>>
>>>> Fantastic idea, +1.
>>>>
>>>>
>>>> On 27/06/12 05:39, Jason Porter wrote:
>>>>
>>>>> Hey everyone!
>>>>>
>>>>> I wanted to bring up the idea of having a sandbox to add bits and
>> other
>>>>> non-core extensions. We have a great bunch of people from the Seam
>>>>> development group looking to add their extensions, but they're
>>
>>> either not
>>>>> on the roadmap for DS, or are very far down. I suggest we setup a
>>> sandbox
>>>>> on github people can write to, or at least do pull requests to so
>> we
>>> can
>>>>> get some of these modules and other ideas in and pull them into
>> core as
>>> we
>>>>> get there. We can also use this as a vetting ground for new ideas
>> and
>>> other
>>>>> things which may not exactly fit into core, like the forge
>> extension.
>>>>>
>>>>> To do this we need to
>>>>>
>>>>> 1. Setup the repo somewhere
>>>>> 2. Seed it with a basic structure (pom.xml, contribution
>> instructions,
>>>>> etc)
>>>>> 3. Get some CI setup somewhere (we could leverage OpenShift for
>> this if
>>>>> needed)
>>>>>
>>>>> What does everyone else think? I've cc'd the Seam
>> Development
>>> list here
>>>>> hoping to get some feedback from them as well and hopefully
>> rekindle
>>> some
>>>>> of the fire we had there.
>>>>>
>>>>> --
>>>>> Jason Porter
>>>>> http://lightguard-jp.blogspot.**com
>>> <http://lightguard-jp.blogspot.com>
>>>>> http://twitter.com/**lightguardjp
>>> <http://twitter.com/lightguardjp>
>>>>>
>>>>> Software Engineer
>>>>> Open Source Advocate
>>>>> Author of Seam Catch - Next Generation Java Exception Handling
>>>>>
>>>>> PGP key id: 926CCFF5
>>>>> PGP key available at: keyserver.net <http://keyserver.net>,
>>> pgp.mit.edu <
>>>>> http://pgp.mit.edu>
>>>>>
>>>>>
>>>>>
>>>>> ______________________________**_________________
>>>>> seam-dev mailing list
>>>>> seam-dev(a)lists.jboss.org
>>>>>
>>>
>> https://lists.jboss.org/**mailman/listinfo/seam-dev<https://lists.jboss.org/mailman/listinfo/seam-dev>
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Mehdi Heidarzadeh Ardalani
>>> Independent JEE Consultant, Architect and Developer.
>>> http://www.TheBigJavaBlog.com
>>>
>>
13 years, 2 months
Re: [seam-dev] Sandbox for DeltaSpike
by Jason Porter
If they're not official parts of deltaspike but a proving ground and we can
pull things in, or get iCLAs for people when we pull in their stuff, is
that a problem? Or what if we ask them for an iCLA once they do a pull
request?
I'm worried we're losing some momentum (if it's not already gone) from the
community about contributing. We also have a bunch of Seam devs (Cody,
Marius, George, etc.) asking about when they can put their bits into
DeltaSpike because it's not on the roadmap, or it's very far out on the
roadmap.
On Wed, Jun 27, 2012 at 1:33 PM, Mark Struberg <struberg(a)yahoo.de> wrote:
> basically +1
>
>
> BUT we really have to be careful that we don't do too much at github!
>
> All commits done on github must either be done by a deltaspike committer
> or someone who has at least an iCLA on file.
>
> Commits from other people need to get added via an attachment in a Jira
> ticket.
> I know this sounds not really git-like, but it's the only way we can
> ensure IP clearance.
>
> LieGrue,
> strub
>
>
> ----- Original Message -----
> > From: Mehdi Heidarzadeh <heidarzadeh2(a)gmail.com>
> > To: deltaspike-dev(a)incubator.apache.org
> > Cc:
> > Sent: Wednesday, June 27, 2012 7:28 PM
> > Subject: Re: Sandbox for DeltaSpike
> >
> > +1
> > Great idea.
> >
> > On Wed, Jun 27, 2012 at 4:52 AM, Shane Bryzak <sbryzak(a)redhat.com>
> wrote:
> >
> >> Fantastic idea, +1.
> >>
> >>
> >> On 27/06/12 05:39, Jason Porter wrote:
> >>
> >>> Hey everyone!
> >>>
> >>> I wanted to bring up the idea of having a sandbox to add bits and
> other
> >>> non-core extensions. We have a great bunch of people from the Seam
> >>> development group looking to add their extensions, but they're
> > either not
> >>> on the roadmap for DS, or are very far down. I suggest we setup a
> > sandbox
> >>> on github people can write to, or at least do pull requests to so we
> > can
> >>> get some of these modules and other ideas in and pull them into core
> as
> > we
> >>> get there. We can also use this as a vetting ground for new ideas and
> > other
> >>> things which may not exactly fit into core, like the forge extension.
> >>>
> >>> To do this we need to
> >>>
> >>> 1. Setup the repo somewhere
> >>> 2. Seed it with a basic structure (pom.xml, contribution instructions,
> >>> etc)
> >>> 3. Get some CI setup somewhere (we could leverage OpenShift for this
> if
> >>> needed)
> >>>
> >>> What does everyone else think? I've cc'd the Seam Development
> > list here
> >>> hoping to get some feedback from them as well and hopefully rekindle
> > some
> >>> of the fire we had there.
> >>>
> >>> --
> >>> Jason Porter
> >>> http://lightguard-jp.blogspot.**com
> > <http://lightguard-jp.blogspot.com>
> >>> http://twitter.com/**lightguardjp
> > <http://twitter.com/lightguardjp>
> >>>
> >>> Software Engineer
> >>> Open Source Advocate
> >>> Author of Seam Catch - Next Generation Java Exception Handling
> >>>
> >>> PGP key id: 926CCFF5
> >>> PGP key available at: keyserver.net <http://keyserver.net>,
> > pgp.mit.edu <
> >>> http://pgp.mit.edu>
> >>>
> >>>
> >>>
> >>> ______________________________**_________________
> >>> seam-dev mailing list
> >>> seam-dev(a)lists.jboss.org
> >>>
> > https://lists.jboss.org/**mailman/listinfo/seam-dev<
> https://lists.jboss.org/mailman/listinfo/seam-dev>
> >>>
> >>
> >>
> >
> >
> > --
> > Mehdi Heidarzadeh Ardalani
> > Independent JEE Consultant, Architect and Developer.
> > http://www.TheBigJavaBlog.com
> >
>
--
Jason Porter
http://lightguard-jp.blogspot.com
http://twitter.com/lightguardjp
Software Engineer
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling
PGP key id: 926CCFF5
PGP key available at: keyserver.net, pgp.mit.edu
13 years, 2 months
Seam 3.1.1 status
by Cody Lerum
I've recently had some improvements and bug fixes commited to the Seam
mail module and I would like to get them out in the open in
non-SNAPSHOT form.
Is a 3.1.1 release still being planned, or would it be possible to do
individual module releases as needed?
-C
13 years, 2 months
