[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2945) seam-gen test readme.txt has out of date jars listed
by Jay Balunas (JIRA)
seam-gen test readme.txt has out of date jars listed
----------------------------------------------------
Key: JBSEAM-2945
URL: http://jira.jboss.com/jira/browse/JBSEAM-2945
Project: Seam
Issue Type: Task
Components: Documentation Issues
Affects Versions: 2.0.2.CR2
Reporter: Jay Balunas
The readme.txt file that gets put in the seam-gen test source directory contains out of date jar files. Below is the complete readme.
Changes need (from what I can see):
- embedded-api.jar --> jboss-embedded-api.jar
- jboss-deployers.jar --> jboss-deployers-client-spi.jar, jboss-deployers-core-spi.jar
readme.txt
If you want to run tests using the Eclipse TestNG plugin, you'll need to add
these jars to the top of your TestNG classpath. Using the Run Dialog, select
xml suite to run, and add /lib/test/jboss-embedded-all.jar,
/lib/test/hibernate-all.jar, /lib/test/thirdparty-all.jar, /lib/embedded-api.jar,
/lib/jboss-deployers.jar and /bootstrap as the first entries in the User
classpath.
To add tests to your project create a TestNG xml descriptor called *Test.xml e.g.
FooTest.xml next to your test classes and run ant test.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 8 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1526) Support selective validation with a:region
by Christian Bauer (JIRA)
Support selective validation with a:region
------------------------------------------
Key: JBSEAM-1526
URL: http://jira.jboss.com/jira/browse/JBSEAM-1526
Project: JBoss Seam
Issue Type: Feature Request
Components: JSF
Reporter: Christian Bauer
In complex forms I'd like to be able to customize validation per region:
<h:form>
<a:region>
<h:inputText value="#{foo.bar}"/>
<a:region>
<h:inputText value="#{bar.foo}"/>
<a:commandButton action="#{bar.baz}"/>
</a>
<a:commandButton action="#{foo.baz}"/>
</a>
</h:form>
If the nested button is pressed, I only want #{bar.foo} validated (there is an <s:validateAll> around it). If the outer button is pressed, I want both properties validated. I realize that this is a major issue regarding model updates, however, I don't need to update the model for any non-validated property because
a) it is not decoded on the server anyway (? I don't understand the a:region docs)
b) i don't need an updated model because my action doesn't expect it
c) i don't need an updated model because i am re-rendering an area that doesn't expect it
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 9 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2325) ejb3/seam-gwt-remoting/gwt security integration
by darren hartford (JIRA)
ejb3/seam-gwt-remoting/gwt security integration
-----------------------------------------------
Key: JBSEAM-2325
URL: http://jira.jboss.com/jira/browse/JBSEAM-2325
Project: JBoss Seam
Issue Type: Task
Components: Remoting, Security
Affects Versions: 2.0.0.GA
Environment: jboss 4.2.1
seam 2.0.0.GA
win2k
Any security-domain will work with name 'SpringPoweredRealm' with a user having 'security_role' role.
Reporter: darren hartford
Assigned To: Shane Bryzak
Attachments: ejb3-gwt-security-sample.zip
Attached is a sample project showing a problem related to Seam-GWT-Remoting integration with a GWT app, and security integration challenge.
Error is detailed in forum link, top level server-side error is "[[/sample-ejb3-gwt-client]] Exception while dispatching incoming RPC call org.jboss.seam.security.NotLoggedInException "
Not sure what integration method would be the best approach for secured methods for Seam-GWT-Remoting on the server side to the GWT client side.
Expectations:
*Once logged into web application, use of secured method/services to succeed automatically with appropriate roles without additional login (role based security assumed with Seam @Restrict annotation).
*Once logged into web application, use of secured method/services to fail for insufficient role authorization, with sufficient information to determine it was a security failure instead of a service failure.
*Anonymous web application login with a GWT widget requesting a secured Seam Remoting service/method would require either re-routing to web-app login page, or login to ONLY use the requested secured Seam service/method. This could be managed with GWT code to meet this expectation.
thanks, learning as best as I can with available documentation. Permission given under LGPL license to use as an example in future documentation/examples.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 9 months