Re: Enterprise patterns

[Dr Heinz M. Kabutz]

Wonderful Marco, thank you very much.  Great work.

All that I need to do to make the images appear on the website is to run a script on the server, which makes the latest build and docs.  This also puts the gifs on the server.

I would like to propose that we use a different package name for these patterns.

Here are some suggestions:

1. org.jpatterns.jee (for Java Enterprise Edition)

2. org.jpatterns.enterprise (can have others besides core j2ee patterns)

3. org.jpatterns.j2ee (a catalog of j2ee patterns according to the book)

4. org.jpatterns.ee (leave it like it is)

Please cast your vote, jpatterns group.  I'll wait until the end to cast my vote.

Regards

Heinz
-- 
Dr Heinz M. Kabutz (PhD CompSci)
Author of "The Java(tm) Specialists' Newsletter"
Sun Java Champion
http://www.javaspecialists.eu
Tel: +30 69 72 850 460
Skype: kabutz 

On 8/21/10 5:02 PM, Marco Tedone wrote:

Hi Heinz,

 

I’ve added a couple of patterns under the org.jpatterns.ee package. I also added a .gif with the UML for the patterns. However the web address: http://www.jpatterns.org/uml/ee/<image-name>.gif doesn’t work. I guess the images need to be added to the website? If you let me know how to add them I’ll be happy to do that.

 

Regards,

 

Marco

[Marco Tedone]

Hi Heinz,

 

First consideration: would it be possible to have a trigger which runs the script on the server automatically after every check-in, so that the images become immediately available?

 

As for the vote,

 

I’m happy with either jee or ee. J2ee in my view is too limitative, since J2EE belongs now to the past. “enterprise” is too long J

 

Regards,

 

Marco

[Dr Heinz M. Kabutz]

Hey Marco,

I tried setting up my script as a cron job that runs every 5 minutes, but for some unknown reason it did not work.  However, it might be better to not do that part completely automatically as the jar file will be publicly available and we don't want to put anything up there that might be broken.

Here is my script at the moment, it's really primitive, but does work when I run it manually.  We could probably break it up into several smaller scripts, that only get called when the previous step completed successfully.

pushd /export/home/www/jpatterns/git/jpatterns
git pull
mvn install javadoc:javadoc
rm -rf /export/home/www/jpatterns/htdocs/uml
cp -R uml /export/home/www/jpatterns/htdocs
rm -rf /export/home/www/jpatterns/htdocs/apidocs
cp -R target/site/apidocs /export/home/www/jpatterns/htdocs
cp target/jpattern*.jar /export/home/www/jpatterns/htdocs/builds
popd

   

Regards

Heinz
-- 
Dr Heinz M. Kabutz (PhD CompSci)
Author of "The Java(tm) Specialists' Newsletter"
Sun Java Champion
http://www.javaspecialists.eu
Tel: +30 69 72 850 460
Skype: kabutz 

--
You received this message because you are subscribed to the Google Groups "jpatterns" group.
To post to this group, send email to jpat...@googlegroups.com.
To unsubscribe from this group, send email to jpatterns+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/jpatterns?hl=en.

[Michael Hunger]

You could just use git clone on an empty repository or git --rebase pull if there are no local changes.

Perhaps we should create a remote release branch which is only updated with a working, releasable version.

Then we can just pull that release branch which is known to work and not the current working master branch.

We could also do mvn site:site that would create a complete website including test results, apidocs and more. We could then just link to the artifacts that we'd like to publish.

Regarding the naming of the package. If those are the patterns from the j2ee patterns I would name them so. Don't forget there are other "enterprise" patterns like those from Martin Patterns of Enterprise Application Architecture (PoEAA) - http://martinfowler.com/eaaCatalog/.

gregor hohpes eai-patterns can be found here: http://www.eaipatterns.com

Michael

[Marco Tedone]

The ones from the J2EE book which I'm including in the code base are valid
also after J2EE (we are now in EE5) and that's the only reason I included
them. The others aren't actual anymore mainly due to their belonging to the
old EJB 2.x architecture.

I like the idea of running mvn site:site (which runs tests, javadocs and
builds the site); especially if Heinz is running the jpatterns.org website
"at home" he could setup a Continous Integration environment (e.g. Hudson)
which could then build the code and run the mvn site:site everytime a change
has been detected, deploying to the file system exposed to the HTTP server.

As for other enterprise patterns, I'd be careful in adding them to the code
base; some of those which I've seen on Fowler's website IMHO don't' really
say a lot. Maybe we should put to the votes which enterprise patterns the
community would like to be available from JPatterns, or maybe we should
define our own...(just a thought)

Marco

[Michael Hunger]

then perhaps lets call them jee

hudson also integrates well with git, that's true, it could just pull the release branch and then build everything.

I'd be careful for excluding patterns. Most of the Fowler patterns may not say that much on the website (but in the book they do) and many of them are heavily used in all kinds of architectures not just Java ones.

I wouldn't want the community decide which patterns to leave off but rather which to add.

Michael

[Marco Tedone]

Ok, I will change the package name to jee. As for the community
contribution, my suggestion was about asking which patterns they would like
to see, not excluded, so we are on the same page there.

[Dr Heinz M. Kabutz]

Hi Marco,

we have about 13 people on the jpatterns google group, so we should wait a bit (at least until Tuesday) to see if anyone else wants to weigh in with a vote.  Maybe just leave it as is until then.

(Remember, I haven't voted yet either :-))

Regards

Heinz
-- 
Dr Heinz M. Kabutz (PhD CompSci)
Author of "The Java(tm) Specialists' Newsletter"
Sun Java Champion
http://www.javaspecialists.eu
Tel: +30 69 72 850 460
Skype: kabutz 

[Dr Heinz M. Kabutz]

No problem Marco.  Leave it at jee for now, until someone raises an objection.  I'll update the build on our website.

I actually wonder how many companies still use J2EE.  Probably more than we might imagine.  I still have people on my courses who are thinking of going over to Java 1.5 ...

Regards

Heinz
-- 
Dr Heinz M. Kabutz (PhD CompSci)
Author of "The Java(tm) Specialists' Newsletter"
Sun Java Champion
http://www.javaspecialists.eu
Tel: +30 69 72 850 460
Skype: kabutz 

On 8/22/10 12:06 PM, Marco Tedone wrote:

Hi Heinz,

 

Sorry I changed it to jee (which shouldn’t make a huge difference to ee) but I will be happy to change it to whatever we decide it’s best.

 

Marco

[Dr Heinz M. Kabutz]

Seeing that we have not had any further comments, let's leave it as jee :-)  Oh, we will also need to put some disclaimers on our website somewhere so we don't get sued by the owners of the JEE trademark...

Regards

Heinz
-- 
Dr Heinz M. Kabutz (PhD CompSci)
Author of "The Java(tm) Specialists' Newsletter"
Sun Java Champion
http://www.javaspecialists.eu
Tel: +30 69 72 850 460
Skype: kabutz 

On 8/22/10 12:06 PM, Marco Tedone wrote:

Hi Heinz,

 

Sorry I changed it to jee (which shouldn’t make a huge difference to ee) but I will be happy to change it to whatever we decide it’s best.

 

Marco

 

From: jpat...@googlegroups.com [mailto:jpat...@googlegroups.com] On Behalf Of Dr Heinz M. Kabutz

Sent: 22 August 2010 05:26