[jboss-user] [JBoss Seam] - s:decorate question
I've been trying to use s:decorate in a form. Here is the fragment I am using
to 'decorate':
| ui:composition ...
|
| s:div id=#{id} style=margin-bottom:9px;
| label class=topLabel
| ui:insert name=labelField Label/ui:insert
| /label
| div
| ui:insert name=fieldForm Field/ui:insert
| s:span styleClass=required rendered=#{required}*/s:span
| /div
| s:message styleClass=invalid/
| /s:div
| /ui:composition
|
and in my form, I'm using this with s:decorate like such:
| a4j:form id=newApplication
|
| h:messages/
|
| s:decorate
template=/WEB-INF/view/components/label-on-top-fieldset.xhtml
| ui:param name=id value=nameRow/
| ui:define name=labelName:/ui:define
| ui:define name=field
| h:inputText id=name value=#{appToEdit.name}
|styleClass=textField style=font-weight:bold;
|size=32 required=true/
| /ui:define
| /s:decorate
|
|
|
|
The problem I am having is that in addition to a submit button, I want to use a
cancel button (or link); no matter which technique (button or link) I use,
validation is invoked and thus I can never 'cancel' out of my form.
Is there a way to tell s:decorate to not invoke validate for a JSF request?
Thanks,
Brad Smith
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4127863#4127863
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4127863
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - 2.0.1.GA - Ye Ole Maven2 + JBoss Embeddable problems
What's changed w.r.t. to JBoss Embeddable and / or SeamTest ? I was able to move from Seam 2.0.0 to Seam 2.0.1.CR1 (yes the bootstrap stuff changed a bit in that transition). But now, when trying to upgrade to 2.0.1.GA, I'm getting several exceptions - Here's the first: | 10:12:49,242 WARN org.jboss.mx.loading.UnifiedLoaderRepository3.(addClassLoader:713) - Tried to add non-URLClassLoader. Ignored | 10:12:50,406 ERROR org.jboss.embedded.DeploymentScanner.(start:109) - Failed to deploy | org.jboss.deployers.spi.DeploymentException: Error populating deployment vfsfile:/home/brad/work/BrooklineInfo/ejbs/target/test-classes/conf/jboss-service.xml | at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) | at org.jboss.deployers.structure.spi.helpers.AbstractStructureBuilder.populateContext(AbstractStructureBuilder.java:77) | at org.jboss.deployers.structure.spi.helpers.AbstractStructuralDeployers.determineStructure(AbstractStructuralDeployers.java:89) | at org.jboss.deployers.plugins.main.MainDeployerImpl.determineStructure(MainDeployerImpl.java:743) | at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:280) | at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:237) | at org.jboss.embedded.DeploymentGroup.add(DeploymentGroup.java:153) | at org.jboss.embedded.DeploymentGroup.add(DeploymentGroup.java:166) | at org.jboss.embedded.DeploymentGroup.addResource(DeploymentGroup.java:326) | at org.jboss.embedded.DeploymentScanner.start(DeploymentScanner.java:81) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:56) | at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:110) | at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66) | at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:214) | at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:45) | at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:108) | at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:69) | at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:221) | at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:135) | at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:46) | at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) | at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) | at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) | at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309) | at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:574) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:398) | at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBean(AbstractKernelDeployer.java:309) | at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBeans(AbstractKernelDeployer.java:279) | at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deploy(AbstractKernelDeployer.java:130) | at org.jboss.kernel.plugins.deployment.xml.BeanXMLDeployer.deploy(BeanXMLDeployer.java:96) | at
[jboss-user] [JBoss Seam] - Re: extra jars needed when deploying a Seam 2.0.1.CR2 app in
It would be nice if Seam 2.0.1 GA tracked the the jboss-embeddable that appeared in 2.0.1.CR1 instead of whatever it got released with. I'm all for bug fixes, documentation improvements, maybe a new feature or feature improvement. The volatility of the Seam(Test) + JBoss Embeddable stuff is quite a pain (I'm coming from a maven2 perspective - not a RHDS and/or seam-gen perspective). View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4125202#4125202 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4125202 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: 2.0.1.GA - Ye Ole Maven2 + JBoss Embeddable problems
Error in your docs already: http://docs.jboss.com/seam/2.0.1.GA/reference/en/html/testing.html#d0e22927 Table 33.1. anonymous wrote : org.jboss.seam.embedded jboss-embedded-api lib/test/jboss-embedded-api.jar looks to me like this jar is in the /lib directory, not /lib/test. Brad View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4125242#4125242 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4125242 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Seam Security - NotLoggedInException
Hello, Is it possible to come up with something 'quieter' for the case where a user is not logged in and needs redirection to become logged in? Having lots of these exceptions | 10:58:07,196 ERROR [SeamPhaseListener] uncaught exception | org.jboss.seam.security.NotLoggedInException | at org.jboss.seam.navigation.Pages.redirectToLoginView(Pages.java:517) | at org.jboss.seam.navigation.Pages.postRestore(Pages.java:372) | at org.jboss.seam.jsf.SeamPhaseListener.postRestorePage(SeamPhaseListener.java:528) | at org.jboss.seam.jsf.SeamPhaseListener.afterRestoreView(SeamPhaseListener.java:374) | at org.jboss.seam.jsf.SeamPhaseListener.afterServletPhase(SeamPhaseListener.java:211) | at org.jboss.seam.jsf.SeamPhaseListener.afterPhase(SeamPhaseListener.java:184) | at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:280) | at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) | at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at com.evergreen.filter.RequestDumper.doFilter(RequestDumper.java:87) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) | at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:68) | at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) | at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85) | at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) | at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) | at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) | at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:44) | at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) | at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:141) | at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:281) | at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:60) | at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) | at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) | at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) | at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) | at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) | at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) | at com.evergreen.architecture.sso.catalina.CASSSOAuthenticatorValve.invoke(CASSSOAuthenticatorValve.java:423) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) | at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) | at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) | at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:437) | at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:366) | at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) | at java.lang.Thread.run(Thread.java:595) | show up in server logs is not exactly ideal. Any ideas about how to turn these off are
[jboss-user] [JBoss Seam] - Re: Seam Security - NotLoggedInException
I see I've already asked for this before - thanks for the update. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4117627#4117627 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4117627 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: how to 'stay in conversation' with rich suggestionbox?
Pete, It's a been a few weeks (~6 ;-)) but I ultimately reverted to session scope for most of our state in the simple application in which the issue arose. Thus, I don't have a solution for the problem I ran into here. I will be in my office mid-next week and can look at that specific application again - we're using suggestionbox quite a bit in it. On another note, I have solved the Seam-with-maven2-and-jboss-embedded-for-testing problem. I've been meaning to post something on a site of my own that provides detailed instructions for how to repeat the solution. Maybe I'll get that out today... Brad View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4115524#4115524 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4115524 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: how to 'stay in conversation' with rich suggestionbox?
Damian, thirdPartyHelper is a SLSB - the intent here is to simply provide the suggested options - it takes about 2-3 seconds to respond. my core:manager settings are as follows: | core:manager concurrent-request-timeout=500 | conversation-timeout=90 | conversation-id-parameter=cid/ | I believe my conversation timeout parameter is longer than your suggestion (15 minutes above). I wonder what that concurrent-request-timeout param does... Thanks, Brad View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4104089#4104089 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4104089 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Seam 2.0.0.0GA + Maven2 doesn`t work...
Here's one difference between my poms for an ear and yours.
In the parent pom, it's my experience that I should generally build the ejb
jar(s) before the webapp war(s) - often the webapp(s) depend on the ejb(s)
(mainly for custom converters).
| modules
| moduleejb/module
| modulewebapp/module
| moduleear/module
| /modules
|
Also, presumably, you've put a seam.properties file in
${PROJECT_HOME}/ejb/src/main/resources - there have been times in a new project
when I haven't done this and run into the same problem. After you've checked
that, my guess is it's time to double check the jndiPattern in your webapp's
components.xml file.
Good Luck
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4104099#4104099
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4104099
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: how to 'stay in conversation' with rich suggestionbox?
Pete, I went to 10 seconds concurrent-request-timeout=1 - no luck. I looked over the documentation on that in the manual (just above section 6.9.1 which I used to come up with the settings used in the suggestionbox attributes). The basic flow I am trying to 'do' is: a.) on an editor page, select or create a new (parent) entity for edit purposes b.) add a new child entity to the parent by clicking a link (JSF commandButton which should preserve conversation id - it does). c.) return to parent editor page. It's while working on b.), during selection of a suggested entity, that I am losing track of the SFSB and other conversational objects (particularly the parent entity) that are bijected on the SFSB using the @In/@Out annotations. Isn't it correct that an entity which is @Out'ed from a SFSB is @Out'ed to the same scope as the SFSB? The default scope for a SFSB should be conversational. Notice above in post one that I put the conversation ID (cid) in the form as extra 'insurance' that my events occur in the scope of the same conversation. Also, I've made sure that my navigation rules 'join' the conversation as well (frustration meter rising! ;-)) Thanks, Brad View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4104113#4104113 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4104113 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Is facelets a MUST for a seam application?
Seam-mail requires facelets - maybe some of the other seam components do too. I think you can simply add facelets to your .war or .ear and not use it for view (page) template creation. Why not just add it? From your exception above, it seems like the Tomcat loader is complaining about Facelets not being found - my first guess is that in your web.xml or in faces-config.xml, you've explicitly declared that you want to include Facelets - I don't see a seam class in that stack trace. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4104190#4104190 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4104190 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - how to 'stay in conversation' with rich suggestionbox?
I am having trouble 'staying in conversation' using a SFSB that backs a parent
form and a child form.
From the parent form, I have the following navigation rule:
| page view-id=/MMktIssuer.xhtml login-required=true
| ...
| navigation from-action=#{moneyMarketIssuerEditor.insertGuarantor}
| begin-conversation join=true/
| render view-id=/EditGuarantorObligor.xhtml/
| /navigation
| ...
| /page
|
In the child form, I have a (rich) suggestion box. When I select a value from
the suggestions, I have a4j:support tag call a method on my SFSB to update
state. I also have a navigation rule:
| page view-id=/EditGuarantorObligor.xhtml login-required=true
conversation-required=true
| navigation
from-action=#{moneyMarketIssuerEditor.selectThirdPartyByCode}
| begin-conversation join=true/
| render view-id=/EditGuarantorObligor.xhtml/
| /navigation
|
| /page
|
Here is the suggestion box JSF markup that triggers the 'selection'
| a4j:form id=editGuarantorForm
| input type=hidden name=cid value=#{conversation.id}/
| h:inputHidden id=code value=#{editGuarantor.thirdParty.code}/
|
| h:panelGrid columns=2
| h:outputText value=3rd Party Code/
| h:panelGroup
| h:inputText id=thirdPartyCode
value=#{editGuarantor.thirdParty.thirdPartySelectionDisplay} size=60
|
style=height:20px;background:url('img/magnifying-glass.png') no-repeat center
right;vertical-align:middle;
|maxlength=255/
| h:graphicImage value=img/check2-16x16.png alt=Ultimate Parent
| rendered=#{thirdParty.udThirdParty.ultimateParent ==
1}/
| h:graphicImage value=img/spacer.png alt= width=16 height=16
| rendered=#{thirdParty.udThirdParty.ultimateParent !=
1}/
| rich:suggestionbox for=thirdPartyCode minChars=1
requestDelay=750
|
suggestionAction=#{thirdPartyHelper.getThirdPartiesByName}
| var=thirdParty fetchValue=#{thirdParty.code}
| height=270 width=285
| a4j:support event=onselect
action=#{moneyMarketIssuerEditor.selectThirdPartyByCode}
|
onsubmit=$('editGuarantorForm:code').value=$('editGuarantorForm:thirdPartyCode').value;
| reRender=editGuarantorForm/
| facet name=nothingLabel (case sensitive)
| h:outputText value=No matches found.../
| /facet
| h:column
| #{thirdParty.code}#{thirdParty.name}
| h:graphicImage value=img/check2-16x16.png
|
rendered=#{thirdParty.udThirdParty.ultimateParent == 1}/
| /h:column
| /rich:suggestionbox
| /h:panelGroup
|
| ...
| /a4j:form
|
When the a4j:support fires (due to event 'onselect'), the selection should be
added to an object that is part of the conversation (parent-child type of
relationship). What's happening is that the parent object is now 'reset' as if
I started a new conversation help?
Thanks,
Brad Smith
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4103853#4103853
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4103853
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Seam 2.0.0.0GA + Maven2 doesn`t work...
There's been some research into Seam + Maven 2 unit testing in this thread. http://www.jboss.com/index.html?module=bbop=viewtopict=122406postdays=0postorder=ascstart=0 Transitive dependencies suck - anytime you put an exclusion into your pom you're fixing a problem due to this so-called feature of maven2. (IMHO) View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4103866#4103866 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4103866 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Writing SeamTests with Seam 2.0.0. CR2 - What's Changed?
anonymous wrote : Well the error you posted is because your jndiPattern isn't getting set I think. That's what it looks like, but I've set the jndiPattern, even wrote code to query the JNDI tree and list all the bound objects - I'm using the right pattern and seam is not finding it (in my setup). I believe there is a classloader issue here; possibly another components.xml being read (but I haven't looked into this in about a week and a half now) anonymous wrote : This is all further compounded by the fact that Embedded JBoss needs a maintainer. Please, take your frustrations over to the Embedded JBoss forum as well as that is the place to rant to get the right people's attention. | er I wouldn't even use JSF if I hadn't got started with Seam - I don't particularly like JSF. I might have been happy sticking with Hibernate + Spring for entities, DAOs, biz-objects, etc., however, Seam made the case for EJB3. Because I elected to try Seam, I needed to take a look at JSF, Facelets, 1-or-more JSF tag libraries, and EJB3. One of the perils of using Seam, at least for me, is how Seam forces me to track several dimensions (frameworks, API's, configurations, etc.) simultaneously. My point here is that I wouldn't be using the Jboss Embedded if I hadn't followed the seam recommendation to use EJB3 (this was before Seam IOC existed...). I don't think it's responsible for the framework to promote a usage pattern and break that pattern. I think the frustration is well-placed here. I've already mentioned (either here in the forum or to Gavin) that I would have been quite happy to follow Seam 1.2.1 to 1.3.X but, hey, 1.3. is Dead On Arrival. I was looking for fixes in the 1.2.1 -to- 1.3.X codebase. My only forward path with Seam is 1.2.1 to 2.0.0 and thus, I have to resolve solved problems, and thus here we are discussing this stuff Anyway, I'm going to have to waste some more time to get that jboss embedded working via maven 2 - I'm close, but not quite done http://www.nytimes.com/2007/11/06/science/06tier.html View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4103877#4103877 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4103877 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Writing SeamTests with Seam 2.0.0. CR2 - What's Changed?
WEB-INF/components.xml? no - I'm trying to boot the embedded jboss ONLY from an ejb module that's part of a larger ear project. This all worked nicely in Seam 1.2.1. I say that because (as you probably know quite well by now ;-)) that I am immensely frustrated at things like core:ejb disappearing. I can't understand why you wouldn't think about supporting that IN ADDITION TO whatever new form of the JBoss container you want people to be able to boot and test with. As it stands now, in order to migrate our development process from Seam 1.2.1 to Seam 2.0.0, I have to figure out how to get a working jboss embedded (in addition to other things). Although traditionally, the focus of a framework evolution is to fix problems in the current version of the framework and add in new features, this current 'style of evolution' I see in Seam is one in which I am forced to move all dimensions of my development work forward simultaneously. On the subject of maven and transitive dependencies, please do not deploy the Seam 2.0 releases to your public repository with poms that contain transitive dependencies - that's already tripped me up once because Seam 2.0.0.CR3 transitively stuck el-api.jar into my war and that already existed in the server. Transitive dependencies buy you nothing when they cause unexpected problems that take longer to fix (due to the surprise nature) than simply adding the dependencies you know you need due to good documentation. Knowing version dependencies (to me) is a good thing. Hiding versions and/or dependencies is bad. BTW, Pete, I appreciate your discussions / interactions and patience with me ;-). In all my rants on the forum here, my frustrations tend to stem from no smooth transition being available for Seam 1.2.1 - Seam 2.0.0 (on the issues I've posted about). I believe Seam could be a little kinder to its early adopters than it has been. Instead, I have several areas now where I need to 'start from scratch' (e.g. core:ejb/ gone but actually worked fine ... hence this particular thread). View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4100794#4100794 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4100794 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Writing SeamTests with Seam 2.0.0. CR2 - What's Changed?
please start a new thread with this topic I am having trouble simply getting the most basic test to work Thanks View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4100835#4100835 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4100835 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Writing SeamTests with Seam 2.0.0. CR2 - What's Changed?
[EMAIL PROTECTED] wrote : In Seam 1.2 and earlier we used Embedded EJB3, now we use Embedded JBoss, two different projects.anonymous wrote : | | | | Clearly! | | | | anonymous wrote : | | | These are the instructions that I wrote for using the Eclipse TestNG plugin which you may find useful: | | | | | | | Hopefully - thanks. :-| View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4100151#4100151 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4100151 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Writing SeamTests with Seam 2.0.0. CR2 - What's Changed?
Pete, Do you know what's up with vfsfile as a protocol in JBoss Embedded? | ERROR [org.jboss.embedded.DeploymentScanner] Failed to deploy | org.jboss.deployers.spi.DeploymentException: Unable to find deployDir from url: file:/c:/work/BusinessIntelligence/InfoStratGui/app/target/test-clas | ses/deployers/ | at org.jboss.embedded.DeploymentGroup.getDeployerDirUrls(DeploymentGroup.java:536) | at org.jboss.embedded.DeploymentGroup.getDeployerDirUrlsFromResource(DeploymentGroup.java:522) | at org.jboss.embedded.DeploymentGroup.addDirectoryByResource(DeploymentGroup.java:470) | at org.jboss.embedded.DeploymentScanner.start(DeploymentScanner.java:99) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:55) | at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:108) | at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66) | at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:103) | at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:145) | at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:197) | at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.install(KernelControllerContextAction.java:136) | at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) | at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:233) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:724) | at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:445) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:555) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:489) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:289) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:192) | at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBean(AbstractKernelDeployer.java:302) | at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBeans(AbstractKernelDeployer.java:272) | at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deploy(AbstractKernelDeployer.java:119) | at org.jboss.kernel.plugins.deployment.xml.BeanXMLDeployer.deploy(BeanXMLDeployer.java:96) | at org.jboss.embedded.Bootstrap.deployBaseBootstrapUrl(Bootstrap.java:150) | at org.jboss.embedded.Bootstrap.bootstrapURL(Bootstrap.java:162) | at org.jboss.embedded.Bootstrap.bootstrap(Bootstrap.java:201) | at org.jboss.embedded.Bootstrap.bootstrap(Bootstrap.java:214) | at org.jboss.seam.mock.EmbeddedBootstrap.startAndDeployResources(EmbeddedBootstrap.java:11) | at org.jboss.seam.mock.BaseSeamTest.startJbossEmbeddedIfNecessary(BaseSeamTest.java:1006) | at org.jboss.seam.mock.BaseSeamTest.init(BaseSeamTest.java:931) | at org.jboss.seam.mock.SeamTest.init(SeamTest.java:42) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:645) | at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:385) | at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:141) | at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:79) | at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:158) | at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:103) | at org.testng.TestRunner.runWorkers(TestRunner.java:673) | at org.testng.TestRunner.privateRun(TestRunner.java:620) | at org.testng.TestRunner.run(TestRunner.java:480) | at
[jboss-user] [JBoss Seam] - Re: Nested ui:repeat fails
[EMAIL PROTECTED] wrote : [EMAIL PROTECTED] wrote : I suggest you use the latest version of facelets (in which this bug has been fixed. Facelets 1.1.14) and ui:repeat and not tomahawk at all. If you still see this problem with Facelets 1.1.14 then post on the facelets mailing list. | | Tried upgrading to Facelets 1.1.14 but then my pages won't show up at all (i.e., blank page presented but no exceptions generated in the server-log) I guess some other library needs to be updated? Any suggestions on what could cause this? where is Facelets 1.1.14? the latest release I see on their site is 1.1.13. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4100236#4100236 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4100236 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Writing SeamTests with Seam 2.0.0. CR2 - What's Changed?
| [DEBUG] Test Classpath : | [DEBUG] c:\work\BusinessIntelligence\InfoStratGui\app\target\classes | [DEBUG] c:\work\BusinessIntelligence\InfoStratGui\app\target\test-classes | [DEBUG] C:\Documents and Settings\a428302\.m2\repository\javax\faces\jsf-impl\1.2_04\jsf-impl-1.2_04.jar | [DEBUG] C:\Documents and Settings\a428302\.m2\repository\javax\transaction\jta\1.0.1B\jta-1.0.1B.jar | [DEBUG] C:\Documents and Settings\a428302\.m2\repository\junit\junit\3.8.1\junit-3.8.1.jar | [DEBUG] C:\Documents and Settings\a428302\.m2\repository\javax\servlet\el-api\2.1wFacelets1.1.4\el-api-2.1wFacelets1.1.4.jar | [DEBUG] C:\Documents and Settings\a428302\.m2\repository\javax\persistence\ejb3-persistence\1.0\ejb3-persistence-1.0.jar | [DEBUG] C:\Documents and Settings\a428302\.m2\repository\org\jboss\seam\jboss-embedded-all\2.0.0.CR3\jboss-embedded-all-2.0.0.CR3.jar | [DEBUG] C:\Documents and Settings\a428302\.m2\repository\commons-logging\commons-logging\1.0.4\commons-logging-1.0.4.jar | [DEBUG] C:\Documents and Settings\a428302\.m2\repository\org\jboss\jboss-ejb3x\4.0.4.EJB3.RC8\jboss-ejb3x-4.0.4.EJB3.RC8.jar | [DEBUG] C:\Documents and Settings\a428302\.m2\repository\org\jboss\seam\jboss-embedded-api\2.0.0.CR3\jboss-embedded-api-2.0.0.CR3.jar | [DEBUG] C:\Documents and Settings\a428302\.m2\repository\jconnect\jconnect\6.0\jconnect-6.0.jar | [DEBUG] C:\Documents and Settings\a428302\.m2\repository\org\testng\testng\5.5\testng-5.5-jdk15.jar | [DEBUG] C:\Documents and Settings\a428302\.m2\repository\org\jboss\seam\jboss-el\2.0.0.CR3\jboss-el-2.0.0.CR3.jar | [DEBUG] C:\Documents and Settings\a428302\.m2\repository\org\jboss\seam\hibernate-all\2.0.0.CR3\hibernate-all-2.0.0.CR3.jar | [DEBUG] C:\Documents and Settings\a428302\.m2\repository\org\jboss\seam\jboss-seam\2.0.0.CR3\jboss-seam-2.0.0.CR3.jar | [DEBUG] C:\Documents and Settings\a428302\.m2\repository\org\hibernate\hibernate-annotations\3.3.0.GA\hibernate-annotations-3.3.0.GA.jar | [DEBUG] C:\Documents and Settings\a428302\.m2\repository\javax\servlet\servlet-api\2.5\servlet-api-2.5.jar | [DEBUG] C:\Documents and Settings\a428302\.m2\repository\javax\servlet\el-ri\2.1wFacelets1.1.4\el-ri-2.1wFacelets1.1.4.jar | [DEBUG] C:\Documents and Settings\a428302\.m2\repository\com\evergreen\architecture\evg-jaas-components\1.0\evg-jaas-components-1.0.jar | [DEBUG] C:\Documents and Settings\a428302\.m2\repository\javax\faces\jsf-api\1.2_04\jsf-api-1.2_04.jar | [DEBUG] C:\Documents and Settings\a428302\.m2\repository\org\hibernate\hibernate-validator\3.0.0.GA\hibernate-validator-3.0.0.GA.jar | [DEBUG] C:\Documents and Settings\a428302\.m2\repository\org\jboss\seam\thirdparty-all\2.0.0.CR3\thirdparty-all-2.0.0.CR3.jar | [DEBUG] C:\Documents and Settings\a428302\.m2\repository\org\jboss\seam\jboss-deployers\2.0.0.CR3\jboss-deployers-2.0.0.CR3.jar | [DEBUG] Setting system property [localRepository]=[C:\Documents and Settings\a428302\.m2\repository] | [DEBUG] Setting system property [basedir]=[c:\work\BusinessIntelligence\InfoStratGui\app] | classes - my compiled application classes, EJB's, entities, JPA, etc. test-classes - the test classes and the entire directory tree from the bootstrap directory in the Seam 2.0.0.CR3 and a /META-INF/components.xml. Seam is starting but the embedded container is having trouble here. It seems like all the ResourcesToDeploy3 blocks in bootstrap-beans.xml are failing - each one results in a message like this: | ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Start: name=ResourcesToDeploy3 state=Create | org.jboss.deployers.spi.DeploymentException: Unable to find deployDir from url: file:/c:/work/BusinessIntelligence/InfoStratGui/app/target/test-clas | ses/deploy/ | at org.jboss.embedded.DeploymentGroup.getDeployerDirUrls(DeploymentGroup.java:536) | at org.jboss.embedded.DeploymentGroup.getDeployerDirUrlsFromResource(DeploymentGroup.java:522) | at org.jboss.embedded.DeploymentGroup.addDirectoryByResource(DeploymentGroup.java:470) | at org.jboss.embedded.DeploymentScanner.start(DeploymentScanner.java:99) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:55) | at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:108) | at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66) | at
[jboss-user] [JBoss Seam] - Re: Writing SeamTests with Seam 2.0.0. CR2 - What's Changed?
Pete, I have this figured out now. No need to investigate any further. Thanks, Brad View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4100350#4100350 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4100350 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Writing SeamTests with Seam 2.0.0. CR2 - What's Changed?
ok, now I have this to figure out: | On=null whenRequired=Described resolved=false demand=persistence.units:jar=classes.jar,unitName=InfoStratGui} ** | persistence.units:jar=classes.jar,unitName=InfoStratGui - java.lang.NoSuchMethodError: org.hibernate.cfg.AnnotationConfiguration.getReflectionManag | er()Lorg/hibernate/reflection/ReflectionManager; | | at org.jboss.embedded.DeploymentGroup.checkIncomplete(DeploymentGroup.java:151) | at org.jboss.embedded.DeploymentGroup.process(DeploymentGroup.java:129) | at org.jboss.embedded.Bootstrap.deployResourceBases(Bootstrap.java:307) | at org.jboss.seam.mock.EmbeddedBootstrap.startAndDeployResources(EmbeddedBootstrap.java:14) | at org.jboss.seam.mock.BaseSeamTest.startJbossEmbeddedIfNecessary(BaseSeamTest.java:1006) | at org.jboss.seam.mock.BaseSeamTest.init(BaseSeamTest.java:931) | at org.jboss.seam.mock.SeamTest.init(SeamTest.java:42) | View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4100371#4100371 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4100371 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Writing SeamTests with Seam 2.0.0. CR2 - What's Changed?
I don't believe wrong is the correct term to describe the situation, rather, from your (Seam team) perspective, you provide examples that are based on 'things' being in places in the Seam 2.0.0.CR(X) distribution. Thus, jars like jboss-embedded-all.jar are not truly all. I say that because I had to discover (the hard way) that I needed to add jboss-embedded-api.jar and jboss-deployers.jar to my repo and test-scoped dependencies to my pom.xml. No, this is not in the Seam 2.0.0.CR3 docs - I double checked. I'm guessing your ant scripts build up classpaths using the lib and the lib/test directories in the distro and so it's easy to miss this kind of thing. I also just discovered that I need to add hibernate-commons-annotations.jar to my test-scoped dependencies, and thus, again, hibernate-all.jar is not truly all. It would be nice if the 'all' jars were truly 'all'. ;-) I also needed to learn the jboss embedded container layout a bit; this is so that I could put appropriate maven2 testResource instructions into my pom(s) and reproduce the bootstrap directory layout. And... I needed to figure out that I need to copy my target/classes contents to the bootstrap deploy dir (I haven't figured out how to get the bootstrap to treat target/classes as part of the classpath). I'm close now. Thanks, Brad View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4100368#4100368 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4100368 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Writing SeamTests with Seam 2.0.0. CR2 - What's Changed?
I see that if hibernate-annotations 3.3.0 is in the classpath, I get the last error, now I am up to this: | *** CONTEXTS IN ERROR: Name - Error | UNKNOWN - ** UNRESOLVED [EMAIL PROTECTED]:jar=classes,name=RatingsHelperBean,service=EJB3 depen | dsOn=null whenRequired=Described resolved=false demand=persistence.units:jar=classes.jar,unitName=InfoStratGui} ** | persistence.units:jar=classes.jar,unitName=InfoStratGui - java.lang.SecurityException: Invalid authentication attempt, principal=null | | at org.jboss.embedded.DeploymentGroup.checkIncomplete(DeploymentGroup.java:151) | at org.jboss.embedded.DeploymentGroup.process(DeploymentGroup.java:129) | at org.jboss.embedded.Bootstrap.deployResourceBases(Bootstrap.java:307) | at org.jboss.seam.mock.EmbeddedBootstrap.startAndDeployResources(EmbeddedBootstrap.java:14) | at org.jboss.seam.mock.BaseSeamTest.startJbossEmbeddedIfNecessary(BaseSeamTest.java:1006) | at org.jboss.seam.mock.BaseSeamTest.init(BaseSeamTest.java:931) | at org.jboss.seam.mock.SeamTest.init(SeamTest.java:42) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:645) | at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:385) | at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:141) | at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:79) | at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:158) | at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:103) | at org.testng.TestRunner.runWorkers(TestRunner.java:673) | at org.testng.TestRunner.privateRun(TestRunner.java:620) | at org.testng.TestRunner.run(TestRunner.java:480) | at org.testng.SuiteRunner.runTest(SuiteRunner.java:278) | at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:273) | at org.testng.SuiteRunner.privateRun(SuiteRunner.java:253) | at org.testng.SuiteRunner.run(SuiteRunner.java:168) | at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:987) | at org.testng.TestNG.runSuitesLocally(TestNG.java:951) | at org.apache.maven.surefire.testng.TestNGExecutor.executeTestNG(TestNGExecutor.java:161) | at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:101) | at org.apache.maven.surefire.Surefire.run(Surefire.java:132) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:275) | at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:832) | How do I turn off the security stuff for testing? Thanks, Brad View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4100382#4100382 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4100382 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Writing SeamTests with Seam 2.0.0. CR2 - What's Changed?
It looks like when the local-jdbc connection pool manager is trying to connect to the DB, it's running into issues: | 13:43:18,374 DEBUG org.jboss.ejb3.entity.PersistenceUnitDeployment.(start:187) - Found persistence.xml file in EJB3 jar | 13:43:20,156 WARN org.jboss.resource.connectionmanager.JBossManagedConnectionPool.(getConnection:278) - Throwable while attempting to get a new con | nection: null | org.jboss.resource.JBossResourceException: No matching credentials in Subject! | at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnectionFactory.getConnectionProperties(BaseWrapperManagedConnectionFactory.java:472) | | at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:158) | at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:586) | at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:254) | at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:580) | at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:341) | at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:351) | at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:394) | at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:838) | at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:88) | at org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider.getConnection(InjectedDataSourceConnectionProvider.java:47) | at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:76) | at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2006) | at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1289) | at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:691) | at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:127) | at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:246) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:55) | at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:108) | at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66) | at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:103) | at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:145) | at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:197) | at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.install(KernelControllerContextAction.java:136) | at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) | at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:233) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:724) | at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:445) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:555) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:489) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:289) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:192) | at org.jboss.kernel.plugins.dependency.AbstractKernelController.install(AbstractKernelController.java:84) | at org.jboss.kernel.plugins.dependency.AbstractKernelController.install(AbstractKernelController.java:78) | at
[jboss-user] [JBoss Seam] - Re: Writing SeamTests with Seam 2.0.0. CR2 - What's Changed?
hopefully this is the last question I have on the jboss embedded container.
I'm currently having trouble on boot - it says here:
| init(com.wachovia.evergreen.apps.infostrat.BootStrapTest) Time elapsed: 0
sec FAILURE!
| java.lang.RuntimeException: Could not create Component:
commercialPaperHelper
| at
org.jboss.seam.init.Initialization.addComponent(Initialization.java:976)
| at
org.jboss.seam.init.Initialization.installComponents(Initialization.java:903)
| at org.jboss.seam.init.Initialization.init(Initialization.java:548)
| at org.jboss.seam.mock.BaseSeamTest.init(BaseSeamTest.java:939)
| at org.jboss.seam.mock.SeamTest.init(SeamTest.java:42)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at
org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:645)
| at
org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:385)
| at
org.testng.internal.Invoker.invokeConfigurations(Invoker.java:141)
| at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:79)
| at
org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:158)
| at
org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:103)
| at org.testng.TestRunner.runWorkers(TestRunner.java:673)
| at org.testng.TestRunner.privateRun(TestRunner.java:620)
| at org.testng.TestRunner.run(TestRunner.java:480)
| at org.testng.SuiteRunner.runTest(SuiteRunner.java:278)
| at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:273)
| at org.testng.SuiteRunner.privateRun(SuiteRunner.java:253)
| at org.testng.SuiteRunner.run(SuiteRunner.java:168)
| at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:987)
| at org.testng.TestNG.runSuitesLocally(TestNG.java:951)
| at
org.apache.maven.surefire.testng.TestNGExecutor.executeTestNG(TestNGExecutor.java:161)
| at
org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:101)
| at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:275)
| at
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:832)
| Caused by: java.lang.IllegalArgumentException: You must specify
org.jboss.seam.core.init.jndiPattern or use @JndiName: commercialPaperHelper
| at org.jboss.seam.Component.getJndiName(Component.java:437)
| at org.jboss.seam.Component.init(Component.java:242)
| at org.jboss.seam.Component.init(Component.java:216)
| at
org.jboss.seam.init.Initialization.addComponent(Initialization.java:961)
| ... 32 more
|
I've examined the server log and it's not clear to me where in the JNDI tree
the server is deploying the EJB's. My components.xml has the following
core:init tag:
| core:init debug=true jndi-pattern=#{ejbName}/local/
|
In my Seam 1.2.1 app, which uses the (old?) jboss microcontainer, my core:init
tag is identical:
| core:init jndi-pattern=#{ejbName}/local debug=true/
|
and that has and does work fine. Since I can't easily see what's going on with
JBoss naming (org.jboss.naming) even with DEBUG level logging on, I'm not sure
what the pattern is. Does anyone know?
Thanks,
Brad
core:init jndi-pattern=#{ejbName}/local debug=true/
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4100419#4100419
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4100419
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Writing SeamTests with Seam 2.0.0. CR2 - What's Changed?
Strange how ComponentTest doesn't come with support for init()'ing the container environment. I see by adding init() (and begin()) that I can get farther, now Seam doesn't know how to create my component. Guess it's time to try FacesRequest again ... sigh Thanks View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4099929#4099929 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4099929 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Writing SeamTests with Seam 2.0.0. CR2 - What's Changed?
it looks like the version of testng supplied with Seam 2.0.0.CR3 is 5.6-200706070953 (from MANIFEST.MF file). The maven2 surefire plugin docs are based on testng 4.7 (which I was using - see previous post in thread). So has anyone out there found a way to get maven2-surefire to work with testng 5.5 or higher? Thanks View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4099957#4099957 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4099957 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Writing SeamTests with Seam 2.0.0. CR2 - What's Changed?
is this dependency no longer sufficient?
| dependency
| groupIdorg.testng/groupId
| artifactIdtestng/artifactId
| version4.7/version
| scopetest/scope
| classifierjdk15/classifier
| /dependency
|
here is the test I am working with at the moment:
| public class BootStrapTest extends SeamTest {
|
| @Test
| public void test_persistenceMappingsGuud() throws Exception {
|
| new ComponentTest() {
|
| protected void testComponents() throws Exception {
| init();
| begin();
| EntityManager entityManager = (EntityManager)
getInstance(entityManager);
| assert entityManager != null;
| ListType types = entityManager.createQuery(
| from Type t
| ).getResultList();
| assert types != null;
| assert types.size() 0;
| }
|
| }.run();
|
| }
| }
|
I just want to be sure the container is booted and my entity model is 'correct'
before other tests fire, but right now I am stuck with just trying to boot the
container.
Thanks
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4099940#4099940
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4099940
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Writing SeamTests with Seam 2.0.0. CR2 - What's Changed?
oh yes, one rant - if a specific version of testng is required, then what happened to the days when frameworks listed out their depedencies including versions? Has listing depedencies gone the way of documentation? ;-) from an old version of hibernate: | ant.jar (1.5.3) | - Ant core | - buildtime | | c3p0.jar (0.8.3) | - C3P0 JDBC connection pool | - runtime, optional | | cglib2.jar (2.0rc1) | - CGLIB bytecode generator | - runtime, required | | commons-collections.jar (2.1) | - runtime, required | | commons-dbcp.jar (1.1) | - runtime, optional | | commons-lang.jar (1.0.1) | - runtime, optional (required by JCS) | | commons-logging.jar (1.0.3) | - runtime, required | | commons-pool.jar (1.1) | - runtime, optional | | concurrent.jar | - runtime, optional (required by TreeCache) | | connector.jar | - Standard JCA API | - runtime, optional | | dom4j.jar (1.4) | - XML configuration mapping parser | - runtime, required | | ehcache.jar (0.6) | - EHCache cache | - runtime, optional | | hibernate2.jar (2.0) | - Hibernate core | - runtime, required | | jaas.jar | - Standard JAAS API | - runtime, optional (required by JCA) | | jboss-cache.jar (CVS-11.12.03) | - TreeCache clustered cache | - runtime, optional | | jboss-common.jar | - runtime, optional (required by TreeCache) | | jboss-jmx.jar | - runtime, optional (required by TreeCache) | | jboss-system.jar | - runtime, optional (required by TreeCache) | | jcs.jar (1.0-dev) | - JCS cache | - runtime, optional (deprecated) | | jdbc2_0-stdext.jar | - Standard JDBC APIs | - runtime, required for standalone operation (outside application server) | | jgroups.jar (2.2) | - JGroups multicast library | - runtime, optional (required by replicated caches) | | jta.jar | - Standard JTA API | - runtime, required for standalone operation (outside application server) | | junit.jar (3.8.1) | - JUnit test framework | - buildtime | | odmg.jar (3.0) | - ODMG API 3.0 | - runtime, required | | optional.jar (1.5.3) | - Ant optional tasks | - buildtime | | oscache.jar (2.0) | - OpenSymphony OSCache | - runtime, optional | | proxool.jar (0.7.2) | - Proxool JDBC connection pool | - runtime, optional | | swarmcache.jar (1.0rc2) | - SwarmCache replicated cache | - runtime, optional | | xalan.jar (2.4.0) | - XSLT processor | - runtime, required | | xerces.jar (2.4.0) | - SAX parser | - runtime, some SAX parser is required | | xml-apis.jar | - Standard JAXP API | - runtime, some SAX parser is required | View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4099944#4099944 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4099944 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Writing SeamTests with Seam 2.0.0. CR2 - What's Changed?
this link is even better - pay close attention to the maven-surefire-plugin version http://www.martingilday.org/blog/2007/sep/12/testng-and-maven/ View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=409#409 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=409 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Writing SeamTests with Seam 2.0.0. CR2 - What's Changed?
The testng docs provide some assistance with getting Maven2 and Testng 5.X to work http://testng.org/doc/maven.html#maven2... View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=402#402 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=402 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Writing SeamTests with Seam 2.0.0. CR2 - What's Changed?
It looks like you actually need more than the libs in the
${JBOSS_SEAM_HOME}/lib/test/ directory. So far, I've had to add these
dependencies as well:
| dependency!-- required to boot jboss embedded --
| groupIdorg.jboss.seam/groupId
| artifactIdjboss-embedded-api/artifactId
| version2.0.0.CR3/version
| scopetest/scope
| /dependency
|
| dependency!-- required to boot jboss embedded --
| groupIdorg.jboss.seam/groupId
| artifactIdjboss-deployers/artifactId
| version2.0.0.CR3/version
| scopetest/scope
| /dependency
|
but now I'm getting this exception:
| Test set: SampleEJB3Test
|
---
| Tests run: 2, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 1.033 sec
FAILURE!
| init(com.javaplant.mapper.police.PersistenceUnitConfigurationTest) Time
elapsed: 0.038 sec FAILURE!
| org.jboss.deployers.spi.DeploymentException: Unable to find bootstrap file:
conf/bootstrap-beans.xml in classpath
| at org.jboss.embedded.Bootstrap.bootstrap(Bootstrap.java:200)
| at org.jboss.embedded.Bootstrap.bootstrap(Bootstrap.java:214)
| at
org.jboss.seam.mock.EmbeddedBootstrap.startAndDeployResources(EmbeddedBootstrap.java:11)
| at
org.jboss.seam.mock.BaseSeamTest.startJbossEmbeddedIfNecessary(BaseSeamTest.java:1006)
| at org.jboss.seam.mock.BaseSeamTest.init(BaseSeamTest.java:931)
| at org.jboss.seam.mock.SeamTest.init(SeamTest.java:42)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at
org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:645)
| at
org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:385)
| at
org.testng.internal.Invoker.invokeConfigurations(Invoker.java:141)
| at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:79)
| at
org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:158)
| at
org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:103)
| at org.testng.TestRunner.runWorkers(TestRunner.java:673)
| at org.testng.TestRunner.privateRun(TestRunner.java:620)
| at org.testng.TestRunner.run(TestRunner.java:480)
| at org.testng.SuiteRunner.runTest(SuiteRunner.java:278)
| at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:273)
| at org.testng.SuiteRunner.privateRun(SuiteRunner.java:253)
| at org.testng.SuiteRunner.run(SuiteRunner.java:168)
| at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:987)
| at org.testng.TestNG.runSuitesLocally(TestNG.java:951)
| at
org.apache.maven.surefire.testng.TestNGExecutor.executeTestNG(TestNGExecutor.java:161)
| at
org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:101)
| at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:275)
| at
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:832)
|
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4100048#4100048
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4100048
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Writing SeamTests with Seam 2.0.0. CR2 - What's Changed?
so it looks like all that I learned about using JBoss embedded in Seam 1.2.1 and earlier is null and void. I see that I need to now figure out a project configuration that will copy the bootstrap directory stuff into target/test-classes and figure out all the stuff like this: | init(com.javaplant.mapper.police.PersistenceUnitConfigurationTest) Time elapsed: 0.008 sec FAILURE! | org.jboss.deployers.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): | *** CONTEXTS IN ERROR: Name - Error | ResourcesToDeploy3 - java.net.MalformedURLException: unknown protocol: vfsfile | ResourcesToDeploy2 - java.net.MalformedURLException: unknown protocol: vfsfile | ResourcesToDeploy - java.net.MalformedURLException: unknown protocol: vfsfile | at org.jboss.embedded.Bootstrap.checkIncomplete(Bootstrap.java:144) | at org.jboss.embedded.Bootstrap.bootstrapURL(Bootstrap.java:169) | at org.jboss.embedded.Bootstrap.bootstrap(Bootstrap.java:201) | at org.jboss.embedded.Bootstrap.bootstrap(Bootstrap.java:214) | at org.jboss.seam.mock.EmbeddedBootstrap.startAndDeployResources(EmbeddedBootstrap.java:11) | at org.jboss.seam.mock.BaseSeamTest.startJbossEmbeddedIfNecessary(BaseSeamTest.java:1006) | at org.jboss.seam.mock.BaseSeamTest.init(BaseSeamTest.java:931) | at org.jboss.seam.mock.SeamTest.init(SeamTest.java:42) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:645) | at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:385) | at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:141) | at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:79) | at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:158) | at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:103) | at org.testng.TestRunner.runWorkers(TestRunner.java:673) | at org.testng.TestRunner.privateRun(TestRunner.java:620) | at org.testng.TestRunner.run(TestRunner.java:480) | at org.testng.SuiteRunner.runTest(SuiteRunner.java:278) | at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:273) | at org.testng.SuiteRunner.privateRun(SuiteRunner.java:253) | at org.testng.SuiteRunner.run(SuiteRunner.java:168) | at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:987) | at org.testng.TestNG.runSuitesLocally(TestNG.java:951) | at org.apache.maven.surefire.testng.TestNGExecutor.executeTestNG(TestNGExecutor.java:161) | at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:101) | at org.apache.maven.surefire.Surefire.run(Surefire.java:132) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:275) | at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:832) | | A whole new research project, when I already had a decent working solution for testing Seam stuff via maven2 - Totally frustrating! View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4100053#4100053 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4100053 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Writing SeamTests with Seam 2.0.0. CR2 - What's Changed?
Hello,
I used to be able to boot JBoss embedded from Seam tests in my app in the 1.2.1
and earlier days (was it only 6 months ago?). Anyway, now when I run my tests,
I am getting null-pointer exceptions from a class called SeamBaseTest. For
example:
| public class PersistenceUnitConfigurationTest extends SeamTest {
|
| private Log log =
LogFactory.getLog(PersistenceUnitConfigurationTest.class);
|
| @Test
| public void test_GetManagedPersistenceContext_from_Seam() throws
Exception {
|
| new FacesRequest() {
| protected void invokeApplication() throws Exception {
| EntityManager em = (EntityManager)
getInstance(entityManager);
| assert em != null;
| }
| }.run();
|
| }
| }
|
yields
|
---
| Test set: SampleEJB3Test
|
---
| Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.198 sec
FAILURE!
| test_GetManagedPersistenceContext_from_Seam Time elapsed: 0.047 sec
FAILURE!
| java.lang.NullPointerException
| at
org.jboss.seam.mock.BaseSeamTest$Request.run(BaseSeamTest.java:504)
| at
com.javaplant.mapper.police.PersistenceUnitConfigurationTest.test_GetManagedPersistenceContext_from_Seam(PersistenceUnitConfigurationTest.java:22)
|
Ok - so it looks like there is now something called a ComponentTest, so I'll
try that instead:
| public class PersistenceUnitConfigurationTest extends SeamTest {
|
| private Log log =
LogFactory.getLog(PersistenceUnitConfigurationTest.class);
|
| @Test
| public void test_GetManagedPersistenceContext_from_Seam() throws
Exception {
|
| new ComponentTest() {
|
| protected void testComponents() throws Exception {
| EntityManager em = (EntityManager)
getInstance(entityManager);
| assert em != null;
| }
| }.run();
|
| }
| }
|
and this yields:
|
---
| Test set: SampleEJB3Test
|
---
| Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.195 sec
FAILURE!
| test_GetManagedPersistenceContext_from_Seam Time elapsed: 0.07 sec
FAILURE!
| java.lang.NullPointerException
| at
org.jboss.seam.servlet.ServletSessionMap.get(ServletSessionMap.java:54)
| at org.jboss.seam.contexts.BasicContext.get(BasicContext.java:48)
| at
org.jboss.seam.contexts.Contexts.lookupInStatefulContexts(Contexts.java:199)
| at org.jboss.seam.Component.getInstance(Component.java:1844)
| at org.jboss.seam.Component.getInstance(Component.java:1839)
| at
org.jboss.seam.mock.BaseSeamTest.getInstance(BaseSeamTest.java:98)
| at
com.javaplant.mapper.police.PersistenceUnitConfigurationTest.access$000(PersistenceUnitConfigurationTest.java:15)
| at
com.javaplant.mapper.police.PersistenceUnitConfigurationTest$1.testComponents(PersistenceUnitConfigurationTest.java:25)
| at
org.jboss.seam.mock.BaseSeamTest$ComponentTest.run(BaseSeamTest.java:164)
| at
com.javaplant.mapper.police.PersistenceUnitConfigurationTest.test_GetManagedPersistenceContext_from_Seam(PersistenceUnitConfigurationTest.java:22)
|
So what's going on with SeamBaseTest?
Thanks,
Brad Smith
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4099682#4099682
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4099682
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Writing SeamTests with Seam 2.0.0. CR2 - What's Changed?
Pete, Yes - the whole test. I'm mainly trying to recover the ability to bootstrap the JBoss embeddable from maven 2 in the test phase. Figuring that out the first time was horrible (more than a year ago). Is there an enumerated list of dependencies for writing Seam tests that use JPA + EJB3? Also, is there a sample (prototype) configuration for boot strapping? there used to be a core:ejb/ tag that did the trick but that doesn't seem to be a member of the core namespace anymore. Thanks, Brad View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4099684#4099684 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4099684 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Writing SeamTests with Seam 2.0.0. CR2 - What's Changed?
anonymous wrote : we need JBoss Tools to be able to work with a maven structure first. JBoss Tools? Try IDEA 7.0 - works seamlessly with Maven 2 poms ;-) - no need to wait. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4099686#4099686 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4099686 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Seam 2.0.0.CR2: lib jars have lost their versions
tynor wrote : 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. | We're a maven2 - seam shop - we use archetypes to start all our Seam projects. Who knows? now that maven2 is getting uptake on this project, maybe someday seam-gen functionality will be available as an archetype... Anyway, since I spend a fair amount of time making sure our internal repository has the right versions of jars and that our archetype poms are correct, I would like to second the request to have the version numbers left on the jar names. It just makes dependency mgmt / troubleshooting much easier (BTW - not all the jar versions are appended to the lib jars in the previous release(s) - is there any chance that things like JBoss jars could have the server-version number they represent appended? things like servlet-api, and jsf-api have the spec numbers appended? as well). One other thing- I can indeed review the pom.xml for version numbers, however, flipping between the pom and the file system to make the association is tedious and error prone - especially with many dependencies. Thanks, Brad Smith View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4092263#4092263 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4092263 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How can I integrate CAS client into Seam?
wuhaixing wrote : Thanks,I have readed the thread. | And I also found this,http://www.ja-sig.org/wiki/display/CASC/CASLoginModule+for+JAAS+applications | Do u think this is a better way? | I'm know little about JAAS and CAS,so I cann't do the decision by myself. | Thanks for all of you! I looked at the code at that link - on first pass, it's not clear to me how the service=SERVICE param is going to be transmitted from the HTTP request to the CASLoginModule. Thus, I'm not sure that code is the complete solution. The best way to determine if it's a better way is to decide if you like the CASFilter approach (in which you'll want to set wrapRequest to true in web.xml) or, for some reason, you prefer JAAS. You should try both ways and see which way in practice is easiest to repeat from app to app. In my case, the CASFilter approach is the easiest, least invasive, way to integrate with our CAS Server. I put the solution I posted in this thread up on the JA-SIG CAS Clients wiki directly http://www.ja-sig.org/wiki/pages/viewpage.action?pageId=8094192. Hopefully more CAS + Seam users will benefit-from / contribute-to this. Brad Smith View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4091031#4091031 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4091031 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How can I integrate CAS client into Seam?
Use this link http://www.ja-sig.org/wiki/display/CASC/Seam+Identity+Integration+%28Seam+1.2.1+-+2.0.0%29 instead. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4091037#4091037 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4091037 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How can I integrate CAS client into Seam?
I use CAS and I have this working. You may want to review this thread
http://www.jboss.com/index.html?module=bbop=viewtopict=119167.
I use a different approach than the CAS Filter for authentication, but the
process should be the same because by the time Seam steps in to the request
processing cycle, your CAS Filter should already have authenticated the user
(with the user-Principal being available in the HttpServletRequest -
request.getUserPrincipal()).
Here is part of my pages config and the relevant code of my authenticator for
integrating with Seam identity.
?xml version=1.0 encoding=UTF-8?
| pages xmlns=http://jboss.com/products/seam/pages;
|xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
|xsi:schemaLocation=http://jboss.com/products/seam/pages
http://jboss.com/products/seam/pages-2.0.xsd;
|
|no-conversation-view-id=/index.xhtml
|
| page view-id=/index.xhtml action=#{ssoAuthenticator.checkLogin}
login-required=false/
|
| page view-id=/* login-required=true/
|
| exception class=org.jboss.seam.security.NotLoggedInException
| redirect view-id=/index.xhtml
| messagePlease log in first/message
| /redirect
| /exception
|
| ...
|
| /pages
and here is the authenticator
@Name(ssoAuthenticator)
| @Scope(ScopeType.SESSION)
| public class SSOAuthenticator {
|
| @Logger
| private Log log;
|
| private UserPrincipal userPrincipal;
|
| // see http://www.jboss.com/index.html?module=bbop=viewtopict=119167
| // This method is configured in pages.xml as an action called for all
pages:
| // page view-id=/* login-required=true
action=#{authenticator.checkLogin}/
| public void checkLogin() {
| Identity identity = Identity.instance();
| final boolean isLoggedIn = identity.isLoggedIn();
| // user may already be logged in - check
| if (!isLoggedIn) {
| authenticate();
| } /* else {
| do nothing - user is logged in from identity perspective
| } */
| }
|
| public boolean authenticate() {
| Identity identity = Identity.instance();
| boolean authenticated = !(userPrincipal == null);
| if (!authenticated) {
| try {
| // Obtain authenticated UserPrincipal from Servlet container
| FacesContext facesContext =
FacesContext.getCurrentInstance();
| Principal rawPrincipal =
facesContext.getExternalContext().getUserPrincipal();
| userPrincipal = (UserPrincipal) rawPrincipal;
|
| // trigger the identity login sequence and add roles
| if (userPrincipal != null) {
| // Identity must have 'fresh' credentials for
authenticat() call to proceed
| identity.setUsername(userPrincipal.getUserid());
| identity.setPassword(userPrincipal.getUserid());
| identity.authenticate();
| // in my case, our system makes roles available in the
UserPrincipal - do what's right for your system
| Group[] roleGroups = userPrincipal.getUserRoles();
| if (roleGroups != null) {
| for (Group group : userPrincipal.getUserRoles()) {
| Enumeration? extends Principal roles =
group.members();
| while (roles.hasMoreElements()) {
|
identity.addRole(roles.nextElement().getName());
| }
| }
| }
| authenticated = true;
| }
| } catch (Exception e) {
| log.error(e, e);
| }
| }
| return authenticated;
| }
| }
You'll need to work out which URL's the CASFilter handles; you may also need
to tweak a bit with security constraints (in web.xml). But the code above
illustrates a basic approach to integrating Seam identity with any solution in
which the user-Principal has somehow been pre-set on the HttpServletRequest.
Hope this helps.
Brad Smith
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4090702#4090702
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4090702
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: How can I integrate CAS client into Seam?
One other item - CAS SSO server should be deployed standalone in a separate server. Your Seam app (or any app) typically should not be presenting its own login page in a CAS SSO architecture. In other words, there shouldn't be any concept of a 'login.xhtml' in your CAS-adapted Seam application. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4090706#4090706 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4090706 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Security: Better support for single sign on?!
[EMAIL PROTECTED] wrote : You could probably define a navigation rule in
pages.xml for your login page that uses isLoggedIn(true) to attempt an
authentication and if successful redirect to another page without displaying
the login page. You may need to extend Identity (or RuleBasedIdentity) and
override the isCredentialsSet() method depending on how your SSO solution
stores the user credentials.
|
| Unfortunately, JBSEAM-967 has a low priority at the moment.
What exactly should this look like? I've tried:
| page view-id=/index.xhtml action=#{identity.isLoggedIn(true)}/
|
and
| page view-id=/* action=#{identity.isLoggedIn(true)}/
|
And watching the server log, there is no evidence that this action method is
ever invoked.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4089772#4089772
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4089772
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Security: Better support for single sign on?!
stephen.friedrich wrote :
|
| Proposal: Here's a way to make integration into an SSO solution easier:
| Add an attribute to identity that lets me specify a method that is used to
try auto-login:
|
| | security:identity
authenticate-method=#{authenticator.authenticate}
auto-login-method=#{authenticator.tryAutoLogin}/
| |
|
| Like the authenticate-method the auto-login-method on successful login
would set roles at identity and return true.
| That would spare me from configuring a page action for all pages. It would
prevent the spurious Please login. Welcome. messages. Also I would not need
to pass user data in a field from the checkLogin method to the authentiocate
method like I did above.
|
| What do you think?
|
I like this suggestion most. It's consistent with the JIRA issue I've
mentioned earlier in the thread. I wish they would add support for this - I
still don't have a working solution / even using your approach posted earlier -
sigh
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4089729#4089729
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4089729
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Security: Better support for single sign on?!
stephen.friedrich wrote : Brad, can't you use a similar checkLogin() method like in my code above? | It call identity.login(); which will call your authenticate method. | In that method I use |redirect.setViewId(nextPage); | to redirect to a different page depending on the users role. | (With @Redirect redirect; in my Authenticator.) | Not the most beautiful construct, but it gets the job done without showing a login page. | | Or did I misunderstand your problem? Stephen, I will try your approach. One quick question - why do you @In the Identity component and use Identity.instance()? Can you not use the injected Identity in all places in your solution? Thanks, Brad View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4089673#4089673 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4089673 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Security: Better support for single sign on?!
Hello, I want to chime in with a friendly reminder regarding this task http://jira.jboss.org/jira/browse/JBSEAM-967 (which if you search the forum, shane, you'll find that you offered to add this if I posted a JIRA issue). Anyway, by the time the Seam web-app gets to process the request, the user is already authenticated and authorized by the SSO system + Tomcat Realm. What I really need is a way to have my authenticator's authenticate method invoked without redirecting to a login page. Rather, it would be nice if (maybe) there was a special event that you could assign to call the authenticate method in components.xml. I am using the CAS SSO system http://www.ja-sig.org/products/cas/ for SSO authentication - I used one of the CAS client code packages and wrote a Tomcat Realm + Valve implementation. If we use servlet security directly, this works great - we'ld like to use Seam security. Any help / discussion about this is appreciated. Thanks, Brad Smith View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4089513#4089513 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4089513 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - JBoss 4.2.0 / 4.2.1 - Seam 2.0.0B1 - Mail Problem
Hello,
I'm having trouble with Seam Mail on JBoss 4.2 (both 4.2.0 and 4.2.1). What
appears to be happening is that a particular SLSB which requires the mail
session (@In[jected] by Seam), is not being deployed. All other Session beans
which then depend on the Mail SLSB are subsequently not deployed as well. Here
are some config and code fragments I have that use the MailReaderBean:
First, components.xml:
| ?xml version=1.0 encoding=UTF-8?
| components xmlns=http://jboss.com/products/seam/components;
| xmlns:core=http://jboss.com/products/seam/core;
| xmlns:mail=http://jboss.com/products/seam/mail;
| xmlns:framework=http://jboss.com/products/seam/framework;
| xmlns:jms=http://jboss.com/products/seam/jms;
| xmlns:security=http://jboss.com/products/seam/security;
| xmlns:transaction=http://jboss.com/products/seam/transaction;
| xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
| xsi:schemaLocation=
| http://jboss.com/products/seam/core
http://jboss.com/products/seam/core-2.0.xsd
| http://jboss.com/products/seam/components
http://jboss.com/products/seam/components-2.0.xsd
| http://jboss.com/products/seam/framework
http://jboss.com/products/seam/framework-2.0.xsd
| http://jboss.com/products/seam/jms
http://jboss.com/products/seam/jms-2.0.xsd
| http://jboss.com/products/seam/mail
http://jboss.com/products/seam/mail-2.0.xsd
| http://jboss.com/products/seam/security
http://jboss.com/products/seam/security-2.0.xsd
| http://jboss.com/products/seam/transaction
http://jboss.com/products/seam/transaction-2.0.xsd;
|
| core:init jndi-pattern=access-control-1.0/#{ejbName}/local
debug=true/
|
| mail:mail-session session-jndi-name=java:/Mail auto-create=true/
|
|
|
I've also configured a mail service bound to java:/Mail using mail-service.xml
in the server deploy directory. There are no errors generated by the server in
regards to this MailService.
| 11:32:48,292 INFO STDOUT - DEBUG: JavaMail version 1.4ea
| 11:32:48,292 INFO STDOUT - DEBUG: java.io.FileNotFoundException:
C:\Program Files\Java\jdk1.5.0_12\jre\lib\javamail.providers (The system cannot
find the file specified)
| 11:32:48,292 INFO STDOUT - DEBUG: !anyLoaded
| 11:32:48,292 INFO STDOUT - DEBUG: not loading resource:
/META-INF/javamail.providers
| 11:32:48,308 INFO STDOUT - DEBUG: successfully loaded resource:
/META-INF/javamail.default.providers
| 11:32:48,308 INFO STDOUT - DEBUG: Tables of loaded providers
| 11:32:48,308 INFO STDOUT - DEBUG: Providers Listed By Class Name:
{com.sun.mail.smtp.SMTPSSLTransport=javax.mail.Provider[TRANSPORT,smtps,com.sun.mail.smtp.SMTPSSLTransport,Su
| n Microsystems, Inc],
com.sun.mail.smtp.SMTPTransport=javax.mail.Provider[TRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Sun
Microsystems, Inc], com.sun.mail.imap.IMAPSSLStore=
| javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Sun
Microsystems, Inc],
com.sun.mail.pop3.POP3SSLStore=javax.mail.Provider[STORE,pop3s,com.sun.mail.pop3.POP3SSLS
| tore,Sun Microsystems, Inc],
com.sun.mail.imap.IMAPStore=javax.mail.Provider[STORE,imap,com.sun.mail.imap.IMAPStore,Sun
Microsystems, Inc], com.sun.mail.pop3.POP3Store=javax.ma
| il.Provider[STORE,pop3,com.sun.mail.pop3.POP3Store,Sun Microsystems, Inc]}
| 11:32:48,308 INFO STDOUT - DEBUG: Providers Listed By Protocol:
{imaps=javax.mail.Provider[STORE,imaps,com.sun.mail.imap.IMAPSSLStore,Sun
Microsystems, Inc], imap=javax.mail.P
| rovider[STORE,imap,com.sun.mail.imap.IMAPStore,Sun Microsystems, Inc],
smtps=javax.mail.Provider[TRANSPORT,smtps,com.sun.mail.smtp.SMTPSSLTransport,Sun
Microsystems, Inc], pop3
| =javax.mail.Provider[STORE,pop3,com.sun.mail.pop3.POP3Store,Sun
Microsystems, Inc],
pop3s=javax.mail.Provider[STORE,pop3s,com.sun.mail.pop3.POP3SSLStore,Sun
Microsystems, Inc],
|
smtp=javax.mail.Provider[TRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Sun
Microsystems, Inc]}
| 11:32:48,308 INFO STDOUT - DEBUG: successfully loaded resource:
/META-INF/javamail.default.address.map
| 11:32:48,308 INFO STDOUT - DEBUG: !anyLoaded
| 11:32:48,324 INFO STDOUT - DEBUG: not loading resource:
/META-INF/javamail.address.map
| 11:32:48,324 INFO STDOUT - DEBUG: java.io.FileNotFoundException:
C:\Program Files\Java\jdk1.5.0_12\jre\lib\javamail.address.map (The system
cannot find the file specified)
| 11:32:48,324 INFO org.jboss.mail.MailService - Mail Service bound to
java:/Mail
|
Here is part of the SLSB that is not deploying - note also that bean is
intended to serve as a timer that rereads incoming mail from its mailSession:
| @Stateless
| @Name(mailReader)
| public class MailReaderBean implements MailReader {
|
| @Logger
|
[jboss-user] [JBoss Seam] - Re: JBoss 4.2.0 / 4.2.1 - Seam 2.0.0B1 - Mail Problem
Hi Pete, I appreciate your suggestion and info, however, the reason I used the @Resource approach is because in the past, when this bean woke up to perform its timeout method, the Seam annotations would not be obeyed (since the timeout method is not being invoked in a JSF request). I don't know if Seam is capable of intercepting Timeout methods at this point...do you? Thanks, Brad Smith View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4085624#4085624 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4085624 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: page flow question
you can also use basic Servlet-container security to achieve a similar result: | security-constraint | web-resource-collection | web-resource-namerestricted-urls/web-resource-name | url-pattern/myapp/auth/*/url-pattern | /web-resource-collection | auth-constraint | role-name*/role-name | /auth-constraint | !--user-data-constraint | transport-guaranteeCONFIDENTIAL/transport-guarantee | /user-data-constraint-- | /security-constraint | where 'auth' is a directory in your web application that contains pages requiring authentication. Of course you would not put your login page in the auth directory. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4084453#4084453 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4084453 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - pages.xml - no-conversation-view-id problem?
Hello,
I have the following rule:
| page view-id=/abo_edit.xhtml no-conversation-view-id=/index.xhtml
| navigation
from-action=#{aboDelegateManager.setApplicationABODelegate}
| render view-id=/abo_edit_successful.xhtml/
| /navigation
| /page
|
If I type the URL to /abo_edit.seam directly into my browser, I can get to the
page. I expected from reading the documentation that what should happen is
that I should see content from the index.xhtml page in my app.
Why is the no-conversation-view-id attribute not being obeyed by Seam?
I use Seam 1.2.1.
Thanks,
Brad Smith
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4084462#4084462
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4084462
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: pages.xml - no-conversation-view-id problem?
Ah thanks Jacob - that's what I was looking for; a specific suggestion to achieve a result - not a pointer to yet another research path. Thanks very much - that worked! View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4084489#4084489 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4084489 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Cleaner RESTful urls? Any suggestions?
ElliotG wrote : [EMAIL PROTECTED] wrote : Why is that cleaner? Because someone wrote a paper that says so? | | This is the first thread I read in the forum. I am considering Seam for new development projects, I hope this hostility is not prevalent throughout the site and organization. | yeah - I got the same 'hostile' type of response from the same person http://www.jboss.com/index.html?module=bbop=viewtopict=118295postdays=0postorder=ascstart=0 However, there's tons of great information here and usually your questions get answered fast and friendly by both Seam developers and users. Welcome to the forum! View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4084040#4084040 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4084040 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: When would SEAM 2.0.0 GA and SEAM 2.0.1 GA be released a
I've asked this before... Will there be a release of Seam 1.3.0 which appeared as an alpha earlier this year? In particular, I was hoping to get fixes for this http://jira.jboss.org/jira/browse/JBSEAM-967 If my memory is correct, Gavin responded that he has changed the Seam code too much for the 2.0 release in order to continue on with a 1.3 release path. That doesn't make too much sense with source-control tagging. Given also that Seam 2.0 is focussed on being supported with JBoss AS 4.2 (yes it works on 4.0.5 with AS changes supposedly), I'm concerned that those of us on the Seam 1.1, 1.2 path are dead ended already. It's not necessarily straight forward to just force several teams of developers to upgrade their version of Seam, and also their version of JBoss AS in order to obtain bug fixes. So... what's the final word on Seam 1.X releases ? no more? if so, that's a bit frustrating. We'll eventually get to Seam 2.0 and Jboss 4.2, but in the meantime, we'll be trying to develop and maintain existing Seam 1.1- and 1.2-based applications. Thanks, Brad Smith View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4083150#4083150 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4083150 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: When would SEAM 2.0.0 GA and SEAM 2.0.1 GA be released a
[EMAIL PROTECTED] wrote : anonymous wrote : It's not necessarily straight forward to just force several teams of developers to upgrade their version of Seam, and also their version of JBoss AS in order to obtain bug fixes. | | Well, here you actually have a much easier option: Seam 1.2.1 is part of the JBoss Enterprise Application Platform, for which you can buy support/bugfixing services for a few years from Red Hat. Or, because it is open source, you can fix it yourself or pay someone else to fix whatever you don't like. This comment suggests you think I want something for free... We like the Seam framework a lot but we don't want to be in the business of maintaining frameworks. We are, however, paying customers of JBoss (now Red Hat) - we even sent a good number of people to JBoss world for 2 years in a row (no JBoss world this past summer :-( ) - so from my perspective, we're doing our part to be payed customers - we're not looking for a free ride. I think I would be less willing to put my vote in for Seam-specific support after watching the 1.3.0 Alpha disappear - just too much volatility in how it evolves. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4083167#4083167 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4083167 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: renew the @Factory
Let's say your Seam component that contains this @Factory is session scoped;
then you need to remove the current license from the session context. Example:
| public String persistAndContinue(){
| super.persist();
| Contexts.getSessionContext().remove(license);
| setInstance(new License());
| }
|
Hope that helps.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4081417#4081417
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4081417
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: renew the @Factory
anonymous wrote : It didn´t works! Well, you should probably post your entire component then and the markup that you claim is 'submit the action'. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4081449#4081449 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4081449 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: renew the @Factory
Hmmm EntityHome isn't well documented in Seam 1.2.1 (which is what I currently use) and so without reviewing the EntityHome impl code in Seam, I'll have to guess a bit here. On closer inspection of your code, it looks like whether createInstance() is invoked or persistAndContinue() is invoked, both impl's as shown will produce a newly instantiated license. However, you're saying that the 'data of previous object' is in license - are you submitting to a session- or conversational-scoped component? If you are, are you also outjecting license back to session or conversation? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4081463#4081463 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4081463 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Seam Versions and Nightly Build
Hello, Is there going to be a Seam 1.2.2 or 1.3.0 release? Also, the nightly builds have not been available for many weeks. Are nightly builds of Seam 2.0.0 ever going to be available again (http://cruisecontrol.jboss.com/cc/artifacts/jboss-seam-builds)? Thanks, Brad Smith View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4074831#4074831 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4074831 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Seam 2.0 BETA
[EMAIL PROTECTED] wrote : 1) We are now working entirely on Seam2, Seam 1.2.1.GA is part of the Application Platform though, and will be maintained | 2) Not from the community releases, but the application platform will offer this (still should soon be GA IIRC) | 3) The migration guide is in the download for Seam2, or here http://fisheye.jboss.com/browse/JBoss/jboss-seam/seam2migration.txt?r=1.1 | - no, you can't just swap an app between 1.2.1 and 2 - mainly due to repackaging and the upgrade to JSF 2 | | No, Seam 1.3.0 won't be released. 1.3 was the old name for 2 :) why the sudden change in release strategy? Seam 1.3.0 Alpha was out just a couple of weeks ago, now it's gone from the radar? Thanks, Brad Smith View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4058791#4058791 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4058791 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - @Out problem (Seam 1.2.1)
I'm probably missing something trivial, but I am stuck with an @Out issue and
hopefully someone can point something out.
First, I have a Seam component that is JavaBean; annotated as such:
@Name(evergreenUser)
| @Roles( {
| @Role(name=accessRequestUser, scope=ScopeType.CONVERSATION),
| @Role(name=userToClone)
| } )
| public class EvergreenUser implements Serializable {
| ...
| }
I have a method in a SFSB that will, based on the value of a @RequestParameter,
here is the relative code:
@Stateful
| @Name(accessRequestManager2)
| public class AccessRequestManager2Bean implements AccessRequestManager2 {
|
| @Logger
| private Log log;
|
| @PersistenceContext(unitName = accessControlDatabase)
| private EntityManager em;
|
| @In
| private UserPrincipal userPrincipal;
|
| @In(required = false)
| @Out
| private Integer currentStep;
|
| @In
| private Conversation conversation;
|
| @In(create = true)
| private DraftAccessRequestMaster draftAccessRequestMaster;
|
| @RequestParameter
| private String selectedUserId;
|
| @Out
| private ListString errors = new ArrayListString();
|
| @Out(required = false)
| private EvergreenUser accessRequestUser;
|
| /**
| * Start a new add-access request. This method also generates the
conversationId to
| * use in the conversation that beans of this class are associated with.
| */
| @Begin(id = DraftAccessRequestID:#{draftAccessRequestMaster.id}, join
= true)
| public void startAddRequest() {
| log.info(startAddRequest());
|
| draftAccessRequestMaster.setCurrentStep(
| currentStep = 1
| );
|
| }
|
| /**
| * Step 2.
| * Select user to clone (optional)
| * Select 1-or-more applications and entitlements
| */
| public void editAccessRequestDetails() {
| if (selectedUserId == null) {
| log.error(User not Selected...TODO - bounce back to step 1.);
| }
| log.info(selectedUserId - + selectedUserId);
| accessRequestUser = QueryEPeopleUtil.findUserByUid(selectedUserId);
| log.info(accessRequestUser - + accessRequestUser);
|
| draftAccessRequestMaster.setCurrentStep(
| currentStep = 2
| );
| }
|
| }
And I use an s:link ... / tag to call editAccessRequestDetails()
| s:link value=#{eUser.name}
| action=#{accessRequestManager2.editAccessRequestDetails}
propagation=join
| f:param value=#{eUser.anumber} name=selectedUserId/
| /s:link
|
I also have a navigation rule in pages.xml so that when
editAccessRequestDetails() is called, another page is displayed
| page view-id=/user_access_request_step_1.xhtml
| navigation
from-action=#{accessRequestManager2.editAccessRequestDetails}
| evaluate=#{draftAccessRequestMaster.currentStep}
| rule if-outcome=1
| redirect view-id=/user_access_request_step_1.xhtml/
| /rule
| rule if-outcome=2
| redirect view-id=/user_access_request_step_2.xhtml/
| /rule
| /navigation
| navigation from-action=#{accessRequestManager2.cancel}
| redirect view-id=/index.xhtml/
| /navigation
| /page
|
I want to display the @Out-jected accessRequestUser on
user_access_request_step_2.xhtml (which is where we land after clicking the
s:link)
| (from user_access_request_step_2.xhtml)
| #{accessRequestUser.name}
| ... more markup
| h:outputText value=#{accessRequestUser}/
| etc...
|
I can see from the log file that the SFSB method is being called, and that the
accessRequestUser is being populated by my code, however, the
user_access_request_step_2.xhtml page is not able to 'find' the
accessRequestUser in any scope (display of attributes or the entire instance is
blank). I must be missing something, I've looked this over and over and I
can't figure out why @Out isn't working ... help?
Thanks,
Brad Smith
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4056627#4056627
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4056627
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: @Out problem (Seam 1.2.1)
Never mind. Apparently, it's the redirect in pages.xml | rule if-outcome=2 | redirect view-id=/user_access_request_step_2.xhtml/ | /rule | that's causing the problem. I changed to render and now the @Outjection is working. | rule if-outcome=2 | render view-id=/user_access_request_step_2.xhtml/ | /rule | View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4056631#4056631 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4056631 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?
the seam nightly builds are still 'stuck' on 06.14.2007 as the last build - any chance the nightly builds will resume being posted regularly? Thanks, Brad View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4056002#4056002 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4056002 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Help with MDB + Seam + jBPM - transaction issue?
OK - will check this too - thanks! Brad View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4055196#4055196 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4055196 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Help with MDB + Seam + jBPM - transaction issue?
Due to firewall issues, I use the Seam nightly builds for testing 'what's in CVS.' The last build available at http://cruisecontrol.jboss.com/cc/artifacts/jboss-seam-builds is dated jboss-seam-CVS.20070614.zip (as of this morning 20070618). Any chance a nightly build made after your commits to CVS will be made available soon? Thanks, Brad View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4055201#4055201 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4055201 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?
[EMAIL PROTECTED] wrote : This is done in CVS, Brad, please try it out! Ok - it will take me a few days to review this issue and try this out. Thanks, Brad View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4054957#4054957 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4054957 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Conversations - do not work in Seam 1.2.1?
I'm working on some code where I am trying to do the following:
1. User clicks a link to an action method on a SFSB
2. method is annotated with @Begin, using a custom conversation id
2a. the custom conversation id comes from the following
2a-1. a @Factory method in a SLSB creates a new persistent entity; the id of
this entity will be appended to a String to create a custom conversation id
2a-2. the @Factory class would like to use the existing persistent entity if
possible (avoid creating new persistent or querying for existing persistent
entity) - thus, I have an @In for the entity.
2a-3. here is the class with the @Factory method:
| @Stateless
| @Name(draftAccessRequestFinder)
| public class DraftAccessRequestFinderBean implements
DraftAccessRequestFinder {
|
| @Logger
| private Log log;
|
| @PersistenceContext(unitName = accessControlDatabase)
| private EntityManager em;
|
| @In
| private Principal userPrincipal;
|
| @In(#{conversation.id})
| private String conversationId;
|
| @In(required = false) @Out(scope= ScopeType.CONVERSATION)
| private DraftAccessRequestMaster draftAccessRequestMaster;
|
| @Factory(draftAccessRequestMaster)
| public DraftAccessRequestMaster createMaster() {
| log.info(DraftAccessRequestFinderBean.createMaster() :
conversationId - +conversationId);
| log.info(DraftAccessRequestFinderBean.createMaster() :
draftAccessRequestMaster - +draftAccessRequestMaster);
| // create or load draftAccessRequest
| if (conversationId != null conversationId.indexOf(':')0
draftAccessRequestMaster == null) {
| long id =
Long.valueOf(conversationId.substring(conversationId.indexOf(':')+1));
| draftAccessRequestMaster = em.find(
| DraftAccessRequestMaster.class, id
| );
| log.info(loaded draftAccessRequestMaster -
+draftAccessRequestMaster);
| }
|
| if (draftAccessRequestMaster == null) {
| if (userPrincipal == null) {
| throw new RuntimeException(userPrincipal is null.);
| }
| if (!(userPrincipal instanceof UserPrincipal)) {
| throw new RuntimeException(userPrincipal is not an
instance of com.evergreen.jaas.UserPrincipal.);
| }
| draftAccessRequestMaster = new DraftAccessRequestMaster();
| draftAccessRequestMaster.setUserId(
| ((UserPrincipal) userPrincipal).getUserid()
| );
| draftAccessRequestMaster.setUserName(
| ((UserPrincipal) userPrincipal).getPersonName()
| );
| em.persist(draftAccessRequestMaster);
| em.flush(); // we need to obtain a PK for this entity now...
| }
| return draftAccessRequestMaster;
| }
| }
|
3. here is the SFSB that wants the custom conversation id as well as a
reference to the persistent entity:
| @Stateful
| // Seam - defaults to Conversational context...
| @Name(accessRequestManager2)
| public class AccessRequestManager2Bean implements AccessRequestManager2 {
|
| @Logger
| private Log log;
|
| @PersistenceContext(unitName = accessControlDatabase)
| private EntityManager em;
|
| @In
| private UserPrincipal userPrincipal;
|
| // for development purposes only - todo remove this
| @In
| private Conversation conversation;
|
| @In(create=true) @Out(scope= ScopeType.CONVERSATION)
| private DraftAccessRequestMaster draftAccessRequestMaster;
|
| @Out
| private ListString errors = new ArrayListString();
|
|
| /**
| * Start a new add-access request. This method also generates the
conversationId to
| * use in the conversation that beans of this class are associated with.
| *
| * This is complicated - in 1 swoop, we need to
| * 1 - create the DraftAccessRequestMaster for the conversation
component
| * 2 -
| */
| @Begin(id = DraftAccessRequestID:#{draftAccessRequestMaster.id}, join
= true)
| public void startAddRequest() {
| log.info(startAddRequest());
| log.info(conversation);
| log.info(conversation.id = + conversation.getId());
| log.info(conversation.parentId = + conversation.getParentId());
|
| if (draftAccessRequestMaster == null) {
| log.info(draftAccessRequestMaster is null...not expected.);
| }
|
| }
| }
|
4. here is a link that calls the SFSB method:
| s:link action=#{accessRequestManager2.startAddRequest}
value=Add 2
| title=Add entitlements to an application for a user.
| /s:link
|
5. and here is a log of what occurs
|
[jboss-user] [JBoss Seam] - Re: Conversations - do not work in Seam 1.2.1?
Never mind - it looks like (after reviewing in detail the documentation) that conversation is not really a good scope for entities. Instead, it looks like a solution based on private state in an SFSB and using the manager pattern (@Unwrap) may be a better way of doing this. Thanks, Brad Smith View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4054106#4054106 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4054106 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Seam 1.3.0 ALPHA released
Any chance some of these bug fixes will get backported to a Seam 1.2.X release? I (of course) would like the new features and bug fixes of Seam 1.3.0, but I can't necessarily upgrade my entire infrastructure to get the bug fixes. We're probably going to be on JBoss 4.0.4-4.0.5 for a quite a while. Thanks, Brad Smith View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4054112#4054112 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4054112 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - EntityHome doesn't work on JBoss 4.0.4 EJB3 RC8
I ran into the problem described here - http://opensource.atlassian.com/projects/hibernate/browse/HHH-1938 while trying to use EntityHome in Seam 1.2.1 on JBoss 4.0.4 EJB3 RC8. I tried the suggested changes with still no success. I believe that my version of JBoss + EJB3 is the culprit here. My question is ... Is there some sort of known Seam 1.X + JBoxx 4.0.X compatibility matrix available? For example... Seam 1.2.1 Requires JBoss 4.0.4 / EJB3 8. etc... - EntityHome requires JBoss 4.0.5 / EJB RC9, etc... For tinkering around, I can try any version of JBoss, to put an application into production, I am constrained to use JBoss 4.0.4 for now and will be able to use JBoss 4.0.5 in the near future - it's going to be a long time (many months ( 6-9) until we look seriously at using 4.2.0 probably so knowing the limitations of the framework w.r.t. a particular JBoss AS platform will be a big help in making design choices in our applications. Thanks, Brad Smith View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4053522#4053522 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4053522 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: EntityHome doesn't work on JBoss 4.0.4 EJB3 RC8
thanks View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4053665#4053665 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4053665 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - 5.1.1.2. Navigation (Seam 1.2.1)
In section 5.1.1.2. Navigation in the Seam documentation, there is the
following example:
| page view-id=/editDocument.xhtml
|
| navigation from-action=#{documentEditor.update}
| rule if=#{documentEditor.errors.empty}
| redirect view-id=/viewDocument.xhtml/
| /rule
| /navigation
|
| /page
|
that is intended to help us avoid (polluting) our DocumentEditor component
with string-valued return values (the JSF outcomes). I've looked through the
samples and I can't find a concrete example of this navigation rule. Does this
rule imply that a field named errors exists on the bean documentEditor?
Furthermore, the Object represented by errors has a field named empty?
Thanks,
Brad Smith
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4053124#4053124
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4053124
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Question about explicit conversation id
I have the following SeamTest (FacesRequest) method:
| @Override
| protected void invokeApplication() throws Exception {
|
| AccessRequestManager2 arm2 = (AccessRequestManager2)
getInstance(accessRequestManager2);
| assert arm2 != null;
| arm2.startRequest();
| log.info(conversationId = +getConversationId());
|
| }
|
|
and AccessRequestManager2.startRequest() looks like this:
| @Begin(id=#{draftAccessRequestMaster.id},join=true)
| public void startRequest() {
| log.info(draftAccessRequestMaster.id =
+draftAccessRequestMaster.getId());
| }
|
Furthermore, I use the @Factory pattern to create a persistent instance of
draftAccessRequestMaster which is @In(jected) to AccessRequestManager2. When I
run the test, I get the following in the log output:
| 10:36:40,265 INFO
com.evergreen.accesscontrol.AccessRequestManager2Test.(info:94) -
updateModelValues()
| 10:36:40,812 INFO
com.evergreen.accesscontrol.impl.AccessRequestManager2Bean.(startRequest:54) -
draftAccessRequestMaster.id = 5
| 10:36:40,875 INFO
com.evergreen.accesscontrol.AccessRequestManager2Test.(info:94) -
conversationId = 1
|
My question here is
Why isn't the conversationId equal to the explicit id that I created in the
@Begin(...) annotation?
Thanks,
Brad Smith
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4052622#4052622
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4052622
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Question about explicit conversation id
I @In(jected) the conversation component into my bean and then added some code
to dump the conversation id in the method invokation. It looks like that's
working correctly, it's the SeamTest.FacesRequest that appears to be losing
track of the conversation id.
New AccessRequestManager2.startRequest() Code:
|
@Begin(id=DraftAccessRequestID:#{draftAccessRequestMaster.id},join=true)
| public void startRequest() {
| log.info(draftAccessRequestMaster.id =
+draftAccessRequestMaster.getId());
| log.info(conversation);
| log.info(conversation.id = +conversation.getId());
| log.info(conversation.parentId = +conversation.getParentId());
| }
|
with the following output during execution:
| 14:12:28,093 INFO
com.evergreen.accesscontrol.impl.AccessRequestManager2Bean.(startRequest:59) -
draftAccessRequestMaster.id = 6
| 14:12:28,093 INFO
com.evergreen.accesscontrol.impl.AccessRequestManager2Bean.(startRequest:60) -
[EMAIL PROTECTED]
| 14:12:28,093 INFO
com.evergreen.accesscontrol.impl.AccessRequestManager2Bean.(startRequest:61) -
conversation.id = DraftAccessRequestID:6
| 14:12:28,093 INFO
com.evergreen.accesscontrol.impl.AccessRequestManager2Bean.(startRequest:62) -
conversation.parentId = null
| 14:12:28,124 INFO
com.evergreen.accesscontrol.AccessRequestManager2Test.(info:94) -
conversationId = 1
|
So I see that the desired conversation id, DraftAccessRequestID:6, is being
created the way I would like, however, the SeamTest.FacesRequest is not
reflecting this.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4052692#4052692
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4052692
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Question about explicit conversation id
nested conversations? no - I wasn't planning on it in this use case. The main thing here is that I was trying to test from SeamTest.FacesRequest that the explicit (custom-generated) conversation id is the conversation id. It looks like the expression for my explicit id is being evaluated the way I want, I was (am) confused as to why the test case doesn't reflect that when I call getConversationId() after invoking the business method. Thanks View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4052716#4052716 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4052716 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Portal] - Re: http://jira.jboss.com/jira/browse/JBPORTAL-459 You shoul
rharari wrote : Hi Brad, | | I´ve a question: | | anonymous wrote : | | We are evaluating a few open source portals. | | | | Please, can you post or send me and e-mail describing which open source portals your team are evaluating? And also explain why you have decided to use jboss-portal? I´ve also evaluated some portals (open-source and commercial) before starting my project and in my opinion jboss-portal has the best cost/benefit relationships. I agree with you that the documentation is not the best but who provides a complete documentation? Personally, I think source code is some of the best documentation you can have. | | and | | anonymous wrote : | | Google gadget integration (who really needs that?)? | | | | I do! ;p | | | Thanks | | r.harari | Here are some answers to your questions (opinions are liberally sprinkled throughout my response ;-)) Two summers ago, when JBoss Portal was 2.0.1 (+/-), I quickly put together a portal for an intranet project here.At the time, JBoss portal was the smallest, fastest, and easiest to customize. Once JBoss Portal started adding in things like IPC, WSRP, and changing directions with the security model, and of course, adding more 'stuff' to the CMS portion, I find that the portal starts to get significantly slower, much more complex, and often times quite fragile. So this year (late 2006-to-present) we've reevaluated liferay, exo portal, jetspeed 2, and jboss portal. Of these, JBoss is still a better portal primarily because it is easier to get started with and build a development process around. So our reasons for using (or attempting to use) JBoss Portal for a current internal project (moving from BEA Weblogic Portal 8.1.4 to JBoss Portal 2.6.X) are the following: a.) an initial very positive experience with a younger JBoss Portal b.) we're basically standardized on using JBoss App Server, Hibernate, and many other JBoss components in our architecture. c.) relative ease of use, customization, development process (just create multiple wars for a particular portal implementation in JBoss). Some of the pain we have had using JBoss Portal 2.6 and the success we have had using Seam + Ajax4jsf + Facelets has led us to now pursue a path in which JBoss Portal 2.6 will be a temporary stop-gap solution to evolve our original BEA Portal. Our plans now are to continue converting BEA portlets to standard JSR-168 portlets deployed in JBOss Portal; in this conversion, we are now using Facelets and JSF (myfaces + tomahawk) for our presentation layer. After this initial conversion, we will be all set architecturally to drop out the JSR-168 API's and go to a complete Seam-based architecture. I've found that the combination of Seam + Facelets + Ajax4JSF + Richfaces + Tomahawk allows us to solve a vast array of user-interface development problems. Plus, this combination allows us to make a 'portal-enough' user experience that takes full advantage of Ajax and other Web 2.0 techniques without the 'noise' of JSR 168. One comment on the google gadget thingy - I have nothing against a google-gadget portlet or add-on module, but I really think that JBoss Portal would do better if it was a delivered as a basic Portal 'engine' with a lot of the bells and whistles available as easy-drop-in add ons. Unfortunately, a lot of the bells and whistles (such as a google-gadget portlet) are simply lumped into the basic portal - making the whole product complex, hard to document, and fragile at times. Splitting the Portal into logical pieces allows each piece to evolve independently - most likely the core engine won't change too much because the fundamental building blocks are a JSR168 portlet container plus the paging and customization system. And finally, yes, the source code is good documentation - it's an invaluable resource during development for solving the tough problems of using any technology. Hope this helps. Brad Smith View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4046870#4046870 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4046870 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Portal] - Re: http://jira.jboss.com/jira/browse/JBPORTAL-459 You shoul
The only thing that I think I did differently from you is that I didn't use JEMS to create a portal installation - I just created 4.0.5 with ejb3 profile. I can't figure out what I did differently from you - maybe you used a different source for 2.6CR2 than the JBoss website download? Anyway, I appreciate you looking into this with me. Thanks, Brad Smith View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4045786#4045786 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4045786 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Portal] - Re: JBoss Portal Security - You're losing your way...
bsmithjj wrote : As I look into this more, look at the source code for 2.6, the wiki link you supplied, etc. I really am beginning to think that in some ways, you're losing your way with the security layer of JBoss Portal... | I've noticed in the so-called 'candidate releases (CR),' 1 and 2, that the dashboard link doesn't work. This kind of a release practice seems to be typical for the JBoss portal; I mean the practice of releasing alpha-quality software as a CR release. I've assumed that when JBoss labels a technology as CR release, it is suggesting that the technology is basically working and a.) you believe only minor bugs remain in the product, and b.) you'ld like the early adopters to help find bugs by trying to use the product in development. Furthermore, since CR is typically the label JBoss applies to a technology prior to releasing it as stable (GA), all the features that comprise the release of the technology really should be completely working as designed (modulo minor bugs). However, since the dashboard just doesn't work in two CR releases, I have to conclude the dashboard is just not done and thus is really an alpha level feature. Also, I see a barage of new stuff appearing, like the usage of jBPM (which seriously slows down a clean portal install and startup times after installation). Google gadget integration (who really needs that?)? etc... I wouldn't care so much about this, however, we are in the process of migrating a relatively large portal application from BEA Weblogic Portal 8 to JBoss portal and the flakiness of the JBoss releases causes a fair amount of consternation. Also, I must admit that I am bit spoiled by the high quality of coding and documentation of the Seam framework - switching from Seam to JBoss portal to do any work is horrible. Thanks, Brad Smith View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4045467#4045467 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4045467 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Portal] - Re: http://jira.jboss.com/jira/browse/JBPORTAL-459 You shoul
oh yes - I forgot the stack trace | 09:18:40,432 ERROR STDERR - org.jboss.portal.core.controller.ResourceAccessDeniedException: Not Authorized has denied access | 09:18:40,432 ERROR STDERR - at org.jboss.portal.core.model.portal.command.PortalObjectCommand.enforceSecurity(PortalObjectCommand.java:90) | 09:18:40,432 ERROR STDERR - at org.jboss.portal.core.model.portal.command.render.RenderPageCommand.enforceSecurity(RenderPageCommand.java:120) | 09:18:40,432 ERROR STDERR - at org.jboss.portal.core.aspects.controller.PolicyEnforcementInterceptor.invoke(PolicyEnforcementInterceptor.java:68) | 09:18:40,432 ERROR STDERR - at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:38) | 09:18:40,432 ERROR STDERR - at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) | 09:18:40,432 ERROR STDERR - at org.jboss.portal.core.aspects.controller.node.PortalNodeInterceptor.invoke(PortalNodeInterceptor.java:81) | 09:18:40,448 ERROR STDERR - at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:38) | 09:18:40,448 ERROR STDERR - at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) | 09:18:40,448 ERROR STDERR - at org.jboss.portal.core.aspects.controller.NavigationalStateInterceptor.invoke(NavigationalStateInterceptor.java:42) | 09:18:40,448 ERROR STDERR - at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:38) | 09:18:40,448 ERROR STDERR - at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) | 09:18:40,448 ERROR STDERR - at org.jboss.portal.core.controller.ajax.AjaxInterceptor.invoke(AjaxInterceptor.java:51) | 09:18:40,448 ERROR STDERR - at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:38) | 09:18:40,448 ERROR STDERR - at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) | 09:18:40,463 ERROR STDERR - at org.jboss.portal.common.invocation.Invocation.invoke(Invocation.java:157) | 09:18:40,463 ERROR STDERR - at org.jboss.portal.core.controller.ControllerContext.execute(ControllerContext.java:121) | 09:18:40,463 ERROR STDERR - at org.jboss.portal.core.model.portal.PortalObjectResponseHandler.processCommandResponse(PortalObjectResponseHandler.java:63) | 09:18:40,463 ERROR STDERR - at org.jboss.portal.core.controller.classic.ClassicResponseHandler.processHandlers(ClassicResponseHandler.java:96) | 09:18:40,463 ERROR STDERR - at org.jboss.portal.core.controller.classic.ClassicResponseHandler.processCommandResponse(ClassicResponseHandler.java:70) | 09:18:40,463 ERROR STDERR - at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | 09:18:40,463 ERROR STDERR - at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | 09:18:40,463 ERROR STDERR - at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | 09:18:40,479 ERROR STDERR - at java.lang.reflect.Method.invoke(Method.java:585) | 09:18:40,479 ERROR STDERR - at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | 09:18:40,479 ERROR STDERR - at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | 09:18:40,479 ERROR STDERR - at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) | 09:18:40,479 ERROR STDERR - at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | 09:18:40,479 ERROR STDERR - at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) | 09:18:40,479 ERROR STDERR - at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | 09:18:40,479 ERROR STDERR - at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | 09:18:40,494 ERROR STDERR - at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | 09:18:40,494 ERROR STDERR - at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | 09:18:40,494 ERROR STDERR - at $Proxy122.processCommandResponse(Unknown Source) | 09:18:40,494 ERROR STDERR - at org.jboss.portal.core.controller.handler.ResponseHandlerSelector.processCommandResponse(ResponseHandlerSelector.java:72) | 09:18:40,494 ERROR STDERR - at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | 09:18:40,494 ERROR STDERR - at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | 09:18:40,494 ERROR STDERR - at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | 09:18:40,510 ERROR STDERR - at java.lang.reflect.Method.invoke(Method.java:585) | 09:18:40,510 ERROR STDERR - at
[jboss-user] [JBoss Portal] - Re: http://jira.jboss.com/jira/browse/JBPORTAL-459 You shoul
My environment: Windows JBoss 4.0.5 with EJB3 MySQL 5.0.37 with Connector 5.0.4 JDK 1.5 I downloaded JBoss Portal 2.6-CR2, placed it in the deploy directory, started the server up, logged in as admin, clicked the Admin link (that worked), then clicked the dashboard link and got a blank white page with the stack trace I posted earlier. According to another developer here, this was the same for CR1 as well. Thanks View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4045493#4045493 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4045493 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Portal] - Re: http://jira.jboss.com/jira/browse/JBPORTAL-459 You shoul
Yes - I used the JEMS installer (1.2.0) to create 4.0.5 + EJB3. Thanks View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4045511#4045511 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4045511 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Seam - sortable data table options
I am having some issues setting up a simple Tomahawk datatable that is sortable
and as an extra, I've added in the Ajax4jsf tags to try to make the sort
requests function as Ajax requests. The issue I am having is that the table
renders fine on the initial display. When I click a column header, the
data-rows display goes blank and the server log says:
| ...
| 08:31:43,564 ERROR org.apache.myfaces.component.html.ext.SortableModel -
java.lang.IllegalStateException: row not available
| ...
|
This line is repeated 100 times - there are 100 rows in my data set. If I
simply click the same column header again, it will display correctly (with
sorting). If I then, click again, another blank data display with the same
error messages, and so on...
My question is - does anyone know how to 'do' this correctly with Tomahawk and
Ajax4Jsf?
Please - no suggestions like use Icefaces - until I can find instructions that
tell me exactly what files to edit to integrate it into a Seam JSF app (Seam
1.2) I don't want to waste time. Also, Richfaces doesn't even seem to support
clickable sorting on a datatable. That leaves just Tomahawk for this kind of
functionality.
Here is my code.
The backing bean:
| @Name(tableBacker)
| @Scope(ScopeType.SESSION)
| public class TableBacker {
|
| @Logger
| private Log log;
|
| @DataModel
| private ListDataRow dataRows;
|
| @DataModelSelection
| private DataRow dataRow;
|
| @Factory(dataRows)
| public void getDataRows() {
| log.info(dataRows);
| if (dataRows == null) {
| generateDataRows();
| }
| }
|
| private final void generateDataRows() {
| log.info(generateDataRows());
| dataRows = new ArrayListDataRow();
| Random random = new Random(System.currentTimeMillis());
| for (long i = 0; i 100; i++) {
| //DataRow(long id, String name, Date rowDate, String
description)
| final long randomTime = System.currentTimeMillis()
| + random.nextInt(86400 * 10) * ((random.nextBoolean()) ? -1
: 1);
| final byte[] byteArray = new byte[
| 25 + random.nextInt(10) * ((random.nextBoolean()) ? -1 : 1)
| ];
| dataRows.add(
| new DataRow(
| i,
| DataRow # + i,
| new java.util.Date(randomTime),
| new StringBuffer(String.valueOf(i)).append( -
).append(byteArray).toString()
| )
| );
| }
| }
| }
|
The Facelets XHTML view:
| h:form
| a4j:outputPanel id=dataRowsPanel
| The Data:
| a4j:status
|f:facet name=start
| h:graphicImage value=./img/spinner.gif/
|/f:facet
| /a4j:status
| br/
| t:dataTable id=dataRows var=dataRow value=#{dataRows} rows=15
| sortColumn=#{id} sortAscending=false
| preserveDataModel=true preserveSort=true
| t:column defaultSorted=true sortable=true
| f:facet name=header
| t:commandSortHeader columnName=id arrow=true
| h:outputText value=Row ID/
| a4j:support event=onclick reRender=dataRowsPanel/
| /t:commandSortHeader
| /f:facet
| h:outputText value=#{dataRow.id}/
| /t:column
| t:column sortable=true
| f:facet name=header
| t:commandSortHeader columnName=name arrow=true
| h:outputText value=Row Data/
| a4j:support event=onclick reRender=dataRowsPanel/
| /t:commandSortHeader
| /f:facet
| h:outputText value=#{dataRow.name}/
| /t:column
| t:column sortable=true
| f:facet name=header
| t:commandSortHeader columnName=rowDate arrow=true
| h:outputText value=Row Date/
| /t:commandSortHeader
| /f:facet
| h:outputText value=#{dataRow.rowDate}/
| /t:column
| t:column sortable=true
| f:facet name=header
| t:commandSortHeader columnName=rowDate arrow=true
| h:outputText value=description/
| /t:commandSortHeader
| /f:facet
| h:outputText value=#{dataRow.description}/
| /t:column
| /t:dataTable
| /a4j:outputPanel
| /h:form
|
Thanks,
Brad Smith
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4042107#4042107
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4042107
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Seam - sortable data table options
Never mind - I just removed preserveDataModel=true from the t:dataTable .../ tag and all is working now. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4042113#4042113 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4042113 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Seam - sortable data table options
Pete - thanks for the link (looks like we posted at almost the same time). View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4042115#4042115 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4042115 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Where is Gavin?
Hey, I haven't seen Gavin on the forum in a few weeks now - what's going on? Thanks View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4037672#4037672 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4037672 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Where is Gavin?
I missed that post - thanks! View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4037700#4037700 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4037700 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Q: Seam Security - restrict../...
[EMAIL PROTECTED] wrote : As far as I know this should work - there's nothing
special about the EL expressions used for restrictions, i.e. they are not
required to contain only Seam Security-related expressions. As long as the
expression evaluates to a boolean it should be fine.
I have, in pages.xml, the following usage:
| page view-id=/edit_mail_configuration.xhtml
| restrict#{isUserInRole['Admin']}/restrict
| /page
|
When I invoke this page from the browser, I get the following exception:
| 08:11:12,294 ERROR org.jboss.seam.jsf.SeamPhaseListener - uncaught exception
| org.jboss.seam.security.NotLoggedInException
| at org.jboss.seam.security.Identity.checkRestriction(Identity.java:156)
| at org.jboss.seam.pages.Page.enter(Page.java:206)
| at org.jboss.seam.core.Pages.enterPage(Pages.java:276)
| at
org.jboss.seam.jsf.AbstractSeamPhaseListener.enterPage(AbstractSeamPhaseListener.java:276)
| at
org.jboss.seam.jsf.AbstractSeamPhaseListener.beforeRender(AbstractSeamPhaseListener.java:214)
| at
org.jboss.seam.jsf.SeamPhaseListener.beforePhase(SeamPhaseListener.java:56)
| at
org.apache.myfaces.lifecycle.PhaseListenerManager.informPhaseListenersBefore(PhaseListenerManager.java:70)
| at
org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:373)
| at javax.faces.webapp.FacesServlet.service(FacesServlet.java:138)
| at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
| at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at
org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:97)
| at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at
org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:144)
| at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:57)
| at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
| at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
| at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
| at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
| at
com.evergreen.fastpass.catalina.CASSSOAuthenticatorValve.invoke(CASSSOAuthenticatorValve.java:373)
| at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
| at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
| at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
| at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
| at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
| at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
| at
org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
| at java.lang.Thread.run(Thread.java:595)
I have not configured the Identity component - I am not using it. It looks
like the restrict tag does require the Identity component be configured for
restrict checks
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4034035#4034035
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4034035
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Q: Seam Security - restrict../...
anonymous wrote : If you are not using Identity to authenticate then you need
to override Identity.checkRestriction() with your own implementation that
doesn't check isLoggedIn().
This is what I suspected - that restrict\ and @Restrict require the Identity
component. And so it sounds like the answer to my original question is - no,
you can't just put
restrict#{isUserInRole['Admin']}/restrict
on a page in pages.xml or
@Restrict(#{isUserInRole['Admin']})
on a class or a method and have it 'just work' as you would expect in Seam.
The combination of Identity and and/or @Restrict is an all-or-nothing
component.
Thanks
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4034073#4034073
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4034073
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: h:commandLink has to be clicked twice
how could that be a seam issue? h:commandLink is a JSF tag View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4034252#4034252 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4034252 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Q: Seam Security - restrict../...
Hello,
I was trying to make us of the tag in pages.xml to restrict access to a page
based on whether or not a user has a role as reported by the Servlet container
(instead of using Seam security):
| restrict#{isUserInRole['Admin']}/restrict
|
Is this even possible? If not, is it possible to somehow make this check
before allowing access to a page? Also, is there an equivalent to @Restrict
that can work with the isUserInRole component?
Thanks
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4033812#4033812
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4033812
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Seam Security Question - Tomcat Valve
The problem is that the Seam security model is tightly coupled to a JAAS model of security - i.e. the Subject class and friends. With CAS and our custom Tomcat Valve, the servlet container associates/manages a copy of the authenticated Principal (a.k.a. userPrincipal in Seam) with the HttpServletRequest and in the Valve, it's possible for us to make isUserInRole() work as expected as well. It would be ideal for us if Seam allowed us to provide or override the Principal and roles for a user (and even permissions too but we're not using permissions directly) to the Identity component. I would be reluctant to use the approach you show in the previous post because that's sure to be outdated or broken with any future release of Spring - especially since there are JIRA task(s) for the Identity component now. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4033813#4033813 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4033813 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Conversation id - business key - howto
Hello,
I was reading Gavin's blog and saw this:
anonymous wrote :
| Also new in this release is ... and support for conversation propagation
via a business key (ie. instead of seeing conversationId=3 in your URL, you
would see orderId=45656).
|
Looking through the documentation on Conversations, I see this sample:
anonymous wrote :
| @Begin(id=#{myConversationIdGenerator.nextId})
| public void editHotel() { ... }
|
I was wondering (because I don't see something obvious in the Javadocs, is
there an interface, say, ConversationIdGenerator, that one can implement and
register in components.xml as the conversation id generator for a Seam
application?
Thanks
PS - the documentation for the Seam JSF controls section is outstanding now -
great job!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4033254#4033254
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4033254
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Seam 1.2.1 Released
fers wrote : Hello, | | I want to let you know that I have created Maven packages for Seam 1.2.1.GA. | | As usually you can find it on http://software.softeu.cz/seam/ . | | Petr Ferschmann I've deployed this release in our Maven 2 repository as well, but that's on our intranet ;-). Here's a sample pom.xml that anyone can use for ftp deployment of the seam artifacts to a network-accessible repository: | project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; | xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; | modelVersion4.0.0/modelVersion | | groupIdorg.jboss/groupId | artifactIdjboss-seam/artifactId | version1.2.1/version | | packagingjar/packaging | | build | | extensions | extension | groupIdorg.apache.maven.wagon/groupId | artifactIdwagon-ftp/artifactId | version1.0-alpha-6/version | /extension | /extensions | | /build | | /project | put this pom in same directory as the seam jars then execute the following commands and your own repository will be updated with the jars. | mvn deploy:deploy-file -DrepositoryId=ftp-repository -DgeneratePom=true \ | -Durl=ftp://YOUR.REPO.COM -Dpackaging=jar \ | -DgroupId=org.jboss -Dversion=1.2.1 -DartifactId=jboss-seam -Dfile=jboss-seam.jar | | mvn deploy:deploy-file -DrepositoryId=ftp-repository -DgeneratePom=true \ | -Durl=ftp://YOUR.REPO.COM -Dpackaging=jar \ | -DgroupId=org.jboss -Dversion=1.2.1 -DartifactId=jboss-seam-debug -Dfile=jboss-seam-debug.jar | | mvn deploy:deploy-file -DrepositoryId=ftp-repository -DgeneratePom=true \ | -Durl=ftp://YOUR.REPO.COM -Dpackaging=jar \ | -DgroupId=org.jboss -Dversion=1.2.1 -DartifactId=jboss-seam-pdf -Dfile=jboss-seam-pdf.jar | | mvn deploy:deploy-file -DrepositoryId=ftp-repository -DgeneratePom=true \ | -Durl=ftp://YOUR.REPO.COM -Dpackaging=jar \ | -DgroupId=org.jboss -Dversion=1.2.1 -DartifactId=jboss-seam-ui -Dfile=jboss-seam-ui.jar | | mvn deploy:deploy-file -DrepositoryId=ftp-repository -DgeneratePom=true \ | -Durl=ftp://YOUR.REPO.COM -Dpackaging=jar \ | -DgroupId=org.jboss -Dversion=1.2.1 -DartifactId=jboss-seam-mail -Dfile=jboss-seam-mail.jar | | mvn deploy:deploy-file -DrepositoryId=ftp-repository -DgeneratePom=true \ | -Durl=ftp://YOUR.REPO.COM -Dpackaging=jar \ | -DgroupId=org.jboss -Dversion=1.2.1 -DartifactId=jboss-seam-gen -Dfile=jboss-seam-gen.jar | | mvn deploy:deploy-file -DrepositoryId=ftp-repository -DgeneratePom=true \ | -Durl=ftp://YOUR.REPO.COM -Dpackaging=jar \ | -DgroupId=org.jboss -Dversion=1.2.1 -DartifactId=jboss-seam-ioc -Dfile=jboss-seam-ioc.jar | | mvn deploy:deploy-file -DrepositoryId=ftp-repository -DgeneratePom=true \ | -Durl=ftp://YOUR.REPO.COM -Dpackaging=jar \ | -DgroupId=org.jboss -Dversion=1.2.1 -DartifactId=jboss-seam-remoting -Dfile=jboss-seam-remoting.jar | Happy Maven 2'ing! View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4032326#4032326 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4032326 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Confusion on Conversation, Event-Observe, and Bijection
Hello, I have a SFSB1 - it has an a field that is marked @In @Out. This same bean has an @Observer method that listens for an event raised by another SFSB2. Here is the trouble I am having. In a conversation, I click a link which invokes a method on SFSB2 - this method in SFSB2 is annotated with @RaiseEvent(MyEvent), which SFSB1 is 'Observing'. When the @Observer(MyEvent) method gets invoked (due to the event), SFSB1 is throwing a NullPointerException on the field marked @In @Out. | 09:28:35,015 ERROR org.jboss.seam.exceptions.DebugPageHandler - redirecting to debug page | org.jboss.seam.RequiredException: @Out attribute requires non-null value: realmManager.application | | When I coded this, I assumed that @RaiseEvent would fire after outjection occurs on the SFSB1 method - i.e. invoke SFSB1 method - @In occurs - method proceeds - @Out occurs - @RaiseEvent fires from the exception, this looks like what is actually happening is: invoke SFSB1 method - @In occurs - method proceeds - @RaiseEvent fires - @Out occurs (?) Is this second case what is actually happending? If so, isn't the first case a better way to go if you want to have bijection work with raise+observe events? Thanks View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4032337#4032337 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4032337 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: jBPM - What's in scope for a DecisionHandler?
anonymous wrote : I don't understand why you don't call BusinessProcess.instance().setProcessId() before doing any work with jBPM Hey - go easy on me ;-) - BusinessProcess isn't well explained or discussed in the documentation so its taking a while for this stuff to sink in. This is in contrast to, say... conversation state, which is discussed in depth and repeatedly in the docs. I will try the approach you're suggesting above. Thanks View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4031999#4031999 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4031999 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Conceptual/Best Practice Question
In your code that alters data raise an event:
| Events.instance().raiseEvent(YOUR_EVENT_NAME);
|
In code that can refresh the data model:
| @Observer(YOUR_EVENT_NAME)
| public void refreshTheDataModel() {
|
| // your code to refresh the data model goes here
| }
|
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4032044#4032044
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4032044
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - jBPM - What's in scope for a DecisionHandler?
Hello,
I have the following DecisionHandler node:
| decision name=IsTerminationRequest
expression=#{workItemManager.isTerminationRequest}
| transition to=Check Provisioning Type name=isTerminationRequest/
| transition to=ABO Approve-Reject Request name=aboApprove/
| /decision
|
Which Seam - jBPM components point to something meaningful when that expression
is resolved and invoked?
* org.jboss.seam.core.actor
* org.jboss.seam.core.transition
* org.jboss.seam.core.businessProcess
* org.jboss.seam.core.taskInstance
* org.jboss.seam.core.processInstance
* org.jboss.seam.core.jbpmContext
* org.jboss.seam.core.taskInstanceList
* org.jboss.seam.core.pooledTaskInstanceList
* org.jboss.seam.core.taskInstanceListForType
* org.jboss.seam.core.pooledTask
I know jbpmContext is points to something 'good'. What is the contract for all
the rest of these components?
Thanks
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4031782#4031782
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4031782
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: jBPM - What's in scope for a DecisionHandler?
in a request, a task-node get's transitioned to decision handler which transitions to this decision handler. task - decision handler 1 - decision handler 2 So specifically, what I am after is what do I know I can use these components for in decision handler 2? Yes, we get to decision 2 from a JSF click. We should know the task id... Thanks View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4031792#4031792 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4031792 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: jBPM - What's in scope for a DecisionHandler?
A quick test of a few components shows that when DecisionHandler invokes the desired method, we have the following: | 16:42:33,228 INFO com.evergreen.accesscontrol.impl.WorkItemManagerBean - jbpmContext - [EMAIL PROTECTED] | 16:42:33,228 INFO com.evergreen.accesscontrol.impl.WorkItemManagerBean - processInstance - null | 16:42:33,228 INFO com.evergreen.accesscontrol.impl.WorkItemManagerBean - businessProcess - BusinessProcess(processId=null,taskId=null) | View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4031794#4031794 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4031794 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: jBPM - What's in scope for a DecisionHandler?
I would think it's fair to have the processInstance that a DecisionHandler belongs to be in scope - it's not - so now I have to figure out how to resolve this in the EJB method call - or, again, write a custom DecisionHandler and use the executionContext.getProcessInstance() method to achieve the same, but then this means I'll probably want to move all the logic from the EJB into the DecsionHandler impl and then the expression technique isn't so useful here again. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4031799#4031799 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4031799 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: MyFaces, Ajax4jsf and Tomahawk (probably beginners mista
anonymous wrote : I receive the following error: | java.lang.NoClassDefFoundError: org/apache/commons/fileupload/FileUpload | | But I never used this component | Regardless of the fact that you never used it, you need to make sure commons-fileupload is in your classpath. It can be in: | * Your .ear | * Your .war | * Your server's jsf-libs directory | | I put it in my .war in an .ear-based app. | | Hope this helps you View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4030306#4030306 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4030306 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
