[JBoss Seam] - Re: Seam 2.0.0.CR2: lib jars have lost their versions
by pete.muirï¼ jboss.org
So this raises a question on which feedback would be good:
Currently when we create the Seam distribution, we grab all the dependencies and shove them in all in lib/. This has a number of drawbacks
1) Not good for using inside examples (which will soon declare their dependencies through maven
2) Not good for the seam-gen if we decide to use more maven in it
3) Harder to do things like provide example only downloads or downloads without libraries
So, my proposal is that instead of providing a lib directory with loads of thirdparty libraries in it we provide an ant target [1] which will assemble a lib directory [2]. So after downloading the zip, you would run (for example):
ant assemble-libs
Drawback? A little more complex for those who just want to use plain ant.
What do you all think?
[1] If you download "seam-all.zip" you will still have all the required libraries on your machine inside the distribution, just in a mavenized structure. Otherwise this task would reach out to the net/your local maven cache to get the necessary jars.
[2] There could easily be alternative tasks to assemble the libraries with and without version suffixes.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092206#4092206
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092206
18Â years, 6Â months
[JBoss Seam] - Re: Seam 2.0.0.CR2: lib jars have lost their versions
by tynor
anonymous wrote : I think /build/root.pom.xml ought to be enough for figuring out versions, so I don't think a VERSIONS.txt file is necessary.
Perhaps so. My experience on a previous project that used Maven's ant dependency management plugin (as seam-gen apparently does now), is that the explicit dependencies in the pom.xml only tell you so much -- the transitive dependencies that bring in jars indirectly can be difficult to predict. Fortunately, when using maven dependencies directly, the resulting jars have versioned names (:)), so one could always tell what version it ended up choosing.
I don't want this to turn into a religous argument - i just want an "easy" way to tell what version of any given jar Seam has decided to bundle for me -- so when I add a new jar that also depends on, say, commons-digester.jar, I can quickly tell if it is compatible with the one I've already got.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092202#4092202
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092202
18Â years, 6Â months
[JBoss Seam] - Re: Need help updating multi-table dataTable - injecting lis
by asookazian
ok, cool. The updates worked for 3 different rows (6 cells total modified in JSF). I verified with t-sql select to check updates were successfull.
only thing is I am seeing the following error(s) after submit:
14:19:23,918 INFO [CustomerAction] in getCustomers(): user.getUserId() = 4461
| 14:19:24,918 INFO [CustomerAction] in destroy()
| 14:19:38,573 INFO [CustomerAction] in getCustomers(): user.getUserId() = 4461
| 14:19:38,620 INFO [CustomerAction] in submit()
| 14:19:50,588 INFO [CustomerAction] in submit()
| 14:20:13,056 ERROR [SeamPhaseListener] uncaught exception
| java.lang.NullPointerException
| at org.jboss.seam.jsf.AbstractSeamPhaseListener.afterPhase(AbstractSeamPhaseListener.java:157)
I will try to determine if your way of doing is better or not. this is the submit() code:
Iterator it = myList.iterator();
|
| while (it.hasNext()) {
| Object[] result = (Object[])it.next();
| Customers customers = (Customers)result[0];
| em.merge(customers);
| CreditCard creditCard = (CreditCard)result[1];
| em.merge(creditCard);
| }
Is it possible to do it all in one transaction?? Isn't the above doing two merges(updates) per row??
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092197#4092197
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092197
18Â years, 6Â months