[JBoss Seam] - Re: IDE support for Seam
by smithbstl
Same Boat Here Delphi, the visual editor does not work for me either.
As to Netbeans. I used the Facelets plugin for about 6 months (since v0.3). It works pretty well in terms of code completion, syntax highlighting, and some code gen (template creation). The deal breaker for me eventually was the instability it added to Netbeans. It kept crashing. Every couple of days Netbeans would hang. Just got to be too annoying. I opted for Exadel when the pro version became free and am excited about RHDS. I think it is going to be the best bet for full Seam Support (not sure what IDEA has up its sleave, but I know its not a priority for Netbeans or JDeveloper).
Now when the WebBeans JSR becomes a completed spec, a future version of Netbeans may be a viable option.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058905#4058905
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058905
18Â years, 9Â months
[Messaging, JMS & JBossMQ] - Message consumer closing due to error in listening thread ,
by ssuyamboo
Hi,
I close the subscriber and associated session , connection etc by calling
public static void stop() throws JMSException {
if (topicSession != null){
topicSession.close();
}
if (topicConnection != null){
topicConnection.stop();
topicConnection.close();
}
}
Everytime I am being thrown with following messages ,
(mq.SpyMessageConsumer 736 ) Message consumer closing due to error in listening thread.
javax.jms.IllegalStateException: Session is closed.
at org.jboss.mq.SpyMessage.doAcknowledge(SpyMessage.java:319)
at org.jboss.mq.SpyMessageConsumer.run(SpyMessageConsumer.java:728)
at java.lang.Thread.run(Thread.java:534)
(mq.Connection 460 ) Connection failure, use javax.jms.Connection.setExceptionListener() to handle this error and reconnect
javax.jms.IllegalStateException: Session is closed.
at org.jboss.mq.SpyMessage.doAcknowledge(SpyMessage.java:319)
at org.jboss.mq.SpyMessageConsumer.run(SpyMessageConsumer.java:728)
at java.lang.Thread.run(Thread.java:534)
This looks like a warning message. Is this a bug?
Thanks
Sundar
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058904#4058904
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058904
18Â years, 9Â months
[JBoss Messaging] - Re: Problems with concurrent.jar
by kkoster
Tim, this post did not start out as a rant against JBoss Messaging and as stated in the initial post this was not, necessarily, a messaging issue. It is simply that the problem appeared (and yes it is a problem although not monumental) during the use of messaging. I and probably most of the user community view JBoss as a set of complementary unified components that should work together in a cohesive fashion. My post was to simply point out that there seems to be a difference between an external library of code used fairly extensively throughout the JBoss suite that was causing issues with messaging. Messaging, however, is not the center of the universe, at least not in ours. It is a basic component to a larger whole. All of the JBoss components are important to us and there is a certain expectation of consistency with usage of common code. I am sorry you cannot understand this nor accept this post as an effort to point out this inconsistency instead of a complaint against JBoss messaging.
I do not blame you for nor JBoss for the particular errors that occurred, but merely attempted to lend a hand in pointing out a, probable, deployment issue of one of the independent components in the JBoss suite. If your only answers are patterned after Microsoft (accurate but useless) and colored with condescension then perhaps it would be best for me not burden you with any additional attempts to offer constructive comments regarding your product suite.
Regards,
Karl
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058903#4058903
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058903
18Â years, 9Â months
[JBoss Seam] - Re: Recommendation for layered architecture???
by gavin.kingï¼ jboss.com
anonymous wrote : That's an interesting way to look at it. Do you feel you could say the same for loose-coupling, maintainability, scalability, and all of the arguments people give for layering? Perhaps it's hard for people to see that a lot of the old-school layering techniques are done for you under the covers with Seam, and feel like they're taking the "red pill" by not self-imposing their own layers.
Maintainability is affected by three things:
* How much code there is (less is better)
* How clean and understandable the code is
* How well concerns are separated
If you look at a typical Seam application, I think you'll find that it wins on all three counts compared to a traditional Java EE architecture. Some people might say that our example apps show less separation of concerns between application orchestration and pure business logic, but I think this point is somewhat debatable. Anyway, if you feel this way it is very easy factor out the "pure business logic" into "pure business components".
I'm not sure exactly what you mean by "loose coupling", my view is that business components in Seam applications are much, much, much more loosly coupled than in traditional architectures because they don't need to manage each others lifecycles. IMO this is one of the great strengths of our component model.
Scalability is a red-herring here. The most scalable known architecture is a single physical tier with a horizontal axis of scale. Layering does not contribute to scalability.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058900#4058900
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058900
18Â years, 9Â months