I think it would be save to say that you might have to use xml mapping
for those actions. When adding the "advanced wildards" I found some
problem in convention, which are now fixed in trunk. If you are
comfortable building struts, you might five it a try.
musahcy
On Wed, Sep 30, 2009 at 6:38 AM,
Is a possible reason that it may not be working that I am also using the
convention plugin??
struts-restful wrote:
>
> I also tried this with a / in the namespace so
>
> @Namespace("test/{id}"} and
> @Namespace("/test/{id}"} give a namespace with "".
>
>
>
> struts-restful wrote:
>>
>> O
I also tried this with a / in the namespace so
@Namespace("test/{id}"} and
@Namespace("/test/{id}"} give a namespace with "".
struts-restful wrote:
>
> One more additional piece of information is that the namespaceMatcher does
> contain the compiled pattern for my namespace.
>
> Another t
One more additional piece of information is that the namespaceMatcher does
contain the compiled pattern for my namespace.
Another thing I noticed when messing around trying to figure this out is
that I created a different controller class ain a different package for
example test.MyTestController
Yes I am putting it in the namespace annotation
@Namespace("/person/name/test-example/{id}")
Stepping through the namespace pattern matcher code it does replace the {id}
with ([^/]+) but that is as far as i have got and still dont understand why
it does not work
Thanks in advance
Musachy B
are you putting that in the @Namespace annotation? It will not work on
the @Action annotation.
musachy
On Tue, Sep 29, 2009 at 8:49 AM, struts-restful wrote:
>
> Also I know that the default parameter is id but ideally i am trying to
> create a url as follows
>
> /person/name/{id}/{anotherId}/te
Also I know that the default parameter is id but ideally i am trying to
create a url as follows
/person/name/{id}/{anotherId}/test-example
struts-restful wrote:
>
> I amended my URL to be as follows then using the namespace pattern matcher
>
> /person/name/{id}/test-example
>
> but this no
I amended my URL to be as follows then using the namespace pattern matcher
/person/name/{id}/test-example
but this now maps the config as /person/name/{id}. How would I get rid of
the {id} bit but still pass the parameter through?
Thanks
Musachy Barroso wrote:
>
> the namespace matcher, ad
the namespace matcher, ad the name implies matches parameters only in
the namespace (the part before the action). To map params after the
action name, you have to use wildcards. Because this is confusing, we
introduced the advanced regex patters which will sove all the cases,
see this:
http://cwik
Ok after some further investigating the problem appears to be when the server
is starting up and it is building the namespaceActionConfig map.
because my namespace on the action is set to /person/name/test-example/{id}
when the action config is created the key is set to
/person/name/test-example
Thanks for the help and your reply.
i implemented the named pattern matcher but cant get it to work. I have the
following config in my struts.xml
On my action I added the namespace annotation for example
@Namespace("/person/name/test-example/{id}")
this uses the restActionMapper b
You want to look at wildcards:
http://struts.apache.org/2.x/docs/wildcard-mappings.html
That feature that Alex is refering to (coined advanced wildcards for
lack of imagination), is in trunk and has not been released yet.
musachy
On Mon, Sep 28, 2009 at 5:57 AM, Alex Siman wrote:
>
> Look here
Look here:
http://www.nabble.com/parameters-in-url-td25602877.html
Restful plugin is not so good as it supposed to be.
struts-restful wrote:
>
> Does anyone know how to get the restful web service to call a method
> different to show or edit.
>
> For example I have the following url
>
> http
13 matches
Mail list logo
