Example names
by Shane Bryzak
Guys, we've got to come up with a standard naming scheme for our example
names, because the ones we have look like an rhinoceros sat on them or
something:
helloworld
idmconsole
model
openid-rp
princess-rescue
seam-catch-example-basic-servlet
seam-international-example-timeanddate
seam-jaxrs-exceptions
seam-tasks-statistics
seam-wicket-example-numberguess
short.ly
simple
validation
validation-helloworld
I'm just as guilty as anyone else (in fact I think mine are the most
ambiguous of all). What I propose to clean this up is to prefix the
example name with the module name - e.g:
helloworld becomes remoting-helloworld
simple becomes security-simple
You get the idea. Also, the Maven artifact names for the examples
should be standardised too. We currently have all sorts of variations
here also, so how about we use seam-{module}-example-{name}, as this
seems to be what most people are already using (and therefore would
require the least work).
Using the previous two examples, that would give us artifact names like so:
seam-remoting-example-helloworld
seam-security-example-simple
What do you think?
14 years, 1 month
Demo app with CR1 + Seam2-Seam3 migration strategy?
by Denis Forveille
Sorry if I missed this information or if it has been answered elsewhere but is there an "integrated" test/demo application coming
with CR1 like the booking app in Seam 2?
If so, I could start running it on WebSphere 8 beta (and at the same time educate myself on CDI, Weld and Seam 3..)
If not, what are the plans for such a demo application?
Also have someone already think about the strategy around the seam2-seam3 migration?
Thanks
Denis.
14 years, 2 months
Module documentation
by Shane Bryzak
To assist with the bundled documentation build, could everyone please
ensure that you prefix your docbook id tags with the name of your
module. This is unfortunately necessary as docbook requires unique ID
values and will fail otherwise. To illustrate what I mean, let's
pretend that two of our modules, faces and security both have
introduction chapters:
<chapter id="introduction">
<title>Seam Faces - Introduction</title>
...
<chapter id="introduction">
<title>Seam Security - Introduction</title>
...
Since both chapters have an id of "introduction", docbook fails when
attempting to build the bundled docs. To workaround this restriction,
we can simply add the module name:
<chapter id="faces-introduction">
<title>Seam Faces - Introduction</title>
...
<chapter id="security-introduction">
<title>Seam Security - Introduction</title>
...
Can you also please apply the same naming standard to the docbook source
files, and chapter titles (this will help to keep the bundled
documentation more consistent).
Lastly, if you need to add a new chapter to your module documentation
(or rename an existing one), can you please let one of the core team
devs know. Our bundled documentation build has its own master.xml file
containing all the individual chapters from each module, and new
chapters need to be manually added to this file [1]. Alternatively, you
can make the modification yourself and send a pull request.
Thanks,
Shane
[1]
https://github.com/seam/dist/blob/master/docs/src/main/docbook/en-US/mast...
14 years, 2 months
Seam JCR
by George Gastaldi
I was thinking to create a Seam JCR module to allow JCR (Java Content
Repositories) to be injected in code. It should work for jackrabbit as
well as modeshape or any other jcr 2.0 compliant implementation. Any
suggestions ? Comments appreciated.
14 years, 2 months
Seam 3 Mail Feedback Follow-up
by Cody Lerum
1. From Lincoln
Utilizing an Interface for handling the different ways one could
create an email template. -
https://issues.jboss.org/browse/SEAMMAIL-19
This is Done.
VelocityMailMessage vmm = velocityMailMessage.get();
vmm.from("seam(a)test.test", "Seam Framework")
.to(person)
.subject("HTML Message from Seam Mail - " +
java.util.UUID.randomUUID().toString())
.bodyHtml(new VelocityClassPathTemplate("template.html.vm"))
.put("version", "Seam 3")
.importance(MessagePriority.HIGH)
vmm.send(session.get());
the contact fields also support a interface as well so one only
need implement a getName and getAddress method on their User entity
(for example) in order to pass it directly into an email -
https://github.com/seam/mail/blob/6f70057cca7da712576c21f44bda80082ae1f0a...
2. From Emmanuel
a. the from and all contact fields already support a single argument
being the address
b. the ability to have a var args to("emmanuel(a)nothingtosee.org",
"dan(a)test.com") is something we could do, but we would have to ditch
the to("Dan", "dan(a)test.com"). People would have to create personal +
address recipients via something like to(new BaseEmailContact("Dan".
"dan(a)test.com")...more on that further down
c. all the contact methods (from/to/cc/bcc/replyto) all support
collections being passed into them.
d. I've added an a no arg send() method
e. Typesafe templating is going to have to come later and I'm going
to need to lean on someone for inspiration.
3. From Lincoln on having the EmailAttachment as an interface.
I'm not really sure how useful this is going to be as you are
going to have to implement quite a few methods.
4. From José Rodolfo Carrijo de Freitas reguarding no arg send()
This has been added.
5. From Dan via ALR reguarding ordering of the name and address in
contact methods
I've reordered everything to aways takes Address first and then Name if any.
to("cody(a)test.com")
to("cody(a)test.com", "Cody")
Thats what I have for now. The one question I have is do we just drop
the ability to do
to("cody(a)test.com", "Cody")
and require
to(new BaseEmailContact("cody(a)test.com", "Cody")
this would allow a var args address only to/from/cc/bcc/replyTo
Thus you could do:
to("cody(a)test.com")
to("cody(a)test.com", "dan(a)test.com")
but anything with the acutal name would need to be done with
to(new BaseEmailContact("cody(a)test.com", "Cody")
Of course if people are using existing objects it would be easier to
just implement the EmailContact interface
User user = new User("Cody", "cody(a)test.com", RoleType.ADMIN);
to(user);
Thoughts?
14 years, 2 months
Contributor names
by Shane Bryzak
All module leads,
Could you please send me a list of all the contributors, both past and
present who have contributed to your module. This is required for the
bundled Seam documentation so that we can give credit to everyone who
helped develop Seam.
Thanks,
Shane
14 years, 2 months
