[jira] [Commented] (ISIS-1370) New PublisherService to simplify and replace PublishingService.
[ https://issues.apache.org/jira/browse/ISIS-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282946#comment-15282946 ] ASF subversion and git services commented on ISIS-1370: --- Commit 72705aceee671e2c13b4d132b61b4a181aa50e85 in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=72705ac ] ISIS-1370: improve syntax of comparator static methods in DomainChangeJdoAbstract > New PublisherService to simplify and replace PublishingService. > --- > > Key: ISIS-1370 > URL: https://issues.apache.org/jira/browse/ISIS-1370 > Project: Isis > Issue Type: New Feature > Components: Core >Affects Versions: 1.12.0 >Reporter: Dan Haywood >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.13.0 > > > Most PublishingService implementations (to date) only require the metadata > (action invocation or domain object identity) to publish their events; the > notion of the payload (to eagerly assemble information for the downstream > subscribers) seems less useful. > This ticket is therefore to deprecate the > PublishingService#publish(EventMetadata, EventPayload), and replace with > PublishingService2#publish(EventMetadata). > This also means that @DomainObject#publishingPayloadFactory() and > @Action#publishingPayloadFactory() attributes are deprecated. > ~~~ > In its place, will have a new PublisherService with a simplified API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-1370) New PublisherService to simplify and replace PublishingService.
[ https://issues.apache.org/jira/browse/ISIS-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282942#comment-15282942 ] ASF subversion and git services commented on ISIS-1370: --- Commit ea7c1904429e327647def9a3f5cd7d95a804c9ab in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=ea7c190 ] ISIS-1370: refining the API for PublisherService. > New PublisherService to simplify and replace PublishingService. > --- > > Key: ISIS-1370 > URL: https://issues.apache.org/jira/browse/ISIS-1370 > Project: Isis > Issue Type: New Feature > Components: Core >Affects Versions: 1.12.0 >Reporter: Dan Haywood >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.13.0 > > > Most PublishingService implementations (to date) only require the metadata > (action invocation or domain object identity) to publish their events; the > notion of the payload (to eagerly assemble information for the downstream > subscribers) seems less useful. > This ticket is therefore to deprecate the > PublishingService#publish(EventMetadata, EventPayload), and replace with > PublishingService2#publish(EventMetadata). > This also means that @DomainObject#publishingPayloadFactory() and > @Action#publishingPayloadFactory() attributes are deprecated. > ~~~ > In its place, will have a new PublisherService with a simplified API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-1370) New PublisherService to simplify and replace PublishingService.
[ https://issues.apache.org/jira/browse/ISIS-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282941#comment-15282941 ] ASF subversion and git services commented on ISIS-1370: --- Commit 2a89182879e3d472842958054e5087ba4f2bbc6b in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=2a89182 ] ISIS-1370: cleaning up the API to PublisherService, renaming EnlistedObjectsService to ChangedObjectsService etc. > New PublisherService to simplify and replace PublishingService. > --- > > Key: ISIS-1370 > URL: https://issues.apache.org/jira/browse/ISIS-1370 > Project: Isis > Issue Type: New Feature > Components: Core >Affects Versions: 1.12.0 >Reporter: Dan Haywood >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.13.0 > > > Most PublishingService implementations (to date) only require the metadata > (action invocation or domain object identity) to publish their events; the > notion of the payload (to eagerly assemble information for the downstream > subscribers) seems less useful. > This ticket is therefore to deprecate the > PublishingService#publish(EventMetadata, EventPayload), and replace with > PublishingService2#publish(EventMetadata). > This also means that @DomainObject#publishingPayloadFactory() and > @Action#publishingPayloadFactory() attributes are deprecated. > ~~~ > In its place, will have a new PublisherService with a simplified API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-1370) New PublisherService to simplify and replace PublishingService.
[ https://issues.apache.org/jira/browse/ISIS-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282945#comment-15282945 ] ASF subversion and git services commented on ISIS-1370: --- Commit cd370c597a5c1724695a54bc87a0c78cd3044bfe in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=cd370c5 ] ISIS-1370: adding a new JdoColumnLength constant for status messages (for publishmq impl to reference). > New PublisherService to simplify and replace PublishingService. > --- > > Key: ISIS-1370 > URL: https://issues.apache.org/jira/browse/ISIS-1370 > Project: Isis > Issue Type: New Feature > Components: Core >Affects Versions: 1.12.0 >Reporter: Dan Haywood >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.13.0 > > > Most PublishingService implementations (to date) only require the metadata > (action invocation or domain object identity) to publish their events; the > notion of the payload (to eagerly assemble information for the downstream > subscribers) seems less useful. > This ticket is therefore to deprecate the > PublishingService#publish(EventMetadata, EventPayload), and replace with > PublishingService2#publish(EventMetadata). > This also means that @DomainObject#publishingPayloadFactory() and > @Action#publishingPayloadFactory() attributes are deprecated. > ~~~ > In its place, will have a new PublisherService with a simplified API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-1291) Define new DTO (XSD) as the memento for Command#setMemento
[
https://issues.apache.org/jira/browse/ISIS-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282948#comment-15282948
]
ASF subversion and git services commented on ISIS-1291:
---
Commit 7ebbb70c115636f872d13bb1c367916febc961c3 in isis's branch
refs/heads/master from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=7ebbb70 ]
ISIS-1291: documentation on command and events.
Also:
- adding missing schemas in adocs documentation (for hosting on the web).
- updating bad links to @Xxx_aaa in multiple files
- deprecating some methods in applib API.
> Define new DTO (XSD) as the memento for Command#setMemento
> --
>
> Key: ISIS-1291
> URL: https://issues.apache.org/jira/browse/ISIS-1291
> Project: Isis
> Issue Type: New Feature
> Components: Core
>Affects Versions: 1.11.0
>Reporter: Dan Haywood
>Assignee: Dan Haywood
>Priority: Minor
> Labels: implemented
> Fix For: 1.13.0
>
>
> A command is NOT an action invocation, it is an INTENTION to invoke an
> action. Generally that intention is carried out immediately, hence a
> foreground command. Sometimes though it is carried out in the background, so
> is a deferred intention.
> What this implies is that a command should not contain details of the
> action's results. (If that information is available from reified
> ActionDomainEvents, then they can be contributed/mixed in)
> A command should cope with the concept of being invoked on more than one
> object, ie having a list of targets. nb: this implies that our current
> terminology of "bulk actions" is actually wrong, we ought to be talking about
> "bulk commands".
> We can envisage (at least) two different user intentions when performing a
> bulk command:
> a) perform the operation on as many as possible, or
> b) perform the operation on all of them, or none at all.
> The former suggests that each action is wrapped in its own command: the user
> intends to operate on each object, one after the other. The latter suggests
> that all the actions live in a single command.
> Dan's view is that a command is one:one with a (DB) transaction.
> ~~~
> the original version of this ticket was to change the Command#setMemento to
> use the ActionInvocationMementoDto. However, that now seems to be incorrect:
> - an AimDto is a record of an action being invoked (past tense, if you will),
> not the intention to invoke an action
> - as such an AimDto holds a return value, but that is strictly irrelevant
> to a Command
> - an AimDto relates only to a single target, whereas a Command could have
> multiple targets ("perform this action on all of em, or none of em")
> So, instead, this ticket is to define a new XSD just as the reified form of
> Commands. It needs to be able to handle mxins, and bulk actions. It
> *shouldn't* have action results.
> ~~~
> Note that this will also require some data migration scripts for anyone that
> has used this feature.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ISIS-1370) New PublisherService to simplify and replace PublishingService.
[ https://issues.apache.org/jira/browse/ISIS-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282940#comment-15282940 ] ASF subversion and git services commented on ISIS-1370: --- Commit b01781b0507e5f49a770f8079b4d477a156201fa in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=b01781b ] ISIS-1370: now supports publishing of objects. > New PublisherService to simplify and replace PublishingService. > --- > > Key: ISIS-1370 > URL: https://issues.apache.org/jira/browse/ISIS-1370 > Project: Isis > Issue Type: New Feature > Components: Core >Affects Versions: 1.12.0 >Reporter: Dan Haywood >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.13.0 > > > Most PublishingService implementations (to date) only require the metadata > (action invocation or domain object identity) to publish their events; the > notion of the payload (to eagerly assemble information for the downstream > subscribers) seems less useful. > This ticket is therefore to deprecate the > PublishingService#publish(EventMetadata, EventPayload), and replace with > PublishingService2#publish(EventMetadata). > This also means that @DomainObject#publishingPayloadFactory() and > @Action#publishingPayloadFactory() attributes are deprecated. > ~~~ > In its place, will have a new PublisherService with a simplified API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-1400) bulk-only actions are shown on object forms
[ https://issues.apache.org/jira/browse/ISIS-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282943#comment-15282943 ] ASF subversion and git services commented on ISIS-1400: --- Commit b8d19e67d7f24c4a08683d1f77b9c80160d1dec8 in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=b8d19e6 ] ISIS-1400: filter out any bulk-only actions. > bulk-only actions are shown on object forms > --- > > Key: ISIS-1400 > URL: https://issues.apache.org/jira/browse/ISIS-1400 > Project: Isis > Issue Type: Bug > Components: Core >Affects Versions: 1.12.1 >Reporter: Dan Haywood >Assignee: Dan Haywood >Priority: Minor > Labels: implemented > Fix For: 1.13.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-1291) Define new DTO (XSD) as the memento for Command#setMemento
[
https://issues.apache.org/jira/browse/ISIS-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282949#comment-15282949
]
ASF subversion and git services commented on ISIS-1291:
---
Commit 55d3029a6265524ec3dbf65b2365d8569a42f61d in isis's branch
refs/heads/master from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=55d3029 ]
ISIS-1291: further documentation. Slight extension to the PublishedObjects API
> Define new DTO (XSD) as the memento for Command#setMemento
> --
>
> Key: ISIS-1291
> URL: https://issues.apache.org/jira/browse/ISIS-1291
> Project: Isis
> Issue Type: New Feature
> Components: Core
>Affects Versions: 1.11.0
>Reporter: Dan Haywood
>Assignee: Dan Haywood
>Priority: Minor
> Labels: implemented
> Fix For: 1.13.0
>
>
> A command is NOT an action invocation, it is an INTENTION to invoke an
> action. Generally that intention is carried out immediately, hence a
> foreground command. Sometimes though it is carried out in the background, so
> is a deferred intention.
> What this implies is that a command should not contain details of the
> action's results. (If that information is available from reified
> ActionDomainEvents, then they can be contributed/mixed in)
> A command should cope with the concept of being invoked on more than one
> object, ie having a list of targets. nb: this implies that our current
> terminology of "bulk actions" is actually wrong, we ought to be talking about
> "bulk commands".
> We can envisage (at least) two different user intentions when performing a
> bulk command:
> a) perform the operation on as many as possible, or
> b) perform the operation on all of them, or none at all.
> The former suggests that each action is wrapped in its own command: the user
> intends to operate on each object, one after the other. The latter suggests
> that all the actions live in a single command.
> Dan's view is that a command is one:one with a (DB) transaction.
> ~~~
> the original version of this ticket was to change the Command#setMemento to
> use the ActionInvocationMementoDto. However, that now seems to be incorrect:
> - an AimDto is a record of an action being invoked (past tense, if you will),
> not the intention to invoke an action
> - as such an AimDto holds a return value, but that is strictly irrelevant
> to a Command
> - an AimDto relates only to a single target, whereas a Command could have
> multiple targets ("perform this action on all of em, or none of em")
> So, instead, this ticket is to define a new XSD just as the reified form of
> Commands. It needs to be able to handle mxins, and bulk actions. It
> *shouldn't* have action results.
> ~~~
> Note that this will also require some data migration scripts for anyone that
> has used this feature.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ISIS-1370) New PublisherService to simplify and replace PublishingService.
[ https://issues.apache.org/jira/browse/ISIS-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282944#comment-15282944 ] ASF subversion and git services commented on ISIS-1370: --- Commit b87fc37756f8e14ed74ea42fbec555dc0eed2047 in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=b87fc37 ] ISIS-1370: provide wormhole to allow mixin properties/collections to disable publishing of actions. > New PublisherService to simplify and replace PublishingService. > --- > > Key: ISIS-1370 > URL: https://issues.apache.org/jira/browse/ISIS-1370 > Project: Isis > Issue Type: New Feature > Components: Core >Affects Versions: 1.12.0 >Reporter: Dan Haywood >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.13.0 > > > Most PublishingService implementations (to date) only require the metadata > (action invocation or domain object identity) to publish their events; the > notion of the payload (to eagerly assemble information for the downstream > subscribers) seems less useful. > This ticket is therefore to deprecate the > PublishingService#publish(EventMetadata, EventPayload), and replace with > PublishingService2#publish(EventMetadata). > This also means that @DomainObject#publishingPayloadFactory() and > @Action#publishingPayloadFactory() attributes are deprecated. > ~~~ > In its place, will have a new PublisherService with a simplified API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-1370) New PublisherService to simplify and replace PublishingService.
[ https://issues.apache.org/jira/browse/ISIS-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282947#comment-15282947 ] ASF subversion and git services commented on ISIS-1370: --- Commit 138dc57a082982672f75de629635672f54217c53 in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=138dc57 ] ISIS-1370: adding some additional standard column lengths to applib's JdoColumnLength > New PublisherService to simplify and replace PublishingService. > --- > > Key: ISIS-1370 > URL: https://issues.apache.org/jira/browse/ISIS-1370 > Project: Isis > Issue Type: New Feature > Components: Core >Affects Versions: 1.12.0 >Reporter: Dan Haywood >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.13.0 > > > Most PublishingService implementations (to date) only require the metadata > (action invocation or domain object identity) to publish their events; the > notion of the payload (to eagerly assemble information for the downstream > subscribers) seems less useful. > This ticket is therefore to deprecate the > PublishingService#publish(EventMetadata, EventPayload), and replace with > PublishingService2#publish(EventMetadata). > This also means that @DomainObject#publishingPayloadFactory() and > @Action#publishingPayloadFactory() attributes are deprecated. > ~~~ > In its place, will have a new PublisherService with a simplified API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-1291) Define new DTO (XSD) as the memento for Command#setMemento
[
https://issues.apache.org/jira/browse/ISIS-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282929#comment-15282929
]
ASF subversion and git services commented on ISIS-1291:
---
Commit 55d3029a6265524ec3dbf65b2365d8569a42f61d in isis's branch
refs/heads/ISIS-1291 from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=55d3029 ]
ISIS-1291: further documentation. Slight extension to the PublishedObjects API
> Define new DTO (XSD) as the memento for Command#setMemento
> --
>
> Key: ISIS-1291
> URL: https://issues.apache.org/jira/browse/ISIS-1291
> Project: Isis
> Issue Type: New Feature
> Components: Core
>Affects Versions: 1.11.0
>Reporter: Dan Haywood
>Assignee: Dan Haywood
>Priority: Minor
> Labels: implemented
> Fix For: 1.13.0
>
>
> A command is NOT an action invocation, it is an INTENTION to invoke an
> action. Generally that intention is carried out immediately, hence a
> foreground command. Sometimes though it is carried out in the background, so
> is a deferred intention.
> What this implies is that a command should not contain details of the
> action's results. (If that information is available from reified
> ActionDomainEvents, then they can be contributed/mixed in)
> A command should cope with the concept of being invoked on more than one
> object, ie having a list of targets. nb: this implies that our current
> terminology of "bulk actions" is actually wrong, we ought to be talking about
> "bulk commands".
> We can envisage (at least) two different user intentions when performing a
> bulk command:
> a) perform the operation on as many as possible, or
> b) perform the operation on all of them, or none at all.
> The former suggests that each action is wrapped in its own command: the user
> intends to operate on each object, one after the other. The latter suggests
> that all the actions live in a single command.
> Dan's view is that a command is one:one with a (DB) transaction.
> ~~~
> the original version of this ticket was to change the Command#setMemento to
> use the ActionInvocationMementoDto. However, that now seems to be incorrect:
> - an AimDto is a record of an action being invoked (past tense, if you will),
> not the intention to invoke an action
> - as such an AimDto holds a return value, but that is strictly irrelevant
> to a Command
> - an AimDto relates only to a single target, whereas a Command could have
> multiple targets ("perform this action on all of em, or none of em")
> So, instead, this ticket is to define a new XSD just as the reified form of
> Commands. It needs to be able to handle mxins, and bulk actions. It
> *shouldn't* have action results.
> ~~~
> Note that this will also require some data migration scripts for anyone that
> has used this feature.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ISIS-1291) Define new DTO (XSD) as the memento for Command#setMemento
[
https://issues.apache.org/jira/browse/ISIS-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282690#comment-15282690
]
ASF subversion and git services commented on ISIS-1291:
---
Commit 7ebbb70c115636f872d13bb1c367916febc961c3 in isis's branch
refs/heads/ISIS-1291 from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=7ebbb70 ]
ISIS-1291: documentation on command and events.
Also:
- adding missing schemas in adocs documentation (for hosting on the web).
- updating bad links to @Xxx_aaa in multiple files
- deprecating some methods in applib API.
> Define new DTO (XSD) as the memento for Command#setMemento
> --
>
> Key: ISIS-1291
> URL: https://issues.apache.org/jira/browse/ISIS-1291
> Project: Isis
> Issue Type: New Feature
> Components: Core
>Affects Versions: 1.11.0
>Reporter: Dan Haywood
>Assignee: Dan Haywood
>Priority: Minor
> Labels: implemented
> Fix For: 1.13.0
>
>
> A command is NOT an action invocation, it is an INTENTION to invoke an
> action. Generally that intention is carried out immediately, hence a
> foreground command. Sometimes though it is carried out in the background, so
> is a deferred intention.
> What this implies is that a command should not contain details of the
> action's results. (If that information is available from reified
> ActionDomainEvents, then they can be contributed/mixed in)
> A command should cope with the concept of being invoked on more than one
> object, ie having a list of targets. nb: this implies that our current
> terminology of "bulk actions" is actually wrong, we ought to be talking about
> "bulk commands".
> We can envisage (at least) two different user intentions when performing a
> bulk command:
> a) perform the operation on as many as possible, or
> b) perform the operation on all of them, or none at all.
> The former suggests that each action is wrapped in its own command: the user
> intends to operate on each object, one after the other. The latter suggests
> that all the actions live in a single command.
> Dan's view is that a command is one:one with a (DB) transaction.
> ~~~
> the original version of this ticket was to change the Command#setMemento to
> use the ActionInvocationMementoDto. However, that now seems to be incorrect:
> - an AimDto is a record of an action being invoked (past tense, if you will),
> not the intention to invoke an action
> - as such an AimDto holds a return value, but that is strictly irrelevant
> to a Command
> - an AimDto relates only to a single target, whereas a Command could have
> multiple targets ("perform this action on all of em, or none of em")
> So, instead, this ticket is to define a new XSD just as the reified form of
> Commands. It needs to be able to handle mxins, and bulk actions. It
> *shouldn't* have action results.
> ~~~
> Note that this will also require some data migration scripts for anyone that
> has used this feature.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ISIS-1358) Simpleapp created from archetype and packaged to war fails when deploying to Tomcat
[ https://issues.apache.org/jira/browse/ISIS-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282646#comment-15282646 ] Vladimir Nisevic commented on ISIS-1358: Martin, you're right. I was actually using maven thru IntelliJ. Running maven from command line gives me a war file without jetty-jars, but when I start the maven task from IntelliJ, then I get the war with jetty jars! > Simpleapp created from archetype and packaged to war fails when deploying to > Tomcat > --- > > Key: ISIS-1358 > URL: https://issues.apache.org/jira/browse/ISIS-1358 > Project: Isis > Issue Type: Bug > Components: Archetype: SimpleApp >Affects Versions: 1.12.1 > Environment: Windows 10, Windows 7 > Tomcat version: Apache Tomcat/8.0.33 > JVM: 1.8.0_77-b03 >Reporter: Vladimir Nisevic >Assignee: Dan Haywood > Attachments: catalina.2016-03-31.log, > restfulServicesWhenLaunchingWithTomcat.png, swagger.issue.png > > > Steps to reproduce: > * Created simpleapp from archetype (Version 1.12.0) > * Execute mvn clean package > * Take the file \webapp\target\simpleapp.war and deploy to tomcat thru e.g. > manager UI (http://localhost:8080/manager/html) > Attached the catalina.log -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-1370) New PublisherService to simplify and replace PublishingService.
[ https://issues.apache.org/jira/browse/ISIS-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282599#comment-15282599 ] ASF subversion and git services commented on ISIS-1370: --- Commit cd370c597a5c1724695a54bc87a0c78cd3044bfe in isis's branch refs/heads/ISIS-1291 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=cd370c5 ] ISIS-1370: adding a new JdoColumnLength constant for status messages (for publishmq impl to reference). > New PublisherService to simplify and replace PublishingService. > --- > > Key: ISIS-1370 > URL: https://issues.apache.org/jira/browse/ISIS-1370 > Project: Isis > Issue Type: New Feature > Components: Core >Affects Versions: 1.12.0 >Reporter: Dan Haywood >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.13.0 > > > Most PublishingService implementations (to date) only require the metadata > (action invocation or domain object identity) to publish their events; the > notion of the payload (to eagerly assemble information for the downstream > subscribers) seems less useful. > This ticket is therefore to deprecate the > PublishingService#publish(EventMetadata, EventPayload), and replace with > PublishingService2#publish(EventMetadata). > This also means that @DomainObject#publishingPayloadFactory() and > @Action#publishingPayloadFactory() attributes are deprecated. > ~~~ > In its place, will have a new PublisherService with a simplified API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-1370) New PublisherService to simplify and replace PublishingService.
[ https://issues.apache.org/jira/browse/ISIS-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282600#comment-15282600 ] ASF subversion and git services commented on ISIS-1370: --- Commit 72705aceee671e2c13b4d132b61b4a181aa50e85 in isis's branch refs/heads/ISIS-1291 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=72705ac ] ISIS-1370: improve syntax of comparator static methods in DomainChangeJdoAbstract > New PublisherService to simplify and replace PublishingService. > --- > > Key: ISIS-1370 > URL: https://issues.apache.org/jira/browse/ISIS-1370 > Project: Isis > Issue Type: New Feature > Components: Core >Affects Versions: 1.12.0 >Reporter: Dan Haywood >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.13.0 > > > Most PublishingService implementations (to date) only require the metadata > (action invocation or domain object identity) to publish their events; the > notion of the payload (to eagerly assemble information for the downstream > subscribers) seems less useful. > This ticket is therefore to deprecate the > PublishingService#publish(EventMetadata, EventPayload), and replace with > PublishingService2#publish(EventMetadata). > This also means that @DomainObject#publishingPayloadFactory() and > @Action#publishingPayloadFactory() attributes are deprecated. > ~~~ > In its place, will have a new PublisherService with a simplified API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-1370) New PublisherService to simplify and replace PublishingService.
[ https://issues.apache.org/jira/browse/ISIS-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282601#comment-15282601 ] ASF subversion and git services commented on ISIS-1370: --- Commit 138dc57a082982672f75de629635672f54217c53 in isis's branch refs/heads/ISIS-1291 from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=138dc57 ] ISIS-1370: adding some additional standard column lengths to applib's JdoColumnLength > New PublisherService to simplify and replace PublishingService. > --- > > Key: ISIS-1370 > URL: https://issues.apache.org/jira/browse/ISIS-1370 > Project: Isis > Issue Type: New Feature > Components: Core >Affects Versions: 1.12.0 >Reporter: Dan Haywood >Assignee: Dan Haywood >Priority: Minor > Fix For: 1.13.0 > > > Most PublishingService implementations (to date) only require the metadata > (action invocation or domain object identity) to publish their events; the > notion of the payload (to eagerly assemble information for the downstream > subscribers) seems less useful. > This ticket is therefore to deprecate the > PublishingService#publish(EventMetadata, EventPayload), and replace with > PublishingService2#publish(EventMetadata). > This also means that @DomainObject#publishingPayloadFactory() and > @Action#publishingPayloadFactory() attributes are deprecated. > ~~~ > In its place, will have a new PublisherService with a simplified API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-1358) Simpleapp created from archetype and packaged to war fails when deploying to Tomcat
[ https://issues.apache.org/jira/browse/ISIS-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282587#comment-15282587 ] Martin Grigorov commented on ISIS-1358: --- You must be doing something else there. I've re-run "mvn archetype:generate" you pasted above and it works just fine in Tomcat 8.x. Also there are no Jetty jars in webapp/target/simpleapp.war#WEB-INF/lib/, so there is no need to exclude anything. > Simpleapp created from archetype and packaged to war fails when deploying to > Tomcat > --- > > Key: ISIS-1358 > URL: https://issues.apache.org/jira/browse/ISIS-1358 > Project: Isis > Issue Type: Bug > Components: Archetype: SimpleApp >Affects Versions: 1.12.1 > Environment: Windows 10, Windows 7 > Tomcat version: Apache Tomcat/8.0.33 > JVM: 1.8.0_77-b03 >Reporter: Vladimir Nisevic >Assignee: Dan Haywood > Attachments: catalina.2016-03-31.log, > restfulServicesWhenLaunchingWithTomcat.png, swagger.issue.png > > > Steps to reproduce: > * Created simpleapp from archetype (Version 1.12.0) > * Execute mvn clean package > * Take the file \webapp\target\simpleapp.war and deploy to tomcat thru e.g. > manager UI (http://localhost:8080/manager/html) > Attached the catalina.log -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-1358) Simpleapp created from archetype and packaged to war fails when deploying to Tomcat
[
https://issues.apache.org/jira/browse/ISIS-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282522#comment-15282522
]
Vladimir Nisevic commented on ISIS-1358:
Hi Martin, I will create new ticket with Swagger issue. In this issue I still
believe that default generated war is not deployable on Tomcat.
Here the steps to reproduce:
1. Create archetype as described in guide
{code}
mvn archetype:generate \
-D archetypeGroupId=org.apache.isis.archetype \
-D archetypeArtifactId=simpleapp-archetype \
-D archetypeVersion=1.12.1 \
-D groupId=com.mycompany \
-D artifactId=myapp \
-D version=1.0-SNAPSHOT \
-B
{code}
2. execute "mvn clean install"
3. deploy simpleapp.war to external tomcat, eg. thru tomcat manager webapp
4. ERROR: starting of simpleapp.war will fail, in Tomcat (my Tomcat version
8.0.33) log will appear
{code}
13-May-2016 06:42:30.922 SEVERE [http-apr-8080-exec-31]
org.apache.catalina.core.ContainerBase.addChildInternal ContainerBase.addChild:
start:
org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/simpleapp]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:153)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:725)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:701)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:940)
at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:467)
at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1612)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:300)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(Unknown
Source)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(Unknown Source)
at
org.apache.catalina.manager.ManagerServlet.check(ManagerServlet.java:1451)
at
org.apache.catalina.manager.HTMLManagerServlet.upload(HTMLManagerServlet.java:285)
at
org.apache.catalina.manager.HTMLManagerServlet.doPost(HTMLManagerServlet.java:206)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:648)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:292)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)
at
org.apache.catalina.filters.CsrfPreventionFilter.doFilter(CsrfPreventionFilter.java:136)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)
at
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)
at
org.apache.catalina.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:108)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:212)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:614)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:141)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
at
org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:616)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:522)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1095)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:672)
at
org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.doRun(AprEndpoint.java:2500)
at
[jira] [Commented] (ISIS-1358) Simpleapp created from archetype and packaged to war fails when deploying to Tomcat
[ https://issues.apache.org/jira/browse/ISIS-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282465#comment-15282465 ] Martin Grigorov commented on ISIS-1358: --- The Swagger issue should be reported to in a new ticket, with description how to reproduce or at least a demo application. This ticket should be closed as "Cannot reproduce" if you can't reproduce it too. > Simpleapp created from archetype and packaged to war fails when deploying to > Tomcat > --- > > Key: ISIS-1358 > URL: https://issues.apache.org/jira/browse/ISIS-1358 > Project: Isis > Issue Type: Bug > Components: Archetype: SimpleApp >Affects Versions: 1.12.1 > Environment: Windows 10, Windows 7 > Tomcat version: Apache Tomcat/8.0.33 > JVM: 1.8.0_77-b03 >Reporter: Vladimir Nisevic >Assignee: Dan Haywood > Attachments: catalina.2016-03-31.log, > restfulServicesWhenLaunchingWithTomcat.png, swagger.issue.png > > > Steps to reproduce: > * Created simpleapp from archetype (Version 1.12.0) > * Execute mvn clean package > * Take the file \webapp\target\simpleapp.war and deploy to tomcat thru e.g. > manager UI (http://localhost:8080/manager/html) > Attached the catalina.log -- This message was sent by Atlassian JIRA (v6.3.4#6332)
