[JBoss JIRA] (SEAMWICKET-44) HomePageTest fails
by Jozef Hartinger (Created) (JIRA)
HomePageTest fails
------------------
Key: SEAMWICKET-44
URL: https://issues.jboss.org/browse/SEAMWICKET-44
Project: Seam for Apache Wicket
Issue Type: Bug
Affects Versions: 3.1.0.Beta3
Reporter: Jozef Hartinger
Assignee: Jozef Hartinger
Fix For: 3.1.0.CR1
{noformat}
org.jboss.seam.wicket.examples.numberguess.test.HomePageTest Time elapsed: 1.584 sec <<< ERROR!
java.lang.RuntimeException: Could not invoke deployment method: public static org.jboss.shrinkwrap.api.spec.WebArchive org.jboss.seam.wicket.examples.numberguess.test.HomePageTest.createTestArchive()
at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.invoke(AnnotationDeploymentScenarioGenerator.java:160)
at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.generateDeployment(AnnotationDeploymentScenarioGenerator.java:94)
at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.generate(AnnotationDeploymentScenarioGenerator.java:57)
at org.jboss.arquillian.container.test.impl.client.deployment.DeploymentGenerator.generateDeployment(DeploymentGenerator.java:79)
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:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114)
at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:96)
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:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:68)
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:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:54)
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:597)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114)
at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:80)
at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:158)
at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:290)
at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:45)
at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:175)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:123)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
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:597)
at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68)
Caused by: java.lang.reflect.InvocationTargetException
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:597)
at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.invoke(AnnotationDeploymentScenarioGenerator.java:156)
... 56 more
Caused by: java.lang.ExceptionInInitializerError
at org.jboss.seam.wicket.examples.numberguess.test.HomePageTest.createTestArchive(HomePageTest.java:39)
... 61 more
Caused by: org.jboss.shrinkwrap.resolver.api.ResolutionException: Found 1 problems while building POM model from /opt/sources/Seam_3/modules/wicket/examples/numberguess/pom.xml1/ [FATAL] Non-resolvable parent POM for org.jboss.seam.wicket:seam-wicket-parent:3.1.0-SNAPSHOT: Failed to resolve POM for org.jboss.seam:seam-parent:15 due to Could not find artifact org.jboss.seam:seam-parent:pom:15 in central (http://repo1.maven.org/maven2) and 'parent.relativePath' points at wrong local POM @ org.jboss.seam.wicket:seam-wicket-parent:3.1.0-SNAPSHOT, /opt/sources/Seam_3/modules/wicket/pom.xml
at org.jboss.shrinkwrap.resolver.impl.maven.MavenRepositorySystem.loadPom(MavenRepositorySystem.java:154)
at org.jboss.shrinkwrap.resolver.impl.maven.MavenRepositorySystem.loadPom(MavenRepositorySystem.java:126)
at org.jboss.shrinkwrap.resolver.impl.maven.MavenBuilderImpl.loadMetadataFromPom(MavenBuilderImpl.java:153)
at org.jboss.seam.wicket.examples.numberguess.test.Dependencies.<clinit>(Dependencies.java:10)
... 62 more
Caused by: org.apache.maven.model.building.ModelBuildingException: 1 problem was encountered while building the effective model for org.jboss.seam.wicket:seam-wicket-example-numberguess:3.1.0-SNAPSHOT
[FATAL] Non-resolvable parent POM for org.jboss.seam.wicket:seam-wicket-parent:3.1.0-SNAPSHOT: Failed to resolve POM for org.jboss.seam:seam-parent:15 due to Could not find artifact org.jboss.seam:seam-parent:pom:15 in central (http://repo1.maven.org/maven2) and 'parent.relativePath' points at wrong local POM @ org.jboss.seam.wicket:seam-wicket-parent:3.1.0-SNAPSHOT, /opt/sources/Seam_3/modules/wicket/pom.xml
at org.apache.maven.model.building.DefaultModelBuilder.readParentExternally(DefaultModelBuilder.java:847)
at org.apache.maven.model.building.DefaultModelBuilder.readParent(DefaultModelBuilder.java:670)
at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:308)
at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:232)
at org.jboss.shrinkwrap.resolver.impl.maven.MavenRepositorySystem.loadPom(MavenRepositorySystem.java:140)
... 65 more
{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
12 years, 7 months
[JBoss JIRA] (SOLDER-287) Solder documentation issues
by Marek Schmidt (Created) (JIRA)
Solder documentation issues
---------------------------
Key: SOLDER-287
URL: https://issues.jboss.org/browse/SOLDER-287
Project: Seam Solder
Issue Type: Bug
Components: Documentation
Affects Versions: 3.1.0.Beta3
Reporter: Marek Schmidt
"Seam Solder" still mentioned in several places (e.g. the header), I am not sure if that term should still be used or not.
Chapter 1 Getting Started
1.2. Transitive dependencies
the "tip" still contains old groupId and artifactId (org.jboss.seam.solder, seam-solder-parent, seam.solder.version)
1.3. Pre-Servlet 3.0 configuration
org.jboss.seam.solder.resourceLoader.servlet.ResourceListener
Chapter 3 Annotation Literals
@GenericConfiguration literal is not mentioned in the list of literals
Chapter 4 Evaluating Unified EL
missing description of the @Resolver annotation
Chapter 6 Logging, redesigned
"The license for Seam is " confusing to have Seam in the example if Solder is not part of Seam anymore
6.4 Native logger API
it should probably be "org.jboss.solder.logging.Logger;" instead of "org.jboss.logging.Logger;"
6.6.1. Generating the implementation classes
"TrainMessages_fr.i18n.properties" should be "TrainMessages.i18n_fr.properties" instead
Chapter 7 Annotation and AnnotatedType Utilities
7.1 Annotated Type Builder
in the 1st code block, "AnnotatedTypeBuilder builder = new AnnotatedTypeBuilder() ... .create()" the last line (".create()") should not be there.
in the 4th code block, "RedefinitionContext<A>" should probably be "RedefinitionContext<Unique>" instead,
in the 4th code block, the ".create();" line should not be there.
7.3. Annotation Inspector
1st code block, AnnotationInspector.getAnnotations should have only two arguments
Chapter 8. Obtaining a reference to the BeanManager
"When developing a framework that builds on CDI, you may need to obtain the BeanManager for the application, can't simply inject it as you are not working in an object managed by the container. " missing "you" before "can't simply inject"?
Chapter 10. Properties
Table 10.1 Property methods
methods "Member getMember();" and "void setAccessible()" are not mentioned in the table, could be intentional.
Chapter 11. Unwrapping Producer Methods
"The lifecycle of the bean is are managed by the bean that defines the producer method " one "are" too many.
Chapter 13. Generic Beans
13.1 Using generic beans
"Seam XML" is mentioned twice
Chapter 15. XML Configuration Introduction
error in formatting in the HTML output, some XML piece 'ml_plain">' on each line in the example
"mvn jetty:run" it has to be "mvn -Pjetty jetty:run" now, either the example or the docs should be fixed
Chapter 16.1 XML Namespaces
namespaces need to be updated:
org.jboss.weld.extensions.core
org.jboss.weld.extensions.unwraps
org.jboss.weld.extensions.resourceLoader
Chapter 16.2 Adding, replacing and modifying beans
(or somewhere else) there should be a note on how s:modifies behaves with @Veto
18.3.1. @HandlesExceptions
"The @HandlesExceptions annotation may be deprecated in favor of annotation indexing done by Solder. "
the link links to http://seamframework.org/Seam3/Solder which doesn't make sense, as this text is now inside the solder documentation.
18.3.2. @Handles
"stout" typo? (stdout)
20.3. Supporting ServiceHandlers
"ServiceHandlers make for a very easy and concise way to define exception handlers." link to ServiceHandlers should now be an internal one, as this document is now the solder documenation.
"The following example comes from the jaxrs example in the distribution", there is no "jaxrs" example in the Solder distribution
24.2. Defining a exception handler for a web request
"Currently, @WebRequest is required to catch exceptions initiated by the Servlet integration because of a bug in Solder."
is this stll true? SOLDER-130 is marked as resolved, Should @Any be used?
--
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
12 years, 7 months
[JBoss JIRA] Created: (SEAMCONFIG-49) Support fields of the class Properties: replacing and modifying (regression from seam 2)
by Geoffrey De Smet (JIRA)
Support fields of the class Properties: replacing and modifying (regression from seam 2)
----------------------------------------------------------------------------------------
Key: SEAMCONFIG-49
URL: https://issues.jboss.org/browse/SEAMCONFIG-49
Project: Seam Config
Issue Type: Feature Request
Reporter: Geoffrey De Smet
Assignee: Geoffrey De Smet
In seam 2 you could do something like this:
{code}
<component name="repositoryConfiguration">
<property name="setupProperties">
<key>org.drools.repository.configurator</key><value>org.drools.repository.jackrabbit.JackrabbitRepositoryConfigurator</value>
<!-- the root directory for the repo storage the directory must exist. -->
<!-- <key>repository.root.directory</key><value>/opt/yourpath</value> -->
</property>
</component>
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] Created: (SEAM-94) Shaded jars like seam-solder instead of seam-solder-api and seam-solder-impl result in the same classes twice in the classpath (possibly different versions)
by Geoffrey De Smet (JIRA)
Shaded jars like seam-solder instead of seam-solder-api and seam-solder-impl result in the same classes twice in the classpath (possibly different versions)
------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: SEAM-94
URL: https://issues.jboss.org/browse/SEAM-94
Project: Seam 3 Distribution
Issue Type: Bug
Reporter: Geoffrey De Smet
Shaded jars (like seam-solder) are highly problematic in itself, see WELD-935.
Trying to avoid the shaded jars, is impossible, as this example shows:
{code}
$ mvn dependency:tree
...
[INFO] +- org.jboss.seam.solder:seam-solder-api:jar:3.0.0.Final:compile ===========> my compile dependency on solder-api (the non-shaded jar)
[INFO] +- org.jboss.seam.solder:seam-solder-impl:jar:3.0.0.Final:runtime ==========> my runtime dependency on solder-impl (the non-shaded jar)
[INFO] +- org.jboss.seam.security:seam-security-api:jar:3.0.0.Final:compile
...
[INFO] +- org.jboss.seam.security:seam-security-impl:jar:3.0.0.Final:compile
[INFO] | +- org.jboss.seam.solder:seam-solder:jar:3.0.0.Final:compile ============> transitive dependency on solder (the shaded jar) which shades the classes of solder-api
{code}
Now suppose I depend on solder-api 3.0..Final instead (still with seam-security-impl 3.0.0.Final): I 'd have 2 different versions of solder in my classpath.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] Created: (JBSEAM-4841) Mail MIME Attachment IS NOT TO SPEC
by nathan dennis (JIRA)
Mail MIME Attachment IS NOT TO SPEC
-----------------------------------
Key: JBSEAM-4841
URL: https://issues.jboss.org/browse/JBSEAM-4841
Project: Seam 2
Issue Type: Bug
Components: Mail
Affects Versions: 2.2.0.GA
Environment: Centos 5.x, Centos 6.x, Jboss 5.1.0, Thunderbird 5.x, Thunderbird 6.x
Reporter: nathan dennis
Assignee: Pete Muir
Message containing attachments not intended to be displayed inline are being formatted incorrectly. The current MIME type is not to spec RFC2387. (http://www.ietf.org/rfc/rfc2387.txt) As a result, mail clients that have chosen to strictly follow the spec will no longer correctly handle non inline attachments generated with seam mail.
i believe this is related to JBSEAM-3906. However that work around listed there will create more problems than it will fix. (i actually tried that workaround on my own before i even visited the forum for help.) on closer inspection, it will attach ALL attachments using the inherited parent MIME type mixed which will cause all of your inline content to not be formatted.
ei...
<m:attachment
value="/img.png"
contentType="image/jpeg"
fileName="header.jpg"
status="headerPhoto"
disposition="inline" />
<img src="cid:#{headerPhoto.contentId}" />
will no long work. i actually started rewriting some of UIBody.java only to realize i needed to read and study more before i wrote a patch.
below is a sample message.
Message-ID: <1992253538.401315329484805.JavaMail.jboss@node1>
Subject: Online Credit Application
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_Part_65_749177026.1315329484754"
X-Priority: 5
Priority: Non-urgent
Importance: low
X-Sent-From: Node1
Date: Tue, 6 Sep 2011 13:18:04 -0400 (EDT)
------=_Part_65_749177026.1315329484754
Content-Type: multipart/related; (***********************PROBLEM IS HERE and inherited below*********************)
boundary="----=_Part_66_721653621.1315329484804"
------=_Part_66_721653621.1315329484804
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
------=_Part_66_721653621.1315329484804
Content-Type: application/pdf; name=XXXXXXXXXXX.pdf
Content-Transfer-Encoding: base64
Content-ID: <aeamddeazitbtngdcsln>
Content-Disposition: attachment; filename=XXXXXXXXXXX.pdf
JVBERi0xLjQKJeLjz9MKMyAwIG9iaiA8PC9MZW5ndGggMTY0My9GaWx0ZXIvRmxhdGVEZWNvZGU+
PnN0cmVhbQp4nJVY227bNhi+91MQ2MVSoGEkijrtZkucZHWRUxsPRYfe0BITc5FFl5KbeE/TR91P
yk5s+aeTIUhgh/z+85HfByfjQRjTMCUZS2gWkXE5CMhhEoaUM/vlbDz4NPjufhn5CGd/DkLyOGCM
xiTNGU0TEscBiTgNUmLk4HbjOM1okrvjEDlO8oAyd5pllOf90zShYeQHhzmNQ3ccJzRh/eMgppx7
0XGa0yh1x6D17nESUz/rmOeUrY4xcATmTPxoEDzI/WgQPGBeNE8ZzbLO4oyGvH8cZzQL/egQHOJO
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months