Re: Which dojo?
On Jul 1, 2009, at 10:18 PM, Rex Wang wrote: Yep, the current portlet dev is really complicated, but there will be a huge work to do if we decide to switch pluto to other framework like JSF... not sure how much for Pluto2. And I think we don't have enough time for the migration before G2.2 release.. I agree. But we need to fix the private repo issue now. is anyone looking at my patch or my patch updated to the latest dojo release? Since I don't see problems I'm tempted to apply it. Then we can try to figure out something for the 0.4.3 legacy dojo. thanks david jencks -Rex 2009/7/2 David Jencks david_jen...@yahoo.com If we're going to rewrite bits of the portal, we should consider moving to pluto 2. IIUC there are a bunch of features in portlet 2 spec that may make our portlets simpler. I also think we should investigate frameworks such as jsf or even wicket or something because the current portlet code is ridiculously complicated for what it does. There must be a more sensible way to write a web app. thanks david jencks On Jul 1, 2009, at 9:41 AM, Joseph Leong wrote: So unfortunately what happened between Dojo 0.4.3- Mostly anything newer especially 1.3.1 is that they had the idea to classify their libraries to Dijit (Widgets) and other subsections. As such, the porting effort is not small. I believe the debug-views portlets and such still depend on 0.4.3. At this point in time, my opinion would be to not try and migrate any 0.4.3 dependent code. There has been so much change between the dojo versions that it would be probably simpler and cleaner to just rewrite these portlets. I think it'd be a good choice to get rid of the old Dojo libraries once and for all as they add a bit to the geronimo footprint size.. not to mention there are a lot more features in the latest Dojo release that can probably accomplish what you wanted to in the older versions. Thanks, Joseph Leong On Wed, Jul 1, 2009 at 12:10 PM, David Jencks david_jen...@yahoo.com wrote: On Jul 1, 2009, at 1:14 AM, Ivan wrote: I think the one is what need, no samples and testcases are included. But I found 1.3.1 is released, why not use the newest one ? Newer would be better if we can get it to work. I set this up a few days ago and forgot the details... I think that I saw some problem and wasn't sure what was causing it and tried changing to an earlier dojo version. I didn't actually have any reason to think the problem was caused by dojo so very likely the more recent release should work. And for the legacy dojo 0.4.3, how shall we handle it ? Like tomcat, maitaine a our own repo ? Ideally I think we would migrate our code to up-to-date dojo. Unfortunately I have no idea how hard that would be. Does anyone? If we can't, I think there is some release of some 0.4.3 dojo, perhaps we can investigate using or repackaging it. There's also dwr but I think working on one dependency at a time will be less confusing. thanks david jencks 2009/7/1 David Jencks david_jen...@yahoo.com In my attempt to remove our svn repo I found that dojo releases a dojo-war that looks pretty similar to our repacked dojo war. I can make the build work with the substitution but I don't know enough about dojo to know if/what it breaks. Is there anyone who understands our use of dojo well enough to take a look and see if this replacement is plausible? I recall some discussion in the distant past about not including all of dojo... I'm not sure if this is still a concern, but if the released dojo-war works and is too big we can use maven to come up with a smaller war. See https://issues.apache.org/jira/browse/GERONIMO-4723 for my patch. thanks david jencks -- Ivan
Re: Problem when deploy CXF WebService (Service resource injection failed)
Can anyone help me, please?
Thanks,
Westhveg
Westhveg wrote:
And if I try to test the webservice developing this spring client:
?xml version=1.0 encoding=UTF-8?
beans xmlns=http://www.springframework.org/schema/beans;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:jaxws=http://cxf.apache.org/jaxws;
xsi:schemaLocation=http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
http://cxf.apache.org/jaxws
http://cxf.apache.org/schemas/jaxws.xsd;
!--
If I uncomment this, I get the same exception. But if I leave it
commented, I must import FastInfoset.jar library.
import resource=classpath:META-INF/cxf/cxf.xml /
import resource=classpath:META-INF/cxf/cxf-extension-soap.xml /
import resource=classpath:META-INF/cxf/cxf-servlet.xml /
--
jaxws:client id=helloWordClient
serviceClass=com.test.HelloWorld
address=http://localhost:8080/helloWorld; /
/beans
30-jun-2009 23:52:33 org.apache.cxf.bus.spring.BusApplicationContext
getConfigResources
INFO: No cxf.xml configuration file detected, relying on defaults.
30-jun-2009 23:52:34
org.apache.cxf.service.factory.ReflectionServiceFactoryBean
buildServiceFromClass
INFO: Creating Service {http://test.com/}HelloWorldService from class
com.test.HelloWorld
30-jun-2009 23:52:34 org.apache.cxf.phase.PhaseInterceptorChain
doIntercept
INFO: Interceptor has thrown exception, unwinding now
org.apache.cxf.interceptor.Fault: Could not send Message.
at
org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:64)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:236)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:471)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:301)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:253)
at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
at
org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:121)
at $Proxy44.postMessage(Unknown Source)
at com.test.TestWsClient.main(TestWsClient.java:15)
Caused by: java.io.IOException: Not Found
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2064)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:2015)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1940)
at
org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66)
at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:627)
at
org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
... 8 more
Exception in thread main javax.xml.ws.soap.SOAPFaultException: Could not
send Message.
at
org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:141)
at $Proxy44.postMessage(Unknown Source)
at com.test.TestWsClient.main(TestWsClient.java:15)
Caused by: java.io.IOException: Not Found
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2064)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:2015)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1940)
at
org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66)
at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:627)
at
org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:236)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:471)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:301)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:253)
at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
at
org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:121)
... 2 more
Westhveg wrote:
Jarek,
Now the exception is:
Distribution of module failed. See log for details.
AbstractWebModuleBuilder: Could not load listener class:
org.springframework.web.context.ContextLoaderListener
org.apache.geronimo.common.DeploymentException:
AbstractWebModuleBuilder: Could not load listener class:
org.springframework.web.context.ContextLoaderListener
at
Duplicate clustername value sets in config-subsititions file
Hi all, I just noticed there are 2 pairs of clusterName=CLUSTER_NAME in config-substitions.properties. My understanding of them is one for WADI clustering and another for farming. Can we using different keywords to identify them? ie. farmingClusterName and WADIClusterName or sth. like that. Jeff C
[BUILD] trunk: Failed for Revision: 791456
Geronimo Revision: 791456 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090706/build-0900.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090706
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 43 minutes 20 seconds
[INFO] Finished at: Mon Jul 06 09:47:43 EDT 2009
[INFO] Final Memory: 403M/1014M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090706/logs-0900-tomcat/
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:45.665
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/testing/testsuite-testing.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS (0:01:18.901)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:34.460)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:40.861)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:21.046)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:33.205)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced FAILURE (0:03:24.235) Java
returned: 1
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:01.047)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:52.615)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:01:01.313)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:46.611)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:33.925)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:34.470)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:35.866)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:01:16.878)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:00.308)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:50.953)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:32.280)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:52.064)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security SUCCESS (0:00:50.450)
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:34.042)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:31.554)
[INFO] web-testsuite/test-myfaces RUNNING
[INFO] web
Re: Problem when deploy CXF WebService (Service resource injection failed)
Westhveg,
Let's back up a little. You have two options for deploying your web service:
1) Deploy your web application WITH all cxf and spring jars but you
MUST: a) start the server with
-Dorg.apache.geronimo.jaxws.builder.useSimpleFinder=true AND b)
specify a bunch of filters in geronimo-web.xml.
or
2) Deploy your web application WITHOUT any cxf AND spring jars and
without CXFServlet in the web.xml. In this case your web application
should only contain the web service class and any other jars/classes
that the web service needs. The war file should be much smaller. Don't
set org.apache.geronimo.jaxws.builder.useSimpleFinder property or any
filters in geronimo-web.xml.
With option 2) you are relying on the app server to deploy your web
service. The app server will use its own web service engine to deploy
and manage your web service. That's why you don't need all these
spring or cxf jars or the cxf servlet or cxf configuration files. With
option 1) you are not relying on the app server to deploy and manage
your web service. The web application you are deploying has it own web
services engine which will deploy and manage the web service. And to
prevent conflicts between the web app web service engine and the app
server web service engine you need to set those filters and that
property.
Jarek
On Mon, Jul 6, 2009 at 5:13 AM, Westhvegwesthstud...@gmail.com wrote:
Can anyone help me, please?
Thanks,
Westhveg
Westhveg wrote:
And if I try to test the webservice developing this spring client:
?xml version=1.0 encoding=UTF-8?
beans xmlns=http://www.springframework.org/schema/beans;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:jaxws=http://cxf.apache.org/jaxws;
xsi:schemaLocation=http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
http://cxf.apache.org/jaxws
http://cxf.apache.org/schemas/jaxws.xsd;
!--
If I uncomment this, I get the same exception. But if I leave it
commented, I must import FastInfoset.jar library.
import resource=classpath:META-INF/cxf/cxf.xml /
import resource=classpath:META-INF/cxf/cxf-extension-soap.xml /
import resource=classpath:META-INF/cxf/cxf-servlet.xml /
--
jaxws:client id=helloWordClient
serviceClass=com.test.HelloWorld
address=http://localhost:8080/helloWorld; /
/beans
30-jun-2009 23:52:33 org.apache.cxf.bus.spring.BusApplicationContext
getConfigResources
INFO: No cxf.xml configuration file detected, relying on defaults.
30-jun-2009 23:52:34
org.apache.cxf.service.factory.ReflectionServiceFactoryBean
buildServiceFromClass
INFO: Creating Service {http://test.com/}HelloWorldService from class
com.test.HelloWorld
30-jun-2009 23:52:34 org.apache.cxf.phase.PhaseInterceptorChain
doIntercept
INFO: Interceptor has thrown exception, unwinding now
org.apache.cxf.interceptor.Fault: Could not send Message.
at
org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:64)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:236)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:471)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:301)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:253)
at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
at
org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:121)
at $Proxy44.postMessage(Unknown Source)
at com.test.TestWsClient.main(TestWsClient.java:15)
Caused by: java.io.IOException: Not Found
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2064)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:2015)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1940)
at
org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66)
at
org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:627)
at
org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
... 8 more
Exception in thread main javax.xml.ws.soap.SOAPFaultException: Could not
send Message.
at
org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:141)
at $Proxy44.postMessage(Unknown Source)
at com.test.TestWsClient.main(TestWsClient.java:15)
Caused by: java.io.IOException: Not Found
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2064)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:2015)
Re: Trunk Builds
Shawn, I recently modified ConfirmMessageTag.java so that it points to the right locations for dojo resources. It used to point to http://localhost:8080/dojo/dojo/dojo.js (which does not work) but now points to http://localhost:8080/dojo/dojo/dojo/dojo.js (which does work). That made the confirmation box to display again. The confirmation box does display now when you use the web browser and follow the steps of the test but somehow it fails in our automatic tests. The test does pass for me when I execute it on my machine in the same way as the automatic tests do... so that's why I thought it was a timing issue. But there might be something else going on, I'm not sure. Jarek On Fri, Jul 3, 2009 at 10:53 AM, Shawn Jianggenspr...@gmail.com wrote: On Fri, Jul 3, 2009 at 2:53 AM, Jarek Gawor jga...@gmail.com wrote: Shawn, The one failure in console/advanced on Tomcat is caused by fixing that prompting issue in the console. I'm hoping it's just a timing issue It's not a timing issue. This is caused by a modification on ConfirmMessageTag.java recently . After that change, dojo.js can't be found so that the prompting dialog can't be display anymore. Revert the bvt change and update the code private static final String DOJO_BASE = /dojo/dojo to private static final String DOJO_BASE = /dojo can fix this. since its takes a bit of time to load all the Dojo stuff for the first time. So I just increased the wait time for the window to show up in that test. Jarek On Wed, Jul 1, 2009 at 9:31 PM, Shawn Jianggenspr...@gmail.com wrote: I can't recreate the same console/advanced failure in my local machine. But I do find another console testsuite bug and filed a JIRA: https://issues.apache.org/jira/browse/GERONIMO-4720 (patch provided) The failure of enterprise-testsuite/sec-tests is related to run-as propagation from a servlet to another servlet. I'm looking into it and will provide a patch. On Thu, Jun 25, 2009 at 11:58 PM, Jarek Gawor jga...@gmail.com wrote: Based on running the testsuite yesterday and with fixes committed last night I *think* we should be passing all tests on Tomcat and fail enterprise-testsuite/sec-tests and webservices-testsuite/jaxws-tests on Jetty. The webservices-testsuite/jaxws-tests fails because of GERONIMO-4645. Not sure what's going on with enterprise-testsuite/sec-tests. Jarek On Thu, Jun 25, 2009 at 11:00 AM, Kevan Millerkevan.mil...@gmail.com wrote: A search of emails shows that our last successful automated build of trunk was on May 26th. I know that there have been increasing frustration with these recent build issues. We seem to be closing in on getting these issues resolved. I built last night. I built successfully, last night, but had 7 testsuite failures -- 3 jetty, 4 tomcat. I think it would do us a lot of good to have a concerted effort to get these final issues resolved. Here are the test failures that I'm seeing: 3 common errors: [INFO] The following tests failed: [INFO] * console-testsuite/advanced - /Users/kevan/geronimo/server/trunk/testsuite/console-testsuite/advanced/build.log [INFO] * enterprise-testsuite/sec-tests - /Users/kevan/geronimo/server/trunk/testsuite/enterprise-testsuite/sec-tests/build.log [INFO] * webservices-testsuite/jaxws-tests - /Users/kevan/geronimo/server/trunk/testsuite/webservices-testsuite/jaxws-tests/build.log 1 Tomcat unique failure: [INFO] * web-testsuite/test-tomcat - /Users/kevan/geronimo/server/trunk/testsuite/web-testsuite/test-tomcat/build.log Is this consistent with what others are seeing? --kevan -- Shawn -- Shawn
[jira] Created: (GERONIMO-4727) Setting a parameterized pojo in blueprint throws exception
Setting a parameterized pojo in blueprint throws exception
--
Key: GERONIMO-4727
URL: https://issues.apache.org/jira/browse/GERONIMO-4727
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Reporter: Gert Vanthienen
When the setter of property uses a parameterized type (e.g.
*{{setLruList(LruListPaxLoggingEvent events)}}*) and the bean being injected
is the raw type (e.g. *{{new LruList()}}*, we get: this exception:
{noformat}
org.osgi.service.blueprint.container.ComponentDefinitionException:
Unable to convert property value from org.apache.felix.karaf.gshell.log.LruList
to
org.apache.felix.karaf.gshell.log.LruListorg.ops4j.pax.logging.spi.PaxLoggingEvent
for injection
public void
org.apache.felix.karaf.gshell.log.VmLogAppender.setEvents(org.apache.felix.karaf.gshell.log.LruList)
at
org.apache.geronimo.blueprint.container.BeanRecipe.setProperty(BeanRecipe.java:604)
at
org.apache.geronimo.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:571)
at
org.apache.geronimo.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:552)
at
org.apache.geronimo.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:501)
at
org.apache.geronimo.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:62)
at
org.apache.geronimo.blueprint.di.RefRecipe.internalCreate(RefRecipe.java:60)
at
org.apache.geronimo.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:62)
...
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4727) Setting a parameterized pojo in blueprint throws exception
[
https://issues.apache.org/jira/browse/GERONIMO-4727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen updated GERONIMO-4727:
--
Attachment: GERONIMO-4727.diff
This patch will give the raw type 'the benefit of the doubt' during type
conversion before invoking the setter.
Setting a parameterized pojo in blueprint throws exception
--
Key: GERONIMO-4727
URL: https://issues.apache.org/jira/browse/GERONIMO-4727
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Reporter: Gert Vanthienen
Attachments: GERONIMO-4727.diff
When the setter of property uses a parameterized type (e.g.
*{{setLruList(LruListPaxLoggingEvent events)}}*) and the bean being
injected is the raw type (e.g. *{{new LruList()}}*, we get: this exception:
{noformat}
org.osgi.service.blueprint.container.ComponentDefinitionException:
Unable to convert property value from
org.apache.felix.karaf.gshell.log.LruList to
org.apache.felix.karaf.gshell.log.LruListorg.ops4j.pax.logging.spi.PaxLoggingEvent
for injection
public void
org.apache.felix.karaf.gshell.log.VmLogAppender.setEvents(org.apache.felix.karaf.gshell.log.LruList)
at
org.apache.geronimo.blueprint.container.BeanRecipe.setProperty(BeanRecipe.java:604)
at
org.apache.geronimo.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:571)
at
org.apache.geronimo.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:552)
at
org.apache.geronimo.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:501)
at
org.apache.geronimo.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:62)
at
org.apache.geronimo.blueprint.di.RefRecipe.internalCreate(RefRecipe.java:60)
at
org.apache.geronimo.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:62)
...
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4727) Setting a parameterized pojo in blueprint throws exception
[
https://issues.apache.org/jira/browse/GERONIMO-4727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen updated GERONIMO-4727:
--
Attachment: GERONIMO-4727.diff
Setting a parameterized pojo in blueprint throws exception
--
Key: GERONIMO-4727
URL: https://issues.apache.org/jira/browse/GERONIMO-4727
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Reporter: Gert Vanthienen
Attachments: GERONIMO-4727.diff, GERONIMO-4727.diff
When the setter of property uses a parameterized type (e.g.
*{{setLruList(LruListPaxLoggingEvent events)}}*) and the bean being
injected is the raw type (e.g. *{{new LruList()}}*, we get: this exception:
{noformat}
org.osgi.service.blueprint.container.ComponentDefinitionException:
Unable to convert property value from
org.apache.felix.karaf.gshell.log.LruList to
org.apache.felix.karaf.gshell.log.LruListorg.ops4j.pax.logging.spi.PaxLoggingEvent
for injection
public void
org.apache.felix.karaf.gshell.log.VmLogAppender.setEvents(org.apache.felix.karaf.gshell.log.LruList)
at
org.apache.geronimo.blueprint.container.BeanRecipe.setProperty(BeanRecipe.java:604)
at
org.apache.geronimo.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:571)
at
org.apache.geronimo.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:552)
at
org.apache.geronimo.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:501)
at
org.apache.geronimo.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:62)
at
org.apache.geronimo.blueprint.di.RefRecipe.internalCreate(RefRecipe.java:60)
at
org.apache.geronimo.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:62)
...
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: Daytrader for Tomcat
Hi Forrest, Are you planning to do anything more with the Daytrader? There was some discussion in http://issues.apache.org/jira/browse/DAYTRADER-68 about next steps with this web-only version of daytrader ... but that was a while ago and I'm not sure if you are still working on these items or if they were displaced by other more pressing issues. Included in jira discussion you mentioned that you would be working on several things, among those: - a description of how the web-only version differs from the full Daytrader including changes made for removal of EJB/JPA dependencies. - support for jetty in addition to tomcat for the web-only version - better instructions in readme for installation on both the minimal assemblies and tomcat/jetty containers - investigation into non-container managed JPA for db access - possible creation of plugins for the webonly installation - and perhaps some work on the dependencies and datasource deployment plan. Can you fill us in on the latest on these items? Thanks, Joe Joe Bohn wrote: Are you getting any closer Forrest? As Kevan mentioned, it might be helpful to get this contributed so that others can collaborate. Thanks, Joe Kevan Miller wrote: On Apr 9, 2009, at 11:26 AM, Forrest Xia wrote: Hi Joe, We recently found some problems in some primitive servlets, so the tomcat version is not really ready for contribution. As to how to package it into daytrader code base, rough idea is to create a sub module in daytrader root, and use maven-war-plugin to create a war ball for tomcat deployment. |-- It would be cool if we could figure out a way (using plugins?) to install the core Daytrader (simplified) and extend it with the full function |-- by another plugin for more robust environments. I will try to see if it is possible, thank you for your suggestion :) Hi Forrest, Things don't have to be perfect before you can start collaborating with community members. Understand the desire to get everything just so. But you might find that other people are willing to help and answer questions. --kevan
[jira] Updated: (GERONIMO-4642) WS-Security support for JAX-WS Web Services
[
https://issues.apache.org/jira/browse/GERONIMO-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rahul Mehta updated GERONIMO-4642:
--
Attachment: usernameToken.patch
Hello Devs,
This patch provides the UsernameToken security to the web service client (for
CXF).
Now user just needs to specify the username token properties in the
geronimo-web.xml to access the secure web service, as following:
usertoken
usernameusername/username
passwordpassword/password
/usertoken
Below is the example of SOAP header (traced by the tcpmonitor), with the
UsernameToken property set:
REQUEST:
soap:Envelope
xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;soap:Headerwsse:Security
xmlns:wsse=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd;
soap:mustUnderstand=1wsse:UsernameToken
xmlns:wsse=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd;
xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
wsu:Id=UsernameToken-739746wsse:Username
xmlns:wsse=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd;username/wsse:Usernamewsse:Password
xmlns:wsse=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd;
Type=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText;password/wsse:Password/wsse:UsernameToken/wsse:Security/soap:Headersoap:Bodyns2:sayHi
xmlns:ns2=http://service.web/;arg0Rahul/arg0/ns2:sayHi/soap:Body/soap:Envelope
RESPONSE:
-
soap:Envelope
xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;soap:Bodyns2:sayHiResponse
xmlns:ns2=http://service.web/;returnHello
Rahul/return/ns2:sayHiResponse/soap:Body/soap:Envelope
Now, I am working on setting the username token security for the server side
and X.509 certificate.
Many Thanks to Jarek for his constant help and all devs for the prompt reply.
Rahul
WS-Security support for JAX-WS Web Services
-
Key: GERONIMO-4642
URL: https://issues.apache.org/jira/browse/GERONIMO-4642
Project: Geronimo
Issue Type: New Feature
Security Level: public(Regular issues)
Components: webservices
Environment: Apache Geronimo, Apache CXF, Apache Axis2, Ws-Security,
Web Services, Java, Linux
Reporter: Rahul Mehta
Priority: Minor
Attachments: site.patch, usernameToken.patch
Original Estimate: 2016h
Remaining Estimate: 2016h
To integrate and enable the WS-Security features of Apache Axis2 and Apache
CXF in Apache Geronimo:
--
Apache Geronimo supports two JAX-WS providers: Axis2 and CXF and both of
these libraries have some WS-Security features. But these features are not
integrated/enabled in Geronimo. So the goal is to enable these features from
within Geronimo. That involves basically two things:
1) that the modules (i.e. WSS4J) that provide the WS-Security features for
Axis2 and CXF are installed with Geronimo, and
2) that the WS-Security features such as [XML Security ('XML Signature' -
allows one to send along with the message a digital signature of it, which
assures that no one modified the message content between the sender and
receiver, 'XML Encryption' -allows one to encrypt the message body or only
its part using the given cryptography algorithm) and Tokens ('Username
Tokens' - WS-Security scenario adds username and password values to the
message header, 'Timestamps' - Timestamps specify how long the security data
remains valid, 'SAML Tokens')] can be enabled and configured on web services
via Geronimo deployment descriptors and/or annotations. For example, given
some web service that is annotated with @WebService; so to ensure that the
service only accepts WS-Security -secured messages, it should be something
like to add @WS-Security annotation.
Further in detail, we can consider WS-Security policies which can be applied
to the SOAP messages that pass between web services and web service controls.
A WS-Security is controlled in WS-Security policy files. The WS-Security
policy file (WSSE file) defines the security policy applied to the SOAP
messages that pass between web services and their clients.[1]
So we can use something like following annotation @WS-Security
file=MyWebServicePolicy.wsse Example: @WebService @WS-Security
file=MyWebServicePolicy.wsse
public class xyz
The @WS-Security annotation determines the WS-Security policy file (WSSE) to
be applied to (1) incoming SOAP invocations of the web service's methods and
(2) the outgoing SOAP messages containing the value
Re: Problem when deploy CXF WebService (Service resource injection failed)
Jarek,
Finally, it works. I've followed the second way.
I have to do this:
· Remove the spring listener from web.xml
· Keep the spring contextConfigLocation in web.xml
· Keep CXF Servlet but calling my interface insted of
'org.apache.cxf.transport.servlet.CXFServlet'.
Thanks a lot for your patience Jarek. You are my savior!
And about this tutorial:
http://cwiki.apache.org/CXF20DOC/writing-a-service-with-spring.html
Is out of date. It follows the first way and neither speak nothing about
filters in geronimo-web.xml nor
'-Dorg.apache.geronimo.jaxws.builder.useSimpleFinder=true' system property.
Where can I post my eclipse project with the working example?
See u!
Westhveg
Jarek Gawor-2 wrote:
Westhveg,
Let's back up a little. You have two options for deploying your web
service:
1) Deploy your web application WITH all cxf and spring jars but you
MUST: a) start the server with
-Dorg.apache.geronimo.jaxws.builder.useSimpleFinder=true AND b)
specify a bunch of filters in geronimo-web.xml.
or
2) Deploy your web application WITHOUT any cxf AND spring jars and
without CXFServlet in the web.xml. In this case your web application
should only contain the web service class and any other jars/classes
that the web service needs. The war file should be much smaller. Don't
set org.apache.geronimo.jaxws.builder.useSimpleFinder property or any
filters in geronimo-web.xml.
With option 2) you are relying on the app server to deploy your web
service. The app server will use its own web service engine to deploy
and manage your web service. That's why you don't need all these
spring or cxf jars or the cxf servlet or cxf configuration files. With
option 1) you are not relying on the app server to deploy and manage
your web service. The web application you are deploying has it own web
services engine which will deploy and manage the web service. And to
prevent conflicts between the web app web service engine and the app
server web service engine you need to set those filters and that
property.
Jarek
On Mon, Jul 6, 2009 at 5:13 AM, Westhvegwesthstud...@gmail.com wrote:
Can anyone help me, please?
Thanks,
Westhveg
Westhveg wrote:
And if I try to test the webservice developing this spring client:
?xml version=1.0 encoding=UTF-8?
beans xmlns=http://www.springframework.org/schema/beans;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:jaxws=http://cxf.apache.org/jaxws;
xsi:schemaLocation=http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
http://cxf.apache.org/jaxws
http://cxf.apache.org/schemas/jaxws.xsd;
!--
If I uncomment this, I get the same exception. But if I leave it
commented, I must import FastInfoset.jar library.
import resource=classpath:META-INF/cxf/cxf.xml /
import resource=classpath:META-INF/cxf/cxf-extension-soap.xml /
import resource=classpath:META-INF/cxf/cxf-servlet.xml /
--
jaxws:client id=helloWordClient
serviceClass=com.test.HelloWorld
address=http://localhost:8080/helloWorld; /
/beans
30-jun-2009 23:52:33 org.apache.cxf.bus.spring.BusApplicationContext
getConfigResources
INFO: No cxf.xml configuration file detected, relying on defaults.
30-jun-2009 23:52:34
org.apache.cxf.service.factory.ReflectionServiceFactoryBean
buildServiceFromClass
INFO: Creating Service {http://test.com/}HelloWorldService from class
com.test.HelloWorld
30-jun-2009 23:52:34 org.apache.cxf.phase.PhaseInterceptorChain
doIntercept
INFO: Interceptor has thrown exception, unwinding now
org.apache.cxf.interceptor.Fault: Could not send Message.
at
org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:64)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:236)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:471)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:301)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:253)
at
org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
at
org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:121)
at $Proxy44.postMessage(Unknown Source)
at com.test.TestWsClient.main(TestWsClient.java:15)
Caused by: java.io.IOException: Not Found
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2064)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:2015)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1940)
at
org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66)
at
[jira] Resolved: (GERONIMO-4727) Setting a parameterized pojo in blueprint throws exception
[
https://issues.apache.org/jira/browse/GERONIMO-4727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved GERONIMO-4727.
---
Resolution: Fixed
Such constructions have been explicitely forbidden.
The reason is that there is no way to make sure if the objects in the list are
actually compatible with what the generic information provides.
The only way to get around such a problem is to register a custom converter to
convert to the generic type.
Setting a parameterized pojo in blueprint throws exception
--
Key: GERONIMO-4727
URL: https://issues.apache.org/jira/browse/GERONIMO-4727
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Reporter: Gert Vanthienen
Attachments: GERONIMO-4727.diff, GERONIMO-4727.diff
When the setter of property uses a parameterized type (e.g.
*{{setLruList(LruListPaxLoggingEvent events)}}*) and the bean being
injected is the raw type (e.g. *{{new LruList()}}*, we get: this exception:
{noformat}
org.osgi.service.blueprint.container.ComponentDefinitionException:
Unable to convert property value from
org.apache.felix.karaf.gshell.log.LruList to
org.apache.felix.karaf.gshell.log.LruListorg.ops4j.pax.logging.spi.PaxLoggingEvent
for injection
public void
org.apache.felix.karaf.gshell.log.VmLogAppender.setEvents(org.apache.felix.karaf.gshell.log.LruList)
at
org.apache.geronimo.blueprint.container.BeanRecipe.setProperty(BeanRecipe.java:604)
at
org.apache.geronimo.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:571)
at
org.apache.geronimo.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:552)
at
org.apache.geronimo.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:501)
at
org.apache.geronimo.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:62)
at
org.apache.geronimo.blueprint.di.RefRecipe.internalCreate(RefRecipe.java:60)
at
org.apache.geronimo.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:62)
...
{noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[BUILD] trunk: Failed for Revision: 791555
Geronimo Revision: 791555 built with tests included
See the full build-1500.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090706/build-1500.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090706
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 42 minutes 46 seconds
[INFO] Finished at: Mon Jul 06 15:47:19 EDT 2009
[INFO] Final Memory: 403M/1015M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090706/logs-1500-tomcat/
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:45.894
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/testing/testsuite-testing.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS (0:01:17.454)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:35.679)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:40.476)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:20.980)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:32.663)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced FAILURE (0:03:48.288) Java
returned: 1
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:01.456)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:54.075)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:01:03.868)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:47.597)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:33.511)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:35.034)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:36.267)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:01:10.244)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:02.229)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:58.583)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:29.948)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:55.338)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security SUCCESS (0:00:50.847)
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:32.465)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:30.909)
[INFO] web-testsuite/test-myfaces RUNNING
[INFO] web
[BUILD] trunk: Failed for Revision: 791656
Geronimo Revision: 791656 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090706/build-2100.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090706
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 39 minutes 35 seconds
[INFO] Finished at: Mon Jul 06 21:43:48 EDT 2009
[INFO] Final Memory: 475M/750M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090706/logs-2100-tomcat/
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:44.006
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/testing/testsuite-testing.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS (0:01:05.216)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:32.829)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:38.601)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:20.394)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:29.808)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced FAILURE (0:03:42.518) Java
returned: 1
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:57.788)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:52.623)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:01:15.363)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:46.379)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:33.145)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:36.184)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:37.148)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:01:11.129)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:01.015)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:51.206)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:29.851)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:53.040)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security SUCCESS (0:00:52.416)
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:34.003)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:32.610)
[INFO] web-testsuite/test-myfaces RUNNING
[INFO] web
Setup a Geonimo FAQ ?
Obviously, there are really some FAQ in the mailing list such as 1, Lib conflict including myface, spring 2, Log4j 3, JPA JTA/Non-JTA DS requirement. 4, web-service out of memory 5, Classloading problem caused by bad EAR package structure. .. We need a formal page to record these FAQ. (only found two related page [1] and [2] with google). [1] http://docs.huihoo.com/apache/geronimo/1.1/geronimo-eclipse-plugin-faq.html [2]http://cwiki.apache.org/GMOxKB/index.html -- Shawn
Re: Setup a Geonimo FAQ ?
The Knowledge Base was intended to be the home for FAQ-ish thingys. --jason On Jul 7, 2009, at 12:04 PM, Shawn Jiang wrote: Obviously, there are really some FAQ in the mailing list such as 1, Lib conflict including myface, spring 2, Log4j 3, JPA JTA/Non-JTA DS requirement. 4, web-service out of memory 5, Classloading problem caused by bad EAR package structure. .. We need a formal page to record these FAQ. (only found two related page [1] and [2] with google). [1]http://docs.huihoo.com/apache/geronimo/1.1/geronimo-eclipse-plugin-faq.html [2]http://cwiki.apache.org/GMOxKB/index.html -- Shawn
Re: Setup a Geonimo FAQ ?
OK, I also noticed that Knowledge Base page can be found as FAQ in geronimo homepage. FAQ http://cwiki.apache.org/confluence/pages/listpages.action?key=GMOxKB Browse Spacehttp://cwiki.apache.org/confluence/spaces/browsespace.action?key=GMOxKB http://cwiki.apache.org/confluence/pages/createpage.action?spaceKey=GMOxKBfromPageId=7513 Add Pagehttp://cwiki.apache.org/confluence/pages/createpage.action?spaceKey=GMOxKBfromPageId=7513 - *V*iew http://cwiki.apache.org/confluence/display/GMOxKB/FAQ - *E*dithttp://cwiki.apache.org/confluence/pages/editpage.action?pageId=7513 - *A*ttachments (0)http://cwiki.apache.org/confluence/pages/viewpageattachments.action?pageId=7513 - *I*nfohttp://cwiki.apache.org/confluence/pages/pageinfo.action?pageId=7513 Added by Jason Dillonhttp://cwiki.apache.org/confluence/display/%7Ejdillon, last edited by Jason Dillonhttp://cwiki.apache.org/confluence/display/%7Ejdillonon Jun 22, 2006 (view changehttp://cwiki.apache.org/confluence/pages/diffpages.action?pageId=7513originalId=7552) Labels: (None) EDIT http://cwiki.apache.org/confluence/display/GMOxKB/FAQ --- Seems it has not been updated from 2006. We need to 1, Remove some stale content. 2, Add some new FAQ there. Hope that can reduce FAQ questions in mailing list. On Tue, Jul 7, 2009 at 1:08 PM, Jason Dillon ja...@planet57.com wrote: The Knowledge Base was intended to be the home for FAQ-ish thingys. --jason On Jul 7, 2009, at 12:04 PM, Shawn Jiang wrote: Obviously, there are really some FAQ in the mailing list such as 1, Lib conflict including myface, spring 2, Log4j 3, JPA JTA/Non-JTA DS requirement. 4, web-service out of memory 5, Classloading problem caused by bad EAR package structure. .. We need a formal page to record these FAQ. (only found two related page [1] and [2] with google). [1] http://docs.huihoo.com/apache/geronimo/1.1/geronimo-eclipse-plugin-faq.html [2]http://cwiki.apache.org/GMOxKB/index.html -- Shawn -- Shawn
