[JBoss JIRA] (JDF-53) TicketMonster - Data grid-based reservation system
by Marius Bogoevici (JIRA)
Marius Bogoevici created JDF-53:
-----------------------------------
Summary: TicketMonster - Data grid-based reservation system
Key: JDF-53
URL: https://issues.jboss.org/browse/JDF-53
Project: JBoss Developer Framework
Issue Type: Feature Request
Components: ticket-monster
Reporter: Marius Bogoevici
Assignee: Marius Bogoevici
Fix For: 2.0.0.Final
1. Use a data grid to hold reservations
2. Introduce a 'hold' reservation state: the system will pre-allocate seats during the reservation process. It should be possible for users to add seats to the cart and confirm or cancel the reservation. Held seats can either be promoted to 'Sold' (upon a successful booking) or freed up (upon cancellation)
3. Demo clustering with data grid
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
Looking for a (visual) metaphor
by Pete Muir
All,
We need a visual metaphor that quickly conveys to people that an example is:
* official, and something we will stand by, answer questions on, support in a product (e.g. TicketMonster)
* something that we plan to add to as an official example later on (e.g. jbossworld keynote 2012)
* something that is really interesting, but is unlikely to be official (e.g. Vineet's example)
We had thought about using ski run colours (green circle, blue square, black diamond) to indicate the level, but they really refer more to difficulty than to recommendation. Anyone got any good ideas?
Pete
12 years, 3 months
Re: [jdf-dev] JBoss Stacks: Requirements
by Pete Muir
Max, your best source is https://github.com/jboss-jdf/jdf-stack/blob/Beta2/stacks.yaml which I think is most up to date.
There are three roots: BOMs, archetypes and runtimes. Runtimes is what ties it all together though.
On 31 Jul 2012, at 14:01, Max Rydahl Andersen wrote:
> Sorry for getting in late (3 weeks PTO) - so if this is answered somewhere else please let me know :)
>
> Looking at the diagram i'm reading it as the runtime defines/contains the BOM/Archetypes since the runtime is the root or
> am I misreading this ?
>
> i.e. IMO an archetype has to be able to work with multiple versions, otherwise we need to release every archetype at every minor update of the runtime.
>
> Thus I assume i'm wrong in reading that, but just wanted to be sure "root of YAML file" is not the runtime.
>
> /max
>
>
> On 11 Jul 2012, at 14:00, Rafael Benevides <benevides(a)redhat.com> wrote:
>
>> Yesterday I started to work on this new yaml format and I tried to capture all requirements that was discussed in this Thread. The result was the following attached uml diagram.
>>
>> I think that's the better way to try comprehending what is needed and what will be covered. Today (or maybe tomorrow) I'll convert this idea to an example yaml file that is the representation of the diagram.
>>
>> The closest of the idea is something like similar to:
>>
>> bom: &jboss-with-x
>> name: JBoss With X
>> description: lorem ipsum
>> otherProperties: otherValues
>> availableVersions:
>> - 1.0.0.Final
>> - 1.0.1.CR1
>>
>> bom: &jboss-with-y
>> name: JBoss With Y
>> description: lorem ipsum
>> otherProperties: otherValues
>> availableVersions:
>> - 1.0.0.Final
>> - 1.0.1.CR1
>>
>> runtime: &jbosseap6
>> version: 6.0
>> type: EAP
>> boms:
>> - *jboss-with-x
>> - *jboss-with-y
>> recommendedBOM: *jboss-with-x
>>
>> Em 03-07-2012 13:01, Rafael Benevides escreveu:
>>>
>>> Em 03-07-2012 12:53, James Perkins escreveu:
>>>>> We could do that as well.
>>>>>
>>>>> 7.0.1.Final:
>>>>> properties:
>>>>> arguments: -logmodule
>>>>> cli: not-available
>>>> I like this approach.
>>> I like this approach either!
>> <Class Diagram.png>
>
12 years, 5 months
JBoss Stacks: Requirements
by Pete Muir
All,
I chatted with Max at JBoss World about requirements for what I'm code-naming JBoss Stacks, which is a really an extension of the JBoss BOMs project.
The JBoss Stacks project takes all the BOMs, all the archetypes, and all the runtimes, and identifies which work with which. This can then be used by tools (like JBDS, Forge, Maven plugins) to correctly configure users projects.
The stacks project requires 3 different dictionaries:
* available BOMs
* available archetypes
* available runtimes
and the ability to see the intersection between these things (i.e. if I'm on runtime version 1.2.3.Final, what BOMs are possible, what BOM is recommended, what archetypes are available, what is recommended).
The runtime should include a download URL, so that plugins such as James' AS plugin for forge can download it. It should also contain a some options. I'm not sure exactly what is needed here, but James can provide details and what makes most sense.
The runtimes should include what type they are (e.g. JBoss AS, EAP) to allow categorisation, filtering, sorting
The Yaml parser in use should be pluggable, to avoid introducing uncessary extra dependencies
There should be a recommended runtime per major version and per minor version (so you can say "I want JBoss AS 7" and you get back AS 7.1.1.Final or you can say "I want JBoss AS 7.0" and you get back 7.0.2.Final).
We're going to need to be careful about compat, eventually, so we need to get everything in there, and get it right. We'll have a long beta cycle ;-)
There will be a client utility, written in Java. This should be a single source file, which projects can copy in. It must have no dependencies other than a Yaml parser.
I think Rafael is going to take the lead on this. But we'll decide on Monday next week.
Pete
12 years, 5 months