-
15. Re: While Seam is great, is any weakness of this framework?
I was referring to the following reference of integration of Quartz or jBPM business calendars.
http://jira.jboss.com/jira/browse/JBSEAM-161 -
16. Re: While Seam is great, is any weakness of this framework?
Well, maybe you can look at the existing asynchronous/scheduled processing with EJB3 timers and submit an implementation for Quartz etc.
-
17. Re: While Seam is great, is any weakness of this framework?
Is there anyone else working on this? From the jira issue is appeared that there was a need.
-
18. Re: While Seam is great, is any weakness of this framework?
"fperedo" wrote:
Maybe it is just me.. but I feel that lines between "cant be done without J2EE5" and "can't be done without the microcontainer" and "can be done with just tomcat" are blurry... perhaps if the documentation included some kind of feature matrix comparing the functionality of seam on each case? (also... if it can be deployed to tomcat shouldn't that mean it should be easy to deploy pretty much everywhere?)
Feel free to raise a JIRA issue and someone can review this. Forum posts tend to get lost, putting it in JIRA means it will get looked at :)"fperedo" wrote:
The thing I don't like about seam-gen, is that I feel like my applications gets to have lots of code I don't quite understand... and therefore... if something it that generated code fails... its going to be really hard to fix... I would like to be able to build a really really simple example and add stuff to it, to understand exactly what is done by each piece of the project...
pretty much *everything* in a skeleton seam app is necessary! Ok, i guess you drop the security stuff, but the rest..."supernovasoftware.com" wrote:
Is there anyone else working on this? From the jira issue is appeared that there was a need.
not afaik. i would expect this in a later beta of 1.3 or even a 1.3 point release. or perhaps shane has it up his sleeve ;) i agree its impotant, and if its not being looked at in June, I'll push for it."vwu98034" wrote:
In general, I will use a framework with a great flexibility that allows me to integrate other technologies easily.
whilst seam doesn't have as many integrations as version 1 million of some other frameworks at the moment, it has a very strong base that makes integrations great! seam's ws support will not only add ws (obviously!), it will also add a model for integrating seams conversations with non-jsf/ejb3 participants which we can then use in many other situations - for example a seam conversation conducted via email.
otherwise: bpm, rules, email, pdf, richfaces, icefaces, ajax4jsf, trinidad, gwt- the list goes on!"fperedo" wrote:
I will have to integrate part of my projects with Flex, so I have to use eclipse (Flex is an eclipse plugin) if it werent for that, I would prefer to use Netbeans IDE
Interesting you mention flex - we should definitely have a flex/seam example (using seam remoting).
And yes, use ant and seam-gen in eclipse! ;) -
19. Re: While Seam is great, is any weakness of this framework?
"stu2" wrote:
but personally I suspect the 80 remaining items in Jira mean sometime in June.
The 2 blockers (IMO) on a beta of seam 1.3 are now ws and javaone. lots of those 80 issues will get slipped to later betas/versions ;) -
20. Re: While Seam is great, is any weakness of this framework?
and generally, regarding eclipse and seam-gen - rhds will transform seam-gen into an eclipse plugin. i know max is strongly in favour of a wtp style structure so i think that will be in there!
-
21. Re: While Seam is great, is any weakness of this framework?
Btw... any release date on rhds... my exadel trial license is about to end in 11 days...
-
23. Re: While Seam is great, is any weakness of this framework?
i know max is strongly in favour of a wtp style structure so i think that will be in there!
Can you elaborate on what a wtp style structure is? Do you mean a standard web project type structure i.e. an organized seam-gen project in the IDE?
I really can't wait for RHDS to come out, I just hope they don't sell licenses in packs of 5 developer licence like they are now, since like many developers, I want a licence at home for personal use without having to buy 4 I'm not going to use. I'm looking forward to seeing the JBoss IDE stuff integrated with the Exadel stuff to get the best of both worlds.
Also, pete, I hate to be a pain, but can you take a look at this thread, I'm just wondering if you had issues with pageflows and <begin-conversation> in pages.xml and the switcher code. I know you use this, and wondered whether it is a problem or not. If so, I'll create a JIRA issue.
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=107853 -
24. Re: While Seam is great, is any weakness of this framework?
"Delphi's Ghost" wrote:
I really can't wait for RHDS to come out, I just hope they don't sell licenses in packs of 5 developer licence like they are now, since like many developers, I want a licence at home for personal use without having to buy 4 I'm not going to use. I'm looking forward to seeing the JBoss IDE stuff integrated with the Exadel stuff to get the best of both worlds.
All the plugins that make up rhds will be available free on an eclipse update site - so for home dev you maynot even need a licenseAlso, pete, I hate to be a pain, but can you take a look at this thread, I'm just wondering if you had issues with pageflows and <begin-conversation> in pages.xml and the switcher code. I know you use this, and wondered whether it is a problem or not. If so, I'll create a JIRA issue.
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=107853
It's starred in my gmail for when I have a minute. -
25. Re: While Seam is great, is any weakness of this framework?
All the plugins that make up rhds will be available free on an eclipse update site - so for home dev you maynot even need a license
It's a question of this whole RHDS vs the community version which hasn't fully been explained clearly. From my last take on it, from a thread on TheServerSide, it sounded like the freely available one was just a collection of plugins and it was up to me to get it all working together. Whereas the the RHDS was a fully tested, everything works together set of plugins, just download and start programming. Otherwise, why pay for it, when the same thing is available for free (minus the support).
Either way, I can't wait to see it, and it's probably still cheaper than the Borland Delphi upgrades I paid for year after year.
It's starred in my gmail for when I have a minute.
Thanks, I have the switcher working now. -
26. Re: While Seam is great, is any weakness of this framework?
The only complaint I have about Seam so far, is the recommended packaging for Tomcat. The Microcontainer-based packaging places very serious restrictions on the application (for example, try passing the Tomcat-configured DataSource into the MC-based app) that makes this configuration not acceptable for production environments, leaving us Tomcat users feeling like second-class citizens.
There are alternatives (using a JTA implementation), but they are not documented anywhere, so whoever decides to take this route is basically on their own (it took me awhile to get my environment running). Heck, some of the open-source JTA implementations are even coming from JBoss itself (JBoss Transactions), so why not dump the MC abomination altogether and use JBoss JTA/JCA modules directly, instead? -
27. Re: While Seam is great, is any weakness of this framework?
Why are so many people not willing to just download JBoss AS for free and use the embedded Tomcat?
What are the advantages of just using plain tomcat? -
28. Re: While Seam is great, is any weakness of this framework?
Because we're a major bank where everyone cannot run whatever they please. There are tons of regulations regarding what is allowed to run production environments. There's an architectural department that makes such decisions for a few years ahead. There are administrators that are hired with specific skill sets. But, yes, I guess I'll simply go to our production admins and say "Hey, why aren't you willing to just download JBoss AS for free and use the embedded Tomcat?". Yes, that suddenly seems a terribly good idea...
Seriously though, we here have WebSphere for mission-critical apps (no, I don't want to go into argument why are we using it), plus Tomcat for everything else that doesn't require a full-blown appserver. Tomcat administration is order of magnitude simpler than it is for an appserver, so, in the long run, these guys are saving a good money on support costs, both hardware and salaries. -
29. Re: While Seam is great, is any weakness of this framework?
So, because your production department is saving money on the deployment environment, you need to spend more money (time) on the development side. Sorry, but nothing is free.