August 2007 - jboss-user - Jboss List Archives

[JBoss Seam] - Re: EntityConverter: Entity Manager not found

by pete.muir＠jboss.org

"mgrouch" wrote : Yes. Requirement to use SMPC is a problem for me. | I load list of entities via Stateless Session EJB call (so no SMPC). | The entities are reverse engineered from DB at build time by hibernate tools (so no equals() method there). Hmm. Yes, in this case s:convertEntity won't work, agreed. anonymous wrote : Please, take a closer look at my code. Do you think solution provided by Seam for dropdowns is better than mine? So many people keep reporting issues with s:convertEntity... Yes. I prefer the s:convertEntity approach. And yes, its certainly not perfect, it has , I think, two restrictions: 1) You must use an SMPC to load the list 2) You must be in a conversation (you can get round both of these by implementing equals) My main problem with approach you describe below is: 1) You must extend EntitySelector in code. This works very badly with the Seam Framework and components.xml 2) To keep your entities managed, you must cache all entities in your dropdown in the conversation scope (yes, I know you can put them in the event or page scope, but then they won't be managed). 3) No support for xml mapped entities (and you're not going to get this to work afaics) 4) correct implementation of toString() on all keys (think about composite keys here) Most can be fixed, but (2) is the killer for me and I can't see how you get round it. I think its fair to say that s:convertEntity is best used in a fully Seam managed environment (Seam managed transactions, Seam managed persistence context), and probably using the application framework. However, what I'm planning to do (as discussed in another thread) is make it possible to swap out parts of the entityconverter, and I will certainly make it possible to swap out the logic which decides *what* to store to in the cache, and what scope the cache should be. This should mean you can implement what you have below inside the entity converter. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4071745#4071745 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4071745

18 years, 8 months

1
0
0 / 0

[JBossCache] - Re: Getting InterruptedException while putting into tree cac

by genman

JBoss Cache uses the older Doug Lea concurrent library which throws InterruptedException from all lock methods if the thread was interrupted. The newer 1.5 concurrent methods mostly don't do this. It's mostly done as a favor. If a thread is interrupted, typically the purpose of this interrupt is for timely shutdown of the thread. Regarding the exception thrown, any method in Java can throw a RuntimeException, which is what is happening here. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4071744#4071744 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4071744

18 years, 8 months

1
0
0 / 0

[JBoss Seam] - Re: convertEntity with non-Id key?

by nickarls

I can think of cases where a table has some String-type field that could technically work as an @Id, but the table has had an new Integer @Id added later on. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4071743#4071743 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4071743

18 years, 8 months

1
0
0 / 0

[JBoss Seam] - Re: Trinidad: Validation still not working

by stephen.friedrich

I had some help from the trinidad mailing list and did some more debugging. Ultimately it seems the bug is in facelets. They try to determine a component's JSF version by checking if it subclasses UIComponentBase, which fails for Trinidad (which has its own UIXComponentBase). This makes facelets use JSF 1.1 style ValueBindings instead of 1.2's ValueExpressions, which in turn makes Trinidad ignore the ELContext that Seam passes. I created an issue in facelets' issue tracker: https://facelets.dev.java.net/issues/show_bug.cgi?id=239 What could be a better way to check for the version? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4071742#4071742 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4071742

18 years, 8 months

1
0
0 / 0

[Installation, Configuration & DEPLOYMENT] - Re: Configuration Problem - Incompletely deployed packages

by PeterJ

The 'all' configuration assumes that it will be clustered with multiple app servers. As such, it requires more from your network than a non-clustered configuration. I recommend that you try the 'default' configuration first. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4071741#4071741 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4071741

18 years, 8 months

1
0
0 / 0

[JBoss Seam] - Re: DataModelSelection is null

by ilya78

"tim_ph" wrote : try scope CONVERSATION or wider Thanks, I have tried: It only works with session and long running conversation. But using such a wider scope introduces more complications, like ending the conversation, cleaning the data from the session, etc. I understood from the docs that Page scope was designed to do just this - persist the data to the client to be available to the next request. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4071740#4071740 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4071740

18 years, 8 months

1
0
0 / 0

[JBoss Seam] - CVS - build failed - PluginDescriptor was not found

by oblivion1200

I downloaded jboss seam from cvs and try to compile. I get exception ant | Buildfile: build.xml | | initcore: | [echo] Build JBoss Seam Core 2.0 | | select-compiler: | | antlr: | | compilecore: | [javac] Compiling 26 source files to /home/pete/bin/jboss-seam/classes/coreclasses | | jarcore: | | initpdf: | [echo] Build JBoss Seam PDF 2.0 | | installExtraDependencies: | [artifact:install] [INFO] Installing /home/pete/bin/jboss-seam/lib/jboss-cache-jdk50.jar to /home/pete/.m2/repository/jboss/jboss-cache-jdk50/1.4.1.GA-jboss-seam-2.0.0.BETA/jboss-cache-jdk50-1.4.1.GA-jboss-seam-2.0.0.BETA.jar | [artifact:install] [INFO] Installing /home/pete/bin/jboss-seam/lib/testng-5.6-jdk15.jar to /home/pete/.m2/repository/org/testng/testng/5.6-jboss-seam-2.0.0.BETA/testng-5.6-jboss-seam-2.0.0.BETA.jar | [artifact:install] [INFO] Installing /home/pete/bin/jboss-seam/lib/jbpm-jpdl.jar to /home/pete/.m2/repository/jboss/jbpm-jpdl/3.2.1-jboss-seam-2.0.0.BETA/jbpm-jpdl-3.2.1-jboss-seam-2.0.0.BETA.jar | | init.m2: | [artifact:install] [INFO] Installing /home/pete/bin/jboss-seam/pom.xml to /home/pete/.m2/repository/jboss/jboss-seam/2.0.0.BETA/jboss-seam-2.0.0.BETA.pom | | jarui: | [artifact:install] [INFO] Installing /home/pete/bin/jboss-seam/jboss-seam.jar to /home/pete/.m2/repository/jboss/jboss-seam-core/2.0.0.BETA/jboss-seam-core-2.0.0.BETA.jar | [echo] Installed jboss-seam-core pom | [java] [INFO] Scanning for projects... | [java] [INFO] Reactor build order: | [java] [INFO] JBoss Seam | [java] [INFO] Seam JSF Controls | [java] [INFO] ---------------------------------------------------------------------------- | [java] [INFO] Building JBoss Seam | [java] [INFO] task-segment: [package] | [java] [INFO] ---------------------------------------------------------------------------- | [java] [INFO] [site:attach-descriptor] | [java] [INFO] ---------------------------------------------------------------------------- | [java] [INFO] Building Seam JSF Controls | [java] [INFO] task-segment: [package] | [java] [INFO] ---------------------------------------------------------------------------- | [java] [INFO] ------------------------------------------------------------------------ | [java] [ERROR] FATAL ERROR | [java] [INFO] ------------------------------------------------------------------------ | [java] [INFO] The PluginDescriptor for the plugin Plugin [org.ajax4jsf.cdk:maven-cdk-plugin] was not found. | [java] [INFO] ------------------------------------------------------------------------ | [java] [INFO] Trace | [java] java.lang.IllegalStateException: The PluginDescriptor for the plugin Plugin [org.ajax4jsf.cdk:maven-cdk-plugin] was not found. | [java] at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:297) | [java] at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:201) | [java] at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:166) | [java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1257) | [java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(DefaultLifecycleExecutor.java:1221) | [java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:987) | [java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458) | [java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) | [java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) | [java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) | [java] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:330) | [java] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123) | [java] at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) | [java] at java.lang.reflect.Method.invoke(libgcj.so.8rh) | [java] at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) | [java] at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) | [java] at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) | [java] at org.codehaus.classworlds.Launcher.main(Launcher.java:375) | [java] [INFO] ------------------------------------------------------------------------ | [java] [INFO] Total time: 22 seconds | [java] [INFO] Finished at: Tue Aug 07 22:59:59 GMT+02:00 2007 | [java] [INFO] Final Memory: 11M/20M | [java] [INFO] ------------------------------------------------------------------------ | [java] Java Result: 1 | | BUILD FAILED | /home/pete/bin/jboss-seam/build.xml:621: Warning: Could not find file /home/pete/bin/jboss-seam/ui/target/jboss-seam-ui.jar to copy. | | Total time: 31 seconds | It looks like I don't have plugin description The PluginDescriptor for the plugin Plugin [org.ajax4jsf.cdk:maven-cdk-plugin] was not found. What I have to do to make it working? Thanks in advance. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4071739#4071739 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4071739

18 years, 8 months

1
0
0 / 0

[JBoss jBPM] - Re: task-node attribute create-tasks

by arjunbalraj

If i understand this right, when you specify the create-tasks attribute for a task node in the process defintion, it automatically creates a taskinstance when the processinstances enters the node. Then it depends on the signalling flag(Rule to exit the node on task completion) of the node 'last', 'last-wait' etc to exit the node to the specified transition. If the create-task attribute is specified, all you got to do it get it from the list of taskinstances using TaskMgmtInstance. If you create a taskinstance on your own in this case, you will have duplicate taskinstances and the node will not exit until both are completed. Hope this helps! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4071738#4071738 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4071738

18 years, 8 months

1
0
0 / 0

[JBoss Messaging] - Re: exception while starting JBoss Messaging in a cluster

by icruz

Problem solved: I was passing a name in -b option, the same name in both nodes, which resolved to each node address through /etc/hosts. It seems to confuse jbossremoting... I was supposing it to resolve the name before using it in a URL View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4071737#4071737 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4071737

18 years, 8 months

1
0
0 / 0

[JBoss jBPM] - task-node attribute create-tasks

by warfster

I'm currently working in a jbpm3.1.3 environment. I have run into an unexplained behavior with the create-tasks attribute of the task-node element. In a process definition where task-nodes do NOT contain this attribute, instantiating a new process instance and task instances, then signalling the processinstance, works as expected. It reaches the end state and creates new taskinstances along the way. In a process definition where task-nodes DO contain this attribute, instantiating a new process instance and task instances, then signalling the processinstance, does not work as expected. It ignores the transitons included in the signal and takes the default transition for every task node. The only difference is the addition of the create-tasks attribute using the eclipse plugin. Any and all ideas, suggestions, or criticisms are welcome. dhw View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4071736#4071736 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4071736

18 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user August 2007