Marek Novotny (JIRA | 21 May 14:12

[JBoss JIRA] (JBSEAM-4957) JBoss Tools and M2e-WTP doesn't filter properly

Marek Novotny created JBSEAM-4957:
-------------------------------------

             Summary: JBoss Tools and M2e-WTP doesn't filter properly
                 Key: JBSEAM-4957
                 URL: https://issues.jboss.org/browse/JBSEAM-4957
             Project: Seam 2
          Issue Type: Task
          Components: Tools
    Affects Versions: 2.3.0.BETA1, 2.3.0.BETA2
         Environment: JBoss Tools nightly build from 21st May 
            Reporter: Marek Novotny

Imported examples from SVN into JBoss Tools are not correctly build. There is blocked filtering of @@
tokens and that causes errors in deployment phase for instance @jndiPattern@ are not evaluated correctly.

{noformat}
Caused by: java.lang.IllegalArgumentException: Exception setting property
org.jboss.seam.core.init.jndiPattern on component org.jboss.seam.core.init.  Expression
@jndiPattern@ evaluated to null.
{noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JBoss JIRA] (SEAMSECURITY-149) IdentityImpl.runAs causes NullPointerException

Krzysztof Borgul created SEAMSECURITY-149:
---------------------------------------------

             Summary: IdentityImpl.runAs causes NullPointerException
                 Key: SEAMSECURITY-149
                 URL: https://issues.jboss.org/browse/SEAMSECURITY-149
             Project: Seam Security
          Issue Type: Bug
    Affects Versions: 3.0.0.Final
            Reporter: Krzysztof Borgul
            Priority: Critical

When you invoke runAs method and systemOp field is null (it's default situation) it will create new
ThreadLocal object with initial value equals null. Next value of thread local will be got and autounboxed
it into boolean type. This causes NPE because it cast null value into boolean type.

You can fix it replacing:
{code}
boolean savedSystemOp = systemOp.get();
{code}

by
{code}
boolean savedSystemOp = systemOp.get();
{code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
(Continue reading)

Cody Lerum (JIRA | 18 May 21:38

[JBoss JIRA] (SEAMMAIL-36) Start TLS session property uses wrong MailConfig variable

Cody Lerum created SEAMMAIL-36:
----------------------------------

             Summary: Start TLS session property uses wrong MailConfig variable
                 Key: SEAMMAIL-36
                 URL: https://issues.jboss.org/browse/SEAMMAIL-36
             Project: Seam Mail
          Issue Type: Bug
    Affects Versions: 3.1.0.Final
            Reporter: Cody Lerum
            Assignee: Cody Lerum
             Fix For: 3.1.1.Final

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Tomas Remes (JIRA | 18 May 14:06

[JBoss JIRA] (JBSEAM-4956) seam-gen still uses richfaces-3.3.0

Tomas Remes created JBSEAM-4956:
-----------------------------------

             Summary: seam-gen still uses richfaces-3.3.0
                 Key: JBSEAM-4956
                 URL: https://issues.jboss.org/browse/JBSEAM-4956
             Project: Seam 2
          Issue Type: Bug
          Components: Tools
    Affects Versions: 2.3.0.BETA2
         Environment: Seam-2.3.0.BETA2-SNAPSHOT from 2012-05-18
            Reporter: Tomas Remes
             Fix For: 2.3.0.BETA2

Project generated in seam-gen is still using richfaces-3.3.0.Final and that's why it couldn't be
deployed now:
{noformat}
Deploy of deployment "myproject.war" was rolled back with failure message {"JBAS014771: Services with
missing/unavailable dependencies" =>
["jboss.deployment.unit.\"myproject.war\".component.\"org.richfaces.taglib.SubTableTag\".START
Missing[JBAS014861: <one or more transitive
dependencies>]","jboss.deployment.unit.\"myproject.war\".component.\"org.richfaces.taglib.OrderingListTag\".START
Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.unit.\"myproject.war\".component
{noformat}

There should be only richfaces 4.2.2.Final in distribution lib.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
(Continue reading)

Marek Novotny (JIRA | 18 May 12:52

[JBoss JIRA] (JBSEAM-4955) Custom converter tags are not available

Marek Novotny created JBSEAM-4955:
-------------------------------------

             Summary: Custom converter tags are not available
                 Key: JBSEAM-4955
                 URL: https://issues.jboss.org/browse/JBSEAM-4955
             Project: Seam 2
          Issue Type: Task
          Components: JSF Controls
    Affects Versions: 2.3.0.BETA2
            Reporter: Marek Novotny

Richfaces CDK 4 doesn't support generation of custom tags for converters in case you use @JsfConverter
neither adding and combining generated taglib configuration with existing fragment of taglib.xml file

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
David Miller (JIRA | 16 May 16:31

[JBoss JIRA] (JBSEAM-4954) Incorrect documentation for Remoting

David Miller created JBSEAM-4954:
------------------------------------

             Summary: Incorrect documentation for Remoting
                 Key: JBSEAM-4954
                 URL: https://issues.jboss.org/browse/JBSEAM-4954
             Project: Seam 2
          Issue Type: Task
          Components: Documentation Issues
    Affects Versions: 2.2.2.Final
            Reporter: David Miller
            Priority: Minor

In the remoting section of the seam documentation (Chapter 25. Remoting,
http://docs.jboss.org/seam/2.2.2.Final/reference/en-US/html_single/#remoting) the 
@WebRemote annotation should be in the HelloAction class, not the interface HelloLocal(http://docs.jboss.org/seam/2.2.2.Final/reference/en-US/html_single/#d0e22796).
I can only get @WebRemote to work if it's in the class.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JBoss JIRA] (JBSEAM-4953) Need to add default-flush-mode="manual" by default.

Daniel Hinojosa created JBSEAM-4953:
---------------------------------------

             Summary: Need to add default-flush-mode="manual" by default.
                 Key: JBSEAM-4953
                 URL: https://issues.jboss.org/browse/JBSEAM-4953
             Project: Seam 2
          Issue Type: Feature Request
         Environment: All
            Reporter: Daniel Hinojosa
            Assignee: Daniel Hinojosa
            Priority: Minor

Few customers I have done consulting with never knows this option is available, it would be easier to enable
by default. I don't think there are many out there that have a strong desire for it to be AUTOMATIC.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Tomas Remes (JIRA | 16 May 16:19

[JBoss JIRA] (SEAMSECURITY-148) Authorization, Idmconsole examples are not working corectly on JDK7 due to RuntimeDroolsException

Tomas Remes created SEAMSECURITY-148:
----------------------------------------

             Summary: Authorization, Idmconsole examples are not working corectly on JDK7 due to RuntimeDroolsException
                 Key: SEAMSECURITY-148
                 URL: https://issues.jboss.org/browse/SEAMSECURITY-148
             Project: Seam Security
          Issue Type: Bug
    Affects Versions: 3.1.0.Final
         Environment: Seam 3, SUN JDK7, JBoss AS 7.1.1.Final
            Reporter: Tomas Remes

{noformat}
org.drools.RuntimeDroolsException: value '1.7' is not a valid language level
	org.drools.rule.builder.dialect.java.JavaDialectConfiguration.getDefaultLanguageLevel(JavaDialectConfiguration.java:162)
	org.drools.rule.builder.dialect.java.JavaDialectConfiguration.init(JavaDialectConfiguration.java:57)
	org.drools.compiler.PackageBuilderConfiguration.addDialect(PackageBuilderConfiguration.java:279)
	org.drools.compiler.PackageBuilderConfiguration.buildDialectConfigurationMap(PackageBuilderConfiguration.java:268)
	org.drools.compiler.PackageBuilderConfiguration.init(PackageBuilderConfiguration.java:181)
	org.drools.compiler.PackageBuilderConfiguration.<init>(PackageBuilderConfiguration.java:159)
	org.drools.builder.impl.KnowledgeBuilderFactoryServiceImpl.newKnowledgeBuilderConfiguration(KnowledgeBuilderFactoryServiceImpl.java:22)
	org.drools.builder.KnowledgeBuilderFactory.newKnowledgeBuilderConfiguration(KnowledgeBuilderFactory.java:75)
	org.jboss.seam.security.permission.SecurityRuleLoader.init(SecurityRuleLoader.java:42)
	sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	java.lang.reflect.Method.invoke(Method.java:601)
	org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:267)
	org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:52)
	org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:137)
(Continue reading)

Tomas Remes (JIRA | 16 May 15:21

[JBoss JIRA] (SOLDER-328) TetstSuite compilation error on JDK7

Tomas Remes created SOLDER-328:
----------------------------------

             Summary: TetstSuite compilation error on JDK7
                 Key: SOLDER-328
                 URL: https://issues.jboss.org/browse/SOLDER-328
             Project: Solder
          Issue Type: Bug
          Components: Test Suite
    Affects Versions: 3.1.0.Final
         Environment: Solder 3.1.1.Final, JDK 7
            Reporter: Tomas
Remes

solder/testsuite/src/test/java/org/jboss/solder/test/core/fullyqualified/package-info.java:[17,0]
error: annotation type not applicable to this kind of declaration

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Tomas Remes (JIRA | 14 May 14:28

[JBoss JIRA] (SEAM-137) Booking compilation error on IBM JDK 7

Tomas Remes created SEAM-137:
--------------------------------

             Summary: Booking compilation error on IBM JDK 7
                 Key: SEAM-137
                 URL: https://issues.jboss.org/browse/SEAM-137
             Project: Seam 3 Distribution
          Issue Type: Bug
          Components: Shared Examples
    Affects Versions: 3.1.0.Final
         Environment: IBM J9 VM build 2.6, JRE 1.7.0 Linux x86-32 20110810_88604
            Reporter: Tomas Remes

Cannot compile booking example on IBM JDK 7 because of weird following exception:
{noformat}
[ERROR] Failure executing javac, but could not parse the error:
chyba:Cannot read org.jboss.seam.examples.booking.log package files, cause :
java.io.FileNotFoundException: org.jboss.seam.examples.booking.log/BookingLog
  	at com.sun.tools.javac.processing.JavacFiler.getResource(JavacFiler.java:476)
  	at org.jboss.logging.generator.apt.TranslationClassGenerator.findTranslationFiles(TranslationClassGenerator.java:132)
  	at org.jboss.logging.generator.apt.TranslationClassGenerator.processTypeElement(TranslationClassGenerator.java:95)
  	at org.jboss.logging.generator.apt.LoggingToolsProcessor.process(LoggingToolsProcessor.java:153)
  	at com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:805)
  	at com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:734)
  	at com.sun.tools.javac.processing.JavacProcessingEnvironment.access$1700(JavacProcessingEnvironment.java:109)
  	at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1041)
  	at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1175)
  	at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1118)
  	at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:836)
  	at com.sun.tools.javac.main.Main.compile(Main.java:429)
(Continue reading)

[JBoss JIRA] (SEAM-136) EAR deployment - error injecting HTTP objects - before they have been initialized

Matthew Hibberd created SEAM-136:
------------------------------------

             Summary: EAR deployment - error injecting HTTP objects - before they have been initialized
                 Key: SEAM-136
                 URL: https://issues.jboss.org/browse/SEAM-136
             Project: Seam 3 Distribution
          Issue Type: Bug
    Affects Versions: 3.1.0.Final
         Environment: JBoss 7.1.1.Final, JDK 7
            Reporter: Matthew Hibberd

Packaging a Seam 3 application in an EAR creates problems with trying to inject HTTP objects.
For e.g. Error injecting HttpSession on identity.logout results in the stack trace below.
A thread in the Seam 3 forums regarding this issue can be found
[here|https://community.jboss.org/thread/199410]. It includes an example EAR packaged project to test.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

Gmane