Please file a ticket with the JSON that didn't work, and I'll take a look at
it.
John
On 3/15/11 3:15 PM, "fr...@meruvian.org" wrote:
> We just solved the extentension problem, we can replace json.jar using jackson
> now
>
> Jackson have jsonfactory, may be interest all of u
>
> Will blog ab
We just solved the extentension problem, we can replace json.jar using jackson
now
Jackson have jsonfactory, may be interest all of u
Will blog about this soon
John,
We got that using the default json, the output gone like blank, the json is not
big, we try geneology tree json model,
/m/
Another thing to keep in mind here... The way the conventions plugin
works is that it hooks in UnknownHandlers. If conventions is to become
the new default, I think a classpath-scanning ConfigurationProvider
should be created (IMHO).
-Wes
On Tue, Mar 15, 2011 at 4:26 PM, Philip Luppens
wrote:
>
On Tue, Mar 15, 2011 at 9:13 PM, Ben McCann wrote:
> I didn't realize you could setup Struts2 without XML. That sounds fantastic
> to me. I'd vote in favor of moving it to the core or at least highlighting
> it in the documentation. Having to do configuration in XML is the one thing
> I dislike
I didn't realize you could setup Struts2 without XML. That sounds fantastic
to me. I'd vote in favor of moving it to the core or at least highlighting
it in the documentation. Having to do configuration in XML is the one thing
I dislike about Struts2 despite being a longtime and happy user of th
On Tue, Mar 15, 2011 at 3:48 PM, Matt Raible wrote:
> If the conventions plugin allows for no XML and extensionless URLs, I'd like
> to see it rolled into the and defaulted. I'm happy to endure the pain of
> upgrading for those two features.
>
Or you could use the plugin...
The way I see it, the
If the conventions plugin allows for no XML and extensionless URLs, I'd like
to see it rolled into the and defaulted. I'm happy to endure the pain of
upgrading for those two features.
On Tue, Mar 15, 2011 at 1:43 PM, Wes Wannemacher wrote:
> I'm with Dave and Chris... I like the conventions plug
I'm with Dave and Chris... I like the conventions plugin, but I think
it is too big of a change to make it a new default.
It could potentially be the kind of thing that we look at for Struts 3
-Wes
On Tue, Mar 15, 2011 at 3:36 PM, Chris Pratt wrote:
> I'm with Dave on this one (obviously)
> (*
I'm with Dave on this one (obviously)
(*Chris*)
On Tue, Mar 15, 2011 at 12:19 PM, Dave Newton wrote:
> I'm still against having it be the default, though. If it's enabled
> with a single switch, I'd be okay with that.
>
> Dave
>
> On Tue, Mar 15, 2011 at 3:08 PM, Johannes Geppert
> wrote:
> >
I'm still against having it be the default, though. If it's enabled
with a single switch, I'd be okay with that.
Dave
On Tue, Mar 15, 2011 at 3:08 PM, Johannes Geppert wrote:
> My intention is not to replace the XML Configuration. Both configurations
> ways work well together.
>
> I only like to
My intention is not to replace the XML Configuration. Both configurations
ways work well together.
I only like to see the convention configuration as default. Because with
Convention
Plugin it is much more easier for the user to get involved with Struts2.
And this Feature is not so well known by
How big is the JSON data that you are parsing?
I have heard good reports about Jackson's performance, but we will need to
investigate whether it can support all the hooks provided by the current
implementation.
John
On 3/15/11 4:24 AM, "Frans Thamura" wrote:
> we find here to implement JSON u
+1
I've actually extended the DTD with additional configuration for security
features. The XML is easier to review for errors and ommissions because it
is centralized.
John
On 3/15/11 9:25 AM, "Steven Benitez" wrote:
> I love annotations for a lot of things, but I also prefer the XML based
>
I love annotations for a lot of things, but I also prefer the XML based
configuration for actions, interceptors, results, etc.
On Tue, Mar 15, 2011 at 12:16 PM, Dave Newton wrote:
> There's a tension between large-scale maintainability and small-scale
> "hurry!" apps.
>
> I think it's important
There's a tension between large-scale maintainability and small-scale
"hurry!" apps.
I think it's important that S2 can do both, and our documentation
should reflect its suitability for each style, and provide insight
and/or mechanisms into transitioning between the two (struts.xml from
annotation
-1. I find programming by religion (or convention or whatever you want to
call it when the computer tries to guess what you mean) to be a very bad
long term decision. For small programs it works out fine, but for anything
with any scale you start to run into unimagined problems because someone
na
And it's easier to create documentation automatically. (Not way
easier, but still.)
I guess I'd be opposed to making Convention be "enabled" by default,
but we could certainly make an effort to highlight in a more effective
way.
Dave
On Tue, Mar 15, 2011 at 9:30 AM, Ian Roughley wrote:
> In dev
In development mode, using XML, you can also make real-time production
configuration changes without
needing to restart :-)
/Ian
On 03/15/2011 07:27 AM, Frans Thamura wrote:
> we find also using old xml is easier thatn @Action/@Result
>
> what happen if we wanna to change the result from velocit
we find also using old xml is easier thatn @Action/@Result
what happen if we wanna to change the result from velocity to jsp, to jasper
the new one cannot
F
On Tue, Mar 15, 2011 at 6:25 PM, Maurizio Cucchiara <
maurizio.cucchi...@gmail.com> wrote:
> Johannes,
> I don't know, I'd prefer to keep
Johannes,
I don't know, I'd prefer to keep the core the more slight as possible
(but my opinion could be biased cause I am an old fashion XML coder :)
)
On 15 March 2011 11:03, Johannes Geppert wrote:
> Only a thought, what are you thinking about moving the convention plugin into
> core?
>
> Man
we find here to implement JSON using current json jar is not scalable
enough, jackson can parse bigger json
that why we extend the json plugin using jackson jar here
www.github.com/blueoxygen/cimande -> jackson
but we find we cannot replace the current json.jar, with jackson.
so we must use the
When you talk about jackson parser you mean serialize, deserialize, both?
On 15 March 2011 11:47, wrote:
> +1
> Can we use another json parser like jackson
>
>
> --Original Message--
> From: Johannes Geppert
> To: dev@struts.apache.org
> ReplyTo: Struts Developers List
> Subject: Re: Roa
+1
Can we use another json parser like jackson
--Original Message--
From: Johannes Geppert
To: dev@struts.apache.org
ReplyTo: Struts Developers List
Subject: Re: Roadmap for 2.3
Sent: Mar 15, 2011 5:03 PM
Only a thought, what are you thinking about moving the convention plugin into
core?
Only a thought, what are you thinking about moving the convention plugin into
core?
Many People don't know the convention plugin and offen i hear that Struts2
is
an old fashion XML configuration MVC Framework.
Johannes
--
View this message in context:
http://struts.1045723.n5.nabble.com/Road
24 matches
Mail list logo
