[JBoss JIRA] (WFLY-3697) Custom http handlers support
by Nicky Mølholm (JIRA)
[ https://issues.jboss.org/browse/WFLY-3697?page=com.atlassian.jira.plugin.... ]
Nicky Mølholm commented on WFLY-3697:
-------------------------------------
Okay thanks - that makes sense.
Btw: You could consider supporting "auto discovery" of annotated types too. So that pointing out the module would be enough - after which the extension will scan the module resources for certain, say, @GlobalHttpHandlers. I still like the XML declarative way too though - so this idea is by no means an alternative suggestion.
> Custom http handlers support
> ----------------------------
>
> Key: WFLY-3697
> URL: https://issues.jboss.org/browse/WFLY-3697
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Reporter: Tomaz Cerar
> Assignee: Tomaz Cerar
> Fix For: 9.0.0.Beta1
>
>
> We need support for custom handlers & filters
> something along the lines
> {code:xml}
> <handlers>
> <handler name="myhandler" class="full.class.name" module"full.module.name" />
> <handlers>
> <filters>
> <filter name="myfilter" class="full.class.name" module"full.module.name" />
> <filters>
> {code}
> There should also be a way to pass in arbitrary config options
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (WFLY-3697) Custom http handlers support
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3697?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-3697:
-----------------------------------
This is just for undertow HttpHandlers as this stuff kicks in way before servlet container is started.
If you want servlet filters / servlets then just deploy war with them.
by undertow rules, HttpHandler can be filter or handler depending on its implementation, if it is last in chain it is handler, otherwise if it delegates to next handler it is filter.
> Custom http handlers support
> ----------------------------
>
> Key: WFLY-3697
> URL: https://issues.jboss.org/browse/WFLY-3697
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Reporter: Tomaz Cerar
> Assignee: Tomaz Cerar
> Fix For: 9.0.0.Beta1
>
>
> We need support for custom handlers & filters
> something along the lines
> {code:xml}
> <handlers>
> <handler name="myhandler" class="full.class.name" module"full.module.name" />
> <handlers>
> <filters>
> <filter name="myfilter" class="full.class.name" module"full.module.name" />
> <filters>
> {code}
> There should also be a way to pass in arbitrary config options
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JGRP-1864) UDP unable to bind to ephemeral port: port out of range:65536
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/JGRP-1864?page=com.atlassian.jira.plugin.... ]
Dan Berindei commented on JGRP-1864:
------------------------------------
Ion, could you issue a PR with your change to log the initial error instead of the "port out of range" error? I'd really like to get that in, even if we can't fix the underlying issue.
Bela, I have a hunch there's a problem if the JVM starts with {{java.net.preferXXX}} unset, and {{Util.ip_stack_type}} is initialized with {{StackType.IPv6}}, and then the program sets {{java.net.preferIPv4Stack=true}} before creating the JGroups channel. But I tried running our {{integrationtests/osgi}} test suite with {{java.net.preferIPv6Addresses=true}} to reproduce it on my machine, and I didn't get any failures.
> UDP unable to bind to ephemeral port: port out of range:65536
> -------------------------------------------------------------
>
> Key: JGRP-1864
> URL: https://issues.jboss.org/browse/JGRP-1864
> Project: JGroups
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.4.4
> Reporter: Dan Berindei
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.4.5, 3.5
>
>
> It looks like {{UDP.createEphemeralDatagramSocket()}} swallows any errors it gets while creating the socket, and throws this exception after trying to bind to all ports in the 0 - 65535 range:
> {noformat}
> java.lang.IllegalArgumentException: port out of range:65536
> at java.net.InetSocketAddress.checkPort(InetSocketAddress.java:143)
> at java.net.InetSocketAddress.<init>(InetSocketAddress.java:185)
> at java.net.DatagramSocket.<init>(DatagramSocket.java:284)
> at org.jgroups.util.DefaultSocketFactory.createDatagramSocket(DefaultSocketFactory.java:62)
> at org.jgroups.protocols.UDP.createEphemeralDatagramSocket(UDP.java:429)
> at org.jgroups.protocols.UDP.createSockets(UDP.java:311)
> at org.jgroups.protocols.UDP.start(UDP.java:216)
> at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:966)
> at org.jgroups.JChannel.startStack(JChannel.java:889)
> at org.jgroups.JChannel._preConnect(JChannel.java:547)
> at org.jgroups.JChannel.connect(JChannel.java:282)
> at org.jgroups.JChannel.connect(JChannel.java:273)
> at org.infinispan.remoting.transport.jgroups.JGroupsTransport.startJGroupsChannelIfNeeded(JGroupsTransport.java:200)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (WFLY-3697) Custom http handlers support
by Nicky Mølholm (JIRA)
[ https://issues.jboss.org/browse/WFLY-3697?page=com.atlassian.jira.plugin.... ]
Nicky Mølholm commented on WFLY-3697:
-------------------------------------
So handlers would refer to "undertow httphandlers". Would filters (thats javax servlet filters in my book) then be necessary too?
> Custom http handlers support
> ----------------------------
>
> Key: WFLY-3697
> URL: https://issues.jboss.org/browse/WFLY-3697
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Reporter: Tomaz Cerar
> Assignee: Tomaz Cerar
> Fix For: 9.0.0.Beta1
>
>
> We need support for custom handlers & filters
> something along the lines
> {code:xml}
> <handlers>
> <handler name="myhandler" class="full.class.name" module"full.module.name" />
> <handlers>
> <filters>
> <filter name="myfilter" class="full.class.name" module"full.module.name" />
> <filters>
> {code}
> There should also be a way to pass in arbitrary config options
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (SECURITY-850) Update Hibernate to a recent version
by Sanne Grinovero (JIRA)
[ https://issues.jboss.org/browse/SECURITY-850?page=com.atlassian.jira.plug... ]
Sanne Grinovero updated SECURITY-850:
-------------------------------------
Description:
We're using PicketBox in Infinispan, but we also use Hibernate and WilFly.
The version of Hibernate used by PicketBox is extremely outdated (I think more than 5 years), it would be very helpful to any user of PicketBox if you could use a recent version to not conflict with other requirements.
was:
We're using PicketBox in Infinispan, but we also use Hibernate and WilFly.
The version used by PicketBox is extremely outdated (I think more than 5 years), it would be very helpful to any user of PicketBox if you could use a recent version to not conflict with other requirements.
> Update Hibernate to a recent version
> ------------------------------------
>
> Key: SECURITY-850
> URL: https://issues.jboss.org/browse/SECURITY-850
> Project: PicketBox
> Issue Type: Component Upgrade
> Security Level: Public(Everyone can see)
> Reporter: Sanne Grinovero
> Assignee: Stefan Guilhen
>
> We're using PicketBox in Infinispan, but we also use Hibernate and WilFly.
> The version of Hibernate used by PicketBox is extremely outdated (I think more than 5 years), it would be very helpful to any user of PicketBox if you could use a recent version to not conflict with other requirements.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (SECURITY-850) Update Hibernate to a recent version
by Sanne Grinovero (JIRA)
Sanne Grinovero created SECURITY-850:
----------------------------------------
Summary: Update Hibernate to a recent version
Key: SECURITY-850
URL: https://issues.jboss.org/browse/SECURITY-850
Project: PicketBox
Issue Type: Component Upgrade
Security Level: Public (Everyone can see)
Reporter: Sanne Grinovero
Assignee: Stefan Guilhen
We're using PicketBox in Infinispan, but we also use Hibernate and WilFly.
The version used by PicketBox is extremely outdated (I think more than 5 years), it would be very helpful to any user of PicketBox if you could use a recent version to not conflict with other requirements.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (WFLY-3697) Custom http handlers support
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3697?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-3697:
------------------------------
Description:
We need support for custom handlers & filters
something along the lines
{code:xml}
<handlers>
<handler name="myhandler" class="full.class.name" module"full.module.name" />
<handlers>
<filters>
<filter name="myfilter" class="full.class.name" module"full.module.name" />
<filters>
{code}
There should also be a way to pass in arbitrary config options
was:
We need support for custom handlers & filters
something along the lines
{code:xml}
<handler name="myhandler" class="full.class.name" module"full.module.name" />
{code:xml}
There should also be a way to pass in arbitrary config options
> Custom http handlers support
> ----------------------------
>
> Key: WFLY-3697
> URL: https://issues.jboss.org/browse/WFLY-3697
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Reporter: Tomaz Cerar
> Assignee: Tomaz Cerar
> Fix For: 9.0.0.Beta1
>
>
> We need support for custom handlers & filters
> something along the lines
> {code:xml}
> <handlers>
> <handler name="myhandler" class="full.class.name" module"full.module.name" />
> <handlers>
> <filters>
> <filter name="myfilter" class="full.class.name" module"full.module.name" />
> <filters>
> {code}
> There should also be a way to pass in arbitrary config options
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (WFLY-3697) Custom http handlers support
by Tomaz Cerar (JIRA)
Tomaz Cerar created WFLY-3697:
---------------------------------
Summary: Custom http handlers support
Key: WFLY-3697
URL: https://issues.jboss.org/browse/WFLY-3697
Project: WildFly
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Web (Undertow)
Reporter: Tomaz Cerar
Assignee: Tomaz Cerar
Fix For: 9.0.0.Beta1
We need support for custom handlers & filters
something along the lines
{code:xml}
<handler name="myhandler" class="full.class.name" module"full.module.name" />
{code:xml}
There should also be a way to pass in arbitrary config options
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JGRP-1864) UDP unable to bind to ephemeral port: port out of range:65536
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1864?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1864:
--------------------------------
Sorry, no matter what type of IPv6 address I used (link-local or global), this always works.
Get me a standalone JGroups case with
- config
- exact description of how to run it
- command line options
, so I can reproduce it.
Closing this for now.
> UDP unable to bind to ephemeral port: port out of range:65536
> -------------------------------------------------------------
>
> Key: JGRP-1864
> URL: https://issues.jboss.org/browse/JGRP-1864
> Project: JGroups
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.4.4
> Reporter: Dan Berindei
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.4.5, 3.5
>
>
> It looks like {{UDP.createEphemeralDatagramSocket()}} swallows any errors it gets while creating the socket, and throws this exception after trying to bind to all ports in the 0 - 65535 range:
> {noformat}
> java.lang.IllegalArgumentException: port out of range:65536
> at java.net.InetSocketAddress.checkPort(InetSocketAddress.java:143)
> at java.net.InetSocketAddress.<init>(InetSocketAddress.java:185)
> at java.net.DatagramSocket.<init>(DatagramSocket.java:284)
> at org.jgroups.util.DefaultSocketFactory.createDatagramSocket(DefaultSocketFactory.java:62)
> at org.jgroups.protocols.UDP.createEphemeralDatagramSocket(UDP.java:429)
> at org.jgroups.protocols.UDP.createSockets(UDP.java:311)
> at org.jgroups.protocols.UDP.start(UDP.java:216)
> at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:966)
> at org.jgroups.JChannel.startStack(JChannel.java:889)
> at org.jgroups.JChannel._preConnect(JChannel.java:547)
> at org.jgroups.JChannel.connect(JChannel.java:282)
> at org.jgroups.JChannel.connect(JChannel.java:273)
> at org.infinispan.remoting.transport.jgroups.JGroupsTransport.startJGroupsChannelIfNeeded(JGroupsTransport.java:200)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months