Collect the usage of org.apache.geronimo.jaxws.builder.useSimpleFinder as
followed into (1):
org.apache.geronimo.jaxws.builder.useSimpleFinder
Applied commands: TODO
Option: true, false
Default: not set
Description: Use SimpleWARWebServiceFinder to locate WebServiceInfo
objects,otherwise use Advan
[
https://issues.apache.org/jira/browse/GERONIMO-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rex Wang updated GERONIMO-4216:
---
Attachment: GERONIMO-4216-b21-updated.patch
Use the updated patch to eliminate using the switchCas
[
https://issues.apache.org/jira/browse/GERONIMO-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rex Wang updated GERONIMO-4216:
---
Attachment: (was: GERONIMO-4216-b21.patch)
> Examine setters methods in connector builder
> --
Hi Rahul.soa,
Could you let me know how you bypass the error, your tips might be
contributed to our doc.
Thanks in advance.
Jeff C
On Sat, Jun 27, 2009 at 1:15 AM, rahul.soa wrote:
> Hello all,
>
> You can ignore this email as I built a new server.
>
> Thanks.
>
> Best Regards,
> Rahul
>
>
>
Hello Jeff,
I did *build new trunk* as I had an old one and was getting a few different
errors too. Thus, did nothing to bypass that particular error.
Thanks.
Rahul
On Tue, Jun 30, 2009 at 9:48 AM, chi runhua wrote:
> Hi Rahul.soa,
>
> Could you let me know how you bypass the error, your tips
Got it. thanks for your prompt reply.
Jeff
On Tue, Jun 30, 2009 at 4:00 PM, rahul.soa wrote:
> Hello Jeff,
>
> I did *build new trunk* as I had an old one and was getting a few different
> errors too. Thus, did nothing to bypass that particular error.
>
> Thanks.
> Rahul
>
> On Tue, Jun 30, 200
Hi David,
One question here. As I remember, Geronimo has 2 thread pools: "*
ConnectorThreadPool* is used in J2EE Connector Architecture (JCA), and *
DefaultThreadPool* is used by Jetty and System database. " Both of them have
no connection with Tomcat Web connector prior to this change.
What the
Geronimo Revision: 789569 built with tests included
See the full build-0300.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090630/build-0300.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090630
[INFO] BUILD
Hello RunHua Chi,
I'm using windows so I edit geronimo.bat (that is executed by eclipse
plugin) by this way:
set GERONIMO_OPTS=%GERONIMO_OPTS% %JPDA_OPTS%
to
set GERONIMO_OPTS=-Dorg.apache.geronimo.jaxws.builder.useSimpleFinder=true
Thanks,
Westhveg
RunHua Chi wrote:
>
> Collect the usag
[
https://issues.apache.org/jira/browse/GERONIMO-4689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks closed GERONIMO-4689.
--
Resolution: Fixed
After rev 785478 (implementation improvements) and 789622 (moving stuff ar
[
https://issues.apache.org/jira/browse/GERONIMO-4645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks closed GERONIMO-4645.
--
Resolution: Fixed
Reimplemented the web services security stuff in rev 789622.
Generally th
I've worked on GERONIMO-4645, however I'm getting strange results from
running the testsuite. When I look at build.log for a test bit I
don't see errors but the console output claims a lot of bits failed.
So hopefully your automated tests won't have this problem and we can
see how successf
[
https://issues.apache.org/jira/browse/GERONIMO-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rex Wang updated GERONIMO-4216:
---
Attachment: GERONIMO-4216-b21-updated.patch
> Examine setters methods in connector builder
> -
[
https://issues.apache.org/jira/browse/GERONIMO-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rex Wang updated GERONIMO-4216:
---
Attachment: (was: GERONIMO-4216-b21-updated.patch)
> Examine setters methods in connector buil
I was investigating a problem and happened to notice that our XSS/XSRF
filters are triggering the creation of Session objects. I then noticed
that they are creating a session when I hit an arbitrary url (I'm
expecting a 404). This is plain wrong, IMO. This was on 2.1.4, but I
would assume t
In order to give us more information, I'm following this tutorial:
http://cwiki.apache.org/CXF20DOC/writing-a-service-with-spring.html
But I don't use the same version for all libraries (I use the highest I
found):
commons-logging-1.1.jar
ยท geronimo-activation_1.1_spec-1.0-M1.jar -->
geronimo-
To catch XSS/XSRF attacks, the code is run as the first item in the
filter chain before the web app's servlet is ever reached. The session
has to be created before the request gets to the webapp, so we can
register the session id and a unique value before a response is created
to protect again
Geronimo Revision: 789483 built with tests included
See the full build-2000.log file at
http://people.apache.org/builds/geronimo/server/binaries/2.0/20090630/build-2000.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/2.0/20090630/unit-test-reports
I tried some random URIs and always received a 404 back in my tests.
This could be a problem with the filter on the welcome application. It
currently has a context-root of "/" and the filter is registered with a
URL pattern of "/*".
Joe
Donald Woods wrote:
To catch XSS/XSRF attacks, the c
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods resolved GERONIMODEVTOOLS-581.
---
Resolution: Fixed
Fix Version/s: 2.1.5
Patch for missing NLS
David,
Some errors on the console (or in the logs) are to be expected. The
tests check if for example the service that requires security can be
accessed without security. That should generate some errors and that's
what the test expects.
As to securing ?wsdl access, a while ago I added a feature
On Jun 30, 2009, at 10:09 AM, Donald Woods wrote:
To catch XSS/XSRF attacks, the code is run as the first item in the
filter chain before the web app's servlet is ever reached. The
session has to be created before the request gets to the webapp, so
we can register the session id and a uni
Geronimo Revision: 789690 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090630/build-0900.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090630
[INFO] BUILD
On Jun 30, 2009, at 10:26 AM, Joe Bohn wrote:
I tried some random URIs and always received a 404 back in my tests.
This could be a problem with the filter on the welcome application.
It currently has a context-root of "/" and the filter is registered
with a URL pattern of "/*".
OK, that
[
https://issues.apache.org/jira/browse/GERONIMO-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rex Wang updated GERONIMO-4628:
---
Attachment: GERONIMO-4628-b21-updated.patch
Thanks very much, David! That is a good way to solve t
[
https://issues.apache.org/jira/browse/GERONIMO-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725666#action_12725666
]
Rex Wang commented on GERONIMO-4628:
and I will make a trunk patch later if this pat
Thanks for going to test this Jarek.
It sounds like I would need to being this up with JCP-224 then.
--Kurt
Jarek Gawor wrote:
Kurt,
I'm pretty sure that's what the spec mandates. I can test this out to
see if it breaks the TCK signature tests but even if it doesn't you
might still run into t
Kurt,
The signature tests fail with this change so we can't add
Serializable to the Holder class.
Jarek
On Tue, Jun 30, 2009 at 12:00 AM, Jarek Gawor wrote:
> Kurt,
>
> I'm pretty sure that's what the spec mandates. I can test this out to
> see if it breaks the TCK signature tests but even i
Thanks Jarek,
I'll take it up the JCP.
--Kurt
Jarek Gawor wrote:
Kurt,
The signature tests fail with this change so we can't add
Serializable to the Holder class.
Jarek
On Tue, Jun 30, 2009 at 12:00 AM, Jarek Gawor wrote:
Kurt,
I'm pretty sure that's what the spec mandates. I can t
On Tue June 30 2009 11:38:35 am Kurt T Stam wrote:
> Thanks for going to test this Jarek.
>
> It sounds like I would need to being this up with JCP-224 then.
I'm pretty sure you won't like the answer. :-)
Basically, the jcp224/jaxws folks (and the jaxb folks), at one point long ago,
specifical
Kevan Miller wrote:
On Jun 30, 2009, at 10:26 AM, Joe Bohn wrote:
I tried some random URIs and always received a 404 back in my tests.
This could be a problem with the filter on the welcome application.
It currently has a context-root of "/" and the filter is registered
with a URL pattern
Thx for the backgroud info Dan :(
Isn't it great, the also decided to make the class 'final'? So I can't
even make a wrapper.
I've send a request to jsr-224-pub...@jcp.org. Hoping for the best..
--Kurt
Daniel Kulp wrote:
On Tue June 30 2009 11:38:35 am Kurt T Stam wrote:
Thanks for goi
IMO, I don't think the welcome page need this filter. The filter only deal
with the links that have the request parameters and the form request, but in
the welcome page, there is no such links, so the filter won't take any
effects.
The reason why add the filtering to welcome project, as the G-4597
Probably can be removed, since we no longer allow users to install
Sample plugins from the welcome page.
As long as the Login page and everything behind it is protected, we
should be okay.
-Donald
Joe Bohn wrote:
Kevan Miller wrote:
On Jun 30, 2009, at 10:26 AM, Joe Bohn wrote:
I trie
Thanks for the input Donald and Rex. So it sounds like we all agree that
we should remove the filter from welcome.
Kevan,
Did you want to remove this or would you like me to make the change?
Did you already create a JIRA for this?
Thanks,
Joe
Donald Woods wrote:
Probably can be removed, sin
You might also want to add:
META-INF/cxf
I don't know where org.xmlsoap.schemas.wsdl.http.AddressType comes
from but you could try adding a filter for its package as well.
Jarek
On Mon, Jun 29, 2009 at 3:08 PM, Westhveg wrote:
>
> Jarek,
>
> Thanks for your reply. Setting the system property an
XSS/XSRF filters are triggering Session object creation for unknown URLs
Key: GERONIMO-4722
URL: https://issues.apache.org/jira/browse/GERONIMO-4722
Project: Geronimo
I
You have to remove both, CXF and Spring. And please include a full
stack trace to see what's loading that
org.springframework.context.ApplicationListener class.
Jarek
On Mon, Jun 29, 2009 at 3:56 PM, Westhveg wrote:
>
> And if I remove the spring or cfx jar files from WAR, I get a
> ClassNotFound
On Jun 30, 2009, at 1:06 PM, Joe Bohn wrote:
Thanks for the input Donald and Rex. So it sounds like we all agree
that we should remove the filter from welcome.
Kevan,
Did you want to remove this or would you like me to make the change?
Did you already create a JIRA for this?
Just created
[
https://issues.apache.org/jira/browse/GERONIMO-4722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725723#action_12725723
]
Joe Bohn commented on GERONIMO-4722:
It appears that we were too aggressive in the a
[
https://issues.apache.org/jira/browse/GERONIMO-4722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bohn reassigned GERONIMO-4722:
--
Assignee: Joe Bohn
> XSS/XSRF filters are triggering Session object creation for unknown URL
Hi Jarek,
Removing both jars, the exception is:
Distribution of module failed. See log for details.
Failed to load servlet class org.apache.cxf.transport.servlet.CXFServlet
org.apache.geronimo.common.DeploymentException: Failed to load servlet
class org.apache.cxf.transport.servlet.CXFServl
Jarek,
Adding this filter:
META-INF/cxf
I get the same exception, but if I add a filter for package:
org.xmlsoap.schemas.wsdl.http
Then I get the following exception:
Redeploy of module failed. See log for details.
start of default/ViewControllerWS/1.0/car failed
org.apache.geronimo.k
Ok, making progress on this front... Remove the CXFServlet from
web.xml file and add a servlet (and servlet-mapping) for the class
that is your web service implementation.
Jarek
On Tue, Jun 30, 2009 at 2:18 PM, Westhveg wrote:
>
> Hi Jarek,
>
> Removing both jars, the exception is:
>
> Distributi
Are you sure you're running with
-Dorg.apache.geronimo.jaxws.builder.useSimpleFinder=true? Because
Geronimo should not be finding and deploying
org.apache.cxf.js.rhino.DOMMessageProvider with that option. Or maybe
that's from previous deployments?
Jarek
On Tue, Jun 30, 2009 at 2:26 PM, Westhveg w
[
https://issues.apache.org/jira/browse/GERONIMO-4722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bohn resolved GERONIMO-4722.
Resolution: Fixed
I've committed changes in branches/2.1 (rev. 789881) and trunk (rev. 789885).
On Jun 30, 2009, at 7:35 AM, Jarek Gawor wrote:
David,
Some errors on the console (or in the logs) are to be expected. The
tests check if for example the service that requires security can be
accessed without security. That should generate some errors and that's
what the test expects.
As us
[
https://issues.apache.org/jira/browse/GERONIMO-4645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor reopened GERONIMO-4645:
---
David,
This is still not working right. Please run
testsuite/webservices-testsuite/jaxws-tes
Geronimo Revision: 789862 built with tests included
See the full build-1500.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090630/build-1500.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090630
[INFO] BUILD
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 c
And if I try to test the webservice developing this spring client:
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
Geronimo Revision: 790005 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090630/build-2100.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090630
[INFO] BUILD
If Dojo is only used to display a nice box in this case, I think we
should just get rid off it and use the regular dialog boxes.
Jarek
On Tue, Jun 30, 2009 at 2:12 AM, Ivan wrote:
> I checked the codes of ConfirmMessageTag, its main purpose is to import Dojo
> js file and some styles for showing
Yes, the regular dialog boxes are also OK. I remembered that I had discussed
it with the patch contributor Jeff, our final result is that since more and
more portlets are using Dojo, why not use it :-)
I also wish the console would use Dojo to do some validation stuff in the
future.
Ivan
2009/7/1
54 matches
Mail list logo
